On 3/24/2011 2:36 PM, richardtoo...@paradise.net.nz wrote: > Quoting "Steven R. Gerber" <open...@gerber-systems.com>: > >> -------- Original Message -------- >> Subject: Re: rdist times out but will not die >> Date: Thu, 24 Mar 2011 21:49:01 +1300 >> From: Richard Toohey <richardtoo...@paradise.net.nz> >> To: Steven R. Gerber <sger...@gerber-systems.com> >> CC: t...@openbsd.org >> >> On 24/03/2011, at 4:06 PM, Steven R. Gerber wrote: >> >>> On 3/20/2011 2:07 PM, Steven R. Gerber wrote: >>>> I want to do local/remote mirror/backup (or should that be >> local-mirror >>>> / offsite-backup). >>>> So a two-part question: >>>> 1. Even if there is a timeout, shouldn't the job/process exit? >>>> >> ************************************************************* >> **************** >> * >>>> rdist@thedump: thedump: /mnt/mirror2/public/read_only/movies: chown >> from >>>> rdist:operator to cdripper:operator >>>> rdist@thedump: thedump: >>>> /mnt/mirror2/public/read_only/movies/The_Thomas_Crown_Affair_1999: >> chown >>>> from rdist:operator to root:operator >>>> rdist@thedump: >>>> >> /mnt/stripe2/public/read_only/movies/The_Thomas_Crow >> n_Affair_1999/THOMAS_CROW >> N_AFFAIR_16X9.md5: >>>> updating >>>> rdist@thedump: >>>> >> /mnt/stripe2/public/read_only/movies/The_Thomas_Crow >> n_Affair_1999/THOMAS_CROW >> N_AFFAIR_16X9.iso: >>>> installing >>>> rdist@thedump: LOCAL ERROR: Response time out >>>> rdist@thedump: updating of rdist@thedump finished >>>> $ ps -ax|grep rdist >>>> 26025 ?? I 0:00.00 tee /var/log/rdist/2011-03-20 >>>> 11059 ?? I 0:00.01 rdist -f /etc/Distfile >>>> 28446 ?? I 0:22.99 rdist: update rdist@thedump (rdist) >>>> 7795 ?? I 1:10.32 ssh -l rdist thedump r >>>> 13045 p0 S+ 0:00.00 grep rdist >>>> >> ************************************************************* >> **************** >> * >>>> 2. I know that they happen from time to time. How can I >> avoid/prevent >>>> timeouts? The default is 900 sec AKA 15 min? How can this happen >>>> between two local machines? >> >> How big is the file? > > So, how big is the file that it times out on? > > More than 2Gb? Guess so if a movie file? > > I might be barking up the wrong tree, but it will take you two seconds to see > if > there's anything in this > 2Gb idea and if I'm wrong, move on. > > Regardless of that, yes, put more debugging on - might give you some more > clues. > > OpenBSD helps those who help themselves. Richard, Thanks for the help. I had already read the IBM note 'LOCAL ERROR: response time out' (from 2006). (Google is not my enemy?) I had already checked: the file is >2GB (4.4GB). I ASSUMED that I can't the only who has tried to push large files with rdist. I searched the OpenBSD list archives (mine go back to 2006) and found nothing significant/useful. Maybe I missed something? I immediately moved to the misc list per your suggestion. I did a (manual) run of rdist with "-D" and got similar results -- I am still analyzing those messages. I usually do not compile OpenBSD, so it will take a while to review the rdist source code (client.c?).
Thanks again. >> >> Sure it is not *something* like this? >> >> https://www-304.ibm.com/support/docview.wss?uid=isg1IY85396 >> >> client.c >> >> 869 /* >> 870 * Parse size >> 871 */ >> 872 size = (off_t) strtol(cp, (char **)&cp, 10); >> >> *Maybe* that strtol() should be strtoll()? >> >> Anyway, don't I think tech@ is necessarily the list for this - misc@ or >> file a >> bug. >> >> And/or keep debugging & digging - the source is all there! >> >> HTH. >> >>>> >>>> Thanks. >>>> >>>> >>>> >>> >>> Sorry to reply to myself, but I really need help with this. >>> The movies always timeout via rdist. If I transfer the movies myself >>> via sftp then there are no timeouts. >>> The processes continue to accumulate everyday unless I manually kill >> them. >>> I know that I am missing something. Should I edit /etc/daily to turn >> on >>> debugging? >>> >>> Please/Thanks.
