Bug#334295: slow syslogd makes system unusable
On Sun, Oct 16, 2005 at 10:50:30PM -0700, Steve Langasek wrote: > > I've seen this cause a boot take hours. The system looks like it's > > mostly idle, but everything which uses syslog is excruciatingly slow. > > > It is possible that this is the same which is mentioned in bug 273269, > > as both systems I've seen this on run with -r and -l, but the > > explanation looks suspicious, as I believe the last time I saw it DNS > > was actually working. In that case, -l wasn't working, but reverse > > resolution was - every host was logged with the full reverse name > > instead of the short name. In another case, the slowdown kept openvpn > > from starting, and thus all actual log messages were from localhost. > > I'm pretty sure that 'critical' is not the right severity for this bug, > since you are the first to report it. Either hardly anyone is using -r -l, > and we should consider such a configuration contraindicated; or most people > using -r -l are not experiencing such symptoms, and we should wonder what is > special about your setup that's different from theirs. This problem could > also be worked around by running two instances of syslogd -- one for local > logging that's started as normal, and one for remote logging that is started > later and is configured not to use /dev/log. > > > /etc/init.d/sysklogd restart solved the problem in both situations. > > This is the most curious part of this bug report. If this is related to bug > #273269, why should restarting the daemon have any effect? I wonder if this bug is somehow related to 301511, also submitted against sysklogd 1.4.1-16. It sounds as though that bug report relates to some harsher symptoms, so I doubt it's the same thing. Can this bug be reproduced using 1.4.1-17.1 from unstable? How consistantly reproducible is it? Can it be reproduced on systems that are not using both -r and -l options to syslogd? I have never seen it on the few production systems I support that use -r, but none of them use -l. On test machines I've built, I've used -r and -l with no ill effects. Given my inability to reproduce this bug, coupled with the lack of anybody else complaining of similar problems in the several months since the most recent activity, I'm going to decrease the severity of this bug to 'normal'. noah signature.asc Description: Digital signature
Bug#334295: slow syslogd makes system unusable
On Sun, Oct 16, 2005 at 01:50:21PM +0200, Kai Henningsen wrote: > I've seen this cause a boot take hours. The system looks like it's > mostly idle, but everything which uses syslog is excruciatingly slow. > It is possible that this is the same which is mentioned in bug 273269, > as both systems I've seen this on run with -r and -l, but the > explanation looks suspicious, as I believe the last time I saw it DNS > was actually working. In that case, -l wasn't working, but reverse > resolution was - every host was logged with the full reverse name > instead of the short name. In another case, the slowdown kept openvpn > from starting, and thus all actual log messages were from localhost. I'm pretty sure that 'critical' is not the right severity for this bug, since you are the first to report it. Either hardly anyone is using -r -l, and we should consider such a configuration contraindicated; or most people using -r -l are not experiencing such symptoms, and we should wonder what is special about your setup that's different from theirs. This problem could also be worked around by running two instances of syslogd -- one for local logging that's started as normal, and one for remote logging that is started later and is configured not to use /dev/log. > /etc/init.d/sysklogd restart solved the problem in both situations. This is the most curious part of this bug report. If this is related to bug #273269, why should restarting the daemon have any effect? Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#334295: slow syslogd makes system unusable
Package: sysklogd Version: 1.4.1-16 Severity: critical I've seen this cause a boot take hours. The system looks like it's mostly idle, but everything which uses syslog is excruciatingly slow. It is possible that this is the same which is mentioned in bug 273269, as both systems I've seen this on run with -r and -l, but the explanation looks suspicious, as I believe the last time I saw it DNS was actually working. In that case, -l wasn't working, but reverse resolution was - every host was logged with the full reverse name instead of the short name. In another case, the slowdown kept openvpn from starting, and thus all actual log messages were from localhost. /etc/init.d/sysklogd restart solved the problem in both situations. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (995, 'testing'), (550, 'experimental'), (550, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.13.2+kai.20050930 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages sysklogd depends on: ii klogd [linux-kernel-log-dae 1.4.1-16 Kernel Logging Daemon ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
