Upgrade to 2.1 ntpd service have to manually start each time now.
-
My previous post is a bit ambiguous, maybe even wrong. When running it by hand I meant running ntpd as-is with no arguments. That, as I now found out on the working box, is not how it's run from the GUI.
so then I ran
/usr/local/bin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pidwhich is how it's run from the GUI, and sure enough it did crash. So then next step I wanted it to not fork, so I can maybe catch more output. I ran it like this```
/usr/local/bin/ntpd -n -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pidI'm not sure what to make of this. Is there anyway I can help the devs in figuring this one out. I'm a dev myself. Thanks, Miki -
hi
I have the same problem with ntp
kernel: pid 71748 (ntpd), uid 0: exited on signal 11 (core dumped)
I upgraded from 2.0.3 to 2.1 (amd64) on physical machine with Xeon X3430 @ 2.40GHz 4GB
The only solution on my system is go to System > Generel Setup > Click on 'Save' After this the NTPd starts automatically and peers are present under Status > NTP
My System log: (this happens every morning after periodic reset)
Jan 21 01:00:18 kernel: pid 25498 (ntpd), uid 0: exited on signal 11 (core dumped)
Jan 21 01:00:16 check_reload_status: Reloading filter
Jan 21 01:00:16 check_reload_status: Starting packages
Jan 21 01:00:16 php: rc.newwanip: pfSense package system has detected an ip change x.x.x.179 -> x.x.x.179 … Restarting packages.
Jan 21 01:00:14 php: rc.newwanip: Creating rrd update script
Jan 21 01:00:14 php: rc.newwanip: Resyncing OpenVPN instances for interface WAN1.
Jan 21 01:00:09 php: rc.newwanip: Removing static route for monitor 8.8.4.4 and adding a new route through x.x.x.x
Jan 21 01:00:09 php: rc.newwanip: Removing static route for monitor 8.8.8.8 and adding a new route through x.x.x.x