[Pkg-sysvinit-devel] Bug#771229: Bug#771229: insserv: FATAL

Petter Reinholdtsen pere at hungry.com
Fri Nov 28 08:22:09 UTC 2014

[Salvo Tomaselli]
> Dear Maintainer,
> Please see #771172
> While doing a d-u I got this message:
>> insserv: FATAL: service dnsmasq is missed in the runlevels 2 3 4 5 to
>> use service postfix
> I honestly have no idea what is wrong with postfix or dnsmasq
> services. They were not part of the upgrade.

This message mean that postfix had a dependency on dnsmasq, and that
dnsmasq as far as insserv could tell, were missing.  Looking at
<URL: http://sources.debian.net/src/postfix/2.11.3-1/debian/init.d/ >,
I see this header:

# Provides:          postfix mail-transport-agent
# Required-Start:    $local_fs $remote_fs $syslog $named $network $time
# Required-Stop:     $local_fs $remote_fs $syslog $named $network
# Should-Start:      postgresql mysql clamav-daemon postgrey spamassassin saslauthd dovecot
# Should-Stop:       postgresql mysql clamav-daemon postgrey spamassassin saslauthd dovecot
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Postfix Mail Transport Agent
# Description:       postfix is a Mail Transport agent

The Required-Start and Required-Stop values are hard dependencies and
could cause the error reported.  I suspect the expansion of the $named
facility is the trigger here, and that content in /etc/insserv.conf.d/
listed dnsmasq as a hard requirement of $named.  Do you still see if
when you run 'update-rc.d postfix defaults' as root?  It hard to debug
any further without more information, but you can try to run
/usr/share/insserv/make-testsuite and attach the result to allow us to
try to reproduce the problem.

I doubt it is a bug in insserv, as these things are tested in the
testsuite during build, but it might be a test case that is missing or
some problem with the systemd interaction.
Happy hacking
Petter Reinholdtsen

More information about the Pkg-sysvinit-devel mailing list