NTPD core dumped
-
kernel: pid 75967 (ntpd), uid 0: exited on signal 11 (core dumped)
On half of my pfsenses with 2.1 ntpd will core dump.
2.1-BETA1 (amd64)
built on Tue May 7 05:04:17 EDT 2013I changed settings from unassigned to LAN but this didn't resolve it.
4 of 5 pfsenses from my test environment had this, too, but is fixed after assigning lan interface.
-
Same issue here.
kernel: pid 35663 (ntpd), uid 0: exited on signal 11 (core dumped)
I don't know, but i think it has to do with OpenVPN.
-
Ya, I have seen that several times.
FWIW, I also have OpenVPN configured.
-
We've seen that now and then but haven't found a 100% fix for it. It seems to happen when rc.newwanip resets NTPD after an IP address change or interface up or down event.
-
Don't know if it helps, but if NTP service is down, the only way to bring it back is:
Go to: Services - NTP - Save button. -
Sometimes I've seen ntp not start after OPT1 (3G) goes down. Could it be that the process doesn't exit completely before a new instance is spawned? I run Snort on my system which takes a good minute or so to fully load and while it's loading, it uses 100% CPU on one core.
Is a dump file actually written when ntp dies/fails to restart? Would that help out in figuring out the reason.
-
We've seen that now and then but haven't found a 100% fix for it. It seems to happen when rc.newwanip resets NTPD after an IP address change or interface up or down event.
maybe this will help:
-U number, --updateinterval=number interval in seconds between scans for new or dropped interfaces. This option takes an integer number as its argument. Give the time in seconds between two scans for new or dropped interfaces. For systems with routing socket support the scans will be performed shortly after the interface change has been detected by the system. Use 0 to disable scanning. 60 seconds is the minimum time between scans.
