[Bug 268112] New: klogd will *NOT* start if /var/run/klogd.pid is missing
https://bugzilla.novell.com/show_bug.cgi?id=268112 Summary: klogd will *NOT* start if /var/run/klogd.pid is missing Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: qa@suse.de I had a heck of a time figuring out why no kernel messages were getting logged. Eventually I discovered (through strace) that klogd will *refuse* to start if /var/run/klogd.pid does not exist. It can even be completely empty, but if it doesn't exist it will not start. Furthermore, /etc/init.d/syslog doesn't do anything about it, and in fact the failure to start goes unreported. This seems mighty fragile for such an important logging subsystem. The behavior is the same with either syslog or syslog-ng. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=268112 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |werner@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=268112 werner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Comment #1 from werner@novell.com 2007-04-27 06:21 MST ------- Can not reproduce this. The /var/run/klogd.pid will always removed at boot and the klogd started afterwards, even my test shows boole:werner # rcsyslog stop Shutting down syslog services done boole:werner # pidof klogd boole:werner # rm /var/run/klogd.pid rm: cannot remove `/var/run/klogd.pid': No such file or directory boole:werner # rcsyslog start Starting syslog services done boole:werner # pidof klogd 1226 boole:werner # cat /var/run/klogd.pid 1226 boole:werner # Note, that I've done all updates for my 10.2 workstation. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=268112 jnelson-suse@jamponi.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Comment #2 from jnelson-suse@jamponi.net 2007-04-27 06:43 MST ------- The problem with your test is that it does not accurate represent what (seems) to have happened. Try this: killall klogd stat /var/run/klogd.pid <- note, the process is gone but klogd.pid remains. This is expected in this case. rm /var/run/klogd.pid rcsyslog restart ps wax | grep klog <- no klogd process! No matter how many times you restart syslog, you won't get a klogd. I didn't try a complete reboot of the machine, that's hardly feasible for a server that remains up for long periods of time. I haven't a clue *why* klogd was killed and it's pid removed, perhaps an aborted restart, who knows. Workstation is 100% up-to-date. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=268112 werner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WORKSFORME ------- Comment #3 from werner@novell.com 2007-04-27 07:33 MST ------- Your system is somewhat broken: boole:werner # killall klogd boole:werner # stat /var/run/klogd.pid stat: cannot stat `/var/run/klogd.pid': No such file or directory boole:werner # rm /var/run/klogd.pid rm: cannot remove `/var/run/klogd.pid': No such file or directory boole:werner # rcsyslog restart Shutting down syslog services done Starting syslog services done boole:werner # ps wax | grep klog 7885 ? Ss 0:00 /sbin/klogd -c 1 -x -x 8211 pts/6 S+ 0:00 grep klog boole:werner # IMHO the killall send the signal SIGTERM and this leads /sbin/klogd to stop and run the signal handler to remove /var/run/klogd.pid before exit. boole:werner # rpm -qf /sbin/klogd klogd-1.4.1-584 boole:werner # rpm -V klogd-1.4.1-584 boole:werner # rpm -qf /usr/bin/killall psmisc-22.3-17 boole:werner # rpm -V psmisc-22.3-17 boole:werner # locale LANG=POSIX LC_CTYPE="POSIX" LC_NUMERIC="POSIX" LC_TIME="POSIX" LC_COLLATE="POSIX" LC_MONETARY="POSIX" LC_MESSAGES="POSIX" LC_PAPER="POSIX" LC_NAME="POSIX" LC_ADDRESS="POSIX" LC_TELEPHONE="POSIX" LC_MEASUREMENT="POSIX" LC_IDENTIFICATION="POSIX" LC_ALL= -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=268112 ------- Comment #4 from jnelson-suse@jamponi.net 2007-04-27 09:16 MST ------- (In reply to comment #3)
Your system is somewhat broken:
This is pretty embarrassing. You are right. There was a permissions issue with /var/run that prevented /sbin/klogd from re-creating the pidfile as necessary. it's not /sbin/klogd's fault, it's OPERATOR ERROR (mine). My apologies! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com