lsyncd dies after initial rsync (rsync warning: some files vanished)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start lsyncd on a large tree (about 200GB), that has temporary files in them
2. The initial rsync will exit with a warning (rsync warning: some files 
vanished before they could be transferred)
3. lsyncd will terminate because the returned error code is not 0

What is the expected behavior? What does Lsyncd do instead?

Lsyncd should ignore this warning, since trees will be identical after sync.

What version of Lsyncd are you using? On what operating system (host and
target(s)?

# lsyncd  -version
Version: 2.0.4

# uname -a
Linux xxxx.nl 2.6.21.7-2.fc8xen #1 SMP Fri Feb 15 12:39:36 EST 2008 i686 i686 
i386 GNU/Linux

# cat /etc/redhat-release 
Fedora release 8 (Werewolf)

# rsync --version
rsync  version 3.0.7  protocol version 30

If applicable please copy/paste your Lsyncd configuration file.

/usr/local/bin/lsyncd -nodaemon -log all -rsync /export xxxxx.nl::standby-export

If applicable please copy/paste a logfile generated with '-log all' of a
minimal testcase that raises this problem.

rsync warning: some files vanished before they could be transferred (code 24) 
at main.c(1042) [sender=3.0.7]
22:54:28 Call: collectProcess()
22:54:28 Delay: collected an event
22:54:28 Error: Failure on startup of '/export/'.

Please provide any additional information below.

Original issue reported on code.google.com by bjorn.hijmans@gmail.com on 25 Aug 2011 at 6:24

[GoogleCodeExporter]

Oh, I'll look on this. You can expect this to get fixed in the soon coming 
version 2.0.5.

In the meanwhile you should be able workaround this by replacing line 3506 in 
lsyncd.lua
            if exitcode == 0 then
by
            if exitcode == 0 or (rsync_exitcodes and 
                   rsync_exitcodes[exitcode] == nil) then

Original comment by axk...@gmail.com on 25 Aug 2011 at 7:49

[GoogleCodeExporter]

Thx. Workaround solved it. I will upgrade to 2.0.5 once it is released.

Original comment by bjorn.hijmans@gmail.com on 25 Aug 2011 at 10:22

[GoogleCodeExporter]

Released lsyncd 2.0.5 whch code error code 24 explicitly set as an OK situation.

Original comment by axk...@gmail.com on 25 Aug 2011 at 11:48

• Changed state: Fixed