[Dnsmasq-discuss] dnsmasq.service: Control process exited, code=exited, status=127/n/a

[dnsmasqyq.xpt at neverbox.com]

On Mon, Jul 10, 2023 at 11:17 AM Tong Sun <dnsmasqyq.xpt at neverbox.com> wrote:
>
> Hi, I'm installing in Debian the normal way with
>
> sudo apt install -y dnsmasq
>
> and it fails out of the box with:
>
> ------------------------------
> Created symlink /etc/systemd/system/multi-user.target.wants/dnsmasq.service -> /lib/systemd/system/dnsmasq.service.
> Job for dnsmasq.service failed because the control process exited with error code.
> See "systemctl status dnsmasq.service" and "journalctl -xeu dnsmasq.service" for details.
> invoke-rc.d: initscript dnsmasq, action "start" failed.
> x dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
>      Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; preset: enabled)
>      Active: failed (Result: exit-code) since Mon 2023-07-10 10:52:02 EDT; 14ms ago
>     Process: 506097 ExecStartPre=/etc/init.d/dnsmasq checkconfig (code=exited, status=127)
>         CPU: 14ms
>
> Jul 10 10:52:02 coral systemd[1]: Starting dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server...
> Jul 10 10:52:02 coral systemd[1]: dnsmasq.service: Control process exited, code=exited, status=127/n/a
> Jul 10 10:52:02 coral systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
> Jul 10 10:52:02 coral systemd[1]: Failed to start dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server.
> ------------------------------
>
> What could be wrong? Here is more info:
>
> ------------------------------
> % journalctl -u dnsmasq.service -n 100 --no-hostname --no-pager
> Jul 10 10:52:02 systemd[1]: Starting dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server...
> Jul 10 10:52:02 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=127/n/a
> Jul 10 10:52:02 systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
> Jul 10 10:52:02 systemd[1]: Failed to start dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server.
>
> % sudo netstat -tnlp | grep :53 | wc
>       0       0       0
> ------------------------------

Oh, forgot to mention that I don't have systemd-resolved:

% systemctl status systemd-resolved.service
Unit systemd-resolved.service could not be found.

% systemctl status systemd-resolved
Unit systemd-resolved.service could not be found.


> Is it that my network device is not eth0 but br0 instead?
>
> ------------------------------
> % ip route
> default via 192.168.0.1 dev br0 onlink
> 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
> 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.102
>  ------------------------------
>