On Nov 28, 2008, at 10:19 AM, Philip Prindeville wrote:
Tod Fitch wrote:For AstLinux v0.6.2, I was attempting to setup my box as a firewall/router. Ran into troubles (worry about that later) thenreconfigured as best I could back to having only an EXT_IF with staticIP to resume use as only a Asterisk server. But now the NTP setting does not appear to work. I have the default us.pool.ntp.org server set but the box insists that it is February of 1980. Here is the /etc/ntpd.conf file that is on the box and it looks okay to me....pbx ~ # more /etc/ntpd.conf# Autogenerated. Do not edit. restrict default noquery nopeer notrap nomodify restrict 127.0.0.1 # NTPd server us.pool.ntp.org driftfile /var/db/ntpd.drift# Undisciplined Local Clock. This is a fake driver intended for backup# and when no outside source of synchronized time is available. server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 10 pbx ~ # date Fri Feb 1 12:59:48 PST 1980I don't see ntpdate or the other tools I am used to working with in the path, so am a little bit slow on this. Any ideas? Thanks!Is name service up and running at that point? It might not be able to resolve us.pool.ntp.org ...
It looks like ntpd is dead at the moment. Here are the last /var/log/ messages entries associated with ntp:
Feb 1 01:19:42 pbx daemon.info ntpd[1367]: synchronized to LOCAL(0), stratum 10Feb 1 01:19:42 pbx daemon.notice ntpd[1367]: time slew +0.000000 sFeb 1 01:19:43 pbx daemon.notice ntpd[1371]: ntpd [EMAIL PROTECTED] Wed Nov 26 06:26:44 UTC 2008 (1) Feb 1 01:19:43 pbx daemon.debug ntpd[1373]: signal_no_reset: signal 13 had flags 4000000Feb 1 01:19:43 pbx daemon.info ntpd[1373]: precision = 1.941 usecFeb 1 01:19:43 pbx daemon.debug ntpd[1373]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Feb 1 01:19:43 pbx daemon.info ntpd[1373]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Feb 1 01:19:43 pbx daemon.info ntpd[1373]: Listening on interface #1 lo, 127.0.0.1#123 Enabled Feb 1 01:19:43 pbx daemon.info ntpd[1373]: Listening on interface #2 eth2, 10.7.52.131#123 Enabled Feb 1 01:19:43 pbx daemon.info ntpd[1373]: kernel time sync status 0040 Feb 1 01:22:56 pbx daemon.info ntpd[1373]: synchronized to LOCAL(0), stratum 10 Feb 1 01:22:56 pbx daemon.notice ntpd[1373]: kernel time sync status change 0001 Feb 1 01:24:02 pbx daemon.info ntpd[1373]: synchronized to 64.113.33.2, stratum 2 Feb 1 01:24:02 pbx daemon.err ntpd[1373]: time correction of 909604803 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time.
It looks like ntpd is dead at the moment, which fits with my recollection on what ntpd would do if the jump is too big. It is also my recollection that date does not set things up correctly for ntpd which is why I was looking for ntpdate. And the time server is accessible:
pbx ~ # ps -w | grep ntp 1652 root 1040 S grep ntp pbx ~ # ping us.pool.ntp.org PING us.pool.ntp.org (64.247.17.250): 56 data bytes 64 bytes from 64.247.17.250: seq=1 ttl=48 time=109.185 ms 64 bytes from 64.247.17.250: seq=2 ttl=49 time=102.013 ms 64 bytes from 64.247.17.250: seq=3 ttl=48 time=100.480 ms 64 bytes from 64.247.17.250: seq=4 ttl=49 time=99.754 ms 64 bytes from 64.247.17.250: seq=5 ttl=48 time=99.503 ms
I have manually set the date to be close using the date command and then did a "service ntpd start". Maybe that will be enough to get things going properly.
Thanks for the suggestions!
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
