kerneloops stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (1)

Bug #452000 reported by Marco Rodrigues
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
kerneloops (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: kerneloops

I was installing kerneloops in Karmic.

Setting up kerneloops-daemon (0.12+git20090217-1ubuntu4) ...
update-rc.d: warning: kerneloops stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (1)
 * Starting Kernel Oops catching service kerneloops [ OK ]

Setting up kerneloops-applet (0.12+git20090217-1ubuntu4) ...
Setting up kerneloops (0.12+git20090217-1ubuntu4) ...

ProblemType: Bug
Architecture: i386
CheckboxSubmission: 57eb8f6e69624b84a142b91d06ec87dd
CheckboxSystem: 17d472c9479d8d3a99a4cb183303c69f
Date: Thu Oct 15 10:05:55 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: kerneloops 0.12+git20090217-1ubuntu4
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.45-generic
SourcePackage: kerneloops
Uname: Linux 2.6.31-13-generic i686

Related branches

Revision history for this message
Marco Rodrigues (gothicx) wrote :
Revision history for this message
Tiede (marcarthur) wrote :

I am noticing the same problem on Karmic too, after a regular upgrade. What does it mean?

Paramétrage de kerneloops-daemon (0.12+git20090217-1ubuntu4.1) ...
Installation de la nouvelle version du fichier de configuration /etc/init.d/kerneloops ...
update-rc.d: warning: kerneloops stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (1)

should I be worried?

Revision history for this message
Tiede (marcarthur) wrote :

Forgot to add that this is on the 64-bit of ubuntu, so this pretty much means this is arch independent...

Changed in kerneloops (Ubuntu):
status: New → Confirmed
Revision history for this message
James Westby (james-w) wrote :

No need to worry, this is a cosmetic issue.

Thanks,

James

Changed in kerneloops (Ubuntu):
importance: Undecided → Low
Revision history for this message
hazard (hazard-pad) wrote :

Same thing here.

Fetched 19.3kB in 0s (44.2kB/s)
(Reading database ... 119300 files and directories currently installed.)
Preparing to replace kerneloops-daemon 0.12+git20090217-1ubuntu4 (using .../kerneloops-daemon_0.12+git20090217-1ubuntu4.1_i386.deb) ...
 * Stopping Kernel Oops catching service kerneloops [ OK ]
Unpacking replacement kerneloops-daemon ...
Processing triggers for sreadahead ...
sreadahead will be reprofiled on next reboot
Processing triggers for man-db ...
Setting up kerneloops-daemon (0.12+git20090217-1ubuntu4.1) ...
Installing new version of config file /etc/init.d/kerneloops ...
update-rc.d: warning: kerneloops stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (1)

Revision history for this message
dk75 (amidk75) wrote :
Download full text (3.2 KiB)

this is not a "cosmetic issue"
a whole LSB system init.d script insertion is falling apart and is useless

I wroted a script that stops rtorrent gracefully and want to instert it at INIT 0, 1 and 6 ( halt, silgme-user, reboot ) and configured it with LSB as this:
### BEGIN INIT INFO
# Provides: rtorrent-stop
# Required-Start:
# Required-Stop: $local_fs $remote_fs $syslog
# Default-Start:
# Default-Stop: 0 1 6
# Short-Description: Stop gracefully any rtorrent process durring shutdown/reboot
# Description: Run "kill -2 `pidof rtorrent'" which stops any rtorrent work,
# disconnect it from trackers and close files.
### END INIT INFO

I've invoced "update-rc.d":
sudo update-rc.d rtorrent-stop defults
update-rc.d: warning: rtorrent-stop start runlevel arguments (2 3 4 5) do not match LSB Default-Start values (none)
 Adding system startup for /etc/init.d/rtorrent-stop ...
   /etc/rc0.d/K20rtorrent-stop -> ../init.d/rtorrent-stop
   /etc/rc1.d/K20rtorrent-stop -> ../init.d/rtorrent-stop
   /etc/rc6.d/K20rtorrent-stop -> ../init.d/rtorrent-stop
   /etc/rc2.d/S20rtorrent-stop -> ../init.d/rtorrent-stop
   /etc/rc3.d/S20rtorrent-stop -> ../init.d/rtorrent-stop
   /etc/rc4.d/S20rtorrent-stop -> ../init.d/rtorrent-stop
   /etc/rc5.d/S20rtorrent-stop -> ../init.d/rtorrent-stop

so instead insterting scritp only where it is wanted it instert it into the default positions

here is quote from LSB wiki:
[..]
Default-Start: run_level_1 [run_level_2...],Default-Stop: run_level_1 [run_level_2...]

    * defines the run levels where the script should be started (stopped) by default. For example, if a service should run in runlevels 3, 4, and 5 only, specify "Default-Start: 3 4 5" and "Default-Stop: 0 1 2 6".
[..]

So I configured my script as in this WIKI:
### BEGIN INIT INFO
# Provides: rtorrent-stop
# Required-Start:
# Required-Stop: $local_fs $remote_fs $syslog
# Default-Start: 3 4 5
# Default-Stop: 0 1 2 6
# Short-Description: Stop gracefully any rtorrent process durring shutdown/reboot
# Description: Run "kill -2 `pidof rtorrent'" which stops any rtorrent work,
# disconnect it from trackers and close files.
### END INIT INFO

and that what "update-rc.d" did:
update-rc.d: warning: rtorrent-stop start runlevel arguments (2 3 4 5) do not match LSB Default-Start values (3 4 5)
update-rc.d: warning: rtorrent-stop stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (0 1 2 6)
 Adding system startup for /etc/init.d/rtorrent-stop ...
   /etc/rc0.d/K20rtorrent-stop -> ../init.d/rtorrent-stop
   /etc/rc1.d/K20rtorrent-stop -> ../init.d/rtorrent-stop
   /etc/rc6.d/K20rtorrent-stop -> ../init.d/rtorrent-stop
   /etc/rc2.d/S20rtorrent-stop -> ../init.d/rtorrent-stop
   /etc/rc3.d/S20rtorrent-stop -> ../init.d/rtorrent-stop
   /etc/rc4.d/S20rtorrent-stop -> ../init.d/rtorrent-stop
   /etc/rc5.d/S20rtorrent-stop -> ../init.d/rtorrent-stop

So... it's not working at all.
GARBAGE!!!

I need to do "sudo update-rc.d rtorrent-stop stop 99 0 1 6 ." manually.

Conclusion: "update-rc.d" in Ubuntu ( Karmic ) is working ONLY in legacy mo...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kerneloops - 0.12+git20090217-1ubuntu5

---------------
kerneloops (0.12+git20090217-1ubuntu5) lucid; urgency=low

  * Avoid bug 422536's WARNING as it isn't a WARN().
  * Re-enable kerneloops by default.
  * Call update-rc.d with arguments that mean the link isn't installed for
    rc0 or rc6, matching the headers. (LP: #452000)
  * Install the autostart file in the correct place (LP: #440301)
 -- James Westby <email address hidden> Tue, 16 Feb 2010 17:27:25 +0000

Changed in kerneloops (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
avlas (avlas) wrote :

It seems this came back, I just so this problem in a system update

Revision history for this message
Daniel Hawkins (hwkns) wrote :

I am also seeing this now, after upgrading to Ubuntu 14.04

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.