Unbound.pid error in system log
-
The following errors started popping up in my System Logs:
Aug 22 03:52:01 dhcpleases kqueue error: unkown
Aug 22 03:52:01 dhcpleases Could not deliver signal HUP to process because its pidfile (/var/run/unbound.pid) does not exist, No such process.
Aug 22 03:52:01 dhcpleases /var/etc/hosts changed size from original!However, unbound.pid exists…
ls -lah /var/run/unbound.pid -rw-r--r-- 1 root wheel 6B Aug 22 03:52 /var/run/unbound.pid
cat /var/run/unbound.pid 25713
I am running pfSense 2.3.4.
-
However, unbound.pid exists…
ls -lah /var/run/unbound.pid -rw-r--r-- 1 root wheel 6B Aug 22 03:52 /var/run/unbound.pid
cat /var/run/unbound.pid 25713
I advise you to execute one more cmmand to be sure :
ps 25713
or whatever is the value you find in the file /var/run/unbound.pid.
THis should return something like this :[2.3.4-RELEASE][admin@pfsense.my.system]/root: ps 25713 PID TT STAT TIME COMMAND 11682 - Ss 0:22.62 /usr/local/sbin/unbound -c /var/unbound/unbound.conf
The pid file exists, ok, but what if unbound itself isn't there anymore or has another pid ?
-
Since my original post the value in unbound.pid has changed. I executed the command you suggested with the new value and received the following results.
ps 11204 PID TT STAT TIME COMMAND 11204 - Ss 0:01.93 /usr/local/sbin/unbound -c /var/unbound/unbound.conf
The errors pop up in the log when I save any changes to the DHCP Server settings.
-
As far as I know it's a cosmetic bug in Unbound caused by chrooting it under /var/unbound. There is no real problem.
-
@kpa:
As far as I know it's a cosmetic bug in Unbound caused by chrooting it under /var/unbound. There is no real problem.
Good to know! Thank you!