Point folks reading the first answer to the rsync-debug script mentioned

[rsync-web.git] / issues.html

diff --git a/issues.html b/issues.html
index 6750b08076d3f581467a7c4c6e980b16cb93c838..45b35d28b4f80da3f68a9481ee7080b7f0eb084d 100644 (file)
--- a/issues.html
+++ b/issues.html
@@ -11,7 +11,30 @@
 
 <li><p><b>Q:</b>
 
-My chrooted rsync daemon crashes when doing an LDAP lookup for a user or group.
+Rsync appears hung -- what should I do?
+
+<p><b>A:</b>
+
+When experiencing a hang or freeze <b>please</b> gather the following
+information before killing the rsync process:
+
+<ul>
+
+<li> The state of the send/receive queues shown with netstat on the two ends.
+
+<li> The system call that each of the 3 processes is stuck in (use truss on
+solaris, strace on Linux, etc.).
+
+</ul>
+
+<p>See the "rsync-debug" script below for an example of how to grab strace
+information from the remote rsync process(es).  If you need help, send email to
+the mailing list. 
+
+<li><p><b>Q:</b>
+
+Why does my chrooted rsync daemon crash when doing an LDAP lookup for a user or
+group?
 
 <p><b>A:</b>
 
@@ -24,7 +47,7 @@ getting rid of LDAP lookups.
 
 <li><p><b>Q:</b>
 
-Transfers die with something like
+Why does my transfer die with something like the following error?
 
 <pre>rsync: error writing 4 unbuffered bytes - exiting: Broken pipe
 rsync error: error in rsync protocol data stream (code 12) at io.c(463)
@@ -46,7 +69,8 @@ figure out is <b>why</b>, and that can involve some investigative work.
 the daemon's log file to see if it logged an error explaining why it
 aborted the transfer.
 
-<p>Rsync 2.6.3 does a better job of retreiving the error from the remote
+<p>Beginning with version 2.6.3, rsync now does a better job of retreiving
+the error from the remote
 process than older versions of rsync, so you may wish to try upgrading and
 see if you now get sent the error message from the remote rsync.
 
@@ -100,8 +124,8 @@ that and using the above daemon approach to debug what is going on.
 
 <li><p><b>Q:</b>
 
-When connecting to an rsync daemon (using the "::" syntax) the
-connection fails immediately with an error like this:
+Why does my connection to an rsync daemon (using the "::" syntax)
+fail immediately with an error like the following?
 
 <pre>rsync: connection unexpectedly closed (24 bytes read so far)
 rsync error: error in rsync protocol data stream (code 12) at io.c(342)
@@ -120,13 +144,12 @@ get returned to all rsync clients, old or new alike.
 
 <li><p><b>Q:</b>
 
-Using --dry-run (-n) doesn't show all changed directories.
+Why doesn't --dry-run (-n) show all the changed directories?
 
 <p><b>A:</b>
 
-Correct.  Rsync shows most other changes, but some directory changes are
-not currently described in --dry-run mode.  Hopefully a future version
-will fix this.
+This was a bug in versions prior to 2.6.4.  Upgrade both rsync versions (or at
+least the receiving side).
 
 <li><p><b>Q:</b>