From: "R." <redag2@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] DHCP server not working after dnsmasq restarts
Date: Wed, 13 Aug 2014 12:07:40 -0400 [thread overview]
Message-ID: <CACj-SW2NK08g1fcLOievbkgtqzmUvL0Wt9pMa9GNvRTFBGbpQA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Woke up today to find a lack of connectivity/ip address. After some
digging through the logs, it looks like the DHCP server was working
within the first few moments of the router booting up, then sort of
died after dnsmasq was restarted.
While my apprentice eyes cannot figure the reason the DHCP server did
not come alive, they did notice that a root-spawned
"/usr/sbin/dnsmasq" process was missing. I suppose that one could
install a watchdog to make sure that this process is alive. Comments?
Attached is the relevant log explaining the situation.
[-- Attachment #2: dnsmasq-dhcp-failure-cerowrt-3.10.50.txt --]
[-- Type: text/plain, Size: 2284 bytes --]
Observation of the bad scenario shows no reference to dnsmasq-dhcp after dnsmasq is restarted.
* added for emphasis.
----
Good scenario:
dnsmasq[2599]: exiting on receipt of SIGTERM
dnsmasq[2938]: started, version 2.71 cachesize 5000
dnsmasq[2938]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC
dnsmasq[2938]: DNSSEC validation enabled
dnsmasq[2938]: DNSSEC signature timestamps not checked until first cache reload
*dnsmasq-dhcp[2938]: DHCP, IP range 172.30.42.130 -- 172.30.42.155, lease time 1d
*dnsmasq-dhcp[2938]: DHCP, IP range 172.30.43.100 -- 172.30.43.164, lease time 1d
*dnsmasq-dhcp[2938]: DHCP, IP range 172.30.42.2 -- 172.30.42.27, lease time 1d
dnsmasq[2938]: using local addresses only for domain home.lan
dnsmasq[2938]: reading /tmp/resolv.conf.auto
dnsmasq[2938]: using local addresses only for domain home.lan
dnsmasq[2938]: using nameserver 66.28.0.45#53
Relevant processes (with context):
2575 root 1180 S /usr/sbin/polipo -c /var/etc/polipo.conf
2938 nobody 2480 S /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf -k --dnssec-no-timecheck
*2941 root 2396 S /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf -k --dnssec-no-timecheck
3315 root 1128 S /usr/sbin/miniupnpd -f /var/etc/miniupnpd.conf
14381 root 0 SW [kworker/u2:1]
---
Bad scenario:
dnsmasq[2605]: exiting on receipt of SIGTERM
dnsmasq[2985]: started, version 2.71 cachesize 5000
dnsmasq[2985]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC
dnsmasq[2985]: DNSSEC validation enabled
dnsmasq[2985]: DNSSEC signature timestamps not checked until first cache reload
dnsmasq[2985]: using local addresses only for domain home.lan
dnsmasq[2985]: reading /tmp/resolv.conf.auto
dnsmasq[2985]: using local addresses only for domain home.lan
dnsmasq[2985]: using nameserver 66.28.0.45#53
Relevant processes (with context):
2581 root 1180 S /usr/sbin/polipo -c /var/etc/polipo.conf
2985 nobody 2404 S /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf -k --dnssec-no-timecheck
3192 root 1128 S /usr/sbin/miniupnpd -f /var/etc/miniupnpd.conf
5599 root 0 SW [kworker/u2:1]
next reply other threads:[~2014-08-13 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 16:07 R. [this message]
2014-08-13 16:15 ` David Personette
2014-08-13 16:33 ` R.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACj-SW2NK08g1fcLOievbkgtqzmUvL0Wt9pMa9GNvRTFBGbpQA@mail.gmail.com \
--to=redag2@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox