Re: [BackupPC-users] Repeated error on more than one client; rsync timeout
Hi, that's the strange thing: initial backups worked, only the following backups showed the timeout. Kind regards, Hans Am 23.10.2013 00:29, schrieb Holger Parplies: Hi, Hans Kraus wrote on 2013-10-22 19:25:30 +0200 [Re: [BackupPC-users] Repeated error on more than one client; rsync timeout]: It was very simple: I copied the 'rsyncd.conf' file on the Clients [...] That example file contains the line: timeout = 600 After changing that value to 3600 it seems to work. that seems to imply that backups have never worked for those clients rather than to have suddenly begun failing. That was not clear from your original message. Good that you solved your problem, though, and thank you for sharing your findings with us. That is certainly something to keep in mind. Regards, Holger --- Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz ist aktiv. http://www.avast.com -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Repeated error on more than one client; rsync timeout
On Wed, Oct 23, 2013 at 10:35 AM, Hans Kraus h...@hanswkraus.com wrote: that's the strange thing: initial backups worked, only the following backups showed the timeout. Maybe the timeout really means 'idle time'. Backups after the first will spend a lot of time comparing matching data and not sending anything. -- Les Mikesell lesmikes...@gmail.com -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Repeated error on more than one client; rsync timeout
Hans Kraus h...@hanswkraus.com wrote on 10/23/2013 11:35:47 AM: Hi, that's the strange thing: initial backups worked, only the following backups showed the timeout. I'd get that. With the initial backup, there are no checksums performed: what would you checksum on the backup server? So rsync is simply copying data non-stop, and never hits the timeout. But the second time you do have files to checksum, and that's probably where you hit the timeout: while one side or the other was calculating the checksum. First time I've ever heard of an *rsync* timeout value... Glad to know of it! :) I'm actually wondering now if it might be the source of some weirdness I've seen on one particular rsync setup I'm using... Tim Massey Out of the Box Solutions, Inc. Creative IT Solutions Made Simple! http://www.OutOfTheBoxSolutions.com tmas...@obscorp.com 22108 Harper Ave. St. Clair Shores, MI 48080 Office: (800)750-4OBS (4627) Cell: (586)945-8796 -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Repeated error on more than one client; rsync timeout
Hi, Am 22.10.2013 01:25, schrieb Holger Parplies: Hi, [...] Of course, it *would* be interesting to actually trace this bug down (which would probably include examining attrib files). Which version of BackupPC are you running? Regards, Holger It was very simple: I copied the 'rsyncd.conf' file on the Clients ( all Debian at the moment) from an example file, as I read in http://howden.net.au/thowden/2012/11/rsync-on-debian/. Namely I did 'cp /usr/share/doc/rsync/examples/rsyncd.conf'. That example file contains the line: timeout = 600 After changing that value to 3600 it seems to work. Kind regards, Hans --- Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz ist aktiv. http://www.avast.com -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Repeated error on more than one client; rsync timeout
Hans Kraus h...@hanswkraus.com wrote on 10/22/2013 01:25:30 PM: It was very simple: I copied the 'rsyncd.conf' file on the Clients ( all Debian at the moment) from an example file, as I read in http://howden.net.au/thowden/2012/11/rsync-on-debian/. Namely I did 'cp /usr/share/doc/rsync/examples/rsyncd.conf'. That example file contains the line: timeout = 600 After changing that value to 3600 it seems to work. 600 is way too small; that's only 10 minutes, and there will be files that take more than 10 minutes to process. Frankly, I don't believe you should have ClientTimeout set in your client files; having that set as a global default in config.pl should be fine, and there the default is 72000 (as 20 hours, or 20 times longer than what you have set now!). I see and understand the value of the ClientTimeout parameter, but I've found that in practice it is almost *never* triggered correctly. The majority of times it is triggered is when a job is legitimately taking a long time. That's why an extreme setting is not so bad. I've found that there is one place where I *do* set it in the client config file: archive. Doing archives does not seem to reset the alarm setting during the process (and I've asked for help with this and gotten none). So, I've taken to seeting my archive ClientTimeout to 72 (as in 200 hours) so that they complete without error. Tim Massey Out of the Box Solutions, Inc. Creative IT Solutions Made Simple! http://www.OutOfTheBoxSolutions.com tmas...@obscorp.com 22108 Harper Ave. St. Clair Shores, MI 48080 Office: (800)750-4OBS (4627) Cell: (586)945-8796 -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Repeated error on more than one client; rsync timeout
On Tue, Oct 22, 2013 at 12:28 PM, Timothy J Massey tmas...@obscorp.com wrote: Hans Kraus h...@hanswkraus.com wrote on 10/22/2013 01:25:30 PM: It was very simple: I copied the 'rsyncd.conf' file on the Clients ( all Debian at the moment) from an example file, as I read in http://howden.net.au/thowden/2012/11/rsync-on-debian/. Namely I did 'cp /usr/share/doc/rsync/examples/rsyncd.conf'. That example file contains the line: timeout = 600 After changing that value to 3600 it seems to work. 600 is way too small; that's only 10 minutes, and there will be files that take more than 10 minutes to process. Frankly, I don't believe you should have ClientTimeout set in your client files; having that set as a global default in config.pl should be fine, and there the default is 72000 (as 20 hours, or 20 times longer than what you have set now!). That was a setting in the target host's rsyncd.conf, not on the backuppc side. 'man rsyncd.conf' does indeed suggest a 10 minute timeout but that's for 'anonymous rsync daemons', not full system backups. -- Les Mikesell lesmikes...@gmail.com -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Repeated error on more than one client; rsync timeout
Hi, Hans Kraus wrote on 2013-10-22 19:25:30 +0200 [Re: [BackupPC-users] Repeated error on more than one client; rsync timeout]: It was very simple: I copied the 'rsyncd.conf' file on the Clients [...] That example file contains the line: timeout = 600 After changing that value to 3600 it seems to work. that seems to imply that backups have never worked for those clients rather than to have suddenly begun failing. That was not clear from your original message. Good that you solved your problem, though, and thank you for sharing your findings with us. That is certainly something to keep in mind. Regards, Holger -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Repeated error on more than one client; rsync timeout
On Mon, Oct 21, 2013 at 3:42 PM, Hans Kraus h...@hanswkraus.com wrote: Hi, I get on more than one client the error in /var/log/syslog: rsync error: timeout in data send/receive (code 30) at io.c(137) [sender=3.0.9] which then leads to the backuppc error: backup failed (Child exited prematurely). This happens for incremental and full backups. I'm using rsyncd as transfer method. Is there any coure for that? Google brought up some cases with the same or similar error(s), but no remedy. I think that the ClientTimeOut setting is supposed to be for idle time on the network connection, but under some circumstances it isn't reset on activity and becomes the total timeout for the run.Try bumping it much higher, especially if your current setting is approximately the time when a timeout occurs. Also rsync can have long periods of idle time reading blocks where there are no differences from the comparison base. If the connection goes through a NAT gateway or a stateful firewall, the devices may time the connection out and be blocked. If you are running over ssh, you can enable keepalives on the ssh connection with the ServerAliveInterval option.Standalone rsync may also have a way to enable keepalives but I don't know where to set it. -- Les Mikesell lesmikes...@gmail.com -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Repeated error on more than one client; rsync timeout
Hi, Les Mikesell wrote on 2013-10-21 16:12:34 -0500 [Re: [BackupPC-users] Repeated error on more than one client; rsync timeout]: On Mon, Oct 21, 2013 at 3:42 PM, Hans Kraus h...@hanswkraus.com wrote: Hi, I get on more than one client the error in /var/log/syslog: on the client and in /var/log/syslog would both seem to mean that it's rsyncd reporting the error. rsync error: timeout in data send/receive (code 30) at io.c(137) [sender=3.0.9] which then leads to the backuppc error: backup failed (Child exited prematurely). This message would seem to mean that the child exited prematurely, not that BackupPC got an alarm signal. This happens for incremental and full backups. Which is a pity. You can't try simply forcing a full backup, which would otherwise be an option. I'm using rsyncd as transfer method. Is there any coure for that? Google brought up some cases with the same or similar error(s), but no remedy. I think that the ClientTimeOut setting is supposed to be for idle time on the network connection, but under some circumstances it isn't reset on activity and becomes the total timeout for the run.Try bumping it much higher, especially if your current setting is approximately the time when a timeout occurs. Nope, that's obviously not the cause. Also rsync can have long periods of idle time reading blocks where there are no differences from the comparison base. If the connection goes through a NAT gateway or a stateful firewall, the devices may time the connection out and be blocked. Well, you could look into this, but I wouldn't put too much hope into it. If I'm not totally mistaken, it's the *sender* that does most of the work, so the sender timing out sounds more like a protocol exchange problem, most probably caused by a corrupt attrib file. You could look at the XferLOG and try to find out whether the timeout always occurs at the same point. You could try checking attrib files for consistency (Jeffrey, have you got a script for that?). You could try deleting the reference backup (or perhaps moving it out of the way, though you might have to additionally patch the backups file) so BackupPC will use an older reference backup. That might be messy. Alternatively, you could try switching your XferMethod to 'tar', running one full backup, then switching back to 'rsyncd', and run another full backup. Just some suggestions that spring to a rather tired mind. You say you have several clients with the problem, so you could maybe test some things with a smaller or less important client. Of course, it *would* be interesting to actually trace this bug down (which would probably include examining attrib files). Which version of BackupPC are you running? Regards, Holger -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
