Re: HELP: Failed powerpc autobuild upload again, p.d.o is rejecting my rsync.

2004-09-12 Thread Rick Thomas
Then it's probably not a hardware problem.
On Sunday, September 12, 2004, at 06:00 AM, Sven Luther wrote:
On Sun, Sep 12, 2004 at 05:10:53AM -0400, Rick_Thomas wrote:
On Sun, 2004-09-12 at 03:06, Sven Luther wrote:
Here is the error in my log :
powerpc/netboot/2.4/vmlinuz-chrp.initrd
powerpc/netboot/2.4/vmlinuz-prep.initrd
Read from remote host people.debian.org: Connection reset by peer
rsync: writefd_unbuffered failed to write 4 bytes: phase 
"unknown": Broken pipe
rsync error: error in rsync protocol data stream (code 12) at 
io.c(839)
Sun Sep 12 05:28:26 UTC 2004

Anyone has an idea on what is going on ?
Whenever I've seen error messages similar to those, it's been 
because an
ethernet interface has gotten confused.  Usually rebooting the 
relevant
machine clears it up (but sometimes only for a while.)  If it 
comes back
after a reboot, it's likely a sign that the interface hardware is
failing and should be replaced.
Err, the box in question is always online, gets my mail and host 
my irc client
under screen. I am thus continously connected to it or something, 
and i don't
see any failure in it. Furthermore, if i do the upload by hand, it 
always
seems to work.

Friendly,
Sven Luther

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Re: HELP: Failed powerpc autobuild upload again, p.d.o is rejecting my rsync.

2004-09-12 Thread Colin Watson
On Sun, Sep 12, 2004 at 09:06:09AM +0200, Sven Luther wrote:
> I think i would have prefered to use scp -r instead of rsync or something
> such, which seems much more fiable.
> 
> Here is the error in my log :
> 
> powerpc/netboot/2.4/vmlinuz-chrp.initrd
> powerpc/netboot/2.4/vmlinuz-prep.initrd
> Read from remote host people.debian.org: Connection reset by peer

If rsync-over-ssh gets ECONNRESET, there is no good reason to suspect
that scp (i.e. rcp-over-ssh) wouldn't.

-- 
Colin Watson   [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: HELP: Failed powerpc autobuild upload again, p.d.o is rejecting my rsync.

2004-09-12 Thread Sven Luther
On Sun, Sep 12, 2004 at 05:10:53AM -0400, Rick_Thomas wrote:
> On Sun, 2004-09-12 at 03:06, Sven Luther wrote:
> 
> > Here is the error in my log :
> > 
> > powerpc/netboot/2.4/vmlinuz-chrp.initrd
> > powerpc/netboot/2.4/vmlinuz-prep.initrd
> > Read from remote host people.debian.org: Connection reset by peer
> > rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe
> > rsync error: error in rsync protocol data stream (code 12) at io.c(839)
> > Sun Sep 12 05:28:26 UTC 2004
> > 
> > Anyone has an idea on what is going on ? 
> 
> Whenever I've seen error messages similar to those, it's been because an
> ethernet interface has gotten confused.  Usually rebooting the relevant
> machine clears it up (but sometimes only for a while.)  If it comes back
> after a reboot, it's likely a sign that the interface hardware is
> failing and should be replaced.

Err, the box in question is always online, gets my mail and host my irc client
under screen. I am thus continously connected to it or something, and i don't
see any failure in it. Furthermore, if i do the upload by hand, it always
seems to work.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: HELP: Failed powerpc autobuild upload again, p.d.o is rejecting my rsync.

2004-09-12 Thread Rick_Thomas
On Sun, 2004-09-12 at 03:06, Sven Luther wrote:

> Here is the error in my log :
> 
> powerpc/netboot/2.4/vmlinuz-chrp.initrd
> powerpc/netboot/2.4/vmlinuz-prep.initrd
> Read from remote host people.debian.org: Connection reset by peer
> rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe
> rsync error: error in rsync protocol data stream (code 12) at io.c(839)
> Sun Sep 12 05:28:26 UTC 2004
> 
> Anyone has an idea on what is going on ? 

Whenever I've seen error messages similar to those, it's been because an
ethernet interface has gotten confused.  Usually rebooting the relevant
machine clears it up (but sometimes only for a while.)  If it comes back
after a reboot, it's likely a sign that the interface hardware is
failing and should be replaced.

Just a thought...

Rick



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



HELP: Failed powerpc autobuild upload again, p.d.o is rejecting my rsync.

2004-09-12 Thread Sven Luther
On Sun, Sep 12, 2004 at 02:28:06AM -0400, Rick Thomas wrote:
> 
> On Thursday, September 9, 2004, at 01:23 PM, Sven Luther wrote:
> 
> >On Thu, Sep 09, 2004 at 12:45:29PM -0400, Rick Thomas wrote:
> >>
> >>Ummm... The contents of
> >>
> >>http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy-2.4/
> >>
> >>haven't changed in the last few days.  Is the build process stalled
> >>somewhere?
> >
> >[DIR] 2004-09-08_RSYNC_IN_PROGRESS/ 07-Sep-2004 22:05  -
> >[DIR] 2004-09-09_RSYNC_IN_PROGRESS/ 08-Sep-2004 22:05  -
> 
> Hmmm.. It seems to be doing it again...
> 
>  2004-09-11/   10-Sep-2004 23:13  -
>  2004-09-12_RSYNC_IN_PROGRESS/ 11-Sep-2004 22:05  -
>  daily/10-Sep-2004 23:13  -
> 
> It's been this way for over an hour...

Damnit, indeed it does, and i really don't know why. I will be launching a
manual build later on. 

I think i would have prefered to use scp -r instead of rsync or something
such, which seems much more fiable.

Here is the error in my log :

powerpc/netboot/2.4/vmlinuz-chrp.initrd
powerpc/netboot/2.4/vmlinuz-prep.initrd
Read from remote host people.debian.org: Connection reset by peer
rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(839)
Sun Sep 12 05:28:26 UTC 2004

Anyone has an idea on what is going on ? 

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]