Package: dnsmasq
Version: 2.76-5
Severity: important
Dear Maintainer,
dnsmasq doesn't start anymore.
$ /etc/init.d/dnsmasq start
[....] Starting dnsmasq (via systemctl): dnsmasq.serviceJob for
dnsmasq.service failed because the control process exited with error
code.
See "systemctl status dnsmasq.service" and "journalctl -xe" for details.
$ systemctl status dnsmasq.service
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Thu 2017-06-01 19:48:58
CEST; 9s ago
Process: 4488 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited,
status=1/FAILURE)
Process: 4485 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited,
status=0/SUCCESS)
CPU: 6ms
Jun 01 19:48:58 hostname systemd[1]: Starting dnsmasq - A lightweight
DHCP and caching DNS server...
Jun 01 19:48:58 hostname dnsmasq[4485]: dnsmasq: syntax check OK.
Jun 01 19:48:58 hostname dnsmasq[4488]: dnsmasq: junk found in command line
Jun 01 19:48:58 hostname systemd[1]: dnsmasq.service: Control process
exited, code=exited status=1
Jun 01 19:48:58 hostname systemd[1]: Failed to start dnsmasq - A
lightweight DHCP and caching DNS server.
Jun 01 19:48:58 hostname systemd[1]: dnsmasq.service: Unit entered
failed state.
Jun 01 19:48:58 hostname systemd[1]: dnsmasq.service: Failed with result
'exit-code'.
debugging the initscript with systemd-exec command (by prepending
"echo"), i found that systemd-exec tries to append dns records to the
command line:
exec /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -7
/etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new --local-service . 172800
IN DS
19036,8,2,49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
. 172800 IN DS
20326,8,2,e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
running dnsmasq or dnsmasq -d without appending such records works with
my config just fine.
I am not sure what it is appending there, but i do not see why i should
want it there anyway, even when it would have the correct syntax.
I think a initscript should start a service as vanilla as possible, i
have my own dnsmasq.conf and are a bit surprised that the initscript
wants to add stuff i did not add myself.
Alex
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
(x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dnsmasq depends on:
ii dnsmasq-base 2.76-5+b1
ii init-system-helpers 1.48
ii netbase 5.4
dnsmasq recommends no packages.
Versions of packages dnsmasq suggests:
pn resolvconf <none>
-- Configuration Files:
/etc/dnsmasq.conf changed [not included]
/etc/init.d/dnsmasq changed [not included]
-- no debconf information
