Huge rsyncd.log file - what do I grep for to debug rscync failures

[Kevin Korb]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Connection reset by peer essentially means that the program you were
talking to went away (crashed).  Therefore whatever is at or near the
end is probably what is important.

On 09/06/12 14:52, Dariusz Dolecki wrote:
> Hi,
> 
> -rw-r--r--   1 root     other    5291457346 Sep  6 13:44
> rsyncd.log
> 
> what pattern should I grep for to send you guys more information
> on rsync failures (server side)
> 
> 
> Client side messages are: rsync of /oradb/d10 appeared to complete
> with NON-NOMINAL status (rc=12) at Thu Sep  6 07:33:58 PDT 2012 
> with the following files reported in output:
> 
> 
> receiving incremental file list HR8PRD/temp1_02.dbf rsync: read
> error: Connection reset by peer (131) rsync error: error in rsync
> protocol data stream (code 12) at io.c(759) [receiver=3.0.6] rsync:
> connection unexpectedly closed (88 bytes received so far)
> [generator] rsync error: error in rsync protocol data stream (code
> 12) at io.c(600) [generator=3.0.6]
> 
> 
> 
> errors are being generated ONLY on sparse files I had put in the 
> --sparse switch, now trying with the -avS options
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Thank you
> 
> 

- -- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at FutureQuest.net  (work)
	Orlando, Florida		kmk at sanitarium.net (personal)
	Web page:			http://www.sanitarium.net/
	PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBI8nAACgkQVKC1jlbQAQcFDACfaET2zVwoNo0NtFgMi9UI2wKw
8HcAn07HijcBE4K8XpUi76OhzNofJepU
=uYAH
-----END PGP SIGNATURE-----