dnsmasq and resolvconf hangs on start

Bug #1778073 reported by Thomas on 2018-06-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dnsmasq (Debian)
dnsmasq (Ubuntu)

Bug Description

I installed today dnsmasq and I use resolvconf in background.

Problem is, that systemd takes 1 minute or so after service start and than reports:

root@proxy:~# service dnsmasq status

 dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
   Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled)
  Drop-In: /run/systemd/generator/dnsmasq.service.d
           50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
   Active: failed (Result: timeout) since Do 2018-06-21 15:58:13 CEST; 2min 10s ago
  Process: 3295 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf (code=killed, signal=TERM)
  Process: 3865 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=killed, signal=TERM)
  Process: 3837 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS)
  Process: 3825 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS)
 Main PID: 3862 (code=exited, status=0/SUCCESS)

Jun 21 15:56:43 proxy dnsmasq[3862]: Benutze Namensserver
Jun 21 15:56:43 proxy dnsmasq[3865]: * Awakening mail retriever agent:
Jun 21 15:56:43 proxy dnsmasq[3865]: ...done.
Jun 21 15:56:43 proxy postfix[3951]: Postfix is running with backwards-compatible default settings
Jun 21 15:56:43 proxy postfix[3951]: See http://www.postfix.org/COMPATIBILITY_README.html for details
Jun 21 15:56:43 proxy postfix[3951]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"
Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Start-post operation timed out. Stopping.
Jun 21 15:58:13 proxy systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Unit entered failed state.
Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Failed with result 'timeout'.

when I look into the start script /etc/init.d/dnsmasq there is a func systemd-start-resolvconf which points to start-resolvconf.

There is this part:

        for interface in $DNSMASQ_EXCEPT
                [ $interface = lo ] && return

Before I had not defined DNSMASQ_EXCEPT in /etc/defaults/dnsmasq. Problem is, that this part MUST be faulty! When I commend it out, I can start dnsmasq! It looks like it loops forever there?!

Also if I define DNSMASQ_EXCEPT to my listen interface, it works - but is is really needed?

I found a other user which had the same problem:

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dnsmasq 2.75-1ubuntu0.16.04.4 [modified: etc/default/dnsmasq]
ProcVersionSignature: Ubuntu 4.15.0-23.25~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Thu Jun 21 16:12:14 2018
InstallationDate: Installed on 2017-02-27 (479 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8)
PackageArchitecture: all
 PATH=(custom, no user)
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.default.dnsmasq: 2018-06-21T16:07:24.818774

Thomas (t.c) wrote :
description: updated
Changed in dnsmasq (Debian):
status: Unknown → New

Sounds related / similar to bug 1761096

tags: added: server-next

The other bug had mentioned being resolved in latter versions.
Can you cross-try the same on e.g. 18.04 to be sure on the scope of this?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.