[FS#464] Syslog dnsmasq errors, where dnsmasq thinks it is running as pid 1 (procd) when using ujail/seccomp

LEDE Bugs lede-bugs at lists.infradead.org
Tue Feb 7 03:28:40 PST 2017


The following task has a new comment added:

FS#464 - Syslog dnsmasq errors, where dnsmasq thinks it is running as pid 1 (procd) when using ujail/seccomp
User who did this - Kevin Darbyshire-Bryant (kdarbyshirebryant)

----------
OK, another theory, but this one's a corker and fits with available facts.  Looking through the logfile it's a more a case of what's missing rather than what's present.... normally dnsmasq starts with 'dnssec timestamp checks' disabled and waits for a -SIGHUP (via procd) caused by a hotplug/ntpd script signalling time is now valid.

The logfile shows dnsmasq starting in 'no timestamp mode' but it never gets the signal that timestamps are valid (via the SIGHUP) even though ntpd has gone through it's 'time is valid' hotplug script.  I suspect procd is signalling the procd jailer, rather than the procd jailee.  And procd jailer responds to sighup by closing shop as it should.

No idea how to fix...but that's what I think is going on.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=464#comment1642



More information about the lede-bugs mailing list