Lonnie, I tried using the -4 and -6 parameter with both the old and new version of ntpd. Neither seem to be affected in any way. Even if I use -6 on the old (and working) version, it does not attempt to listen on ::. Which makes me think it wasn't compiled with ipv6 support. And the new (non working) version will always attempt to use :: even if I use -4 (which is the default in the init script) and crash saying it can't bind to it.
But to the last comment, I don't think ipv6 support in ntp is required for ipv6 dns queries. I was able to do those even when ntpd was not running and I didn't even know it. Or did you mean ipv6 ntp queries? -James On 06/26/2010 12:42 PM, Lonnie Abelbeck wrote: > James, > > If you have IPV6=yes, you could try hacking /etc/init.d/ntpd and add > > if [ "$IPV6" != "yes" ]; then > NTPAF="-4" > + else > + NTPAF="-6" > fi > > OR, since ntpd is not running, try from the CLI for a test > > $ ntpd -6 -g -q -c /etc/ntpd.conf > > This will force IPv6 DNS lookups, may be worth a shot. > > Lonnie > > > On Jun 26, 2010, at 9:59 AM, James Babiak wrote: > > >> Guy, >> >> Thanks! I think you may have found out exactly what the problem is. I do in >> fact have ipv6 enabled in the kernel, and my problem is identical to that. >> >> You know it's funny, because when I first saw that error message, I noticed >> the :: indicating ipv6, so thought maybe there was an issue with it not able >> to bind because of something else listening on that socket, but never >> thought about the fact that enabling ipv6 in and of itself could have caused >> the problem. >> >> I'm really curious why 4.2.4p7 works with ipv6 and 4.2.4p8 doesn't. Lonnie >> mentioned something about a 'HIGH' security fix being the difference, so I >> wonder if it's related... >> >> But that does kind of put me between a rock and a hard place. I want ntpd >> running obviously, but I also want to enable ipv6. Based on your link Guy, >> it seems like there is a way to compile the newer ntpd version without ipv6 >> support. I guess I can try that, and maybe it should be done like that for >> the official release version if astlinux plans on officially supporting ipv6 >> in the future. >> >> Though since :123 isn't reachable from the Wan, and I'm not as concerned >> about it on the Lan, I guess I can also just run the older version for the >> time being. >> >> I'll have to mess around with it later. The ipv6 module is in use, so I >> can't remove it with the system up, so I'll have to try removing it for the >> next reboot and see what happens. But I'm pretty convinced that it's the >> answer. >> >> Thanks!!! >> >> -James >> >> On 06/26/2010 10:16 AM, Guy Neale wrote: >> >>> If you've been playing with IPV6 then this looks suspiciously similar. >>> >>> http://www.mail-archive.com/[email protected]/msg23669.html >>> >>> Guy >>> >>> On 26/06/2010, at 11:39 PM, Guy Neale wrote: >>> >>> >>>> ntpd is running ok on my VIA EPIA MII-Series (C3 Processor) >>>> >>>> ps >>>> 2516 root 1156 S ntpd -4 -c /etc/ntpd.conf >>>> >>>> ntpd -? >>>> ntpd - NTP daemon program - Ver. 4.2.4p8 >>>> >>>> Guy >>>> >>>> On 26/06/2010, at 9:52 PM, Lonnie Abelbeck wrote: >>>> >>>> >>>>> James, >>>>> >>>>> This is weird, indeed... >>>>> >>>>> ntpd 4.2.4p7 -> 4.2.4p8 was just a (Severity: HIGH) security fix. >>>>> >>>>> I haven't seen any ntpd problems, but I don't have a 'via' box. >>>>> >>>>> Did you build this yourself, or from the repository? >>>>> >>>>> Michael mentioned to try 4.2.6p1, but so far the 4.2.6 series has an >>>>> issue for us, we first do (equivalent to the retired ntpdate) >>>>> $ ntpd -g -q -c /etc/ntpd.conf >>>>> >>>>> to reset the clock in one big step, but in 4.2.6 (4.2.6p1 appears to be >>>>> the same per Michael's log) >>>>> >>>>> Jun 26 12:05:34 alix daemon.notice ntpd[2447]: ntpd: time slew +0.000000 s >>>>> >>>>> the clock is not immediately slew'ed as 4.2.4 does, which is a problem >>>>> for us. >>>>> >>>>> >>>>> In 0.7.2 try the new command >>>>> $ show-union >>>>> >>>>> without arguments shows the contents of the ASTURW unionfs overlay (minus >>>>> the sounds and kd), the list should be fairly short, maybe some old edit >>>>> is causing a problem. >>>>> >>>>> Lonnie >>>>> >>>>> >>>>> On Jun 25, 2010, at 11:17 PM, James Babiak wrote: >>>>> >>>>> >>>>>> 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 >>>>>> [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 >>>>>> [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 >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> 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]. >>>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> 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]. >>>>> >>>>> >>>>> >>>> >>> >>> ------------------------------------------------------------------------------ >>> 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]. >>> >> ------------------------------------------------------------------------------ >> 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]. >> > > ------------------------------------------------------------------------------ > 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]. > ------------------------------------------------------------------------------ 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].
