Bas van Schaik
2007-Feb-23 15:14 UTC
Receive more information about transfer problems in server log?
Hi all, I'm probably using the most basic rsync-setup: just running the rsync-daemon and use plain transfers (no encryption or other shells, plain rsync). Transfer logging is enabled. I've got a lot of client machines rsyncing their backups, both Linux and Windows. For some rsyncs, the log tells me this:> 2007/02/23 02:42:04 [29077] connect from ***.nl (*.*.*.*) > 2007/02/23 02:42:05 [29077] rsync to 192168162 from 192168162@***.nl (*.*.*.*) > 2007/02/23 02:42:05 [29077] receiving file list > 2007/02/23 02:42:06 [29077] IO error encountered -- skipping file deletion > 2007/02/23 02:42:06 [29077] rsync / > 2007/02/23 02:42:06 [29077] rsync error: some files could not be transferred (code 23) at main.c(872) [generator=2.6.9](all entries about PID 29077) I can see that something went wrong during this sync. But what exactly? Which files could not be transferred exactly, and why? According to the error code (23), some files where partially transferred due to an error, but there are no files in the transfer log! And which error did occur exactly? Of course, I can browse the client logfiles every day, but that isn't really an option: there are more than 50 clients! Can anyone help me getting more information in my server log about transfer problems? Thanks! Regards, -- Bas van Schaik
Bas van Schaik
2007-Mar-08 16:11 UTC
Receive more information about transfer problems in server log?
Hi Dave, Dave Markham wrote:> What are you the Rsync options you are using ?Clientside: rsync -vratz --password-file=somefile --force --delete-excluded --delete --exclude-from=somefile --files-from=somefile Serverside: rsync --no-detach --daemon --config /etc/rsyncd.conf with rsyncd.conf:> motd file = /etc/rsyncd.motd > log file = /var/log/rsync/rsyncd.log > pid file = /var/run/rsyncd.pid > secrets file = /etc/rsyncd.secrets > read only = no > uid = rsync > use chroot = yes > transfer logging = yes > timeout = 14400 > max connections = 25 > incoming chmod = u+rwThanks for your help! Regards, -- Bas> > On 2/23/07, *Bas van Schaik* <bas@tuxes.nl <mailto:bas@tuxes.nl>> wrote: > > Hi all, > > I'm probably using the most basic rsync-setup: just running the > rsync-daemon and use plain transfers (no encryption or other shells, > plain rsync). Transfer logging is enabled. > I've got a lot of client machines rsyncing their backups, both Linux > and > Windows. For some rsyncs, the log tells me this: > > > 2007/02/23 02:42:04 [29077] connect from ***.nl (*.*.*.*) > > 2007/02/23 02:42:05 [29077] rsync to 192168162 from > 192168162@***.nl (*.*.*.*) > > 2007/02/23 02:42:05 [29077] receiving file list > > 2007/02/23 02:42:06 [29077] IO error encountered -- skipping file > deletion > > 2007/02/23 02:42:06 [29077] rsync / > > 2007/02/23 02:42:06 [29077] rsync error: some files could not be > transferred (code 23) at main.c(872) [generator=2.6.9] > (all entries about PID 29077) > > I can see that something went wrong during this sync. But what exactly? > Which files could not be transferred exactly, and why? According to the > error code (23), some files where partially transferred due to an > error, > but there are no files in the transfer log! And which error did occur > exactly? Of course, I can browse the client logfiles every day, but that > isn't really an option: there are more than 50 clients! > > Can anyone help me getting more information in my server log about > transfer problems? Thanks! > > Regards, > > -- Bas van Schaik > -- > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html > >
Seemingly Similar Threads
- rsync reports "some files could not be transferred" (code 23) when problems occur with password-file
- rsyncd + scripting
- opendir(somedir/somefile): Not enough space -- why?
- ZFS send | verify | receive
- DO NOT REPLY [Bug 3925] New: rsync is unable to sync large (approx 4G) sparse files