[jaunty] klogd still active at shutdown prevents clean unmount of root filesystem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sysklogd (Ubuntu) |
Fix Released
|
Undecided
|
Michael Vogt |
Bug Description
Binary package hint: sysklogd
Description: Ubuntu jaunty (development branch)
Release: 9.04
sysklogd:
Installed: 1.5-5ubuntu1
Candidate: 1.5-5ubuntu1
Version table:
*** 1.5-5ubuntu1 0
500 http://
100 /var/lib/
From https:/
Kernel logging re-started after SIGSTOP
During shutdown, kernel logging daemon keeps restarting, preventing clean unmount of root filesystem and forces check at startup. If on laptop and on battery power, this can lead to root mounted read-only and needs superuser privileges to perform manual check.
Have a look to Bug #302871 for more info and Albert Damen solution:
[...]
As a work-around, I have created symlinks in /etc/rc{0,6}.d to terminate klogd and syslogd, and now I can shutdown and reboot without problems. Also, the log lines "Kernel logging re-started after SIGSTOP" have stopped.
[...]
description: | updated |
Changed in sysklogd: | |
assignee: | nobody → mvo |
status: | Confirmed → In Progress |
This bug is caused by the combination of:
sysklogd (1.4.1-18ubuntu2) edgy; urgency=low
* Remove stop links from rc0 and rc6
and the new Debian change:
sysklogd (1.5-3) unstable; urgency=low
* Add syslogd and klogd PIDs to omit list of sendsigs (closes: #468649)
So now sysklogd and klogd are neither stopped by the rc0/6 stop symlinks nor by the sendsigs script. Therefore the file system remains busy and cannot be unmounted during shutdown or reboot.