On Mon, Feb 02, 2004 at 02:27:29PM +0000, [EMAIL PROTECTED] wrote:
>
> Hello
>
> I came about the following phenomeon when
> the server ( dell poweredge 2650 ) is rsyncing to
> the same and remote server.
> the connection was close and copying the file didn't finish
> yet.
>
> Network Topology:
>
> Dell2650 ----L2SW---L3SW---Dell2650
>
> L2SW: Procurve4108gl
> L3SW: BigIron15000
>
> when the unexpected failed come about, the ping
> of end-to-end is no problem, and telnet is O.K
> when I look at the output message of
> " netstat -i " the statistics of errors and collision
> packet was pointing to " 0 " so it looks like no problem at all.
>
> I'll put the log
>
> ------------------------------------------------------------
> # ./bin/PD_rsync.sh
> rsync: error writing 4096 unbuffered bytes - exiting: Broken pipe
> rsync error: error in rsync protocol data stream (code 12) at io.c(463)
> rsync: writefd_unbuffered failed to write 4092 bytes: phase
> "unknown":
> Broken pipe
> rsync: connection unexpectedly closed (13452651072 bytes read so far)
> rsync error: error in rsync protocol data stream (code 12) at io.c(515)
> rsync error: received SIGUSR1 or SIGINT (code 20) at main.c(867)
> ------------------------------------------------------------
>
> what kind of things can you guess ?
A Broken pipe means the process at the other end of the pipe
terminated. This could be because of an error or it could
be because the session got dropped.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: [EMAIL PROTECTED]
Remember Cernan and Schmitt
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
