Pardon my noobiness; I meant to say that instances of "dnsmasq-dhcp" in the log were present before dnsmasq was terminated, but no longer were after dnsmasq came alive. This usually does not happen on a "good boot". Included full logs now, about 10 minute of usage for each scenario. On Wed, Aug 13, 2014 at 12:15 PM, David Personette wrote: > Well, dnsmasq is the DHCP server. As for why it didn't restart, without > logs, I'm not sure that we can help... > > -- > David P. > > > On Wed, Aug 13, 2014 at 12:07 PM, R. wrote: >> >> 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. >> >> _______________________________________________ >> Cerowrt-devel mailing list >> Cerowrt-devel@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/cerowrt-devel >> >