Re: Possible serious problem with the newest sysklogd?
On Sun, Oct 18, 1998 at 12:36:37PM +0200, Martin Schulze wrote: > Could you try the next prelimnary version? > > ftp://ftp.infodrom.north.de/pub/people/joey/debian/sysklogd_1.3-29.2_i386.deb Great! This seems to fix it, no problems here. -- Stephen Crowley Debian GNU/Linux Developer -- pgpvX5cXPlt7x.pgp Description: PGP signature
Re: Possible serious problem with the newest sysklogd?
Gregory S. Stark wrote: > > You'll also find the new version which has the offending code removed: > > > > ftp://ftp.infodrom.north.de/pub/people/joey/debian/sysklogd_1.3-28_i386.deb > > Does -29 have it reinserted? I'm seeing the same problem. Yes. That was the intention - which failed again. *sigh* Could you try the next prelimnary version? ftp://ftp.infodrom.north.de/pub/people/joey/debian/sysklogd_1.3-29.2_i386.deb Regards, Joey -- Let's call it an accidental feature. --Larry Wall
Re: Possible serious problem with the newest sysklogd?
Martin Schulze <[EMAIL PROTECTED]> writes: > > You'll also find the new version which has the offending code removed: > > ftp://ftp.infodrom.north.de/pub/people/joey/debian/sysklogd_1.3-28_i386.deb Does -29 have it reinserted? I'm seeing the same problem. greg
Re: Possible serious problem with the newest sysklogd?
Seth M. Landsman wrote: > I've traced the problem to splogger blocking. If I kill splogger, > everything is happy, but no qmail messages get logged. The problem is that no new unix domain sockets are accept()'ed. I don't know why. > Furthermore, I've found that qmail writes to the log for the first > n messages, and then just stops writing, even though messages get through > in the 30 minutes or so that splogger is happy. Also, I've found that the > initial qmail : starting message is not written to logs via this version > of syslogd. > > If no one has a definite clue or course of action, can someone > tell me where I can find the previous version of syslogd? If I can get > the previous version, I think I could probably figure out what is going > on. I seem to remember that I already answered this afternoon. In this special case the old version of syklogd could be found on my private ftp dir: ftp://ftp.infodrom.north.de/pub/people/joey/debian/sysklogd_1.3-26_i386.deb You'll also find the new version which has the offending code removed: ftp://ftp.infodrom.north.de/pub/people/joey/debian/sysklogd_1.3-28_i386.deb Regards, Joey -- Install joe (Joey's Own Editor) correct: Joe's Own Editor
Re: Possible serious problem with the newest sysklogd?
Seth M. Landsman wrote: > On Thu, Oct 15, 1998 at 04:59:42PM +0200, Martin Schulze wrote: > > Seth M. Landsman wrote: > > > Hmm, so I just updated the syslogd on my system yesterday (using > > > dselect, slink 2.1 i386 system). Then I stopped receiving mail completely > > > via qmail. About 4 hours later I realized I hadn't received any mail for > > > the day and saw no qmail entries in my logs. > > > I restarted qmail and received tons of mail, which trickled down > > > and eventually stopped. Within 30 minutes, I couldn't receive any more > > > mail. > > > I've traced the problem to splogger blocking. If I kill splogger, > > > everything is happy, but no qmail messages get logged. > > > Furthermore, I've found that qmail writes to the log for the first > > > n messages, and then just stops writing, even though messages get through > > > in the 30 minutes or so that splogger is happy. Also, I've found that the > > > initial qmail : starting message is not written to logs via this version > > > of syslogd. > > > > > > If no one has a definite clue or course of action, can someone > > > tell me where I can find the previous version of syslogd? If I can get > > > the previous version, I think I could probably figure out what is going > > > on. > > > > I guess that I've identified the offending part of the code. However > > i don't know why it didn't work. Mainly it is described in the bug > > wrt OpenBSD `-a' feature. After disabling that one syslogd runs > > perfectly on my loghost again, and there are lots of messages through > > syslog, so I guess it works again. > > > > I'll upload it later. > > Great. If you want me to give it a shakedown first, I'd be happy > to. Please find a snapshot at ftp://ftp.infodrom.north.de/pub/people/joey/debian/ The source package of -27.1 might be broken, I got some errors. Regards, Joey > -Seth > > -- > "It is by will alone I set my mind in motion" -- Install joe (Joey's Own Editor) correct: Joe's Own Editor
Re: Possible serious problem with the newest sysklogd?
Seth M. Landsman wrote: > Hmm, so I just updated the syslogd on my system yesterday (using > dselect, slink 2.1 i386 system). Then I stopped receiving mail completely > via qmail. About 4 hours later I realized I hadn't received any mail for > the day and saw no qmail entries in my logs. > I restarted qmail and received tons of mail, which trickled down > and eventually stopped. Within 30 minutes, I couldn't receive any more > mail. > I've traced the problem to splogger blocking. If I kill splogger, > everything is happy, but no qmail messages get logged. > Furthermore, I've found that qmail writes to the log for the first > n messages, and then just stops writing, even though messages get through > in the 30 minutes or so that splogger is happy. Also, I've found that the > initial qmail : starting message is not written to logs via this version > of syslogd. > > If no one has a definite clue or course of action, can someone > tell me where I can find the previous version of syslogd? If I can get > the previous version, I think I could probably figure out what is going > on. I guess that I've identified the offending part of the code. However i don't know why it didn't work. Mainly it is described in the bug wrt OpenBSD `-a' feature. After disabling that one syslogd runs perfectly on my loghost again, and there are lots of messages through syslog, so I guess it works again. I'll upload it later. Regards, Joey -- Install joe (Joey's Own Editor) correct: Joe's Own Editor
