Your message dated Mon, 18 Feb 2019 04:04:41 -0500 with message-id <4204701.4fQq0siWrB@kitterma-e6430> and subject line Re: insserv: refuses to start postfix at boot because dnsmasq is disabled has caused the Debian Bug report #773170, regarding insserv: refuses to start postfix at boot because dnsmasq is disabled to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 773170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: insserv Version: 1.16.0-5 Severity: critical Justification: breaks unrelated software Dear Maintainer, insserv refuses to start postfix at boot, because I have configured dnsmasq to be disabled. I don't use dnsmasq as a DNS cache, but as a DHCP server for when I create an ad-hoc network, so dnsmasq active or not has totally no effect on the ability of my system to resolve names. As you can see, postfix can be manually started (and works fine), but it can't be started at boot automatically. # systemctl enable postfix Synchronizing state for postfix.service with sysvinit using update-rc.d... Executing /usr/sbin/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 *** Error in `systemctl': double free or corruption (fasttop): 0x00007f9c9443e9c0 *** Annullato # service postfix start # service dnsmasq status ● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled) Drop-In: /run/systemd/generator/dnsmasq.service.d └─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf Active: inactive (dead) # service postfix status ● postfix.service - LSB: Postfix Mail Transport Agent Loaded: loaded (/etc/init.d/postfix) Drop-In: /run/systemd/generator/postfix.service.d └─50-postfix-$mail-transport-agent.conf Active: active (running) since lun 2014-12-15 10:52:31 CET; 11s ago Process: 1204 ExecStart=/etc/init.d/postfix start (code=exited, status=0/SUCCESS) CGroup: /system.slice/postfix.service ├─1325 /usr/lib/postfix/master ├─1326 pickup -l -t fifo -u -c └─1327 qmgr -l -t fifo -u dic 15 10:52:31 hal9000 postfix[1204]: Starting Postfix Mail Transport Agent: postfix. dic 15 10:52:31 hal9000 systemd[1]: Started LSB: Postfix Mail Transport Agent. dic 15 10:52:31 hal9000 postfix/master[1325]: daemon started -- version 2.11.3, configuration /etc/postfix -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.2d (SMP w/4 CPU cores; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages insserv depends on: ii libc6 2.19-13 ii libdbus-1-3 1.9.4-1 insserv recommends no packages. Versions of packages insserv suggests: pn bootchart2 <none> -- no debconf information
--- End Message ---
--- Begin Message ---On Tue, 23 May 2017 01:21:17 -0400 Scott Kitterman <deb...@kitterman.com> wrote: ... > This should work now as of 3.1.4-5 (at least when using the default init > system). Please let us know if you can replicate this issue with that version > or later. > > Scott K Closing based on nearly 2 years of no more complaints and no response to the moreinfo request. Scott K
--- End Message ---
