file `./00000000000000000849.xlog` wasn't correctly closed - tarantool

When i try start my tarantool, see in log this messages:
2016-03-28 17:42:14.813 [31296] main/101/ia.lua C> log level 4
2016-03-28 17:42:14.999 [31296] main/101/ia.lua recovery.cc:211 W> file `./00000000000000000012.xlog` wasn't correctly closed
2016-03-28 17:42:15.001 [31296] main/101/ia.lua recovery.cc:211 W> file `./00000000000000000118.xlog` wasn't correctly closed
2016-03-28 17:42:15.002 [31296] main/101/ia.lua recovery.cc:211 W> file `./00000000000000000849.xlog` wasn't correctly closed
2016-03-28 17:42:15.004 [31296] main/101/ia.lua recovery.cc:211 W> file `./00000000000000000849.xlog` wasn't correctly closed
What does it mean ?

This message means that Tarantool did not write the end of file marker at shutdown, which it normally does. This can happen after a crash or hard reset, in other words, any kind of ungraceful server shutdown. The message as such is harmless, it warns you that some last transactions may have been not flushed to WAL since last start.

Related

xCode 7 Cocoapod Archive error

I have used cocoa pod and try to archive. After that, I got this error.
I looked solution from here but it doesn't work too. How shall I do?
how to fix the issue "Command /bin/sh failed with exit code 1" in iphone
sent 29 bytes received 20 bytes 98.00 bytes/sec
total size is 0 speedup is 0.00
building file list ... done
rsync: push_dir#3 "/Users/khantthulinn/Library/Developer/Xcode/DerivedData/SMRTConnect-emozrftvltrpagajdyydwrdgnacg/Build/Intermediates/ArchiveIntermediates/SMRTConnect/InstallationBuildProductsLocation" failed: No such file or directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/main.c(580) [receiver=2.6.9]
rsync: connection unexpectedly closed (8 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/io.c(453) [sender=2.6.9]
Command /bin/sh failed with exit code 12

Expect Script: Interrupted and Successful Connections both returns EOF

I'm trying to push a set of commands to Cisco devices. The last command, obviously is "exit".
How can I determine the difference between the two since both of them can be tracked through eof.
All commands have been pushed successfully.
The connection was interrupted while executing the commands due to network connectivity loss.
I'm currently using expect_after/expect_before to catch eof.
Here's the dummy command set:
!test
!test
!test
!test
!test
!test
!LAST!!!!
exit
My expect_before statement:
expect_before {
eof {
RGenerateLog "${logdir}sendconfig-error.log" "${logprefix} Connection was interrupted."
exit 11
}
}
SCENARIO 1 (Successful):
sw05-00-00-2960.1194.POE#!test
sw05-00-00-2960.1194.POE#!test
sw05-00-00-2960.1194.POE#!test
sw05-00-00-2960.1194.POE#!test
sw05-00-00-2960.1194.POE#!test
sw05-00-00-2960.1194.POE#!test
sw05-00-00-2960.1194.POE#!LAST!!!!
sw05-00-00-2960.1194.POE#exit
Connection closed by foreign host.
Log:
2015-05-27 12:32:13 [cisco.exp]: User=XXXXXXXX; Device=10.218.8.199; Action=config_change - Connection was interrupted.
SCENARIO 2 (Interrupted - I've closed the connection explicitly in the firewall):
sw05-00-00-2960.1194.POE#
sw05-00-00-2960.1194.POE#Connection closed by foreign host.
[root#tritone /tritone/system/send-config]#
2015-05-27 12:35:40 [cisco.exp]: User=XXXXXXXX; Device=10.218.8.199; Action=config_change - Connection was interrupted
So my problem is, how will I know if all the commands were successfully pushed?

Julia doesn't like it when I add and remove processes without doing any parallel processing

UPDATE: Confirmed as a bug. For more detail, see the link and details provided by #ViralBShah below.
Julia throws a strange error when I add and remove processes (addprocs and rmprocs), but only if I don't do any parallel processing in between. Consider the following example code:
#Set parameters
numCore = 4;
#Add workers
print("Adding workers... ");
addprocs(numCore - 1);
println(string(string(numCore-1), " workers added."));
#Detect number of cores
println(string("Number of processes detected = ", string(nprocs())));
# Do some stuff (COMMENTED OUT)
# XLst = {rand(10, 1) for i in 1:8};
# XMean = pmap(mean, XLst);
#Remove the additional workers
print("Removing workers... ");
rmprocs(workers());
println("Done.");
println("Subroutine complete.");
Note that I've commented out the only code that actually does any parallel processing (the call to pmap). If I run this code on my machine (Julia 0.2.1, Ubuntu 14.04), I get the following output in the console:
Adding workers... 3 workers added.
Number of processes detected = 4
Removing workers... Done.
Subroutine complete.
fatal error on
In [86]: fatal error on 88: ERROR: 87: ERROR: connect: connection refused (ECONNREFUSED)
in yield at multi.jl:1540
connect: connection refused (ECONNREFUSED) in wait at task.jl:117
in wait_connected at stream.jl:263
in connect at stream.jl:878
in Worker at multi.jl:108
in anonymous at task.jl:876
in yield at multi.jl:1540
in wait at task.jl:117
in wait_connected at stream.jl:263
in connect at stream.jl:878
in Worker at multi.jl:108
in anonymous at task.jl:876
The first four lines are printed by my program, and seem to indicate that it runs to completion. But then I get a fatal error. Any ideas?
The most interesting thing about this error is if I uncomment the code with the call to pmap (ie if I actually do some parallel processing), the fatal error goes away.
This issue is being tracked at https://github.com/JuliaLang/julia/issues/7646 and I reproduce the answer by Amit Murthy:
pid 1 does an addprocs(3)
addprocs returns after it has established connections with all 3 new workers.
However, at this time the the connections between workers may not have been setup, i.e. from pids 3 -> 2, 4 -> 2 and 4 -> 3.
Now pid 1 calls rmprocs(workers()) , i.e., pids 2, 3 and 4.
As pid 2 exits, the connection attempt in 4 to 2, results in an error.
Since we have redirected the output of pid 4, to the stdout of pid 1, we see the same error printed.
The system is still in a consistent state, though the printing of said error messages may suggest something amiss.

Extract part of a log file based on time stamp [duplicate]

This question already has answers here:
Filter log file entries based on date range
(5 answers)
Closed 4 years ago.
I have an application that appends to the same log file. As this file is rather large (around 8 gb), I'd like to extract portions based on the timestamp at the beginning of the line.
-bash-3.2$ cat application.log | egrep --color "Starting Application|Exception"
08:46:01.328 [main] INFO Starting Application...
09:14:53.670 [Thread-1] ERROR Resolver - Caught exception -> com.jgoodie.AuthzException: Authorization failed
Caused by: com.jgoodie.AuthzException: Authorization failed
09:56:15.739 [main] INFO Starting Application...
10:17:08.932 [Thread-1] ERROR Resolver - Caught exception -> com.jgoodie.AuthzException: Authorization failed
Caused by: com.jgoodie.AuthzException: Authorization failed
In the above example, I'd like to extract the logs for the first run of the application (between 08:46:01.328 and 09:56:15.739). Is there any simple way (preferably a one liner) to do this?
Thanks
sed -n '/08:46:01.328/,/09:56:15.739/p' application.log
perl -lne 'if(/^08:46:01.328/.../^09:56:15.739/){print}' your_file

rsync error: error in rsync protocol data stream (code 12)

I'm trying to do an rsync to transfer 500GB of files from one server to another. I use this command;
rsync -vrPt -e 'ssh -p 2222' uname#server.com:/folder /newfolder
It works and syncs just fine for about 10/15 minutes, then it throws this error every time;
rsync: connection unexpectedly closed (5321016884 bytes received so
far) [receiver] rsync: writefd_unbuffered failed to write 4 bytes to
socket [generator]: Broken pipe (32) rsync error: error in rsync
protocol data stream (code 12) at io.c(1525) [generator=3.0.6] rsync
error: error in rsync protocol data stream (code 12) at io.c(600) [receiver=3.0.6]
What could the problem be?
It looks like it is a router timing out the NAT table entry. (I assume one of the servers is on a DSL link.)
Or it could be this: "An idle connection caused a router or remote-shell server to close the connection." from http://rsync.samba.org/issues.html

Resources