Ubuntu
sysklogd package

[jaunty] klogd still active at shutdown prevents clean unmount of root filesystem

Bug #304774 reported by Graziano on 2008-12-03

This bug affects 1 person

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://it.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

From https://bugs.launchpad.net/bugs/302871

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.
[...]

See original description

Related branches

lp:ubuntu/karmic/sysklogd

lp:ubuntu/natty/sysklogd

Graziano (graziano-giuliani-gmail) on 2008-12-03

description:

updated

Revision history for this message

Albert Damen (albrt) wrote on 2008-12-03:

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.

Changed in sysklogd:
assignee:	nobody → albrt
status:	New → In Progress

Revision history for this message

Albert Damen (albrt) wrote on 2008-12-06:

sysklogd.debdiff Edit (1.7 KiB, text/plain)

The issue can be solved in two ways:
- re-create the stop symlinks in rc0.d and rc6.d, or
- do not add syslogd and klogd pids to the omit list of sendsigs

As the removal of the stop symlinks was part of an approved spec, the second option seems to be the best and is what I did in the attached debdiff.

The update builds fine in a jaunty pbuilder, installs and works properly on a jaunty system. Shutdown and reboot work without problems.

To verify: with 1.5-5ubuntu1 symlinks to the syslogd and klogd pid files are created in /lib/init/rw/sendsigs.omit.d/.
With 1.5-5ubuntu2 the symlinks are no longer created after a reboot.

Changed in sysklogd:
assignee:	albrt → nobody
status:	In Progress → Confirmed

Michael Vogt (mvo) on 2008-12-17

Changed in sysklogd:
assignee:	nobody → mvo
status:	Confirmed → In Progress

Revision history for this message

Launchpad Janitor (janitor) wrote on 2008-12-17:

This bug was fixed in the package sysklogd - 1.5-5ubuntu2

---------------
sysklogd (1.5-5ubuntu2) jaunty; urgency=low

  * debian/rc, debian/rc.klogd: do not add syslogd and klogd PIDs to omit
    list of sendsigs. Ubuntu does not use stop symlinks in rc0.d and rc6.d,
    so sysklogd and klogd must be terminated by sendsigs (LP: #304774).

-- Albert Damen <email address hidden> Sat, 06 Dec 2008 13:01:39 +0100

Changed in sysklogd:
status:	In Progress → Fix Released

Revision history for this message

abgalphabet (abgalphabet) wrote on 2009-03-31:

i just installed jaunty beta and have the sysklogd (1.5-5ubuntu3) installed.
The same problem of system cannot be shutdown/restart all the way happens again.
i'm using fujitsu S6420 laptop.

do i miss any config steps to make the system shutdown/restart properly?