rsync - Mar 2008 - rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe

Hi,

i installed rsync 3.0 on a Sun Solaris 10 Sparc Server and tried to 
Backup the Server via BackupPC

the complete rsync command from the backup server is this:

/usr/bin/ssh -q -x -l root IP /usr/bin/rsync --numeric-ids --perms 
--owner --group -D --links --hard-links --times --block-size=2048 
--recursive --checksum-seed=32761 --log-file=/var/log/rsync.log 
--ignore-times . /

in the log on the sun i see this:

2008/03/28 16:35:46 [5573] rsync: writefd_unbuffered failed to write 4 
bytes [sender]: Broken pipe (32)
2008/03/28 16:35:46 [5573] rsync error: errors with program diagnostics 
(code 13) at log.c(236) [sender=3.0.0]

its the same rsync command that we use on our other Server and it works 
there.

i found many Threads via google but nothing that helped me.

I hope i can get help here

-- 
Mit freundlichen Gr??en


Sebastian K?sters

systems architect
Trade Haven GmbH
In der Steele 37,      40599 D?sseldorf
T +49 211 749659 14    mailto:skoesters@tradehaven.de
F +49 211 749659 29    http://www.tradehaven.de
--------------------------------------------------------------------
Gesch?ftsf?hrer: Michael Heck | Oliver Wagner Handelsregister D?sseldorf:  HRB
53379

On Fri, Mar 28, 2008 at 04:41:26PM +0100, Sebastian K?sters
wrote:
> 2008/03/28 16:35:46 [5573] rsync: writefd_unbuffered failed to write 4
bytes [sender]: Broken pipe (32)
This tells you that the connection unexpectedly closed, so you should
look to see why BackupPC went away.

..wayne..

I do not think that this is the Problem. 

Both Server are reachable from each other without Problems.

When I start the ssh/rsync command on the Backuppc you can see the command
via ps ax all the time. It never stops with a timeout or something like
that. On the sun the command (in ps ef) went away after about 2 Minutes with
the error message I sent you.

So Backuppc is thinking that the rsync command is running but it has stopped
a long time before.

I have 2 suns. One with rsync 2.6.9 and one with 3.0.0. Both have the
Problem. I also have 40 other Server (most of them linux) and the same
command that?s not working on these 2 suns is working on the other machines
(also on 3 other suns with the same version I am using but I don?t find what
is different between this Servers - they have also the same ssh version).

Regards Sebastian

-----Urspr?ngliche Nachricht-----
Von: Wayne Davison [mailto:wayned@samba.org] 
Gesendet: Freitag, 28. M?rz 2008 17:03
An: Sebastian K?sters
Cc: rsync@lists.samba.org
Betreff: Re: rsync: writefd_unbuffered failed to write 4 bytes [sender]:
Broken pipe

On Fri, Mar 28, 2008 at 04:41:26PM +0100, Sebastian K?sters
wrote:
> 2008/03/28 16:35:46 [5573] rsync: writefd_unbuffered failed to write 4
bytes [sender]: Broken pipe (32)

This tells you that the connection unexpectedly closed, so you should
look to see why BackupPC went away.

..wayne..

On Mon, Mar 31, 2008 at 10:48:18AM +0200, Sebastian K?sters
wrote:
> On the sun the command (in ps ef) went away after about 2 Minutes with
> the error message I sent you.
That makes it look like a connection failure then.  Perhaps a firewall
is closing an idle connection?  e.g. I once had a Linksys box that would
close my ssh connections for me unless I set a keep-alive option in the
protocol.

..wayne..

i now tested it on a fresh installes sun with Solaris 10 sparc without 
installing any patches and rsync works.

If i install all patches the error message comes.

Any idea?

Mit freundlichen Gr??en


Sebastian K?sters

systems architect
Trade Haven GmbH
In der Steele 37,      40599 D?sseldorf
T +49 211 749659 14    mailto:skoesters@tradehaven.de
F +49 211 749659 29    http://www.tradehaven.de
--------------------------------------------------------------------
Gesch?ftsf?hrer: Michael Heck | Oliver Wagner Handelsregister D?sseldorf:  HRB
53379



Wayne Davison schrieb:
> On Mon, Mar 31, 2008 at 10:48:18AM +0200, Sebastian K?sters wrote:
>   
>> On the sun the command (in ps ef) went away after about 2 Minutes with
>> the error message I sent you.
>>     
>
> That makes it look like a connection failure then.  Perhaps a firewall
> is closing an idle connection?  e.g. I once had a Linksys box that would
> close my ssh connections for me unless I set a keep-alive option in the
> protocol.
>
> ..wayne..
>
>