When i recently updated my yunohost installation i am unable to start the DNSMASQ and get the following error
Error: "500"
Action: "PUT" /yunohost/api/services/dnsmasq/start
Error message:
Could not start the service ‘dnsmasq’
Recent service logs:-- Logs begin at Wed 2022-08-17 22:02:11 UTC, end at Wed 2022-08-17 22:03:42 UTC. – – No entries –
Possibly cp /etc/init.d/dnsmasq.dpkg-dist /etc/init.d/dnsmasq (and restarting the service) may fix the issue, though not 100% sure …
Hmokay then let’s look at systemctl start dnsmasq and systemctl status dnsmasq | cat, hopefully there’ll be some proper error message in there…
Mokay then let’s look at
yunohost tools regen-conf dnsmasq --dry-run --with-diff
and
head -n 15 /etc/dnsmasq.conf
I have tried that and it still doesnt start 
This is the log from the admin console
LOGFILE: journalctl
– Logs begin at Fri 2022-08-19 06:02:25 UTC, end at Fri 2022-08-19 15:47:58 UTC. –
Aug 19 15:16:49 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server…
Aug 19 15:16:49 dnsmasq[739]: dnsmasq: syntax check OK.
Aug 19 15:16:49 dnsmasq[741]: dnsmasq: illegal repeated keyword at line 10 of /etc/dnsmasq.conf
Aug 19 15:16:49 dnsmasq[741]: illegal repeated keyword at line 10 of /etc/dnsmasq.conf
Aug 19 15:16:49 dnsmasq[741]: FAILED to start up
Aug 19 15:16:49 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=1/FAILURE
Aug 19 15:16:49 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’.
Aug 19 15:16:49 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
Aug 19 15:18:22 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server…
Aug 19 15:18:22 dnsmasq[782]: dnsmasq: syntax check OK.
Aug 19 15:18:22 dnsmasq[783]: dnsmasq: illegal repeated keyword at line 10 of /etc/dnsmasq.conf
Aug 19 15:18:22 dnsmasq[783]: illegal repeated keyword at line 10 of /etc/dnsmasq.conf
Aug 19 15:18:22 dnsmasq[783]: FAILED to start up
Aug 19 15:18:22 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=1/FAILURE
Aug 19 15:18:22 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’.
Aug 19 15:18:22 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
Aug 19 15:22:18 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server…
Aug 19 15:22:18 dnsmasq[949]: dnsmasq: syntax check OK.
Aug 19 15:22:18 dnsmasq[951]: dnsmasq: illegal repeated keyword at line 10 of /etc/dnsmasq.conf
Aug 19 15:22:18 dnsmasq[951]: illegal repeated keyword at line 10 of /etc/dnsmasq.conf
Aug 19 15:22:18 dnsmasq[951]: FAILED to start up
Aug 19 15:22:18 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=1/FAILURE
Aug 19 15:22:18 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’.
Aug 19 15:22:18 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
… Yes the command do not produce any effect by themselves … The point was to share the output to investigate and try to understand why dnsmasq is broken …
My apologies i wasnt aware of that. I have added the output here:
admin@kilomail:~$ sudo yunohost tools regen-conf dnsmasq --dry-run --with-diff
Warning: /usr/share/yunohost/helpers.d/apt: line 400: syntax error near unexpected token `do'
Warning: /usr/share/yunohost/helpers.d/apt: line 400: ` do'
Warning: The configuration file '/etc/dnsmasq.d/01-pihole.conf' has been manually modified and will not be updated
dnsmasq:
applied:
/etc/resolv.dnsmasq.conf:
diff: @@ -1,20 +1,20 @@
+nameserver 89.234.141.66
+nameserver 2001:1608:10:25::1c04:b12f
+nameserver 2001:1608:10:25::9249:d69b
+nameserver 185.233.100.101
+nameserver 84.200.70.40
+nameserver 195.160.173.53
+nameserver 80.67.169.40
+nameserver 84.200.69.80
+nameserver 194.150.168.168
+nameserver 91.239.100.100
nameserver 2a0c:e300::100
-nameserver 194.150.168.168
nameserver 2a01:3a0:53:53::
+nameserver 2001:910:800::40
+nameserver 2a00:5881:8100:1000::3
+nameserver 2001:67c:28a4::
+nameserver 185.233.100.100
+nameserver 2001:910:800::12
+nameserver 89.233.43.71
+nameserver 2a0c:e300::101
nameserver 80.67.169.12
-nameserver 2001:1608:10:25::9249:d69b
-nameserver 84.200.69.80
-nameserver 195.160.173.53
-nameserver 91.239.100.100
-nameserver 2001:1608:10:25::1c04:b12f
-nameserver 2001:910:800::12
-nameserver 2001:67c:28a4::
-nameserver 2a00:5881:8100:1000::3
-nameserver 84.200.70.40
-nameserver 2a0c:e300::101
-nameserver 2001:910:800::40
-nameserver 89.234.141.66
-nameserver 80.67.169.40
-nameserver 185.233.100.101
-nameserver 89.233.43.71
-nameserver 185.233.100.100
status: updated
pending:
/etc/dnsmasq.d/01-pihole.conf:
diff: @@ -1,47 +0,0 @@
-# Pi-hole: A black hole for Internet advertisements
-# (c) 2015, 2016 by Jacob Salmela
-# Network-wide ad blocking via your Raspberry Pi
-# http://pi-hole.net
-# dnsmasq config for Pi-hole
-#
-# Pi-hole is free software: you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation, either version 2 of the License, or
-# (at your option) any later version.
-
-###############################################################################
-# FILE AUTOMATICALLY POPULATED BY PI-HOLE INSTALL/UPDATE PROCEDURE. #
-# ANY CHANGES MADE TO THIS FILE AFTER INSTALL WILL BE LOST ON THE NEXT UPDATE #
-# #
-# IF YOU WISH TO CHANGE THE UPSTREAM SERVERS, CHANGE THEM IN: #
-# /etc/pihole/setupVars.conf #
-# #
-# ANY OTHER CHANGES SHOULD BE MADE IN A SEPERATE CONFIG FILE #
-# OR IN /etc/dnsmasq.conf #
-###############################################################################
-
-addn-hosts=/etc/pihole/gravity.list
-addn-hosts=/etc/pihole/black.list
-addn-hosts=/etc/pihole/local.list
-
-
-localise-queries
-
-
-#no-resolv
-
-
-
-cache-size=10000
-
-#log-queries=extra
-log-facility=/var/log/pihole.log
-
-local-ttl=2
-
-log-async
-server=8.8.8.8
-server=8.8.4.4
-domain-needed
-bogus-priv
-interface=eth0
status: modified
And the other command
admin@kilomail:~$ sudo head -n 15 /etc/dnsmasq.conf
domain-needed
expand-hosts
localise-queries
interface=lo
resolv-file=/etc/resolv.dnsmasq.conf
Hmf yeah I don’t know what the hell is happening, maybe that’s pihole fucking up the dnsmasq config …
i did try removing pihole the other say because i read someone had adguard installed and it fucked up their DNSMASQ but it still doesnt work even after i tried removing it.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.