[Pkg-sysvinit-devel] Bug#738775: insserv: Insserv 1.16 tries to connect to systemd even though system is running on sysv-init

Jan Binder wheel at herr-der-mails.de
Thu Feb 13 16:35:01 UTC 2014

Am Donnerstag, 13. Februar 2014, 11:11:26 schrieb Petter Reinholdtsen:
> I've tried to reproduce this part of your problem report:
> > * What was the outcome of this action?
> > Cannot install initscripts after installing insserv 1.16 because it
> > tries to connect to systemd which is present on the system but not
> > used as PID 1.
> I have no problem installing initscripts or any other package, even if
> insserv spew out lots of error messages.  So the problem you reported
> seem to be non-fatal and irrelevant for any installation problem.  Can
> you tell me more about how the installation of initscripts fail?
> The svn version of insserv reduces the amount of messages, but are
> still printing warnings.  The behaviour do not change, as far as I can
> tell.

Ok, I agree that the systemd messages are gone with the SVN version and were not fatal:

LANG=C apt-get install initscripts
Reading package lists... Done
Building dependency tree       
Reading state information... Done
initscripts is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 78 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up initscripts (2.88dsf-49) ...
insserv: FATAL: service dnsmasq is missed in the runlevels 2 3 4 5 to use service cups-browsed
insserv: FATAL: service rpcbind is missed in the runlevels 2 3 4 5 to use service nfs-common
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package initscripts (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)

So it looks like the real problem is that insserv has problems with some script headers,
especially rpcbind (see also bug #738532) and dnsmasq.
I don't know if there is anything wrong with those initscripts, but insserv dies and update-rc.d does
not like that and returns an error which in turn dpkg does not like.

I have attached the offensive initscripts, they are from dnsmasq 2.68-1 and rpcbind 0.2.1-2
despite not knowing what is wrong with them or any other part of my init configuration.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rpcbind
Type: application/x-shellscript
Size: 2512 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20140213/b9ff1593/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dnsmasq
Type: application/x-shellscript
Size: 7197 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20140213/b9ff1593/attachment-0001.bin>

More information about the Pkg-sysvinit-devel mailing list