The problems with rsync continues. (code 255)

[Paul Slootman]

On Fri 25 Feb 2011, Xabi Vazquez wrote:
> 
> ------------------------------------- 8< ----------------------- 8< --------------------
> [Fri Feb 25 05:21:05 CET 2011] /usr/bin/rsync -az --delete --numeric-ids --relative --delete-excluded --rsh=/usr/bin/ssh root at server1:/opt/apache/conf /data/backups/daily.0/server1
> [Fri Feb 25 05:21:05 CET 2011] /usr/bin/rsync -az --delete --numeric-ids --relative --delete-excluded --rsh=/usr/bin/ssh root at server1:/opt/apache/logs /data/backups/daily.0/server1
> ssh: connect to host server1 port 22: Connection timed out
> rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
> rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.3]
> [Fri Feb 25 05:21:26 CET 2011] /usr/bin/rsync -az --delete --numeric-ids --relative --delete-excluded --rsh=/usr/bin/ssh root at server1:/usr/local/webs /data/backups/daily.0/server1
> [Fri Feb 25 05:21:31 CET 2011] /usr/bin/rsync -az --delete --numeric-ids --relative --delete-excluded --rsh=/usr/bin/ssh root at server1:/var/mail /data/backups/daily.0/server1
> ssh: connect to host server1 port 22: Connection timed out
> rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
> rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.3]
> [Fri Feb 25 05:21:52 CET 2011] /usr/bin/rsync -az --delete --numeric-ids --relative --delete-excluded --rsh=/usr/bin/ssh root at server1:/var/spool/mail /data/backups/daily.0/server1
> [Fri Feb 25 05:21:52 CET 2011] /usr/bin/rsync -az --delete --numeric-ids --relative --delete-excluded --rsh=/usr/bin/ssh root at server1:/var/spool/exim /data/backups/daily.0/server1
> ssh: connect to host server1 port 22: Connection timed out
> rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
> rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.3]
> [Fri Feb 25 05:22:13 CET 2011] /usr/bin/rsync -az --delete --numeric-ids --relative --delete-excluded --rsh=/usr/bin/ssh root at server1:/opt/qpsmtpd /data/backups/daily.0/server1
> [Fri Feb 25 05:22:18 CET 2011] /usr/bin/rsync -az --delete --numeric-ids --relative --delete-excluded --rsh=/usr/bin/ssh root at server1:/opt/spamassassin /data/backups/daily.0/server1
> [Fri Feb 25 05:22:28 CET 2011] /usr/bin/rsync -az --delete --numeric-ids --relative --delete-excluded --rsh=/usr/bin/ssh root at server1:/opt/exim /data/backups/daily.0/server1
> ssh: connect to host server1 port 22: Connection timed out
> rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
> rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.3]
> [Fri Feb 25 05:22:49 CET 2011] /usr/bin/rsync -az --delete --numeric-ids --relative --delete-excluded --rsh=/usr/bin/ssh root at server1:/var/spool/cron /data/backups/daily.0/server1
> ------------------------------------- 8< ----------------------- 8< --------------------
> 
> As you can see seems to be a timeout problem cause the timeout arrises 21 seconds after the command is invoked.
> But why this happens in some paths and not in others?
> The paths are always the same paths (from day to day).

No, they're not.
In the first log you showed a couple of days ago it was only the clamav
path that failed (I don't see that one now).
That time /var/spool/exim succeeded, now it fails, for example.

> What can I do? Where can I change timeouts?

As I said before: it's not an rsync issue, ssh fails to connect, hence
it's network related, e.g. a firewall that doesn't work correctly.


Paul