[Dnsmasq-discuss] Dnsmasq-discuss Digest, Vol 234, Issue 2

Wed Nov 6 16:22:02 UTC 2024

On 11/6/24 04:00, dnsmasq-discuss-request at lists.thekelleys.org.uk wrote:

Send Dnsmasq-discuss mailing list submissions to
	dnsmasq-discuss at lists.thekelleys.org.uk

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

or, via email, send a message with subject or body 'help' to
	dnsmasq-discuss-request at lists.thekelleys.org.uk

You can reach the person managing the list at
	dnsmasq-discuss-owner at lists.thekelleys.org.uk

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Dnsmasq-discuss digest..."

Today's Topics:

   1. DNSmasq will not start, failed (Result: protocol) (Paul Kelly)
   2. Re: DNSmasq will not start, failed (Result: protocol)
      (Geert Stappers)
   3. Monthly Posting (Monthly Posting)
   4. Re: DNSmasq will not start, failed (Result: protocol)
      (Neil Darlow)
   5. Re: DNSmasq will not start, failed (Result: protocol)
      (Matus UHLAR - fantomas)

----------------------------------------------------------------------

Message: 1
Date: Tue, 5 Nov 2024 16:13:08 -0800
From: Paul Kelly <pksings at gmail.com> <pksings at gmail.com>
To: dnsmasq-discuss at lists.thekelleys.org.uk
Subject: [Dnsmasq-discuss] DNSmasq will not start, failed (Result:
	protocol)
Message-ID:
	<CAL1e7buRfzsmJL3ZGDUVX5qA=5XzdNw3PpTH_htsjfUJNaieUw at mail.gmail.com>
<CAL1e7buRfzsmJL3ZGDUVX5qA=5XzdNw3PpTH_htsjfUJNaieUw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

$ systemctl start dnsmasq
Failed to start dnsmasq.service: Connection timed out
See system logs and 'systemctl status dnsmasq.service' for details.

$ systemctl status dnsmasq.service
? dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
     Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; preset:
enabled)
     Active: failed (Result: protocol) since Tue 2024-11-05 15:24:46 PST;
44min ago
    Process: 29169 ExecStartPre=/etc/init.d/dnsmasq checkconfig
(code=exited, status=0/SUCCESS)
    Process: 29172 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited,
status=0/SUCCESS)
    Process: 29175 ExecStartPost=/etc/init.d/dnsmasq
systemd-start-resolvconf (code=exited, status=0/SUCCESS)
    Process: 29178 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf
(code=exited, status=0/SUCCESS)
        CPU: 69ms

3 days and numerous searches found 1 hit and it did not offer a solution,
I"m stumped.

Thanks in advance.

Paul Kelly
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20241105/457ee7a2/attachment-0001.htm>
<http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20241105/457ee7a2/attachment-0001.htm>

------------------------------

Message: 2
Date: Wed, 6 Nov 2024 07:13:13 +0100
From: Geert Stappers <stappers at stappers.nl> <stappers at stappers.nl>
To: dnsmasq-discuss at lists.thekelleys.org.uk
Subject: Re: [Dnsmasq-discuss] DNSmasq will not start, failed (Result:
	protocol)
Message-ID: <ZysI+TOorc6cqJiO at gpm.stappers.nl>
<ZysI+TOorc6cqJiO at gpm.stappers.nl>
Content-Type: text/plain; charset=iso-8859-1

On Tue, Nov 05, 2024 at 04:13:08PM -0800, Paul Kelly wrote:

$ systemctl start dnsmasq
Failed to start dnsmasq.service: Connection timed out
See system logs and 'systemctl status dnsmasq.service' for details.

$ systemctl status dnsmasq.service
? dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
     Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled;
preset: enabled)
     Active: failed (Result: protocol) since Tue 2024-11-05 15:24:46
PST; 44min ago
    Process: 29169 ExecStartPre=/etc/init.d/dnsmasq checkconfig
(code=exited, status=0/SUCCESS)
    Process: 29172 ExecStart=/etc/init.d/dnsmasq systemd-exec
(code=exited, status=0/SUCCESS)
    Process: 29175 ExecStartPost=/etc/init.d/dnsmasq
systemd-start-resolvconf (code=exited, status=0/SUCCESS)
    Process: 29178 ExecStop=/etc/init.d/dnsmasq
systemd-stop-resolvconf (code=exited, status=0/SUCCESS)
        CPU: 69ms

3 days and numerous searches found 1 hit and it did not offer a
solution, I"m stumped.

Describe better what is on the system that is supposed to run dnsmasq.

Thanks in advance.

Cheap.   I did read: "I have told you my problem, you must solve it. Do
not expect any further response, I have already said thanks, just fix
my problem".   Less cheap: Leave out "in advance gratitude", remain
owner of the challenge, do further research in parallel of waiting on
response from the community, report progress.

A true "Thanks" will be sharing the solution or a workaround.

Groeten
Geert Stappers

I am a USA grown american and was trying to be polite like my parents
taught me. Sorry to offend you.

offering thanks in advance is a custom, it is saying I am grateful for your
help, I think you misunderstand it, I apologize, I did not know your
customs do not recognize it as such.

I believe that the intent of this list and my post are asking for
suggestions as to how to proceed, thank you all who offered that.

This is a laptop that is used for commercial DJ work and home music
listening. It is Debian 12. Systemd is NOT installed. Resolvconf is not
installed, nor is any other systemd programs.

This is the result of running  ExecStart=/etc/init.d/dnsmasq systemd-exec.

$ ExecStart=/etc/init.d/dnsmasq systemd-exec
bash: systemd-exec: command not found

All network interfaces are DHCP. /etc/resolv.conf is static and immutable.
I have two other systems with this same configuration that are working
fine.  This one stopped working about three weeks ago.

With the exception of DNSmasq this machine is running perfectly and
seemingly healthy.

I just realized that DNSmasq is being started by a systemd process.

I tried manually starting it from CLI as root and it worked.  It is being
initialized incorrectly for this system. Different problem, this one is
resolved.

Thank you, without your input I would have never found it.

This should be closed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20241106/2a4f0b53/attachment.htm>