Using Solaris SunOS 5.10 in two machines we notice from time to time rsync
hanging. Below are the results from truss on two pids from one client rsync and
the results on the server side from 4 different pids as we rsync from two
different clients. Please let me know of anything else you would like me to try
on my end. All servers are running the same rsync version:
$ /opt/csw/bin/rsync --version
rsync version 3.0.9 protocol version 30
Copyright (C) 1996-2011 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/Capabilities:
64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
append, ACLs, no xattrs, iconv, no symtimes

[Bug 10035] rsync hangs in solaris

--- Comment #3 from Nestor Urquiza <[hidden email]> 2013-07-19 23:33:11 UTC ---
Now that I removed the -vvv switch rsync hangs only at 3AM. All Solaris 10
machines run around that time something. Here is the relevant information from
root cron:

[Bug 10035] rsync hangs in solaris

--- Comment #4 from Nestor Urquiza <[hidden email]> 2013-07-24 15:02:19 UTC ---
Yesterday the script actually hanged 6 times from 11PM to 5AM so it is now
discarded this is anything related to specific commands running at any specific
time. The fact that I am running it now from two different clients at the same
time and it hands exacrly at the same time from both is telling me that the
issue is most likely on the server side.

Is this enough information so far to find anything to be fixed on rsync running
on the server side?

My guess is that a hiccup in the network could be causing this but I am running
out of tools.

Someone recommended in a private email to run the below around the time the
issue happens but I cron it and it did not do any difference:
svcadm restart svc:/system/name-service-cache:default

[Bug 10035] rsync hangs in solaris

--- Comment #6 from Nestor Urquiza <[hidden email]> 2013-07-25 17:23:06 UTC ---
I set my script which uses rsync to run every hour. Last night I logged a snoop
result (tcp sniffer) but also a netstat result every minute. It failed two
ties:

At this point from netstat we can see the same connection for as long as one
complete hour:
192.168.5.124.22 client.46480 49640 0 49640 0 ESTABLISHED

It is not until the next hour when that connection disappears and the new
connection from the new rsync instance shows up. Why the rsync timeout does not
work I do not know but it should have closed that connection 30 minutes after
it started:
192.168.5.124.22 client.47122 46720 5319 49640 0 ESTABLISHED