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

Salvo Tomaselli tiposchi at tiscali.it
Fri Nov 28 09:47:11 UTC 2014

In data venerdì 28 novembre 2014 09:22:09, Petter Reinholdtsen ha scritto:
> [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?  

# update-rc.d postfix defaults
insserv: FATAL: service dnsmasq has to be enabled to use service postfix
insserv: exiting now!
update-rc.d: error: insserv rejected the script header

I don't use dnsmasq normally, it is configured to be started manually, and I 
use it to provide dhcp for when I create a wi-fi network with my laptop, to 
share the wired connection using NAT.
Possibly dnsmasq should not be the only provider of named, since I can resolve 
names just fine when it's not running, or maybe postfix shouldn't depend on 
named to be started?

Basically I use postfix to relay outgoing emails to gmail, I don't receive 
anything because the machine is a laptop and has no stable IP or connection.
I have a script to create a wi-fi network that will use masquerading and will 
start dnsmasq to provide dhcp on the wi-fi interface. In my configuration 
dnsmasq doesn't even listen to localhost.

> 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.
I see that it might be a problem with the declared dependencies in one of the 
daemons… But it is peculiar because I've had this configuration for ages and 
it was not giving me problems before.

Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di 
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
                -- Galileo Galilei

-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.txt.bz2
Type: application/x-bzip
Size: 5204 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20141128/2bc7f847/attachment-0001.bin>

More information about the Pkg-sysvinit-devel mailing list