Bug #2735
closedwarning during update-rc.d
Added by Gonéri Le Bouder over 12 years ago. Updated over 9 years ago.
Description
root@srv00015:~# update-rc.d rudder-agent stop update-rc.d: using dependency based boot sequencing Use of uninitialized value in string eq at /usr/sbin/update-rc.d line 500. update-rc.d: warning: rudder-agent start runlevel arguments (none) do not match LSB Default-Start values (2 3 4 5) update-rc.d: warning: rudder-agent stop runlevel arguments (none) do not match LSB Default-Stop values (0 1 6) root@srv00015:~# update-rc.d rudder-agent disable update-rc.d: using dependency based boot sequencing insserv: warning: current start runlevel(s) (empty) of script `rudder-agent' overwrites defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `rudder-agent' overwrites defaults (0 1 6).
Updated by Jonathan CLARKE about 12 years ago
- Status changed from New to 2
- Assignee changed from Jonathan CLARKE to Nicolas PERRON
- Priority changed from N/A to 3
- Target version set to 2.4.0~beta4
Thanks for the report, Gonéri.
This needs fixing in 2.4.
Updated by Jonathan CLARKE about 12 years ago
- Assignee changed from Nicolas PERRON to Matthieu CERDA
- Target version changed from 2.4.0~beta4 to 2.4.0~rc1
Matthieu, can you add the LSB headers in any init scripts missing them?
Updated by Jonathan CLARKE about 12 years ago
- Assignee changed from Matthieu CERDA to Nicolas PERRON
Updated by Nicolas PERRON about 12 years ago
I don't understand what's wrong. Isn't these messages "normal" ?
Actually, rudder-agent have an LSB script:
### BEGIN INIT INFO # Provides: rudder-agent # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Should-Start: $network $time # Should-Stop: $network $time # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: CFEngine Community # Description: CFEngine Community init script provided by Normation ### END INIT INFO
Indeed, using update-rc.d like you did result in the display you had:
root@squeezedev:~# update-rc.d rudder-agent stop update-rc.d: using dependency based boot sequencing Use of uninitialized value in string eq at /usr/sbin/update-rc.d line 500. update-rc.d: warning: rudder-agent start runlevel arguments (none) do not match LSB Default-Start values (2 3 4 5) update-rc.d: warning: rudder-agent stop runlevel arguments (none) do not match LSB Default-Stop values (0 1 6)
But it's the same for anything which have an LSB header:
root@squeezedev:~# head -11 /etc/init.d/dbus #!/bin/sh ### BEGIN INIT INFO # Provides: dbus # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: # Short-Description: D-Bus systemwide message bus # Description: D-Bus is a simple interprocess messaging system, used # for sending messages between applications. ### END INIT INFO root@squeezedev:~# update-rc.d dbus stop update-rc.d: using dependency based boot sequencing Use of uninitialized value in string eq at /usr/sbin/update-rc.d line 500. update-rc.d: warning: dbus start runlevel arguments (none) do not match LSB Default-Start values (2 3 4 5)
Updated by Gonéri Le Bouder about 12 years ago
I've the same warning with Sid and your LSB header looks good. I believe you should use "insserv -v -s" to understand what's going on instead.
Updated by Nicolas PERRON about 12 years ago
Gonéri Le Bouder wrote:
I've the same warning with Sid and your LSB header looks good. I believe you should use "insserv -v -s" to understand what's going on instead.
But what is the problem ?
root@squeezedev:~# update-rc.d rudder-agent stop update-rc.d: using dependency based boot sequencing Use of uninitialized value in string eq at /usr/sbin/update-rc.d line 500. update-rc.d: warning: rudder-agent start runlevel arguments (none) do not match LSB Default-Start values (2 3 4 5) update-rc.d: warning: rudder-agent stop runlevel arguments (none) do not match LSB Default-Stop values (0 1 6) root@squeezedev:~# insserv -v -f /etc/init.d/rudder-agent insserv: creating .depend.boot insserv: creating .depend.start insserv: creating .depend.stop
I don't see any trouble
Updated by Nicolas PERRON about 12 years ago
I suppose this issue can be rejected too, like #2734 ?
Updated by Jonathan CLARKE about 12 years ago
- Status changed from 2 to Discussion
- Assignee changed from Nicolas PERRON to Gonéri Le Bouder
Gonéri, can you explain why you think this is a bug in Rudder? It seems to happen on Debian with any init script... so it looks to me like a Debian bug, not a Rudder bug.
I may be wrong, so please correct me if so, and we'll happily fix what needs fixing.
Updated by Gonéri Le Bouder about 12 years ago
/etc/init.d/cfengine-community, /etc/init.d/slapd, /etc/init.d/jetty init scripts don't have LSB headers here.
root@srv00015:~# dpkg -l|grep rudder ii rudder-cfengine-community 2.3.8-squeeze0 Configuration management and audit tool - CFEngine server component ii rudder-inventory-endpoint 2.3.8-squeeze0 Configuration management and audit tool - service to receive inventory data ii rudder-inventory-ldap 2.3.8-squeeze0 Configuration management and audit tool - OpenLDAP ii rudder-jetty 2.3.8-squeeze0 Configuration management and audit tool - Jetty application server ii rudder-policy-templates 2.3.8-squeeze0 Configuration management and audit tool - policy templates ii rudder-reports 2.3.8-squeeze0 Configuration management and audit tool - reports database ii rudder-server-root 2.3.8-squeeze0 Configuration management and audit tool - root server base package ii rudder-webapp 2.3.8-squeeze0 Configuration management and audit tool - webapp
root@srv00015:~# for i in `dpkg -l|grep rudder|awk '{print $2}'`; do dpkg -L $i ; done|grep '/etc/init.d/'|xargs head -n 10 ==> /etc/init.d/cfengine-community <== #!/bin/bash #==================================================================== # Start/stop script for Cfengine Community # (http://www.cfengine.org). # # chkconfig: 2345 85 15 # description: Cfengine Community # ### BEGIN INIT INFO ==> /etc/init.d/slapd <== #!/bin/sh #==================================================================== # Start/stop script for OpenLDAP (2.2 minimum) # (http://www.openldap.org). # Use BerkeleyDB utilities and save data in LDIF format. # # chkconfig: 2345 85 15 # description: OpenLDAP # ==> /etc/init.d/jetty <== #!/usr/bin/env bash # # Startup script for jetty under *nix systems (it works under NT/cygwin too). # To get the service to restart correctly on reboot, uncomment below (3 lines): # ======================== # chkconfig: 3 99 99 # description: Jetty 7 webserver # processname: jetty # ======================== ==> /etc/init.d/rudder-server-root <== #!/bin/sh #============================================== # Start/stop script for all Rudder components # #============================================== # ### BEGIN INIT INFO # Provides: rudder # Required-Start: $local_fs $remote_fs $network $syslog # Required-Stop: $local_fs $remote_fs $network $syslog
Updated by Gonéri Le Bouder about 12 years ago
Hum, sorry this last post was for #2734, not this one. Indeed, I agree to say it's not a Rudder bug actually. Sorry guy for the confusion.
Updated by Jonathan CLARKE about 12 years ago
- Status changed from Discussion to Rejected
Gonéri Le Bouder wrote:
Hum, sorry this last post was for #2734, not this one. Indeed, I agree to say it's not a Rudder bug actually. Sorry guy for the confusion.
OK, thanks for the confirmation. Closing.
Updated by Nicolas PERRON about 12 years ago
- Target version changed from 2.4.0~rc1 to 2.4.0~beta5
Updated by Nicolas PERRON almost 12 years ago
- Project changed from Rudder to 34
- Category deleted (
11)
Updated by Benoît PECCATTE over 9 years ago
- Project changed from 34 to Rudder
- Category set to Packaging