>Hey,
>
>I just noticed that since I upgraded to 0.7.2, that ntpd doesn't work.
>
>I rebooted a phone, and saw that it wasn't able to pull the time. I 
>checked on the box, and saw ntpd wasn't running. Originally I 
>thought it just crashed (which has happened in the past), but I 
>tried restarting the daemon and it error'd out. Even after a reboot 
>(which has occurred three times) I still have the same problem:
>
>/var/log/messages.0:Dec 31 19:01:31 voip daemon.notice ntpd[2705]: 
>ntpd <mailto:[email protected]>[email protected] Thu May 13 00:20:20 UTC 
>2010 (1)
>/var/log/messages.0:Dec 31 19:01:31 voip daemon.debug ntpd[2705]: 
>signal_no_reset: signal 13 had flags 4000000
>/var/log/messages.0:Dec 31 19:01:31 voip daemon.info ntpd[2705]: 
>precision = 1.018 usec
>/var/log/messages.0:Dec 31 19:01:31 voip daemon.debug ntpd[2705]: 
>ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
>/var/log/messages.0:Dec 31 19:01:31 voip daemon.info ntpd[2705]: 
>Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
>/var/log/messages.0:Dec 31 19:01:31 voip daemon.err ntpd[2705]: 
>unable to bind to wildcard socket address :: - another process may 
>be running - EXITING
>
>It can neither query the server for the time to set itself, nor bind 
>to the port to listen for queries itself.
>
>At first I assumed, based on those logs, that something else was 
>listening on port 123, and ntpd couldn't bind to it. But netstat 
>showed that it was not the case. I know it was running perfectly 
>fine before, though I can't say for sure that it never worked with 
>0.7.2, though I upgraded to it recently, and I don't remember for a 
>fact if it ever ran since that point.
>
>Knowing that it did work prior to the upgrade, I copied over an 
>older version of ntpd, and that works fine. The version bundled with 
>0.7.2 is 4.2.4p8, and the version that does work is 4.2.4p7.
>With the older version:
>/var/log/messages:Jun 25 21:47:07 voip daemon.notice ntpd[7286]: 
>ntpd <mailto:[email protected]>[email protected] Tue Apr 20 15:33:00 UTC 
>2010 (1)
>/var/log/messages:Jun 25 21:47:07 voip daemon.debug ntpd[7286]: 
>signal_no_reset: signal 13 had flags 4000000
>/var/log/messages:Jun 25 21:47:07 voip daemon.info ntpd[7286]: 
>precision = 1.018 usec
>/var/log/messages:Jun 25 21:47:07 voip daemon.debug ntpd[7286]: 
>ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
>/var/log/messages:Jun 25 21:47:07 voip daemon.info ntpd[7286]: 
>Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
>/var/log/messages:Jun 25 21:47:07 voip daemon.info ntpd[7286]: 
>Listening on interface #1 lo, 127.0.0.1#123 Enabled
>/var/log/messages:Jun 25 21:47:07 voip daemon.info ntpd[7286]: 
>Listening on interface #2 eth0, 174.58.33.164#123 Enabled
>/var/log/messages:Jun 25 21:47:07 voip daemon.info ntpd[7286]: 
>Listening on interface #3 eth1, 172.20.0.1#123 Enabled
>/var/log/messages:Jun 25 21:47:07 voip daemon.info ntpd[7286]: 
>Listening on interface #4 eth2.30, 172.30.0.1#123 Enabled
>/var/log/messages:Jun 25 21:47:07 voip daemon.info ntpd[7286]: 
>Listening on interface #5 tun0, 172.21.0.1#123 Enabled
>/var/log/messages:Jun 25 21:47:07 voip daemon.info ntpd[7286]: 
>Listening on interface #6 tun2, 172.22.0.5#123 Enabled
>/var/log/messages:Jun 25 21:47:07 voip daemon.info ntpd[7286]: 
>kernel time sync status 0040
>
>Very weird... I've messed around with things trying to figure out 
>why it's broken, but for the life of me can't.
>
>Anyone else have any issues with ntpd 4.2.4p8 and 0.7.2 on a Via system?
>
>Thanks.
>
>-James

Have you also tried the newest version 4.2.6p1?
http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/ntp-4.2/NEWS

I just tried it and it works fine on my Alix.
But I also had ntp problems in the past with some geni586-images on 
old Pentium III hardware.

Jun 26 12:05:32 alix daemon.notice ntpd[2447]: ntpd [email protected] 
Sat Jun 26 10:02:00 UTC 2010 (1)
Jun 26 12:05:32 alix daemon.debug ntpd[2447]: signal_no_reset: signal 
13 had flags 4000000
Jun 26 12:05:32 alix daemon.notice ntpd[2447]: proto: precision = 1.771 usec
Jun 26 12:05:32 alix daemon.debug ntpd[2447]: ntp_io: estimated max 
descriptors: 1024, initial socket boundary: 16
Jun 26 12:05:32 alix daemon.info ntpd[2447]: Listen and drop on 0 
v4wildcard 0.0.0.0 UDP 123
Jun 26 12:05:32 alix daemon.info ntpd[2447]: Listen normally on 1 lo 
127.0.0.1 UDP 123
Jun 26 12:05:32 alix daemon.info ntpd[2447]: Listen normally on 2 
eth0 192.168.xx.xx UDP 123
Jun 26 12:05:32 alix daemon.info ntpd[2447]: Listen normally on 3 
eth1 192.168.xx.xx UDP 123
Jun 26 12:05:32 alix daemon.info ntpd[2447]: Listening on routing 
socket on fd #20 for interface updates
Jun 26 12:05:34 alix daemon.notice ntpd[2447]: ntpd: time slew +0.000000 s
Jun 26 12:05:35 alix daemon.notice ntpd[2454]: ntpd [email protected] 
Sat Jun 26 10:02:00 UTC 2010 (1)
Jun 26 12:05:35 alix daemon.debug ntpd[2456]: signal_no_reset: signal 
13 had flags 4000000
Jun 26 12:05:36 alix daemon.notice ntpd[2456]: proto: precision = 1.799 usec
Jun 26 12:05:36 alix daemon.debug ntpd[2456]: ntp_io: estimated max 
descriptors: 1024, initial socket boundary: 16
Jun 26 12:05:36 alix daemon.info ntpd[2456]: Listen and drop on 0 
v4wildcard 0.0.0.0 UDP 123
Jun 26 12:05:36 alix daemon.info ntpd[2456]: Listen normally on 1 lo 
127.0.0.1 UDP 123
Jun 26 12:05:36 alix daemon.info ntpd[2456]: Listen normally on 2 
eth0 192.168.xx.xx UDP 123
Jun 26 12:05:36 alix daemon.info ntpd[2456]: Listen normally on 3 
eth1 192.168.xx.xx UDP 123
Jun 26 12:05:36 alix daemon.info ntpd[2456]: Listening on routing 
socket on fd #20 for interface updates

Michael

http://www.mksolutions.info

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
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].

Reply via email to