Re: [Dnsmasq-discuss] dnsmasq.service: Control process exited, code=exited, status=127/n/a
> On Jul 10, 2023, at 3:34 PM, dnsmasqyq@neverbox.com wrote: > > It's my own problem. > > On Mon, Jul 10, 2023 at 3:57 PM Tong Sun wrote: > >> 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 > > Hmm... redid my steps in a clean VM and it works just fine. So, > >> I'm now more inclined to think it is dnsmasq's problem, not Debian >> packaging's problem. Comments? > > It's my own problem. > > Sorry about the noise. > > > ___ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss Were you using a migrated configuration file or a fresh configuration file on the original VM? You might have had a configuration line which was telling dnsmasq to bind to a specific interface and that interface wasn’t available on the system. I think by default, the configuration file in most packages don’t specify an interface to bind to, so dnsmasq will bind to all available interfaces. ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] dnsmasq.service: Control process exited, code=exited, status=127/n/a
It's my own problem. On Mon, Jul 10, 2023 at 3:57 PM Tong Sun wrote: > 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 Hmm... redid my steps in a clean VM and it works just fine. So, > I'm now more inclined to think it is dnsmasq's problem, not Debian > packaging's problem. Comments? It's my own problem. Sorry about the noise. ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] dnsmasq.service: Control process exited, code=exited, status=127/n/a
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@neverbox.com wrote: > > On Mon, Jul 10, 2023 at 11:17 AM Tong Sun > > 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@lists.thekelleys.org.uk > https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] dnsmasq.service: Control process exited, code=exited, status=127/n/a
On 7/10/23 17:20, dnsmasqyq@neverbox.com wrote: On Mon, Jul 10, 2023 at 11:17 AM Tong Sun 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? I would also file a bugreport against this Debian package. -- John Doe ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] dnsmasq.service: Control process exited, code=exited, status=127/n/a
On Mon, Jul 10, 2023 at 11:17 AM Tong Sun 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 > -- > ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] dnsmasq.service: Control process exited, code=exited, status=127/n/a
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 -- 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 -- ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
