Could not deliver signal HUP to process because its pidfile doesn't exist
-
in my DHCP system log I see this on startup
Apr 21 14:09:37 dhcplease Sending HUP signal to dns daemon(49953) Apr 21 14:09:37 dhcpleases Sending HUP signal to dns daemon(49953) Apr 21 14:09:41 dhcpleases /etc/hosts changed size from original! Apr 21 14:09:41 dhcpleases Sending HUP signal to dns daemon(49953) Apr 21 14:09:41 dhcpleases Could not deliver signal HUP to process because its pidfile (/var/run/unbound.pid) does not exist, No such process. Apr 21 14:09:41 dhcpleases kqueue error: unkown Apr 21 14:09:41 dhcpleases Sending HUP signal to dns daemon(68711)1st I suspect thats a type in an error message (unkown) should be unknown
2nd Where do I start with cleaning this up? isn't a hup signal an interprocess message? so dchpleases is communicating to unbound and failing?I didn't notice anything interesting in by DNS Resolver (unbound) log
-
This error goes away when I remove the checkmark from DHCP registration in DNS Resolver. Comes back when I re-check it.
-
Found a reference that this may just be a cosmetic bug. I will ignore it unless issues come up.
-
Found a reference that this may just be a cosmetic bug. I will ignore it unless issues come up.
That's what I thought as well.
-
i have a new test install with nothing but DHCP and unbound configured for DHCP forwarding.
I initially tried changing the etc/inc/services.inc
/* If unbound is still running, wait up to 30 seconds for it to terminate. */
for ($i=1; $i <= 30; $i++) {to 60sec but that did not solve.
I can confirm, checking/unchecking the checkbox
"DHCP Registration - Register DHCP leases in the DNS Resolver"
causes the error to appear/disappear. -
@gwaitsi said in Could not deliver signal HUP to process because its pidfile doesn't exist:
unbound configured for DHCP forwarding.
Huh?
-
@johnpoz "dhcpleases kqueue error: unkown"
@jimp there is a bug listed from Jim for 2.5 which seems to be the same as with 2.4.4_p2
https://redmine.pfsense.org/issues/9383it appears on a vanilla install with only DHCP / DNS Resolver turned on on 2.4.4_p2
"DNS Query Forwarding" - Enable/Disabled - makes no difference to the error
"Register DHCP static mappings in the DNS Resolver" - Enable/Disabled - makes no difference to the error
the trigger for the error is "Register DHCP leases in the DNS Resolver"
- checked error occurs, unchecked no error
Error first appears immediately after boot and any time unbound is re-started
In 2.3.4 there was the same error, but for a different reason. But this can be ignored.
https://redmine.pfsense.org/attachments/2097/unbound-stop.diff
