That's logical, it happens when the connection it's "reset by peer" (closed at the other side), so it should happen sometime _after_ the reload ends.
Regards, On Tue, 31 Aug 2004 19:13:39 +0300, Ivars Jukams <[EMAIL PROTECTED]> wrote: > Yes, I think You are right. > But it comes not at the same time when reloading, but ~1minute later. > Then OK, it makes really no problem. > > Thanks! > > Ivars > > > > -----Original Message----- > From: Alejandro Guerrieri [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 31, 2004 6:19 PM > To: Ivars Jukams > Subject: Re: System error 104: Connection reset by peer > > If I'm not wrong, that comes from the HTTP status connection ins�t it?. It > happens after loading (or reloading) the status page via HTTP. I've seen it > all the time on 1.2.1 and 1.3.2 and never caused me any trouble. > > Regards, > > On Tue, 31 Aug 2004 14:24:40 +0300, Ivars Jukams <[EMAIL PROTECTED]> wrote: > > Hi, > > > > What does this error mean: > > 2004-08-31 13:46:57 [32025] [2] ERROR: System error 104: Connection > > reset by peer 2004-08-31 13:48:56 [32025] [2] ERROR: Error reading > > from fd 43: > > > > It happens several times per diem and then next day again... What can > > be the reason? > > > > Ivars > > > > > >
