Hi all,
I am having a problem while sycing file. An error is given as follows:
"io timeout after 55 second - exiting".
I have found this problem being posted in the mailing list previously. But
after reading those mails,
i understood that this problem occured only for files greater than 100M file
size. But the file am trying
to sync is of just 2MB. Let me also make a not that i am using a old version of
rsync ..version 2.4 series.
This is actually being used in the product..due to the less space the binary
takes to execute..so i cant go for
the latest rsync version because of the space constraint. I have mentioned the
rsync commmand line
options used and the error thrown by rsync below for your reference.
Rsync Command:
rsync -aI --stats --copy-links --temp-dir=/tmp/ --timeout=55
srcIp::srcPath/srcFile destPath/destFile
Error Given:
io timeout after 55 second - exiting
Can any bode help me or pointer me as to how can this problem of timeout be
avoided ?
That would be really thankful.
Thanks and Regards,
Vijay Ram.C
-------------- next part --------------
HTML attachment scrubbed and removed
Hi Tony, Thanks for the fast reply.> The timeout depends on file sizes and network speed > and can even depend on cpu speedWe'll the file size is just 1.5MB. The same thing works on a different product with the same network speed and the network processor. (IXP420) is the processor being used. In that case, the file size being synced is 4MB. With the 4MB file i never got this error.> network speeds probably now run from 300 baud to 10gigabit. > Any rule of thumb makes a bunch of assumptions about what is "reasonable" > Outside those boundaries, the rules of thumb are not much good.> I'm not sure of the exact details, but seems like the timeout can refer to > the amount of time without transferring, regardless of why.> Trying to find the first difference in a long file > (rsyncing a long file changed (mostly) at the end) > can be fairly cpu-intensive.> Assuming nothing is broken, up the 55 seconds until you find something that works. > Then add fudge factor for safety.One more point which i would forgot to mention in my previous mail was, this error is also not consisten. It has been occuring 3 of 5 times..and i feel that is really to be bothered about. Could you please tell me which way this problem can be avoided. ? Thanks and Regards, Vijay Ram.C -------------- next part -------------- HTML attachment scrubbed and removed
Hi Tony,> rsync -aI --stats --copy-links --temp-dir=/tmp/ --timeout=55 srcIp::srcPath/srcFile destPath/destFile> I think I'd try it WITHOUT the > l of -al > --copy-links > --temp-dir=/tmp/May i know why is it you would try it without "a" option in "aI". What difference would it make ?> I don't see how they'd do anything useful if copying just ONE file> It's just possible you're sending something off on a wild-goose chase.Actually, in this context RSYNC is used to update a redundant Network Box with the actual one. Rsync in this context syncs the configuration files required by the redundant box which are used on a High Availbility System. So just one file would solve this purpose.> 55 seconds is a long time to move something reasonably small.> When it does work, how long does it take?We'll ya i agree 55 is a long time for such a small file.But it still fails sometimes. The actual time taken while done successfully is nearly 1min 45seconds. These files are actually read and written to flash. That's why it takes so long. The processor used on the network boxes are IXP425. Hope this information can hint you to give me some more options. -------------- next part -------------- HTML attachment scrubbed and removed
On Sun, Jan 08, 2006 at 12:38:51PM +0530, Vijay Ram.C wrote:> Let me also make a not that i am using a old version of rsync > ..version 2.4 series. This is actually being used in the product..due > to the less space the binary takes to execute..How big is your file list? If it is large, the per-file memory optimizations in 2.6.0 and beyond will save a lot of memory. If it is not that big, then you're probably seeing a difference in buffer sizes in the more modern versions, which you can change by editing rsync.h and making some of the defines smaller (e.g. MAX_MAP_SIZE).> io timeout after 55 second - exitingOlder rsync versions require that the receiver be kept busy doing something during the timeout period, and it does not take into account any activity going on between the generator and the sender. A big file can take a long time to get all the checksums from the generator to the sender, and that can cause the receiver to timeout (again, on older versions). Your only options are to increase the timeout value or to upgrade to rsync 2.6.6 on both ends of the connection. ..wayne..