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

[dnsmasqyq.xpt at neverbox.com]

Sending again to the group, with added info.

On Mon, Jul 10, 2023 at 12:32 PM john doe wrote:
>
> On 7/10/23 17:20, dnsmasqyq.xpt at neverbox.com wrote:
> > 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
>
> What Debian release are you using and what dnsmasq version do you have?

All latest:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 12 (bookworm)
Release:        12
Codename:       bookworm

$ apt-cache policy dnsmasq
dnsmasq:
  Installed: 2.89-1
  Candidate: 2.89-1
  Version table:
 *** 2.89-1 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
         100 /var/lib/dpkg/status

> I would also file a bugreport against this Debian package.

Sure, but I'd like to rule out that it's because of my own *unusual* use
case, that my network device is not eth0 but br0 instead.

And it turns out to be exactly the root cause --

reverting from br0 to eth0 & reboot, then do the following

sudo apt install -y --reinstall dnsmasq-base dnsmasq

and it finished without any issue, while previously it was just impossible.

Ref, switching my network device from eth0 to br0 is done via following
https://linuxconfig.org/how-to-use-bridged-networking-with-libvirt-and-kvm

I'm now more inclined to think it is dnsmasq's problem, not Debian
packaging's problem. Comments?


> --
> John Doe
>
>
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss