Re: ntpd problems after port updates
On 23.04.2012 14:52, Dean E. Weimer wrote: On 23.04.2012 14:10, Chuck Swiger wrote: On Apr 23, 2012, at 12:08 PM, Dean E. Weimer wrote: Tried rebuilding without the with SSL option set, oddly it started once after that, but a restart caused same behavior. gdb doesn't give me anything that I know how to interpret, gdb -c /ntpd.core. (I haven't really used gdb before, so if I am not doing something correctly with it, please feel free to let me know) Ah, you need to build ntpd with -g in CFLAGS LDFLAGS for debugging symbols to be present at the risk of sounding like an complete n00b, how do I do that? After reading through the make man page, I decided on trying to build the port with make CFLAGS+=-g LDFLAGS+=-g install clean however I still get the no debugging symbols found message. Does the information in in the Makefile for the port overwrite this option from the command line? Or am I just using the incorrect syntax here? (gdb) file /usr/local/bin/ntpd Reading symbols from /usr/local/bin/ntpd...(no debugging symbols found)...done. Even more odd, I decided to go ahead and try a couple more systems, as this was working fine on my test system and one production system before I got to the one that broke. I now have it running on 4 production systems and 1 test system. The problem is on 2 production systems one with the openssl option one without, both these systems are running on identical hardware (Dell PowerEdge R310 purchased on same order). The other two production systems are both totally different hardware wise, one is virtual on an ESX4 server, the other is on a custom built machine. The first of which had the problem I did a fresh make buildworld and install last night as well as a rebuild of all ports. Problem still persists. I am not sure what it is about these servers that's causing the problem, all other applications are running fine the configurations on these systems are all very similar, almost all the same ports installed. One of the systems has a few more ports installed as its has more web based applications, but the virtual production server has the same ports installed, built with the same /etc/make.conf and /etc/src.conf options against the same /var/db/ports/ directory so they ports were installed with the same settings, only difference is the run time configuration, however the ntpd configuration is the same on all systems. I have also discovered since the last email that the -d option isn't necessary to keep it running, the -n option which keeps it from detaching from the session will work as well. I worked around the issue for now by manually running it with daemon and adding the -n so its detached and running. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntpd problems after port updates
On Apr 23, 2012, at 11:13 AM, Dean E. Weimer wrote: I am running NTPD built from ports on system that has had world rebuilt without ntp. After doing some port updates this morning to the latest OpenSSL which caused ntp to rebuild as its built against the OpenSSL port. ntpd now core dumps at start, in order to attempt and resolve the issue I tried starting ntpd with the -d switch added, at which point it loads fine without any problems. If you run 'ldd /usr/local/bin/ntpd', that might be informative. Only option checked when doing make config on the port is the with OpenSSL option. Consider not doing this-- OpenSSL has a much worse security history than ntpd itself does. In particular, the ASN.1 parser is infamous for trouble, such as CVE-2012-2110. if I execute: /usr/local/bin/ntpd -p /var/run/ntpd.pid The result is a signal 11 core dump. Run gdb against ntpd and the coredump you've gotten to see the crash backtrace. Or run ntpd under gdb. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntpd problems after port updates
On 23.04.2012 13:19, Chuck Swiger wrote: On Apr 23, 2012, at 11:13 AM, Dean E. Weimer wrote: I am running NTPD built from ports on system that has had world rebuilt without ntp. After doing some port updates this morning to the latest OpenSSL which caused ntp to rebuild as its built against the OpenSSL port. ntpd now core dumps at start, in order to attempt and resolve the issue I tried starting ntpd with the -d switch added, at which point it loads fine without any problems. If you run 'ldd /usr/local/bin/ntpd', that might be informative. Only option checked when doing make config on the port is the with OpenSSL option. Consider not doing this-- OpenSSL has a much worse security history than ntpd itself does. In particular, the ASN.1 parser is infamous for trouble, such as CVE-2012-2110. if I execute: /usr/local/bin/ntpd -p /var/run/ntpd.pid The result is a signal 11 core dump. Run gdb against ntpd and the coredump you've gotten to see the crash backtrace. Or run ntpd under gdb. Tried rebuilding without the with SSL option set, oddly it started once after that, but a restart caused same behavior. gdb doesn't give me anything that I know how to interpret, gdb -c /ntpd.core. (I haven't really used gdb before, so if I am not doing something correctly with it, please feel free to let me know) GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd. Core was generated by `ntpd'. Program terminated with signal 11, Segmentation fault. #0 0x0008006878c0 in ?? () (gdb) bt #0 0x0008006878c0 in ?? () #1 0x0c78 in ?? () #2 0x0008006bf800 in ?? () #3 0x7fff0001 in ?? () #4 0x000800687836 in ?? () #5 0x7fffcb60 in ?? () #6 0x7fffcb48 in ?? () #7 0x0066 in ?? () #8 0x00080142b570 in ?? () #9 0x7fffcf80 in ?? () #10 0x0003 in ?? () #11 0x7fffcfc0 in ?? () #12 0x00080166037f in ?? () #13 0x7fffcd70 in ?? () #14 0x0008006bf800 in ?? () [..snip..] #532 0x0008 in ?? () #533 0x in ?? () #534 0x0009 in ?? () #535 0x004040d0 in ?? () #536 0x0007 in ?? () #537 0x00080067f000 in ?? () #538 0x000f in ?? () #539 signal handler called #540 0x in ?? () Previous frame inner to this frame (corrupt stack?) Running from within gdb didn't give me much either. proxy1# gdb GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd. (gdb) set args -c /etc/ntp.conf (gdb) file /usr/local/bin/ntpd Reading symbols from /usr/local/bin/ntpd...(no debugging symbols found)...done. (gdb) run Starting program: /usr/local/bin/ntpd -c /etc/ntp.conf (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100873] (no debugging symbols found)...[New Thread 801c07400 (LWP 100873/ntpd)] Program exited normally. (gdb) quit proxy1# tail -f /var/log/messages [..snip..] Apr 23 13:55:43 proxy1 ntpd[95834]: ntpd 4.2.6p5@1.2349 Mon Apr 23 18:23:07 UTC 2012 (1) Apr 23 13:55:43 proxy1 ntpd[95836]: proto: precision = 0.699 usec Apr 23 13:55:43 proxy1 kernel: pid 95836 (ntpd), uid 0: exited on signal 5 (core dumped) However it seems to have made it farther before crashing. gdb -c /ntpd.core [..snip..] #832 0x0005 in ?? () #833 0x0008 in ?? () #834 0x0006 in ?? () #835 0x1000 in ?? () #836 0x0008 in ?? () #837 0x in ?? () #838 0x0009 in ?? () #839 0x004040d0 in ?? () #840 0x0007 in ?? () #841 0x00080067f000 in ?? () #842 0x000f in ?? () #843 signal handler called #844 0x in ?? () Previous frame inner to this frame (corrupt stack?) Of course it still runs fine with the -d option set. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntpd problems after port updates
On Apr 23, 2012, at 12:08 PM, Dean E. Weimer wrote: Tried rebuilding without the with SSL option set, oddly it started once after that, but a restart caused same behavior. gdb doesn't give me anything that I know how to interpret, gdb -c /ntpd.core. (I haven't really used gdb before, so if I am not doing something correctly with it, please feel free to let me know) Ah, you need to build ntpd with -g in CFLAGS LDFLAGS for debugging symbols to be present Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntpd problems after port updates
On 23.04.2012 14:10, Chuck Swiger wrote: On Apr 23, 2012, at 12:08 PM, Dean E. Weimer wrote: Tried rebuilding without the with SSL option set, oddly it started once after that, but a restart caused same behavior. gdb doesn't give me anything that I know how to interpret, gdb -c /ntpd.core. (I haven't really used gdb before, so if I am not doing something correctly with it, please feel free to let me know) Ah, you need to build ntpd with -g in CFLAGS LDFLAGS for debugging symbols to be present at the risk of sounding like an complete n00b, how do I do that? After reading through the make man page, I decided on trying to build the port with make CFLAGS+=-g LDFLAGS+=-g install clean however I still get the no debugging symbols found message. Does the information in in the Makefile for the port overwrite this option from the command line? Or am I just using the incorrect syntax here? (gdb) file /usr/local/bin/ntpd Reading symbols from /usr/local/bin/ntpd...(no debugging symbols found)...done. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntpd crashes during start - a lot of interfaces
On Feb 5, 2012, at 10:39 PM, Radek Krejča wrote: I have problem with using ntpd on 8.2 amd64 (not tested elsewhere). If I have a lot of interfaces (vlans) ntpd crashes with segmentation fault (core dump). I have tested on my test machine and it really depends on number of interfaces. It try to bind on every of it. I want to reduce it with using some options (like -I em0) but it seems that ntpd ignore it. If I use truss the system calls look same. Is there any way to bind directly on specified interface? -I is supposed to do that, but if it doesn't work right, consider gaining a bit more debugging info (a backtrace from running under gdb or against the corefile) and filing a PR. You could also discuss this with upstream, meaning the NTP mailing list at questi...@lists.ntp.org Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTPd GPS with BU-353 USB on FreeBSD 8.x??
On Sat, January 15, 2011 7:51 pm, Howard Leadmon wrote: I would have sworn I had a doc on configuring the BU-353 GPS receiver on FreeBSD, and in fact why I picked one up on the cheap when I had the chance. That said, I have googled and binged and everything else, and I'll be damned if I can find any definitive instructions as to how to get this working on my FreeBSD server. If anyone has this working, or knows of how I can get this configured and running with ntpd, a little help would be most appreciated... --- Howard I've seen reference to this in the man page for astro/gpsd, you might want to look there. - Craig ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTPd GPS with BU-353 USB on FreeBSD 8.x??
On Fri, Jan 21, 2011 at 2:21 PM, Craig Whipp crwh...@gmail.com wrote: On Sat, January 15, 2011 7:51 pm, Howard Leadmon wrote: I would have sworn I had a doc on configuring the BU-353 GPS receiver on FreeBSD, and in fact why I picked one up on the cheap when I had the chance. That said, I have googled and binged and everything else, and I'll be damned if I can find any definitive instructions as to how to get this working on my FreeBSD server. If anyone has this working, or knows of how I can get this configured and running with ntpd, a little help would be most appreciated... --- Howard I've seen reference to this in the man page for astro/gpsd, you might want to look there. - Craig ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org See: http://desrablog.blogspot.com/2010/02/freebsd-with-gps-to-give-stratum-0-time.html -- Nathan Vidican nat...@vidican.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntpd / time synchronization
Hello, Jerry pisze: ntpd_enable=YES ntpd_flags=-g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntp.drift Assuming you are running the system ntpd file, the above are not really required. They are the defaults anyway. Try commenting out the line and restarting ntpd. Thank you Jerry - that was the problem. If you want to run a default nptd service, you should not have any ntpd flags in the rc.conf file. Thanks - the clock is now synchronized. Thank you everyone! It is wonderful to be part of such a friendly community. Zbigniew Szalbot www.slowo.pl www.fairtrade.net.pl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntpd / time synchronization
On Wed, 29 Jul 2009 08:48:44 +0200 Zbigniew Szalbot z.szal...@lcwords.com wrote: Hello, Jerry pisze: ntpd_enable=YES ntpd_flags=-g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntp.drift Assuming you are running the system ntpd file, the above are not really required. They are the defaults anyway. Try commenting out the line and restarting ntpd. Thank you Jerry - that was the problem. If you want to run a default nptd service, you should not have any ntpd flags in the rc.conf file. I doubt it, I think you must have done something else to fix it. The only difference between what you had, and the defaults is the -g option. That option just allows ntpd to make an initial unlimited correction rather, rather than exiting if the clock is out by 1000s. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntpd / time synchronization
On Tue, 28 Jul 2009 00:44:50 +0200 Zbigniew Szalbot z.szal...@lcwords.com wrote: Hello, I guess there is something simple that is wrong but my server is not really keeping the correct time. I have these options in /etc/rc.conf ntpd_enable=YES ntpd_flags=-g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntp.drift Assuming you are running the system ntpd file, the above are not really required. They are the defaults anyway. Try commenting out the line and restarting ntpd. and here's the details of /etc/ntp.conf file: server 0.pl.pool.ntp.org server 1.pl.pool.ntp.org server 2.pl.pool.ntp.org server 3.pl.pool.ntp.org driftfile /var/db/ntp.drift restrict default nopeer nomodify You are restating the 'driftfile again', why? Take out the restrict line. I doubt if you really need it. I used to have server 0.europe.pool.ntp.org in the ntp.conf file but today changed all entries to *.pl.pool.* At the moment my clock is about 3 minutes behind time. It has been running for a year and I do not have ntpdate enabled so I guess subsequent reboots did not correct the drifting problem. Is there anything obvious I am missing here? Any advice would be greatly appreciated! Thank you all very much! Are there any error messages logged? -- Jerry ges...@yahoo.com Then you admit confirming not denying you ever said that? NO! ... I mean Yes! WHAT? I'll put `maybe.' -- Bloom County ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntpd / time synchronization
On Jul 27, 2009, at 3:44 PM, Zbigniew Szalbot wrote: and here's the details of /etc/ntp.conf file: server 0.pl.pool.ntp.org server 1.pl.pool.ntp.org server 2.pl.pool.ntp.org server 3.pl.pool.ntp.org driftfile /var/db/ntp.drift restrict default nopeer nomodify I used to have server 0.europe.pool.ntp.org in the ntp.conf file but today changed all entries to *.pl.pool.* At the moment my clock is about 3 minutes behind time. It has been running for a year and I do not have ntpdate enabled so I guess subsequent reboots did not correct the drifting problem. Is there anything obvious I am missing here? Any advice would be greatly appreciated! You can't readily combine a restrict statement with using random timeservers from the NTP pool; you would need to list specific servers and add blank restrict statements for each server you trust. What you've configured is likely querying the 4 servers listed for time, but not trusting their responses so your clock never find a server which it is willing to sync to. Running ntpq -p -c rv would be informative Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntpd / time synchronization
On Tue, Jul 28, 2009 at 12:44:50AM +0200, Zbigniew Szalbot wrote: Hello, I guess there is something simple that is wrong but my server is not really keeping the correct time. I have these options in /etc/rc.conf ntpd_enable=YES ntpd_flags=-g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntp.drift and here's the details of /etc/ntp.conf file: server 0.pl.pool.ntp.org server 1.pl.pool.ntp.org server 2.pl.pool.ntp.org server 3.pl.pool.ntp.org driftfile /var/db/ntp.drift restrict default nopeer nomodify I used to have server 0.europe.pool.ntp.org in the ntp.conf file but today changed all entries to *.pl.pool.* At the moment my clock is about 3 minutes behind time. It has been running for a year and I do not have ntpdate enabled so I guess subsequent reboots did not correct the drifting problem. Is there anything obvious I am missing here? Any advice would be greatly appreciated! what does ntpq -p give you? -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntpd / time synchronization
Chuck Swiger pisze: You can't readily combine a restrict statement with using random timeservers from the NTP pool; you would need to list specific servers and add blank restrict statements for each server you trust. What you've configured is likely querying the 4 servers listed for time, but not trusting their responses so your clock never find a server which it is willing to sync to. Running ntpq -p -c rv would be informative Well, it seems you are right :) $ ntpq -p -c rv ntpq: read: Connection refused ntpq: read: Connection refused I took it from http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-ntp.html [quote] If you want to deny all machines from accessing your NTP server, add the following line to /etc/ntp.conf: restrict default ignore [/quote] OK. So removing the restrictions should cause the time to be synced? Thank you for your patience and help! Zbigniew Szalbot www.slowo.pl www.fairtrade.net.pl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntpd / time synchronization
Hi-- On Jul 27, 2009, at 4:08 PM, Zbigniew Szalbot wrote: OK. So removing the restrictions should cause the time to be synced? Thank you for your patience and help! Yes, try it and see-- it's most likely to be the cause of problems. If you want to set a default restrict line, you'll want to use a setup like the following, with explicit restrict statements added for localhost and each of the remote timeservers: server ntp.pbx.org maxpoll 11 server bonehed.lcs.mit.edu maxpoll 9 server sundial.columbia.edu maxpoll 11 server time1.apple.com maxpoll 11 peer ns1.codefab.com maxpoll 9 peer ns2.codefab.com maxpoll 9 restrict default kod nomodify notrap nopeer restrict -6 default kod nomodify notrap nopeer noquery # localhost is unrestricted restrict 127.0.0.1 restrict -6 ::1 restrict ntp.pbx.org restrict bonehed.lcs.mit.edu restrict sundial.columbia.edu restrict time1.apple.com restrict ns1.codefab.com restrict ns2.codefab.com Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTPD on 7.1-PRERELEASE
There was recently a thread that I started relating to ntpd not starting correctly becuase DNS and network were not available at the time of start. Do a ps -U root | grep ntpd If you see 2 processes, then the thread I mention may apply to you. If you see one or no processes, then that thread probably does not apply to you. In the thread, we were talking about how the DNS resolver helper process did not return successfully, causing 2 processes to appear and the ntpd not working. The subject of the thread in question is named and ntpd start order in rc.d. On Tue, Dec 23, 2008 at 10:58 AM, Jason C. Wells j...@highperformance.net wrote: My ntpd will not sync on my newly installed 7.1-PRERELEASE hosts. The configuration is the same as other correctly time synched hosts. They are behind the same firewall. The only difference is that these hosts are running 7.1. Does anyone have any tricks for getting ntpd to sync on 7.1? Did something time related change in the kernel? Thanks, Jason ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntpd and GPS
On 9/19/08, Tom Storey [EMAIL PROTECTED] wrote: Hi all, Ive been toying with setting up my old Garmin GPS12 as a reference for a server (FreeBSD 6.2) running ntpd, but Ive run into an issue. Is it possible the issue isn't what you think it is? Ive searched around a bit and cant find an answer, perhaps because there isnt one. I once (years ago) had a Garmin GPS working with ntpd, so it's reasonable to believe it can be done again, unless support for that capability was dropped (which I doubt). Unfortunately, it was long enough ago that I don't remember what I did. It's possible I used the 1 PPS output without NMEA sentences, but that's not my recollection. Is there any way I can set ntpd to expect a $GPRMC string every 2 seconds, which is the frequency at which the GPS12 transmits them? Alternatively, does anyone know how to make the GPS12 transmit a $GPRMC string every second? I'm almost certain you can't. The complete set of all NMEA sentences takes more than one second at the default 4800 baud, so IIRC it outputs sentences only on odd seconds, and perhaps the older units are too slow to compute a fix once per second. Two things that may work around this are to turn off everything except the GPRMC sentence: $PGRMO,,2 $PGRMO,GPRMC,1 and perhaps free up some CPU time (for faster position calculation) by (oddly enough) reducing the output data rate to 1200 bps: $PGRMC,,1, but I don't think that will actually work. To go back to 4800 bps, use 3 instead of 1. I think there are 11 commas after the C in that command, but my eyes aren't so sharp any more. There is a Linux driver for the Garmin proprietary protocol. Don't know if it is distributed in a FreeBSD version. Try http://jensar.us/~bob/garmin/ If there is a better place I can post this, please let me know. This is probably a good place for this question, but if you don't get a better answer, try the archives of the time nuts mailing list https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts which unfortunately appears to be down right now. General info about that group is at http://www.leapsecond.com/time-nuts.htm If that yields nothing, you might post your question to the Time Nuts list, time-nuts @ febo.com. It is probably a FAQ for them, but they will be polite about it. And I had hoped to once again stick an old Garmin on an NTP server, so I'll be curious to know if this turns out to be insurmountable. Good luck, -- Bob Johnson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd and GPS
Thanks Bob. I did a bit more reading, and it seems that I can turn on additional sentences in the driver. Ive been studying the NMEA output and there are two sentences which will give time figures across two subsequent seconds, so I tried enabling those (mode 6 in the server statement), but still no dice. I can see all of the correct sentences being picked up in ntpq using the clocklist command, but it just doesnt seem to want to work. Essentially my GPS reference just sits like this: building# ntpq -p remote refid st t when poll reach delay offset jitter = = = = = = resolv.internod 128.250.33.242 2 u 72 256 17 19.343 36.263 37.083 sparky.services 131.203.16.6 2 u 64 256 17 24.882 0.279 18.807 GPS_NMEA(0) .GPS.0 l- 6400.000 0.000 4000.00 Which I assume means nope, not working. Is PPS absolutely neccessary? The GPS12 doesnt have PPS, so perhaps this is my issue? The output of NMEA seems to happen every 1.5 seconds, but there are 3 sentences which output a time figure, so I figured I'd enable the two furthest apart in the hope that they may coincide with different seconds, and hopefully ntpd would be able to work it out from that. I even tried enabling all 3 of them (mode 7), but still nothing. Anyway, Im looking at grabbing a Garmin GPS18 LVC, they are only just over $100 so no biggie. People have reported wide success with this device, so I think I'll still with what is known to work and go from there. Cheers, Tom On 20/09/2008, at 8:09 AM, Bob Johnson wrote: On 9/19/08, Tom Storey [EMAIL PROTECTED] wrote: Hi all, Ive been toying with setting up my old Garmin GPS12 as a reference for a server (FreeBSD 6.2) running ntpd, but Ive run into an issue. Is it possible the issue isn't what you think it is? Ive searched around a bit and cant find an answer, perhaps because there isnt one. I once (years ago) had a Garmin GPS working with ntpd, so it's reasonable to believe it can be done again, unless support for that capability was dropped (which I doubt). Unfortunately, it was long enough ago that I don't remember what I did. It's possible I used the 1 PPS output without NMEA sentences, but that's not my recollection. Is there any way I can set ntpd to expect a $GPRMC string every 2 seconds, which is the frequency at which the GPS12 transmits them? Alternatively, does anyone know how to make the GPS12 transmit a $GPRMC string every second? I'm almost certain you can't. The complete set of all NMEA sentences takes more than one second at the default 4800 baud, so IIRC it outputs sentences only on odd seconds, and perhaps the older units are too slow to compute a fix once per second. Two things that may work around this are to turn off everything except the GPRMC sentence: $PGRMO,,2 $PGRMO,GPRMC,1 and perhaps free up some CPU time (for faster position calculation) by (oddly enough) reducing the output data rate to 1200 bps: $PGRMC,,1, but I don't think that will actually work. To go back to 4800 bps, use 3 instead of 1. I think there are 11 commas after the C in that command, but my eyes aren't so sharp any more. There is a Linux driver for the Garmin proprietary protocol. Don't know if it is distributed in a FreeBSD version. Try http://jensar.us/~bob/garmin/ If there is a better place I can post this, please let me know. This is probably a good place for this question, but if you don't get a better answer, try the archives of the time nuts mailing list https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts which unfortunately appears to be down right now. General info about that group is at http://www.leapsecond.com/time-nuts.htm If that yields nothing, you might post your question to the Time Nuts list, time-nuts @ febo.com. It is probably a FAQ for them, but they will be polite about it. And I had hoped to once again stick an old Garmin on an NTP server, so I'll be curious to know if this turns out to be insurmountable. Good luck, -- Bob Johnson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd and GPS
Ok, it was nothing like what I was thinking. Turns out my GPS didnt have a fix on anything. It was getting signals, but no fix. :-) Now that I have it mounted on a pole outside, hey presto: building# ntpq -p remote refid st t when poll reach delay offset jitter = = = = = = +resolv.internod 128.250.33.242 2 u 50 64 377 18.121 -1.127 14.549 *sparky.services 131.203.16.6 2 u 56 64 377 21.275 -9.704 15.235 GPS_NMEA(0) .GPS.0 l3 6410.000 -442.78 0.002 Cheers for your help. I'll keep tweaking it now until I get it working just right (jitter is incrementing and Im sure thats not a good thing). Tom On 20/09/2008, at 8:09 AM, Bob Johnson wrote: On 9/19/08, Tom Storey [EMAIL PROTECTED] wrote: Hi all, Ive been toying with setting up my old Garmin GPS12 as a reference for a server (FreeBSD 6.2) running ntpd, but Ive run into an issue. Is it possible the issue isn't what you think it is? Ive searched around a bit and cant find an answer, perhaps because there isnt one. I once (years ago) had a Garmin GPS working with ntpd, so it's reasonable to believe it can be done again, unless support for that capability was dropped (which I doubt). Unfortunately, it was long enough ago that I don't remember what I did. It's possible I used the 1 PPS output without NMEA sentences, but that's not my recollection. Is there any way I can set ntpd to expect a $GPRMC string every 2 seconds, which is the frequency at which the GPS12 transmits them? Alternatively, does anyone know how to make the GPS12 transmit a $GPRMC string every second? I'm almost certain you can't. The complete set of all NMEA sentences takes more than one second at the default 4800 baud, so IIRC it outputs sentences only on odd seconds, and perhaps the older units are too slow to compute a fix once per second. Two things that may work around this are to turn off everything except the GPRMC sentence: $PGRMO,,2 $PGRMO,GPRMC,1 and perhaps free up some CPU time (for faster position calculation) by (oddly enough) reducing the output data rate to 1200 bps: $PGRMC,,1, but I don't think that will actually work. To go back to 4800 bps, use 3 instead of 1. I think there are 11 commas after the C in that command, but my eyes aren't so sharp any more. There is a Linux driver for the Garmin proprietary protocol. Don't know if it is distributed in a FreeBSD version. Try http://jensar.us/~bob/garmin/ If there is a better place I can post this, please let me know. This is probably a good place for this question, but if you don't get a better answer, try the archives of the time nuts mailing list https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts which unfortunately appears to be down right now. General info about that group is at http://www.leapsecond.com/time-nuts.htm If that yields nothing, you might post your question to the Time Nuts list, time-nuts @ febo.com. It is probably a FAQ for them, but they will be polite about it. And I had hoped to once again stick an old Garmin on an NTP server, so I'll be curious to know if this turns out to be insurmountable. Good luck, -- Bob Johnson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd(8) - bind only to specified interfaces?
On Wed, Jul 9, 2008 at 9:44 PM, Fraser Tweedale [EMAIL PROTECTED] wrote: Having read the man page (also, ntp.conf(5)), it is not apparent that there is a way to tell it to bind only to a particular interface (or particular interfaces). It would be nice if there is actually such a feature, so I figured I'd ask. At the moment, no. Your question could qualify as a FAQ, so it might help in the future to check recent posts or the archives first. Definitely not a major problem is this isn't possible right now, but I figure if it's only going to be receiving NTP requests on one interface, it may as well not listen on the others. The alternative is openntpd (available in ports). Fairly straightforward to set up and use. The caveats are the provided rc script could use some work (see my recent post with the subject of rc scripts), there's no logging (ibid), using it may result in occasional calcru errors (see my recent post on that subject), and reading the overbrief manpage requires remembering to run man -M /usr/local ntpd. I did say straightforward, right? ;-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd not starting at boot time
On Thu, Apr 24, 2008 at 06:39:46AM -0700, David Newman wrote:
I've installed ntp-4.2.4p4 from ports on a FreeBSD 6.3/i386 system.
The ntpd process does not start at boot time. These lines exists in
/etc/rc.conf:
ntpd_enable=YES
ntpd_program=/usr/local/bin/ntpd
ntpd_flags=-c /etc/ntp.conf -p /var/run/ntpd.pid
ntpd_sync_on_start=YES
Manually running '/etc/rc.d/ntpd start' produces this error:
Starting ntpd.
ERROR: only one configfile option allowed
I've pasted the contents of ntp.conf and /etc/rc.d/ntpd files below.
Thanks in advance for clues as to what's missing.
##
# BEGIN /etc/rc.d/ntpd
##
# PROVIDE: ntpd
# REQUIRE: DAEMON ntpdate cleanvar devfs
# BEFORE: LOGIN
# KEYWORD: nojail
. /etc/rc.subr
name=ntpd
rcvar=`set_rcvar`
#command=/usr/sbin/${name}
command=/usr/local/bin/${name}
pidfile=/var/run/${name}.pid
start_precmd=ntpd_precmd
load_rc_config $name
required_files=${ntpd_config}
ntpd_precmd()
{
rc_flags=-c ${ntpd_config} ${ntpd_flags}
You need to set ntpd_config to the path to your config file - as it is
now, you are also setting it in ntpd_flags, which the above line then
expands to something like this:
rc_flags=-c /path/in/ntpd_config -c /etc/ntp.conf
So, remove it from your ntpd_flags definition and all should be well!
Dan
--
Daniel Bye
_
ASCII ribbon campaign ( )
- against HTML, vCards and X
- proprietary attachments in e-mail / \
pgpSvxDE420O7.pgp
Description: PGP signature
Re: ntpd not starting at boot time
On 4/24/08 7:47 AM, Daniel Bye wrote:
{
rc_flags=-c ${ntpd_config} ${ntpd_flags}
You need to set ntpd_config to the path to your config file - as it is
now, you are also setting it in ntpd_flags, which the above line then
expands to something like this:
rc_flags=-c /path/in/ntpd_config -c /etc/ntp.conf
So, remove it from your ntpd_flags definition and all should be well!
Bingo. Thanks!
dn
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd configuration file changes
On Dec 12, 2007, at 9:57 PM, N.J. Thomas wrote: * jekillen [EMAIL PROTECTED] [2007-12-12 20:42:47-0800]: Q: When making changes to ntp.conf it is necessary to restart the server? According to the ntpd docs, yes. The ntpd configuration docs say this: Ordinarily, ntpd reads the ntp.conf configuration file at startup time in order to determine the synchronization sources and operating modes. Q: How is that done? On FreeBSD, it is typically done via /etc/rc.d/ntpd restart. (I suspect ntpd reload or restart per rc script.. along the lines of apachectl restart or postfix reload??? Kill -HUP pid ??? ) I am looking at FreeBSD handbook and ntp documentation and have not found the answers. See the Using rc under FreeBSD section of the Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ configtuning-rcd.html It is based on Luke Mewburn's excellent NetBSD rc.d system. See the document, The Design and Implementation of the NetBSD rc.d system (PDF) here, it is an excellent read: http://www.mewburn.net/luke/bibliography.html Thomas Thank you for your reply: I missed it in the ntp docs I have. But maybe I was reading to fast and impatiently. I asked these questions because I switched the configuration file that has all the tier 2 server listed to another machine and let the remaining machines get time from it. So, now I can get on with it. Jeff K ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd configuration file changes
* jekillen [EMAIL PROTECTED] [2007-12-12 20:42:47-0800]: Q: When making changes to ntp.conf it is necessary to restart the server? According to the ntpd docs, yes. The ntpd configuration docs say this: Ordinarily, ntpd reads the ntp.conf configuration file at startup time in order to determine the synchronization sources and operating modes. Q: How is that done? On FreeBSD, it is typically done via /etc/rc.d/ntpd restart. (I suspect ntpd reload or restart per rc script.. along the lines of apachectl restart or postfix reload??? Kill -HUP pid ??? ) I am looking at FreeBSD handbook and ntp documentation and have not found the answers. See the Using rc under FreeBSD section of the Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-rcd.html It is based on Luke Mewburn's excellent NetBSD rc.d system. See the document, The Design and Implementation of the NetBSD rc.d system (PDF) here, it is an excellent read: http://www.mewburn.net/luke/bibliography.html Thomas -- N.J. Thomas [EMAIL PROTECTED] Etiamsi occiderit me, in ipso sperabo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd time server
On Sat, Sep 15, 2007 at 08:46:09PM -, [EMAIL PROTECTED] wrote: Is it possible to use ntpd as a client as well as a server? Of course. Your server is a client of its own ntpd. I have my firewall setup to get updates from the Internet which it does without any problem. However, I am not seeing any clients syncrhonizing with the firewall. The firewall ntp.conf files contains the following. server ntp-2.mcs.anl.gov prefer driftfile /data_prgs/local/etc/ntp.drift Is my understanding these days the Politically Correct and Polite thing to do is not list a specific machine (unless its yours) as ntp server but to use servers which have volunteered to be placed in a revolving DNS pool, like this: server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org server pool.ntp.org The clients contain the following. server firewall driftfile /var/db/ntp.drift firewall is a resolved via internal DNS, and it is resolved to the correct IP address. Any suggestions would be greatly appreciated. On your clients type ntpd -c peers and one machine should be listed, your server named firewall something like this (on MacOS X): % ntpdc -c peers remote local st poll reach delay offsetdisp === =andraia.local 192.168.123.177 2 40963 0.00085 -0.231870 3.95285 Do the same thing on the server to see what it thinks of the servers it is connected to. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPd not syncing time correctly - No errors either
On 5/31/07, John Webster [EMAIL PROTECTED] wrote: --On Thursday, May 31, 2007 19:02:47 -0400 Schiz0 [EMAIL PROTECTED] wrote: Hey, I'm running a dev server in VMWare (On a WindowsXP host) just to screw around with some things. Running FreeBSD 6.2-STABLE. VMWare causes the clock in FreeBSD to be a inaccurate; it loses about 2 hours every 24 hours. I read the handbook entry on the NTP daemon which automatically syncs the clock. Previously I was using cron to run ntpdate every 2 hours. I set NTPd to update using NTP.org's pool servers. Yet it isn't syncing. I setup NTPd last night. I checked about 20 minutes ago and the time was off by 2 hours. I shutdown ntpd and ran ntpdate manually, and it updated just fine. My logs have only this: /var/log/messages:May 30 23:04:19 Jupiter ntpd[489]: ntpd 4.2.0-a Mon May 28 23:49:40 EDT 2007 (1) /var/log/messages:May 30 23:04:19 Jupiter ntpd[489]: no IPv6 interfaces found /var/log/messages:May 31 16:41:50 Jupiter ntpd[489]: ntpd exiting on signal 15 The first two came up as soon as I started NTPd. The third one was when I stopped it. I rebuild world without IPv6 support. I tried adding the -4 flag to ntpd_flags in /etc/rc.conf as it says in the man page, but NTPd reports that -4 doesn't exist. While NTPd is running, I ran ntpq -np to display the peers. It did output the four servers from pool.ntp.org, so it's connecting fine. My /etc/rc.conf contains: ntpd_enable=YES ntpd_sync_on_start=YES ntpd_flags=-p /var/run/ntpd.pid -f /var/db/ntpd.drift -g Anyone know how I can fix this? Or should I just go back to running ntpdate with cron? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] http://support.ntp.org/bin/view/Support/KnownOsIssues NTP was not designed to run inside of a virtual machine. It requires a high resolution system clock, with response times to clock interrupts that are serviced with a high level of accuracy. No known virtual machine is capable of meeting these requirements. Run NTP on the base OS of the machine, and then have your various guest OSes take advantage of the good clock that is created on the system. Even that may not be enough, as there may be additional tools or kernel options that you need to enable so that virtual machine clients can adequately synchronize their virtual clocks to the physical system clock. Ah, that would do it. I guess I'm back to running ntpdate in cron. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPd not syncing time correctly - No errors either
--On Thursday, May 31, 2007 19:02:47 -0400 Schiz0 [EMAIL PROTECTED] wrote: Hey, I'm running a dev server in VMWare (On a WindowsXP host) just to screw around with some things. Running FreeBSD 6.2-STABLE. VMWare causes the clock in FreeBSD to be a inaccurate; it loses about 2 hours every 24 hours. I read the handbook entry on the NTP daemon which automatically syncs the clock. Previously I was using cron to run ntpdate every 2 hours. I set NTPd to update using NTP.org's pool servers. Yet it isn't syncing. I setup NTPd last night. I checked about 20 minutes ago and the time was off by 2 hours. I shutdown ntpd and ran ntpdate manually, and it updated just fine. My logs have only this: /var/log/messages:May 30 23:04:19 Jupiter ntpd[489]: ntpd 4.2.0-a Mon May 28 23:49:40 EDT 2007 (1) /var/log/messages:May 30 23:04:19 Jupiter ntpd[489]: no IPv6 interfaces found /var/log/messages:May 31 16:41:50 Jupiter ntpd[489]: ntpd exiting on signal 15 The first two came up as soon as I started NTPd. The third one was when I stopped it. I rebuild world without IPv6 support. I tried adding the -4 flag to ntpd_flags in /etc/rc.conf as it says in the man page, but NTPd reports that -4 doesn't exist. While NTPd is running, I ran ntpq -np to display the peers. It did output the four servers from pool.ntp.org, so it's connecting fine. My /etc/rc.conf contains: ntpd_enable=YES ntpd_sync_on_start=YES ntpd_flags=-p /var/run/ntpd.pid -f /var/db/ntpd.drift -g Anyone know how I can fix this? Or should I just go back to running ntpdate with cron? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] http://support.ntp.org/bin/view/Support/KnownOsIssues NTP was not designed to run inside of a virtual machine. It requires a high resolution system clock, with response times to clock interrupts that are serviced with a high level of accuracy. No known virtual machine is capable of meeting these requirements. Run NTP on the base OS of the machine, and then have your various guest OSes take advantage of the good clock that is created on the system. Even that may not be enough, as there may be additional tools or kernel options that you need to enable so that virtual machine clients can adequately synchronize their virtual clocks to the physical system clock. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd crashes every once in a while
On Jan 12, 2007, at 1:03 PM, Guido Demmenie wrote: ntpd crashes every once in a while, sometimes with days in between sometimes within a few hours. And the error I see in my /var/log/messages is: Jan 12 14:21:34 rottnic kernel: pid 516 (ntpd), uid 0: exited on signal 11 (core dumped) My server is in the pool of pool.ntp.org and there is mentioned that I might have to raise my ulimit, but as shown below it is already unlimited as far as I can see. I've been running ntpd as part of the pool for years on FreeBSD 4.11 5.5; ntpd will stay running for at least months at a time if your hardware is OK. Seeing segfaults suggests a RAM problem; try running a memory tester like Memtest86. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
Just a follow up, Turned off NTPD and the clock is still drifting. I set the clock around 1200 on Dec 7th, and the time is reported as Dec 7th 22:20 PST 2006. Have a burning question? Go to www.Answers.yahoo.com and get answers from real people who know. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: NTPD not keeping time
After poking about vmware's web site I've done the following. Installed VMWare tools for FreeBSD and activated it. Also, from the toolbox I checked of sync clock. Not yet implemented: /boot/loader.conf and disabling APIC. I'll try this later. Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--- Peter A. Giessel [EMAIL PROTECTED] wrote: On 2006/12/01 8:56, Kris Anderson seems to have typed: --- Chuck Swiger [EMAIL PROTECTED] wrote: However, if you are dual-booting between FreeBSD and Windows, you will also need to consider whether to keep the CMOS/BIOS clock running in UTC or in your local timezone; see man adjkerntz for details. Nope, not dual booting, see below. :| It could be that the virtual machine is giving FreeBSD the time in UTC, not your local timezone. Try changing the timezone options (you can use sysinstall - Configue - Time Zone and choosing yes) Peter, I'll give that a shot and see what happens. It certainly is mucking things up, that's for sure, poor cron. :( Although the host clock is correct so I just don't get it. Perhaps just not run ntpd and see what happens. I'll try that the next day. Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--- John Webster [EMAIL PROTECTED] wrote: --On Friday, December 01, 2006 10:23:17 -0800 Chuck Swiger [EMAIL PROTECTED] wrote: On Dec 1, 2006, at 9:56 AM, Kris Anderson wrote: Darn the system time strayed over night. One thing I failed to mention is that freebsd is running on a virtual machine. Sigh-- you're right, you should have mentioned this before. One should not attempt to change the clock from within a virtual machine at all, only in the parent or host OS. VMs depend on the host OS to provide the timekeeping, and it is known that systems running inside a VM may experience timing glitches as a result of running inside the machine emulation. http://ntp.isc.org/bin/view/Support/KnownOsIssues#Section_9.2.1. Having read that, my guess is that I should just disable ntp and reboot the system. Just so that all is well in the world. I'll give that a shot the next day. *sigh* Thanks. :) Have a burning question? Go to www.Answers.yahoo.com and get answers from real people who know. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--- Chuck Swiger [EMAIL PROTECTED] wrote: On Nov 30, 2006, at 12:55 PM, Kris Anderson wrote: Your clock is off by a little over an hour; while ntpd can correct very large offsets, doing so takes a long time. Kill ntpd, re-run ntpdate -b, double-check that your clock is sane, and then re-start ntpd. Off by an hour? Let's see the date is November 30th, and 12:41pm, that's what Windows says. Meanwhile freebsd says - Thu Nov 30 00:22:07 PST 2006. Wouldn't that be...nearly 12 hours? I was judging the time-offset by the output of ntpq -p. Ah, okay. Thanks. :) However, if you are dual-booting between FreeBSD and Windows, you will also need to consider whether to keep the CMOS/BIOS clock running in UTC or in your local timezone; see man adjkerntz for details. Nope, not dual booting, see below. :| It's entirely possible that doing a touch /etc/wall_cmos_clock will solve your issue. The file already exists, I have the timezone set to PST. :) [ ... ] If you are not providing time sync to a large subnet, please consider using stratum-2 servers or the NTP pool, ie, pool.ntp.org, or more specific regional parts, such as 0.us.pool.ntp.org, 1.us.pool.ntp.org-- this is assuming from your IP that you are located in the US, otherwise choose the appropriate country code for where-ever you are. I'll give it a shot and see what happens, I did just that yesterday. Okay, changed my pool since it's to keep this computer's time correct. Thanks for your help. :) You are most welcome. -- -Chuck Darn the system time strayed over night. One thing I failed to mention is that freebsd is running on a virtual machine. The system it is runing on is Windows 2003, the time and all that system are correct. I turned on ntpd because for some strange reason the date and time were still not in keeping with the system time, or so I thought. I'ld have to re-investigate that to be sure. Over the weekend I'll stop the ntpd and see what happens to the time when Monday rolls around. Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
On 2006/12/01 8:56, Kris Anderson seems to have typed: --- Chuck Swiger [EMAIL PROTECTED] wrote: However, if you are dual-booting between FreeBSD and Windows, you will also need to consider whether to keep the CMOS/BIOS clock running in UTC or in your local timezone; see man adjkerntz for details. Nope, not dual booting, see below. :| It could be that the virtual machine is giving FreeBSD the time in UTC, not your local timezone. Try changing the timezone options (you can use sysinstall - Configue - Time Zone and choosing yes) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
On Dec 1, 2006, at 9:56 AM, Kris Anderson wrote: Darn the system time strayed over night. One thing I failed to mention is that freebsd is running on a virtual machine. Sigh-- you're right, you should have mentioned this before. One should not attempt to change the clock from within a virtual machine at all, only in the parent or host OS. VMs depend on the host OS to provide the timekeeping, and it is known that systems running inside a VM may experience timing glitches as a result of running inside the machine emulation. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--On Friday, December 01, 2006 10:23:17 -0800 Chuck Swiger [EMAIL PROTECTED] wrote: On Dec 1, 2006, at 9:56 AM, Kris Anderson wrote: Darn the system time strayed over night. One thing I failed to mention is that freebsd is running on a virtual machine. Sigh-- you're right, you should have mentioned this before. One should not attempt to change the clock from within a virtual machine at all, only in the parent or host OS. VMs depend on the host OS to provide the timekeeping, and it is known that systems running inside a VM may experience timing glitches as a result of running inside the machine emulation. http://ntp.isc.org/bin/view/Support/KnownOsIssues#Section_9.2.1. pgpMohInQAgxV.pgp Description: PGP signature
Re: NTPD not keeping time
On Nov 30, 2006, at 11:16 AM, Kris Anderson wrote: I first ran ntpdate from /etc/rc.d/ntpdate and that set the date and time. Good. That should have gotten your clock reasonably sync'ed. Then I ran /etc/rc.d/ntpd and that started up fine. The followind day I find that the system still thinks it is the previous day and such. I thought the purpose of ntp was to keep the time correct, why would it be off? NTPd does a good job of keeping the clock synced if properly configured, so there is likely to be something wrong with your specific circumstances. What does ntpq -p show? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--- Chuck Swiger [EMAIL PROTECTED] wrote: On Nov 30, 2006, at 11:16 AM, Kris Anderson wrote: I first ran ntpdate from /etc/rc.d/ntpdate and that set the date and time. Good. That should have gotten your clock reasonably sync'ed. Then I ran /etc/rc.d/ntpd and that started up fine. The followind day I find that the system still thinks it is the previous day and such. I thought the purpose of ntp was to keep the time correct, why would it be off? NTPd does a good job of keeping the clock synced if properly configured, so there is likely to be something wrong with your specific circumstances. What does ntpq -p show? -- -Chuck Here's the output from ntpq. webdev# ntpq -p remote refid st t when poll reach delay offset jitter == time-a.nist.gov .ACTS. 1 u 485 1024 377 78.454 4307608 923174. india.colorado. .ACTS. 1 u 491 1024 377 22.918 4307064 922326. lerc-dns.grc.na .INIT. 16 u- 10240 0.0000.000 4000.00 Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
On Nov 30, 2006, at 12:16 PM, Kris Anderson wrote: Here's the output from ntpq. webdev# ntpq -p remote refid st t when poll reach delay offset jitter == time-a.nist.gov .ACTS. 1 u 485 1024 377 78.454 4307608 923174. india.colorado. .ACTS. 1 u 491 1024 377 22.918 4307064 922326. lerc-dns.grc.na .INIT. 16 u- 10240 0.0000.000 4000.00 Your clock is off by a little over an hour; while ntpd can correct very large offsets, doing so takes a long time. Kill ntpd, re-run ntpdate -b, double-check that your clock is sane, and then re-start ntpd. You should also note that your third ntp server is not answering queries, so you should try finding some other ntp server to use. Are you providing time syncronization from this machine to other hosts, or are you only running as a standalone client? If you are not providing time sync to a large subnet, please consider using stratum-2 servers or the NTP pool, ie, pool.ntp.org, or more specific regional parts, such as 0.us.pool.ntp.org, 1.us.pool.ntp.org-- this is assuming from your IP that you are located in the US, otherwise choose the appropriate country code for where-ever you are. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
On 2006/11/30 11:16, Kris Anderson seems to have typed: Here's the output from ntpq. webdev# ntpq -p remote refid st t when poll reach delay offset jitter == time-a.nist.gov .ACTS. 1 u 485 1024 377 78.454 4307608 923174. india.colorado. .ACTS. 1 u 491 1024 377 22.918 4307064 922326. lerc-dns.grc.na .INIT. 16 u- 10240 0.0000.000 4000.00 I take it this system was shutdown overnight? It looks like ntpd hasn't been running long at this point. Try starting ntpd with the -g flag On 2006/11/30 10:16, Kris Anderson seems to have typed: server time-a.nist.gov prefer iburst server utcnist.colorado.edu iburst server lerc-dns.lerc.nasa.gov iburst You might also want to consider using the pool instead of all stratum 1 servers, for most the pool is more than accurate enough, so: server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org Unless you really need to be using statum 1 servers... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
On 2006/11/30 11:48, Peter A. Giessel seems to have typed: On 2006/11/30 11:16, Kris Anderson seems to have typed: Here's the output from ntpq. webdev# ntpq -p remote refid st t when poll reach delay offset jitter == time-a.nist.gov .ACTS. 1 u 485 1024 377 78.454 4307608 923174. india.colorado. .ACTS. 1 u 491 1024 377 22.918 4307064 922326. lerc-dns.grc.na .INIT. 16 u- 102400.0000.000 4000.00 I take it this system was shutdown overnight? It looks like ntpd hasn't been running long at this point. Nevermind, I misread the reach column... Sorry. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--- Chuck Swiger [EMAIL PROTECTED] wrote: On Nov 30, 2006, at 12:16 PM, Kris Anderson wrote: Here's the output from ntpq. webdev# ntpq -p remote refid st t when poll reach delay offset jitter == time-a.nist.gov .ACTS. 1 u 485 1024 377 78.454 4307608 923174. india.colorado. .ACTS. 1 u 491 1024 377 22.918 4307064 922326. lerc-dns.grc.na .INIT. 16 u- 1024 0 0.0000.000 4000.00 Your clock is off by a little over an hour; while ntpd can correct very large offsets, doing so takes a long time. Kill ntpd, re-run ntpdate -b, double-check that your clock is sane, and then re-start ntpd. Off by an hour? Let's see the date is November 30th, and 12:41pm, that's what Windows says. Meanwhile freebsd says - Thu Nov 30 00:22:07 PST 2006. Wouldn't that be...nearly 12 hours? You should also note that your third ntp server is not answering queries, so you should try finding some other ntp server to use. Are you providing time syncronization from this machine to other hosts, or are you only running as a standalone client? If you are not providing time sync to a large subnet, please consider using stratum-2 servers or the NTP pool, ie, pool.ntp.org, or more specific regional parts, such as 0.us.pool.ntp.org, 1.us.pool.ntp.org-- this is assuming from your IP that you are located in the US, otherwise choose the appropriate country code for where-ever you are. I'll give it a shot and see what happens, I did just that yesterday. Okay, changed my pool since it's to keep this computer's time correct. Thanks for your help. :) Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--- Peter A. Giessel [EMAIL PROTECTED] wrote: On 2006/11/30 11:16, Kris Anderson seems to have typed: Here's the output from ntpq. webdev# ntpq -p remote refid st t when poll reach delay offset jitter == time-a.nist.gov .ACTS. 1 u 485 1024 377 78.454 4307608 923174. india.colorado. .ACTS. 1 u 491 1024 377 22.918 4307064 922326. lerc-dns.grc.na .INIT. 16 u- 1024 0 0.0000.000 4000.00 I take it this system was shutdown overnight? It looks like ntpd hasn't been running long at this point. Try starting ntpd with the -g flag Going to try and reset the clocks and such and see what happens the next day. :) On 2006/11/30 10:16, Kris Anderson seems to have typed: server time-a.nist.gov prefer iburst server utcnist.colorado.edu iburst server lerc-dns.lerc.nasa.gov iburst You might also want to consider using the pool instead of all stratum 1 servers, for most the pool is more than accurate enough, so: server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org Unless you really need to be using statum 1 servers... Yep, going to add the ntp.org pool and see how that works. Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
On Nov 30, 2006, at 12:55 PM, Kris Anderson wrote: Your clock is off by a little over an hour; while ntpd can correct very large offsets, doing so takes a long time. Kill ntpd, re-run ntpdate -b, double-check that your clock is sane, and then re-start ntpd. Off by an hour? Let's see the date is November 30th, and 12:41pm, that's what Windows says. Meanwhile freebsd says - Thu Nov 30 00:22:07 PST 2006. Wouldn't that be...nearly 12 hours? I was judging the time-offset by the output of ntpq -p. However, if you are dual-booting between FreeBSD and Windows, you will also need to consider whether to keep the CMOS/BIOS clock running in UTC or in your local timezone; see man adjkerntz for details. It's entirely possible that doing a touch /etc/wall_cmos_clock will solve your issue. [ ... ] If you are not providing time sync to a large subnet, please consider using stratum-2 servers or the NTP pool, ie, pool.ntp.org, or more specific regional parts, such as 0.us.pool.ntp.org, 1.us.pool.ntp.org-- this is assuming from your IP that you are located in the US, otherwise choose the appropriate country code for where-ever you are. I'll give it a shot and see what happens, I did just that yesterday. Okay, changed my pool since it's to keep this computer's time correct. Thanks for your help. :) You are most welcome. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd why question..
B. Cook wrote: Looking for why there is an /etc/ntp/ dir by default... The man page for ntpd says /etc/ntp.conf is the config file as does the handbook.. Whats it there for? It's for crypto keys used to authenticate between ntp servers, including the sort symmetric keys commonly used in the ntp.keys file and the private halves of public/private key pairs, both of which need to be kept in more highly protected than usual locations -- hence /etc/ntp/ which should be mode 0700 and ownership root:wheel. See the ntp-keygen(8) man page for more information. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: ntpd not adjusting the clock?
Hello, Thanks Peter for your reply. On Tue, 17 Oct 2006, Peter A. Giessel wrote: What does ntpq -p show? $ ntpq -p remote refid st t when poll reach delay offset jitter == 217.153.131.46 .INIT. 16 u- 102400.0000.000 4000.00 mail.fidesz.hu .INIT. 16 u- 102400.0000.000 4000.00 lokschuppen.zs6 .INIT. 16 u- 102400.0000.000 4000.00 -- Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd not adjusting the clock?
Hello, On Tue, 17 Oct 2006, Chuck Swiger wrote: Unless you've got additional restrict lines which permit some hosts to make changes, using only restrict default ignore will prevent ntpd from paying attention to the timeservers you've listed and it will even prevent ntpd from changing the local clock or being administered via ntpq from localhost. Ok. Thanks a lot. I have corrected it, restarted ntpd and now watching the clock. The time has not been immediately adjusted but I guess it should change in the longer run? Thank you all of you who have responded. It was very helpful. -- Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd not adjusting the clock?
Hello, On Wed, 18 Oct 2006, Matthew Seaman wrote: restrict default ignore driftfile /var/db/ntp.drift That means that anyone can connect to your NTP daemon and poll it for time service or use ntpdc to muck around with your configuration. It's better to use at minimum: restrict default nopeer nomodify restrict localhost I did that - thank you. That was my purpose in using restrict but I must have misunderstood the handbook in that respect. Anyway, I restarted ntpd and as of now the 40 second differance is down to about 10 seconds so it is working. Thank you very much! -- Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd not adjusting the clock?
Matthew Seaman wrote: That means that anyone can connect to your NTP daemon and poll it for time service or use ntpdc to muck around with your configuration. It's better to use at minimum: restrict default nopeer nomodify restrict localhost You *can* block that kind of unwanted external access with a firewall, though it can get tricky with NAT in the equation. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd not adjusting the clock?
On Oct 17, 2006, at 10:51 PM, Matthew Seaman wrote: This misconfiguration will also cause your ntpd to generate excessive numbers of queries, rather than syncing up and reducing the NTP polling interval from minpoll to maxpoll. [1] Remove that line and restart ntpd. That means that anyone can connect to your NTP daemon and poll it for time service or use ntpdc to muck around with your configuration. Setting up ntp.keys would let you control config changes via encryption and pre-shared secrets, if you care, or you can use ntp- genkeys to set up PKI using symmetric crypto. Unless you publish your IP address, it is unlikely that random requests, or even random people using ntpdc to poke at your ntpd, are going to be a significant concern. (Oh, if someone deliberately wants to mess with your network, leaving NTPd's security completely unconfigured isn't a good idea, but neither is it going to be a significant problem; once NTPd has sync'ed the clocks, it will only skew the system time gradually no matter what a malicious intruder might try to change. The max skew permitted is less than one minute per day using -x or tinker step 0.) It's better to use at minimum: restrict default nopeer nomodify restrict localhost (the 'restrict localhost' line actually removes all limitations on access from localhost. Ain't ntp.conf syntax wonderful.) Ideally, you'ld be able to use 'restrict default ignore' then apply restrict 2.pl.pool.ntp.org nopeer nomodify server 2.pl.pool.ntp.org prefer for each server you configure. That works well if you specify individual servers by name. Unfortunately the way NTP pool mechanism works makes that approach unworkable. You could actually use the pool via the combination of restrict and server entries, as NTPd will try to resolve the hostname once and then apply the security restrictions specified to whatever IP comes back from the pool. However, specifying nopeer against all hosts, including the servers you are trying to sync against, may not be a great idea. NTPd is perfectly capable of figuring out the stratum of the timeservers as the communicate for itself, unless you fudge it or otherwise prevent it from doing so. Unless you are running a stratum-1 timeserver and know for certain that your GPS or other external timereference is more reliable than any network peer might be, using nopeer prevents NTPd from gaining a sanity check from the other timeservers it talks with... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd not adjusting the clock?
On 2006/10/17 14:13, Zbigniew Szalbot seems to have typed: What am I doing wrong that instead of having the time synced I see more and more discrepancy. When I rebooted and started the service 6 days ago there was about 20 seconds difference. Now it is well over 30. What does ntpq -p show? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd not adjusting the clock?
On Oct 17, 2006, at 3:13 PM, Zbigniew Szalbot wrote: My ntp.conf file looks like that: server 2.pl.pool.ntp.org prefer server 1.europe.pool.ntp.org server 0.europe.pool.ntp.org restrict default ignore driftfile /var/db/ntp.drift Unless you've got additional restrict lines which permit some hosts to make changes, using only restrict default ignore will prevent ntpd from paying attention to the timeservers you've listed and it will even prevent ntpd from changing the local clock or being administered via ntpq from localhost. This misconfiguration will also cause your ntpd to generate excessive numbers of queries, rather than syncing up and reducing the NTP polling interval from minpoll to maxpoll. [1] Remove that line and restart ntpd. The rc.conf file has these lines: ntpd_enable=YES ntpd_flags=-g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ ntp.drift What am I doing wrong that instead of having the time synced I see more and more discrepancy. When I rebooted and started the service 6 days ago there was about 20 seconds difference. Now it is well over 30. Run: ntpq -c peers ...and you will be able to see the delay and offset from the NTP clocks you've configured in ntp.conf. -- -Chuck [1]: There are entire Linux distributions which have shipped with ntp.conf configured to prevent ntpd from working properly. These client machines end up querying NTP servers in the pool.ntp.org service repeatedly at minpoll (or even faster, if iburst is specified) because they discard the responses given to them, and therefore constitute an abuse of NTP server resources. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd not adjusting the clock?
ntpd won't correct the clock if the difference is too large. So you need to kill ntpd, run ntpdate to set the clock, then start ntpd up again. -Derek At 05:13 PM 10/17/2006, Zbigniew Szalbot wrote: Hello, Sorry to bother again but I run ntpd on FBSD 6.1 and the clock differes by about 30 seconds when I compare the time with top and this link http://www.timeanddate.com/worldclock/city.html?n=262 My ntp.conf file looks like that: server 2.pl.pool.ntp.org prefer server 1.europe.pool.ntp.org server 0.europe.pool.ntp.org restrict default ignore driftfile /var/db/ntp.drift The rc.conf file has these lines: ntpd_enable=YES ntpd_flags=-g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntp.drift What am I doing wrong that instead of having the time synced I see more and more discrepancy. When I rebooted and started the service 6 days ago there was about 20 seconds difference. Now it is well over 30. Many thanks in advance! -- Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd not adjusting the clock?
On Tuesday October 17, 2006 at 06:13:24 (PM) Zbigniew Szalbot wrote: Sorry to bother again but I run ntpd on FBSD 6.1 and the clock differes by about 30 seconds when I compare the time with top and this link http://www.timeanddate.com/worldclock/city.html?n=262 My ntp.conf file looks like that: server 2.pl.pool.ntp.org prefer server 1.europe.pool.ntp.org server 0.europe.pool.ntp.org restrict default ignore driftfile /var/db/ntp.drift The rc.conf file has these lines: ntpd_enable=YES ntpd_flags=-g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntp.drift What am I doing wrong that instead of having the time synced I see more and more discrepancy. When I rebooted and started the service 6 days ago there was about 20 seconds difference. Now it is well over 30. I am using the following configuration and the time is kept accurately. The drift file defaults to '/var/db/ntpd.drift' I believe. In any case, it is presently situated there without any assistance from me. #ntp.conf file # server us.pool.ntp.org server clock.nyc.he.net server sundial.columbia.edu #rc.conf # ntpd_enable=YES -- Gerard It is not the OS's job to stop you from shooting your foot. If you so choose to do so, then it is OS's job to deliver Mr. Bullet to Mr Foot in the most efficient way it knows. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd not adjusting the clock?
On 2006/10/17 14:40, Derek Ragona seems to have typed: ntpd won't correct the clock if the difference is too large. So you need to kill ntpd, run ntpdate to set the clock, then start ntpd up again. -Derek At 05:13 PM 10/17/2006, Zbigniew Szalbot wrote: ntpd_flags=-g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntp.drift From man ntpd: -g Normally, ntpd exits if the offset exceeds the sanity limit, which is 1000 s by default. If the sanity limit is set to zero, no sanity checking is performed and any offset is acceptable. This option overrides the limit and allows the time to be set to any value without restriction; however, this can happen only once. After that, ntpd will exit if the limit is exceeded. This option can be used with the -q option. With the -g flag in there, it shouldn't matter if the difference is too large. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd not adjusting the clock?
Chuck Swiger wrote: On Oct 17, 2006, at 3:13 PM, Zbigniew Szalbot wrote: My ntp.conf file looks like that: server 2.pl.pool.ntp.org prefer server 1.europe.pool.ntp.org server 0.europe.pool.ntp.org restrict default ignore driftfile /var/db/ntp.drift Unless you've got additional restrict lines which permit some hosts to make changes, using only restrict default ignore will prevent ntpd from paying attention to the timeservers you've listed and it will even prevent ntpd from changing the local clock or being administered via ntpq from localhost. This misconfiguration will also cause your ntpd to generate excessive numbers of queries, rather than syncing up and reducing the NTP polling interval from minpoll to maxpoll. [1] Remove that line and restart ntpd. That means that anyone can connect to your NTP daemon and poll it for time service or use ntpdc to muck around with your configuration. It's better to use at minimum: restrict default nopeer nomodify restrict localhost (the 'restrict localhost' line actually removes all limitations on access from localhost. Ain't ntp.conf syntax wonderful.) Ideally, you'ld be able to use 'restrict default ignore' then apply restrict 2.pl.pool.ntp.org nopeer nomodify server 2.pl.pool.ntp.org prefer for each server you configure. That works well if you specify individual servers by name. Unfortunately the way NTP pool mechanism works makes that approach unworkable. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: ntpd with flags in rc.conf
Zbigniew Szalbot wrote: I have a question about ntpd. HOw is the time adjusted? Gradually over time? Because I can see 30-second difference between my pc and FBSD machine. Will it be minimized in the longer run? Thanks! You're best off directing followup questions back to freebsd-questions as you may well get answers quicker than if you just ask me! ntpd adjusts time slowly, but the -g option should make it set the time correctly when it starts from when it should keep in sync. Set --g in your ntpd_flags and then as root run sh /etc/rc.d/ntpd restart With -g it can still take a while (several minutes) before ntpd trusts its servers enough to set the time, Many people, I believe, use ntpdate to set the time once at startup and then use ntpd to keep it in sync. (Ignore the comment on the manual page for ntpdate about it being deprecated. It has said that for a long time and shows no sign of going away). I believe ntpdate will pick up servers from your ntpd.conf. The man page for ntpd has more info on how ntpd keeps the time, and also check out ntpdc which can show you what ntpd is doing (which servers it's using and stuff). When you say the time on your PC is 30 seconds different, do you mean a Windows pc? Maybe it's the one that's wrong, or maybe your local ntpd isn't finding any servers. As root: ntpdc -c dmpeers should get you a list of the servers ntpd is polling and a * shows the one it is currently trusting, if i recall. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd with flags in rc.conf
On Wed, Oct 11, 2006 at 07:28:15PM +0200, Zbigniew Szalbot wrote: Hello, I read this in the handbook: To ensure the NTP server is started at boot time, add the line ntpd_enable=YES to /etc/rc.conf. If you wish to pass additional flags to ntpd(8), edit the ntpd_flags parameter in /etc/rc.conf. Now, I understand that the additional flag may be for example pid (-p /var/run/ntpd.pid). So how do I put that flag in /etc/rc.conf where I have ntpd_enable=Yes? Many thanks for your advice! -- Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] From man rc.conf: ntpd_flags (str) If ntpd_enable is set to ``YES'', these are the flags to pass to the ntpd(8) daemon. Mine is: ntpd_flags= -c /etc/ntp.conf -p /var/run/ntpd.pid -- = Sang-Kil (Sam) Suh ( ext. 262 ) [EMAIL PROTECTED] Agnicorp Inc. 487 Adelaide Street West, Suite 200M5V 1T4 Telephone: 416.203.7838 Facsimile: 416.203.8837 = ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd with flags in rc.conf
Hello Zbigniew, Wednesday, October 11, 2006, 5:28:15 PM, you wrote: Hello, I read this in the handbook: To ensure the NTP server is started at boot time, add the line ntpd_enable=YES to /etc/rc.conf. If you wish to pass additional flags to ntpd(8), edit the ntpd_flags parameter in /etc/rc.conf. Now, I understand that the additional flag may be for example pid (-p /var/run/ntpd.pid). So how do I put that flag in /etc/rc.conf where I have ntpd_enable=Yes? ntpd_flags=-p /var/run/ntpd.pid Many thanks for your advice! -- Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Best regards, Duanemailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd with flags in rc.conf
Zbigniew Szalbot wrote:
I read this in the handbook:
To ensure the NTP server is started at boot time, add the line
ntpd_enable=YES to /etc/rc.conf. If you wish to pass additional
flags to ntpd(8), edit the ntpd_flags parameter in /etc/rc.conf.
Now, I understand that the additional flag may be for example pid (-p
/var/run/ntpd.pid).
So how do I put that flag in /etc/rc.conf where I have ntpd_enable=Yes?
Firstly, you should check what default flags there are already. For 90%
of apps the defaults will be right for you. Look in
/etc/defaults/rc.conf for ntpd_flags and you find:
ntpd_flags=-p /var/run/ntpd.pid -f /var/db/ntpd.drift
In many instances, the right thing is to *add* to rather than replace
the default flags. Let's say you wanted to add a -g to the default
flags for ntpd_flags:
ntpd_flags=${ntpd_flags} -g
That way, if the default flags need to change for some reason, you still
keep up with the defaults and just add your own local customisation. If
you cut-and-paste the default value out of /etc/defaults/rc.conf then
you may not notice when that value changes.
--Alex
PS rc.conf is just a shell script, so all variable assignments follow
the rules you can find in man sh. Don't put anything too clever in
there, though, as this file is read many, many times when the system
starts up (once per /etc/rc.d/* file at least) so anything like an echo,
for example, will be executed many times.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd on FreeBSD
Freminlins [EMAIL PROTECTED] writes: Hello, After a power outaga (Level 3 at Goswell Road, London), all our FreeBSD machines came up OK. Nearly all of them had a problem though with ntpd. I'm guessing that most of these machines booted before the the ntp servers came up. What happens is that the machine runs two copies of ntpd: root 337 0.0 0.3 2964 1772 ?? Ss Sun04PM 0:24.75/usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid root 427 0.0 0.3 2964 1788 ?? SSun04PM 0:00.76/usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid ... and they never sync. The only way to fix this is to kill both ntpds, then restart ntpd. Is there a tidy way round this? It's not much fun logging into 40+ machines and killing a restarting a key process. I have no idea why two ntpds are running in the first place. The machines that are correct have an identical config. For what it's worth, I spent a while looking at it, and I can't see anything that would cause this. Ending up with *no* ntpd running, I can imaging from various failures, but not two. I suspect I would need another clue to look in the right place. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd on FreeBSD
Lowell Gilbert [EMAIL PROTECTED] writes: Freminlins [EMAIL PROTECTED] writes: Hello, After a power outaga (Level 3 at Goswell Road, London), all our FreeBSD machines came up OK. Nearly all of them had a problem though with ntpd. I'm guessing that most of these machines booted before the the ntp servers came up. What happens is that the machine runs two copies of ntpd: root 337 0.0 0.3 2964 1772 ?? Ss Sun04PM 0:24.75/usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid root 427 0.0 0.3 2964 1788 ?? SSun04PM 0:00.76/usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid ... and they never sync. The only way to fix this is to kill both ntpds, then restart ntpd. Is there a tidy way round this? It's not much fun logging into 40+ machines and killing a restarting a key process. I have no idea why two ntpds are running in the first place. The machines that are correct have an identical config. For what it's worth, I spent a while looking at it, and I can't see anything that would cause this. Ending up with *no* ntpd running, I can imaging from various failures, but not two. I suspect I would need another clue to look in the right place. Once I tried ntpd on my laptop. The problem is if it couldn't connect to the server when it starts, it will never sync. I found out that it may be the problem within ntpd itself, so I stopped using that. I can't see why you have two copies of ntpd running. But if these client machines booted before the ntp servers, it's never going to sync. -- Xiao-Yong ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd configuration . . . and errors
On 7/14/06, Owen G [EMAIL PROTECTED] wrote: Hi all, Following the suggestions regarding setting timekeeping up as a daemon I did the following and got these console messages . . . . . . Jul 14 13:04:29 epia ntpd[648]: no IPv6 interfaces found Jul 14 13:04:29 epia ntpd[648]: gethostby*.getanswer: asked for europe.pool.ntp.org IN , got type A This isn't a problem. It asked for an IP6 address if available and it wasn't, so it got an IP4 address instead. Jul 14 13:04:29 epia ntpd[648]: Frequency format error in /var/db/ntpd.drift Jul 14 13:05:44 epia ntpd[656]: no IPv6 interfaces found Notice the process ID changed from 648 to 656 here. It looks like a second copy of ntpd is trying to start. Jul 14 13:05:44 epia ntpd[656]: bind() fd 4, family 2, port 123, addr 0.0.0.0, i n_classd=0 flags=8 fails: Address already in use The second copy can't grab port 123 because the first copy is already using it. The output of ntpq -p should be informative. It will tell you if ntpd is actually working. By the way, you can use multiple servers for greater reliability, e.g. in ntp.conf: server 0.europe.pool.ntp.org server 1.europe.pool.ntp.org server 2.europe.pool.ntp.org will give you three different randomly selected servers, in case one goes down. - Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd configuration . . . and errors
--- Bob Johnson [EMAIL PROTECTED] wrote: On 7/14/06, Owen G [EMAIL PROTECTED] wrote: Following the suggestions regarding setting ntpd as a daemon I did the following and got these console messages . . . . . . Jul 14 13:04:29 epia ntpd[648]: no IPv6 interfaces found Jul 14 13:04:29 epia ntpd[648]: gethostby*.getanswer: asked for europe.pool.ntp.org IN , got type A ntpd This isn't a problem. It asked for an IP6 address if available and it wasn't, so it got an IP4 address instead. Jul 14 13:05:44 epia ntpd[656]: no IPv6 interfaces found Notice the process ID changed from 648 to 656 here. It looks like a second copy of ntpd is trying to start. Jul 14 13:05:44 epia ntpd[656]: bind() fd 4, family 2, port 123, addr 0.0.0.0, i n_classd=0 flags=8 fails: Address already in use The second copy can't grab port 123 because the first copy is already using it. The output of ntpq -p should be informative. It will tell you if ntpd is actually working. By the way, you can use multiple servers for greater reliability, e.g. in ntp.conf: server 0.europe.pool.ntp.org server 1.europe.pool.ntp.org server 2.europe.pool.ntp.org will give you three different randomly selected servers, in case one goes down. - Bob Thanks Bob, I did a reboot to see if the same errors come up this time - without me laying on any hands! After a reboot, when running ntpq -p, as requested . . . it says can't read: connection refused. - and there's no console output. Obviously ntpd isn't starting automatically. Wrong - I used the ntpd_flags=-q as per a previous posting . . . without me having RTFM - mea culpa! Then I corrected this run once and quit option and now get no errors on the console anymore and ntpq -p gives: epia# ntpq -p remote refid st t when poll reach delay offset jitter == *h2348.serverkom 192.53.103.108 2 u 62 128 377 63.3949.194 19.331 epia# BTW, The idea of using europe.pool.ntp.org as the only server was that the address itself resolves to a round robin pool of servers - obviating the need for multiple entries. I will of course sit corrected. My concern is now that ntpd doesn't seem to report that it has checked the time with any timesource. Any ideas how to confirm (apart from changing the time to something wrong but only wrong by less than 1000 seconds?) Cheers, Owen ___ Yahoo! Photos NEW, now offering a quality print service from just 7p a photo http://uk.photos.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd configuration . . . and errors
On Fri, 14 Jul 2006 17:25:52 +0100 (BST) Owen G [EMAIL PROTECTED] wrote: [snip] Then I corrected this run once and quit option and now get no errors on the console anymore and ntpq -p gives: epia# ntpq -p remote refid st t when poll reach delay offset jitter == *h2348.serverkom 192.53.103.108 2 u 62 128 377 63.3949.194 19.331 epia# BTW, The idea of using europe.pool.ntp.org as the only server was that the address itself resolves to a round robin pool of servers - obviating the need for multiple entries. I will of course sit corrected. My concern is now that ntpd doesn't seem to report that it has checked the time with any timesource. Any ideas how to confirm (apart from changing the time to something wrong but only wrong by less than 1000 seconds?) ntpd will log time changes to syslog. On every system I've seen, they end up in /var/log/messages. Note that ntpd is rather conservative. It might spend 30 minutes checking and rechecking the time before it decides to make an adjustment. Let it run for a day and check tomorrow to see if it's making changes. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd core dump
Ntpd build with FreeBSD can't create a local clock (with 127.127.1.0) ??? Hello, I have a core dump with ntpd ( Segmentation fault: 11 (core dumped) ). I try each line of my ntp.conf and the problem is with the line server 127.127.1.0 even if i set fudge 127.127.1.0 stratum 10 This is a FreeBSD 6.1 updated from a 6.0. Tnahks for any help. Ghislain ___ Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Rendez-vous sur http://fr.yahoo.com/set ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problem in release 6.0
2006/1/26, Chuck Swiger [EMAIL PROTECTED]: Vincent Chen wrote: [ ... ] Why I have to restart ntpd to get connected? I don't have this problem with release 4.7. I've seen this once and gotten the impression that ntpd had fired up before DNS was working, because the ntpd was able to connect with local peers listed in the /etc/hosts file. Maybe updating and running mergemaster to make sure the dependencies in the /etc/rc.d/ntpd startup script are OK would be a thought...? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] NTP starts up before DNS and needs working DNS to resolve the IPs. So you can enter bare ips, or change the startup order of NTP and DNS. Regards, -- Димитър Василев Dimitar Vassilev GnuPG key ID: 0x4B8DB525 Keyserver: pgp.mit.edu Key fingerprint: D88A 3B92 DED5 917E 341E D62F 8C51 5FC4 4B8D B525 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problem in release 6.0
On Friday 27 January 2006 14:03, Dimitar Vasilev wrote: 2006/1/26, Chuck Swiger [EMAIL PROTECTED]: Vincent Chen wrote: [ ... ] Why I have to restart ntpd to get connected? I don't have this problem with release 4.7. I've seen this once and gotten the impression that ntpd had fired up before DNS was working, because the ntpd was able to connect with local peers listed in the /etc/hosts file. Maybe updating and running mergemaster to make sure the dependencies in the /etc/rc.d/ntpd startup script are OK would be a thought...? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] NTP starts up before DNS and needs working DNS to resolve the IPs. So you can enter bare ips, or change the startup order of NTP and DNS. Regards, I don't think so: # cd /etc/rc.d rcorder * | egrep named|ntp named ntpdate ntpd OTOH dnscache from djbdns does load after ntpd. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problem in release 6.0
Vincent Chen wrote: [ ... ] Why I have to restart ntpd to get connected? I don't have this problem with release 4.7. I've seen this once and gotten the impression that ntpd had fired up before DNS was working, because the ntpd was able to connect with local peers listed in the /etc/hosts file. Maybe updating and running mergemaster to make sure the dependencies in the /etc/rc.d/ntpd startup script are OK would be a thought...? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems
Shelby Westman [EMAIL PROTECTED] writes: I am a relatively new freeBSD user. The problem I describe below happens on both a 5.4 install and a 6.0 RC1 install. Right after installing the OS, I enable ntpd in rc.conf, and setup a simple config file in /etc/ntp.conf. When I reboot, I get this message: Oct 22 10:40:57 alter ntpd[392]: ntpd 4.2.0-a Sun Oct 9 18:33:33 UTC 2005 (1) Oct 22 10:40:57 alter ntpd[392]: bind() fd 6, family 28, port 123, addr fe80:1::202:55ff:fe58:2957, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address Then ntpd does not synchronize the time. I set the clock manually (using date) five minutes ahead to check and in fact it does not get adjusted. I have tried all sorts of things. I tried assigning numeric addresses rather than host names in the config file. I tried enabling ipv6 in sysinstall. This machine does have a good route to the internet - I can use nslookup to resolve host names, so I know the networking is working. Below I have quoted the ntp.conf. The log file is empty - nothing is being written there. Does anyone have any ideas? I am stumped... thanks for your help. Shelby __ config file as it stands now... logfile /var/log/ntpd.log # deny-by-default policy restrict default ignore #server -4 ntp-2.ece.cmu.edu http://ntp-2.ece.cmu.edu #server -4 ticker.cis.sac.accd.edu http://ticker.cis.sac.accd.edu #server -4 lain.ziaspace.com http://lain.ziaspace.com #server -4 ntp1.linuxmedialabs.com http://ntp1.linuxmedialabs.com server 17.254.0.31 http://17.254.0.31 driftfile /var/spool/ntp.drift You're probably running into problems with your restrict clause, but I'm not sure what offhand. Use the -d flag to ntpd (or more than one) to get more information on what it thinks the problem is. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems
Also... another thought. You might try disabling IPv6 unless you need it. (remove 'options INET6' from kernconf) Yes, after I did that and recompiled the kernel, it got rid of the error message. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems
Regarding ntpd, Lowell wrote # deny-by-default policy restrict default ignore You're probably running into problems with your restrict clause, but I'm not sure what offhand. Use the -d flag to ntpd (or more than one) to get more information on what it thinks the problem is. Yes, I think you are right. When I removed that clause, ntpd started working. I did try the -d flag, but it reported back to me that ntpd was compiled without debugging, so that -d wouldn't report anything. oh, well, I'll restrict access other ways. Thanks Shelby ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems
Shelby Westman wrote: Hello, all, I am a relatively new freeBSD user. The problem I describe below happens on both a 5.4 install and a 6.0 RC1 install. Right after installing the OS, I enable ntpd in rc.conf, and setup a simple Are you intending on running an NTP daemon? Or are you just trying to sync your clock with an NTP source? If the later, try adding the following to your rc.conf: ntpdate_enable=YES ntpdate_flags=your_fav_ntp_server_here HTH. config file in /etc/ntp.conf. When I reboot, I get this message: Oct 22 10:40:57 alter ntpd[392]: ntpd 4.2.0-a Sun Oct 9 18:33:33 UTC 2005 (1) Oct 22 10:40:57 alter ntpd[392]: bind() fd 6, family 28, port 123, addr fe80:1::202:55ff:fe58:2957, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address Then ntpd does not synchronize the time. I set the clock manually (using date) five minutes ahead to check and in fact it does not get adjusted. I have tried all sorts of things. I tried assigning numeric addresses rather than host names in the config file. I tried enabling ipv6 in sysinstall. This machine does have a good route to the internet - I can use nslookup to resolve host names, so I know the networking is working. Below I have quoted the ntp.conf. The log file is empty - nothing is being written there. Does anyone have any ideas? I am stumped... thanks for your help. Shelby __ config file as it stands now... logfile /var/log/ntpd.log # deny-by-default policy restrict default ignore #server -4 ntp-2.ece.cmu.edu http://ntp-2.ece.cmu.edu #server -4 ticker.cis.sac.accd.edu http://ticker.cis.sac.accd.edu #server -4 lain.ziaspace.com http://lain.ziaspace.com #server -4 ntp1.linuxmedialabs.com http://ntp1.linuxmedialabs.com server 17.254.0.31 http://17.254.0.31 driftfile /var/spool/ntp.drift ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Regards, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems
Eric Schuele wrote: Shelby Westman wrote: Hello, all, I am a relatively new freeBSD user. The problem I describe below happens on both a 5.4 install and a 6.0 RC1 install. Right after installing the OS, I enable ntpd in rc.conf, and setup a simple Are you intending on running an NTP daemon? Or are you just trying to sync your clock with an NTP source? If the later, try adding the following to your rc.conf: ntpdate_enable=YES ntpdate_flags=your_fav_ntp_server_here FWIW... after checking the man pages, I think ntpdate is being deprecated some time in the near future. ntpd should be used. So here is what I now have in my rc.conf: ntpd_enable=YES ntpd_flags=-q /etc/ntp.conf contains exactly one line: server north-america.pool.ntp.org Works fine. Also... another thought. You might try disabling IPv6 unless you need it. (remove 'options INET6' from kernconf) HTH. config file in /etc/ntp.conf. When I reboot, I get this message: Oct 22 10:40:57 alter ntpd[392]: ntpd 4.2.0-a Sun Oct 9 18:33:33 UTC 2005 (1) Oct 22 10:40:57 alter ntpd[392]: bind() fd 6, family 28, port 123, addr fe80:1::202:55ff:fe58:2957, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address Then ntpd does not synchronize the time. I set the clock manually (using date) five minutes ahead to check and in fact it does not get adjusted. I have tried all sorts of things. I tried assigning numeric addresses rather than host names in the config file. I tried enabling ipv6 in sysinstall. This machine does have a good route to the internet - I can use nslookup to resolve host names, so I know the networking is working. Below I have quoted the ntp.conf. The log file is empty - nothing is being written there. Does anyone have any ideas? I am stumped... thanks for your help. Shelby __ config file as it stands now... logfile /var/log/ntpd.log # deny-by-default policy restrict default ignore #server -4 ntp-2.ece.cmu.edu http://ntp-2.ece.cmu.edu #server -4 ticker.cis.sac.accd.edu http://ticker.cis.sac.accd.edu #server -4 lain.ziaspace.com http://lain.ziaspace.com #server -4 ntp1.linuxmedialabs.com http://ntp1.linuxmedialabs.com server 17.254.0.31 http://17.254.0.31 driftfile /var/spool/ntp.drift ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Regards, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ntpd problems
This is my ntpd and i haven't got ipv6 connection but i want that ntpd uses ipv4 and not ipv4 and ipv6. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ntpd problems
In my rc.conf , i have that : xntpd_enable=YES xntpd_program=/usr/sbin/ntpd xntpd_flags=-p /var/run/ntpd.pid In ntp.conf , i have that : server 62.4.16.80 prefer server 195.220.94.163 server 134.214.100.6 driftfile /var/db/ntp.drift restrict 127.0.0.1 mask 255.255.0.0 nomodify notrap nopeer notrust restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ntpd problems
# ifconfig xl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=9RXCSUM,VLAN_MTU inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::20a:5eff:fe3e:ebf7%xl0 prefixlen 64 scopeid 0x1 ether 00:0a:5e:3e:eb:f7 media: Ethernet autoselect (100baseTX full-duplex) status: active vr0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::205:5dff:fe64:5a87%vr0 prefixlen 64 scopeid 0x2 ether 00:05:5d:64:5a:87 media: Ethernet autoselect (10baseT/UTP) status: active vr1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.3.1 netmask 0xff00 broadcast 192.168.3.255 inet6 fe80::205:5dff:fea2:98ef%vr1 prefixlen 64 scopeid 0x3 ether 00:05:5d:a2:98:ef media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 pfsync0: flags=0 mtu 2020 pflog0: flags=141UP,RUNNING,PROMISC mtu 33208 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu 1492 inet6 fe80::20a:5eff:fe3e:ebf7%tun0 prefixlen 64 scopeid 0x8 inet 62.212.96.206 -- 62.4.16.246 netmask 0x Opened by PID 272 tap0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::2bd:41ff:fe06:0%tap0 prefixlen 64 scopeid 0x9 ether 00:bd:41:06:00:00 Opened by PID 493 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ntpd problems
On 8/20/05, fire67 [EMAIL PROTECTED] wrote: Hello , i'm on freebsd 5.4 and i tried to configure ntpd but i have this problem : ntpd[546]: bind() fd 16, family 28, port 123, addr fe80:9::2bd:a0ff:fe08:0, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address Anyone knowns this problem ? I never was able to configure ntpd to run on FreeBSD 5.x. Thought that was a widely noticed bug but seems I was wrong. Anyway, now I am using ntpdate in the startup scripts and so far so good. -- Dmitry Mityugov, St. Petersburg, Russia I ignore all messages with confidentiality statements We live less by imagination than despite it - Rockwell Kent, N by E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ntpd problems
At 12:37 PM 8/20/2005, Dmitry Mityugov wrote: On 8/20/05, fire67 [EMAIL PROTECTED] wrote: Hello , i'm on freebsd 5.4 and i tried to configure ntpd but i have this problem : ntpd[546]: bind() fd 16, family 28, port 123, addr fe80:9::2bd:a0ff:fe08:0, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address Anyone knowns this problem ? I never was able to configure ntpd to run on FreeBSD 5.x. Thought that was a widely noticed bug but seems I was wrong. Anyway, now I am using ntpdate in the startup scripts and so far so good. I've got ntpd running under 5.4 without any problems, but my config is very simple. Below is the configuration I use, maybe it'll help, maybe it won't. ntp.conf: server 217.204.76.170 server 64.112.189.11 server 66.69.112.130 server 66.187.233.4 server 80.85.129.25 server 80.237.234.15 server 130.60.7.44 server 134.99.176.3 server 198.144.202.250 server 202.74.170.194 server 204.17.42.199 server 204.87.183.6 server 213.15.3.1 server 213.239.178.33 server 217.114.97.97 clientlimit 100 and in rc.conf: ntpd_enable=YES ntpd_flags=-A -p /var/run/ntpd.pid -f /var/db/ntpd.drift If you don't want just anyone to be able to connect, drop the -A from the flags. -Glenn -- Dmitry Mityugov, St. Petersburg, Russia I ignore all messages with confidentiality statements We live less by imagination than despite it - Rockwell Kent, N by E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ntpd error msg
At 11:15 7/8/2005, Shawn Wall wrote: Hello list, I've just installed a new 5.3 server and I have setup ntpd. When I start the daemon I get this error msg: Wintermute ntpd[512]: Frequency format error in /var/db/ntpd.drift Here is my ntp.conf: Driftfile /var/db/ntpd.drift Server pool.ntp.org Server pool.ntp.org Server pool.ntp.org Server pool.ntp.org Restrict default ignore Ntpd.drift is located in /var/db/ Any ideas? Thanks. shawn You should be able to zero out the file and it should be regenerated. It shouldn't matter, but the drift file is usuallly named ntp.drift and is located in /etc: http://www.US-Webmasters.com/FreeBSD/Install/NTP/ Start Here to Find It Fast! - http://www.US-Webmasters.com/best-start-page/ $8.77 Domain Names - http://domains.us-webmasters.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd and ntp.conf
Niclas Zeising wrote: Hi! I am trying to configure my ntpd to sync my computer clock, but I can't figure ut how to do it. I don't want to use ntpd -q and just sync it on computer startup, because the clock drifts too much. How do I manage to get a properly configured ntpd without giving the whole world access to it? Thanks beforhand! Regards //Niclas man ntpd -- Best regards, Chris Washing your car to make it rain doesn't work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd and ntp.conf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2005-04-02, Chris scribbled these curious markings: How do I manage to get a properly configured ntpd without giving the whole world access to it? Thanks beforhand! Regards //Niclas man ntpd Better yet, check out the Handbook section. Much easier to understand than the manual. Best Regards, Christopher Nehren -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCTtiyk/lo7zvzJioRAgjgAKCCkxa0d2mvEFs5+fBBtLpt9zuFJQCgk1j/ ahE3ffgtKE5lgXnqLwybSDc= =A0bp -END PGP SIGNATURE- -- I abhor a system designed for the user, if that word is a coded pejorative meaning stupid and unsophisticated. -- Ken Thompson If you ask the wrong questions, you get answers like 42 and God. Unix is user friendly. However, it isn't idiot friendly. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd core dumping on 5.3-p5
John Pettitt [EMAIL PROTECTED] wrote: Bill Moran wrote: I'm experiencing a problem similar to the problem described in this thread: http://lists.freebsd.org/pipermail/freebsd-questions/2005-February/078139.html My ntp.conf contains: server clock.psu.edu server fuzz.psc.edu prefer server ntp-1.ece.cmu.edu prefer server ntp-2.ece.cmu.edu prefer If I comment out the first two servers, ntpd works fine. Otherwise, I get coredumps. It seems a little extreme to me that any server could remotely cause ntpd to core. I'm willing to look in to this, but I'm having trouble figuring out how to get ntp built with debugging symbols. FreeBSD bolivia.potentialtech.com 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #0: Thu Feb 24 08:26:07 UTC 2005 root@:/usr/obj/usr/src/sys/WORKING i386 you can only have one preferred server. First off: Where did you get that tidbit. I don't think it's accurate. It says nothing about it in the man page for ntp.conf, and it works fine on previous version of ntpd. Secondly, and more important, it doesn't help anyway. * If I remove all the prefer and try to start ntpd, it still coredumps. * If I set only one prefer, it still coredumps. * If I comment out the first two servers, but set the remaining two _both_ to prefer, it runs fine. Thirdly, even if it were illegal to have multiple prefer directives, the program still should not coredump because of an invalid config file. So, we come badk to my original statement: After additional testing, it still seems as if the first two servers on this list are coredumping ntpd. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd core dumping on 5.3-p5
John Pettitt [EMAIL PROTECTED] wrote: Bill Moran wrote: John Pettitt [EMAIL PROTECTED] wrote: Bill Moran wrote: I'm experiencing a problem similar to the problem described in this thread: http://lists.freebsd.org/pipermail/freebsd-questions/2005-February/078139.html My ntp.conf contains: server clock.psu.edu server fuzz.psc.edu prefer server ntp-1.ece.cmu.edu prefer server ntp-2.ece.cmu.edu prefer If I comment out the first two servers, ntpd works fine. Otherwise, I get coredumps. It seems a little extreme to me that any server could remotely cause ntpd to core. I'm willing to look in to this, but I'm having trouble figuring out how to get ntp built with debugging symbols. FreeBSD bolivia.potentialtech.com 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #0: Thu Feb 24 08:26:07 UTC 2005 root@:/usr/obj/usr/src/sys/WORKING i386 snip Does it core dump as soon as it starts or after a while? It consistenly takes two seconds to coredump. What do ntpq -c rv and ntpq -c peer say? Not really enough time to issue those commands before ntpd cores. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd core dump
Lowell Gilbert wrote: Richard Danter [EMAIL PROTECTED] writes: Hi all, I have 5.3-RELEASE installed. I'm trying to run ntpd but I get a message in /var/log/messages that it exited on signal 11 (core dumped). Is there a known problem with this version or is there somethig wrong with my config file (below)? This file is based on one I use on a Linux host with no problems. Thanks Rich -- server ntp.maths.tcd.ie server bear.zoo.bt.co.uk server ntp.cis.strath.ac.uk server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 10 broadcastdelay 0.008 restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap Hard to say. Try subsets of that config file in order to isolate a portion of the file that produces the problem. Thanks Lowell, I tried commenting out everything and then adding in 1 line at a time. Turns out it is a problem with the very first server in the list. If I remove it then ntpd starts perfectly. This is rather odd as I still have a Linux box using the original file with no problems. It is also add that the result is a core dump rather than a nice error message in the syslog. But such is life. Thanks again, Rich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd core dump
Richard Danter [EMAIL PROTECTED] writes: Thanks Lowell, I tried commenting out everything and then adding in 1 line at a time. Turns out it is a problem with the very first server in the list. If I remove it then ntpd starts perfectly. This is rather odd as I still have a Linux box using the original file with no problems. It is also add that the result is a core dump rather than a nice error message in the syslog. But such is life. A newer version of ntpd has been imported since 5.2.1. Given that it was a technology preview release, maybe it's time to update the system. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd core dump
Richard Danter [EMAIL PROTECTED] writes: Hi all, I have 5.3-RELEASE installed. I'm trying to run ntpd but I get a message in /var/log/messages that it exited on signal 11 (core dumped). Is there a known problem with this version or is there somethig wrong with my config file (below)? This file is based on one I use on a Linux host with no problems. Thanks Rich -- server ntp.maths.tcd.ie server bear.zoo.bt.co.uk server ntp.cis.strath.ac.uk server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 10 broadcastdelay 0.008 restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap Hard to say. Try subsets of that config file in order to isolate a portion of the file that produces the problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems since upgrading to 5.3 - found the problem!
On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote: Ian Moore [EMAIL PROTECTED] writes: I've just realised I'm not running a name server at all on my 5.3 system. I have 4.9 installed on this computer too I'd set up the caching server on it, I guess I forgot that step when I installed 5.3. I'll set it up see that makes any difference. Make sure to switch to using domain names that aren't in use by other people... [A common convention is to use .lan or .local as the top-level domain if you are using non-public domain names.] Thanks, I hadn't thought of using a non-existant top level domain. I've changed the hostname to daemon.foo.lan and now localhost.foo.lan resolves to 127.0.0.1 as it should. Unfortunately, I still get the same response form ntpq: daemon:~ % sudo ntpq -p ntpq: write to localhost.foo.lan failed: Permission denied Even with my firewall disabled I get this response. Cheers, -- Ian Moore GPG Key: http://homepages.picknowl.com.au/imoore/imoore.asc pgpaXjoKVcfku.pgp Description: PGP signature
Re: ntpd problems since upgrading to 5.3 - found the problem!
Ian Moore [EMAIL PROTECTED] writes: On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote: Ian Moore [EMAIL PROTECTED] writes: I've just realised I'm not running a name server at all on my 5.3 system. I have 4.9 installed on this computer too I'd set up the caching server on it, I guess I forgot that step when I installed 5.3. I'll set it up see that makes any difference. Make sure to switch to using domain names that aren't in use by other people... [A common convention is to use .lan or .local as the top-level domain if you are using non-public domain names.] Thanks, I hadn't thought of using a non-existant top level domain. I've changed the hostname to daemon.foo.lan and now localhost.foo.lan resolves to 127.0.0.1 as it should. Unfortunately, I still get the same response form ntpq: daemon:~ % sudo ntpq -p ntpq: write to localhost.foo.lan failed: Permission denied Even with my firewall disabled I get this response. What about ntpq -pn? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems since upgrading to 5.3 - found the problem!
On Sat, 22 Jan 2005 02:32, Lowell Gilbert wrote: Ian Moore [EMAIL PROTECTED] writes: On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote: Ian Moore [EMAIL PROTECTED] writes: I've just realised I'm not running a name server at all on my 5.3 system. I have 4.9 installed on this computer too I'd set up the caching server on it, I guess I forgot that step when I installed 5.3. I'll set it up see that makes any difference. Make sure to switch to using domain names that aren't in use by other people... [A common convention is to use .lan or .local as the top-level domain if you are using non-public domain names.] Thanks, I hadn't thought of using a non-existant top level domain. I've changed the hostname to daemon.foo.lan and now localhost.foo.lan resolves to 127.0.0.1 as it should. Unfortunately, I still get the same response form ntpq: daemon:~ % sudo ntpq -p ntpq: write to localhost.foo.lan failed: Permission denied Even with my firewall disabled I get this response. What about ntpq -pn? No, I get the same response from that too. Cheers, -- Ian GPG Key: http://homepages.picknowl.com.au/imoore/imoore.asc pgpjGfhWMjOdi.pgp Description: PGP signature
Re: ntpd problems since upgrading to 5.3
On Tue, Jan 18, 2005 at 07:26:16AM +0100, Christian Hiris wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 January 2005 01:09, John wrote: This is what goes into the log: Jan 17 18:04:29 pearl ntpd[838]: ntpd 4.2.0-a Sun Jan 9 10:58:59 CST 2005 (1) Jan 17 18:04:29 pearl ntpd[838]: bind() fd 7, family 2, port 123, addr 0.0.0.0,in_classd=0 flags=8 fails: Address already in use I can reproduce this, it only happens if you try start more than one ntp-daemons on the same interfaces. Better start this via rc. # killall ntpd # /etc/rc.d/ntpd start Starting ntpd. # /etc/rc.d/ntpd start ntpd already running? (pid=68961). # /etc/rc.d/ntpd stop Stopping ntpd. Thank you, Christian, but I have confirmed that ntp is not running before the attempt that generates that message. # ps ax | grep ntp # killall ntpd No matching processes were found # ntpdc -c peers ntpdc: read: Connection refused So, I think we can be pretty sure at this point that ntpd is NOT running. Then.. I can't use the script to start ntp, because the config parameters are to not start it, so # ntpd Boom! I immediately get the error message that I gave above! If it were already running, I could understand, but my point is that I've been pretty thorough in determining that it is my first attempt to run it that gets this error message. I have also tried running ntpdate before starting ntpd, or not doing it. If I do it, it works correctly, indicating that ntpd is not running, becuase ntpdate will fail if ntpd is running. I have also NOT run ntpdate first (after a reboot) just to prove to myself that there's nothing residual it could leave that would make ntpd complain about this. It's very puzzling! -- John Lind [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems since upgrading to 5.3 - found the problem!
Ian Moore [EMAIL PROTECTED] writes: I've just realised I'm not running a name server at all on my 5.3 system. I have 4.9 installed on this computer too I'd set up the caching server on it, I guess I forgot that step when I installed 5.3. I'll set it up see that makes any difference. Make sure to switch to using domain names that aren't in use by other people... [A common convention is to use .lan or .local as the top-level domain if you are using non-public domain names.] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems since upgrading to 5.3
On Tue, Jan 18, 2005 at 07:23:41AM -0600, John wrote: On Tue, Jan 18, 2005 at 07:26:16AM +0100, Christian Hiris wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 January 2005 01:09, John wrote: This is what goes into the log: Jan 17 18:04:29 pearl ntpd[838]: ntpd 4.2.0-a Sun Jan 9 10:58:59 CST 2005 (1) Jan 17 18:04:29 pearl ntpd[838]: bind() fd 7, family 2, port 123, addr 0.0.0.0,in_classd=0 flags=8 fails: Address already in use I can reproduce this, it only happens if you try start more than one ntp-daemons on the same interfaces. Better start this via rc. # killall ntpd # /etc/rc.d/ntpd start Starting ntpd. # /etc/rc.d/ntpd start ntpd already running? (pid=68961). # /etc/rc.d/ntpd stop Stopping ntpd. Thank you, Christian, but I have confirmed that ntp is not running before the attempt that generates that message. # ps ax | grep ntp # killall ntpd No matching processes were found # ntpdc -c peers ntpdc: read: Connection refused So, I think we can be pretty sure at this point that ntpd is NOT running. Then.. I can't use the script to start ntp, because the config parameters are to not start it, so # ntpd Boom! I immediately get the error message that I gave above! If it were already running, I could understand, but my point is that I've been pretty thorough in determining that it is my first attempt to run it that gets this error message. I have also tried running ntpdate before starting ntpd, or not doing it. If I do it, it works correctly, indicating that ntpd is not running, becuase ntpdate will fail if ntpd is running. I have also NOT run ntpdate first (after a reboot) just to prove to myself that there's nothing residual it could leave that would make ntpd complain about this. It's very puzzling! OK. Get this. I just generated a custom kernel to get rid of all the good stuff that this laptop will never support. It just so happens to be a couple of days later (in CVS terms) than the one I was running. I decided to take a chance and just do the installkernel rather than install the whole world. Now ntpd works. I didn't change any config files, DNS, or anything else - just installed my custom kernel. I still get an error message, but now it simply says no IPv6 interfaces found and runs successfully. Go figure. My best guess is that my prior cvsup of 5-STABLE had something in the kernel environment and ntpd slightly out of sync, with ntpd being ahead of the kernel, and now, even though I didn't do an installworld, that skew was resolved. While rare, it is the possibility of this skew that makes me uncomfortable with cvsup - but having no better plans, I'll keep using it! I may have to figure out how to maintain a local release tree that is behind the -STABLE tree, or something. I truly do not know what the right answer is. -- John Lind [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems since upgrading to 5.3
On Tue, Jan 18, 2005 at 04:04:30PM -0600, John wrote: On Tue, Jan 18, 2005 at 07:23:41AM -0600, John wrote: On Tue, Jan 18, 2005 at 07:26:16AM +0100, Christian Hiris wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 January 2005 01:09, John wrote: This is what goes into the log: Jan 17 18:04:29 pearl ntpd[838]: ntpd 4.2.0-a Sun Jan 9 10:58:59 CST 2005 (1) Jan 17 18:04:29 pearl ntpd[838]: bind() fd 7, family 2, port 123, addr 0.0.0.0,in_classd=0 flags=8 fails: Address already in use I can reproduce this, it only happens if you try start more than one ntp-daemons on the same interfaces. Better start this via rc. # killall ntpd # /etc/rc.d/ntpd start Starting ntpd. # /etc/rc.d/ntpd start ntpd already running? (pid=68961). # /etc/rc.d/ntpd stop Stopping ntpd. Thank you, Christian, but I have confirmed that ntp is not running before the attempt that generates that message. # ps ax | grep ntp # killall ntpd No matching processes were found # ntpdc -c peers ntpdc: read: Connection refused So, I think we can be pretty sure at this point that ntpd is NOT running. Then.. I can't use the script to start ntp, because the config parameters are to not start it, so # ntpd Boom! I immediately get the error message that I gave above! If it were already running, I could understand, but my point is that I've been pretty thorough in determining that it is my first attempt to run it that gets this error message. I have also tried running ntpdate before starting ntpd, or not doing it. If I do it, it works correctly, indicating that ntpd is not running, becuase ntpdate will fail if ntpd is running. I have also NOT run ntpdate first (after a reboot) just to prove to myself that there's nothing residual it could leave that would make ntpd complain about this. It's very puzzling! OK. Get this. I just generated a custom kernel to get rid of all the good stuff that this laptop will never support. It just so happens to be a couple of days later (in CVS terms) than the one I was running. I decided to take a chance and just do the installkernel rather than install the whole world. Now ntpd works. I didn't change any config files, DNS, or anything else - just installed my custom kernel. I still get an error message, but now it simply says no IPv6 interfaces found and runs successfully. Go figure. My best guess is that my prior cvsup of 5-STABLE had something in the kernel environment and ntpd slightly out of sync, with ntpd being ahead of the kernel, and now, even though I didn't do an installworld, that skew was resolved. While rare, it is the possibility of this skew that makes me uncomfortable with cvsup - but having no better plans, I'll keep using it! I may have to figure out how to maintain a local release tree that is behind the -STABLE tree, or something. I truly do not know what the right answer is. Wow! Now my mind is REALLY blown! Look at the following consecutive runs of ntpdc just a few minutes part, with nothing else going on in between: pearl# !! ntpdc -c peers remote local st poll reach delay offsetdisp === =dexter.starfire 192.168.1.53 3 256 17 0.00026 0.023755 0.93869 =dauntless.starf 192.168.1.53 4 256 17 0.00053 0.016804 0.93942 pearl# pwd /home/john pearl# !nt ntpdc -c peers remote local st poll reach delay offsetdisp === =dexter.starfire 192.168.1.53 3 641 0.00026 0.035822 7.93750 =dauntless.starf 192.168.1.53 4 641 0.00061 0.035934 7.93750 pearl# ps ax | grep ntp 751 ?? Ss 0:00.05 ntpd pearl# That last line is me confirming that it's still the same PID for ntpd. What happened here? The reachability mask went from 17 to 1, the dispersion popped WAY up, the offset increased, and the polling time went down. Maybe this is normal for ntpd in some set of circumstance, but I've not seen it before. The other odd thing, and I haven't shown you enough runs to demonstrate it, is that the offset was INCREASING prior to this apparent reset. Maybe it failed to converge and started over? But the polling interval kept increasing... Anybody know what just happened? -- John Lind [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems since upgrading to 5.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 January 2005 23:14, John wrote: On Tue, Jan 18, 2005 at 04:04:30PM -0600, John wrote: On Tue, Jan 18, 2005 at 07:23:41AM -0600, John wrote: On Tue, Jan 18, 2005 at 07:26:16AM +0100, Christian Hiris wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 January 2005 01:09, John wrote: This is what goes into the log: Jan 17 18:04:29 pearl ntpd[838]: ntpd 4.2.0-a Sun Jan 9 10:58:59 CST 2005 (1) Jan 17 18:04:29 pearl ntpd[838]: bind() fd 7, family 2, port 123, addr 0.0.0.0,in_classd=0 flags=8 fails: Address already in use I can reproduce this, it only happens if you try start more than one ntp-daemons on the same interfaces. Better start this via rc. # killall ntpd # /etc/rc.d/ntpd start Starting ntpd. # /etc/rc.d/ntpd start ntpd already running? (pid=68961). # /etc/rc.d/ntpd stop Stopping ntpd. Thank you, Christian, but I have confirmed that ntp is not running before the attempt that generates that message. # ps ax | grep ntp # killall ntpd No matching processes were found # ntpdc -c peers ntpdc: read: Connection refused So, I think we can be pretty sure at this point that ntpd is NOT running. Then.. I can't use the script to start ntp, because the config parameters are to not start it, so # ntpd Boom! I immediately get the error message that I gave above! If it were already running, I could understand, but my point is that I've been pretty thorough in determining that it is my first attempt to run it that gets this error message. I have also tried running ntpdate before starting ntpd, or not doing it. If I do it, it works correctly, indicating that ntpd is not running, becuase ntpdate will fail if ntpd is running. I have also NOT run ntpdate first (after a reboot) just to prove to myself that there's nothing residual it could leave that would make ntpd complain about this. It's very puzzling! OK. Get this. I just generated a custom kernel to get rid of all the good stuff that this laptop will never support. It just so happens to be a couple of days later (in CVS terms) than the one I was running. I decided to take a chance and just do the installkernel rather than install the whole world. Now ntpd works. I didn't change any config files, DNS, or anything else - just installed my custom kernel. I still get an error message, but now it simply says no IPv6 interfaces found and runs successfully. Go figure. My best guess is that my prior cvsup of 5-STABLE had something in the kernel environment and ntpd slightly out of sync, with ntpd being ahead of the kernel, and now, even though I didn't do an installworld, that skew was resolved. While rare, it is the possibility of this skew that makes me uncomfortable with cvsup - but having no better plans, I'll keep using it! I may have to figure out how to maintain a local release tree that is behind the -STABLE tree, or something. I truly do not know what the right answer is. Wow! Now my mind is REALLY blown! Look at the following consecutive runs of ntpdc just a few minutes part, with nothing else going on in between: pearl# !! ntpdc -c peers remote local st poll reach delay offsetdisp === =dexter.starfire 192.168.1.53 3 256 17 0.00026 0.023755 0.93869 =dauntless.starf 192.168.1.53 4 256 17 0.00053 0.016804 0.93942 pearl# pwd /home/john pearl# !nt ntpdc -c peers remote local st poll reach delay offsetdisp === =dexter.starfire 192.168.1.53 3 641 0.00026 0.035822 7.93750 =dauntless.starf 192.168.1.53 4 641 0.00061 0.035934 7.93750 pearl# ps ax | grep ntp 751 ?? Ss 0:00.05 ntpd pearl# That last line is me confirming that it's still the same PID for ntpd. What happened here? The reachability mask went from 17 to 1, the dispersion popped WAY up, the offset increased, and the polling time went down. Maybe this is normal for ntpd in some set of circumstance, but I've not seen it before. The other odd thing, and I haven't shown you enough runs to demonstrate it, is that the offset was INCREASING prior to this apparent reset. Maybe it failed to converge and started over? But the polling interval kept increasing... Anybody know what just happened? To me, this behaviour seems to be normal. http://www.eecis.udel.edu/~mills/database/papers/trans.pdf http://www.eecis.udel.edu/~mills/database/papers/allan.pdf Cheers, ch - -- Christian Hiris [EMAIL PROTECTED] | OpenPGP KeyID 0x3BCA53BE OpenPGP-Key at hkp://wwwkeys.eu.pgp.net and http://pgp.mit.edu -BEGIN PGP SIGNATURE- Version:
Re: ntpd problems since upgrading to 5.3
On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote: Ian Moore wrote: Hi, Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been getting the following error on boot: ntpd[380]: bind() fd 7, family 28, port 123, addr fe80:1 ::204:61ff:fe46:be89, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address ntpd seems to be working from what I can see in it's log file, but I can't do anything with ntpq to check it. Wether I run it as my normal user or as root, running ntpq -p always gives: ntpq: write to localhost.foo.com failed: Permission denied I had once a problem with ntpd, when also running named. Some hostname resolution failed, because the servers were started in the wrong order. Are you also running named? Here is my ntpd entries in rc.conf: ntpd_enable=YES # Run ntpd Network Time Protocol (or NO). ntpd_program=/usr/sbin/ntpd # path to ntpd, if you want a different one. ntpd_flags=-c /etc/ntp.conf -p /var/run/ntpd.pid I use: ntpd_enable=YES ntpd_flags=-g and the contents of ntp.conf: server 210.48.130.204 server augean.eleceng.adelaide.edu.au driftfile /var/db/ntpd.drift logfile /var/log/ntpd And here I use: driftfile /var/db/ntpd.drift pidfile /var/run/ntpd.pid server nr1.time.server server nr2.time.server server nr3.time.server OK - this is interesting! I have identical ntp.conf files on my 5.2.1 system and my 5.3-STABLE system. Guess what? The 5.2.1 system works, and the 5.3-STABLE system doesn't. Not only that, but the clock on my 5.3-STABLE system is RACING. It is going at almost twice as fast as real time. Here's the ntp.conf file: # stratum 3 time server server 192.168.1.1 driftfile /var/db/ntp.drift In both cases, name resolution is working. On the 5.2.1 system, ntpdc shows: ntpdc peers remote local st poll reach delay offsetdisp === *dexter.starfire 192.168.1.52 3 64 377 0.00073 0.060184 0.00093 ntpdc On the 5.3-STABLE system, it ntpdc shows: ntpdc peers remote local st poll reach delay offsetdisp === =dexter.starfire 192.168.1.5316 640 0.0 0.00 0.0 ntpdc This shows that DNS is working fine, as the remote name is being correctly resolved. (I know I'm showing some of my IP numbers, but it's all NAT). I'm afraid something is broke! Oh, and ntpdate works on the 5.3 system just fine (when ntpd isn't running, of course). The system that is running 5.3-STABLE was a good time keeper before this update (4.9-STABLE). -- John Lind [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems since upgrading to 5.3
On Mon, Jan 17, 2005 at 12:22:48PM -0600, John wrote: On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote: Ian Moore wrote: Hi, Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been getting the following error on boot: ntpd[380]: bind() fd 7, family 28, port 123, addr fe80:1 ::204:61ff:fe46:be89, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address ntpd seems to be working from what I can see in it's log file, but I can't do anything with ntpq to check it. Wether I run it as my normal user or as root, running ntpq -p always gives: ntpq: write to localhost.foo.com failed: Permission denied I had once a problem with ntpd, when also running named. Some hostname resolution failed, because the servers were started in the wrong order. Are you also running named? Here is my ntpd entries in rc.conf: ntpd_enable=YES # Run ntpd Network Time Protocol (or NO). ntpd_program=/usr/sbin/ntpd # path to ntpd, if you want a different one. ntpd_flags=-c /etc/ntp.conf -p /var/run/ntpd.pid I use: ntpd_enable=YES ntpd_flags=-g and the contents of ntp.conf: server 210.48.130.204 server augean.eleceng.adelaide.edu.au driftfile /var/db/ntpd.drift logfile /var/log/ntpd And here I use: driftfile /var/db/ntpd.drift pidfile /var/run/ntpd.pid server nr1.time.server server nr2.time.server server nr3.time.server OK - this is interesting! I have identical ntp.conf files on my 5.2.1 system and my 5.3-STABLE system. Guess what? The 5.2.1 system works, and the 5.3-STABLE system doesn't. Not only that, but the clock on my 5.3-STABLE system is RACING. It is going at almost twice as fast as real time. Here's the ntp.conf file: # stratum 3 time server server 192.168.1.1 driftfile /var/db/ntp.drift In both cases, name resolution is working. On the 5.2.1 system, ntpdc shows: ntpdc peers remote local st poll reach delay offsetdisp === *dexter.starfire 192.168.1.52 3 64 377 0.00073 0.060184 0.00093 ntpdc On the 5.3-STABLE system, it ntpdc shows: ntpdc peers remote local st poll reach delay offsetdisp === =dexter.starfire 192.168.1.5316 640 0.0 0.00 0.0 ntpdc This shows that DNS is working fine, as the remote name is being correctly resolved. (I know I'm showing some of my IP numbers, but it's all NAT). I'm afraid something is broke! Oh, and ntpdate works on the 5.3 system just fine (when ntpd isn't running, of course). The system that is running 5.3-STABLE was a good time keeper before this update (4.9-STABLE). OK. An update. I ran ntpdate 192.168.1.1 ; ntpdate 192.168.1.1 ; ntpdate 192.168.1.1 and suddenly, I'm keeping time MUCH better! My current theory is that whatever is going wrong with adjkerntz, it messed up the kernel time keeping adjustment, and when I ran ntpdate close enough together that it was able to use adjtime rather than stepping the time, that helped things out greatly. ntpd still doesn't work, but my system is keeping time much better! MUCH better! -- John Lind [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems since upgrading to 5.3
On Mon, Jan 17, 2005 at 12:49:00PM -0600, John wrote: On Mon, Jan 17, 2005 at 12:22:48PM -0600, John wrote: On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote: Ian Moore wrote: Hi, Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been getting the following error on boot: ntpd[380]: bind() fd 7, family 28, port 123, addr fe80:1 ::204:61ff:fe46:be89, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address ntpd seems to be working from what I can see in it's log file, but I can't do anything with ntpq to check it. Wether I run it as my normal user or as root, running ntpq -p always gives: ntpq: write to localhost.foo.com failed: Permission denied I had once a problem with ntpd, when also running named. Some hostname resolution failed, because the servers were started in the wrong order. Are you also running named? Here is my ntpd entries in rc.conf: ntpd_enable=YES # Run ntpd Network Time Protocol (or NO). ntpd_program=/usr/sbin/ntpd # path to ntpd, if you want a different one. ntpd_flags=-c /etc/ntp.conf -p /var/run/ntpd.pid I use: ntpd_enable=YES ntpd_flags=-g and the contents of ntp.conf: server 210.48.130.204 server augean.eleceng.adelaide.edu.au driftfile /var/db/ntpd.drift logfile /var/log/ntpd And here I use: driftfile /var/db/ntpd.drift pidfile /var/run/ntpd.pid server nr1.time.server server nr2.time.server server nr3.time.server OK - this is interesting! I have identical ntp.conf files on my 5.2.1 system and my 5.3-STABLE system. Guess what? The 5.2.1 system works, and the 5.3-STABLE system doesn't. Not only that, but the clock on my 5.3-STABLE system is RACING. It is going at almost twice as fast as real time. Here's the ntp.conf file: # stratum 3 time server server 192.168.1.1 driftfile /var/db/ntp.drift In both cases, name resolution is working. On the 5.2.1 system, ntpdc shows: ntpdc peers remote local st poll reach delay offsetdisp === *dexter.starfire 192.168.1.52 3 64 377 0.00073 0.060184 0.00093 ntpdc On the 5.3-STABLE system, it ntpdc shows: ntpdc peers remote local st poll reach delay offsetdisp === =dexter.starfire 192.168.1.5316 640 0.0 0.00 0.0 ntpdc This shows that DNS is working fine, as the remote name is being correctly resolved. (I know I'm showing some of my IP numbers, but it's all NAT). I'm afraid something is broke! Oh, and ntpdate works on the 5.3 system just fine (when ntpd isn't running, of course). The system that is running 5.3-STABLE was a good time keeper before this update (4.9-STABLE). OK. An update. I ran ntpdate 192.168.1.1 ; ntpdate 192.168.1.1 ; ntpdate 192.168.1.1 and suddenly, I'm keeping time MUCH better! My current theory is that whatever is going wrong with adjkerntz, it messed up the kernel time keeping adjustment, and when I ran ntpdate close enough together that it was able to use adjtime rather than stepping the time, that helped things out greatly. ntpd still doesn't work, but my system is keeping time much better! MUCH better! Stranger and stranger. Well, since ntp kept RUNNING, I neglected to check the logs. Shame on me. This is what goes into the log: Jan 17 18:04:29 pearl ntpd[838]: ntpd 4.2.0-a Sun Jan 9 10:58:59 CST 2005 (1) Jan 17 18:04:29 pearl ntpd[838]: bind() fd 7, family 2, port 123, addr 0.0.0.0,in_classd=0 flags=8 fails: Address already in use HOWEVER, when I do a netstat -na | grep \.12 before running it, there is no matches. After running it (and getting the error, but it stays running, and non-functional), I get: udp4 0 0 192.168.1.53.123 *.* udp6 0 0 fe80:5::206:25ff.123 *.* udp6 0 0 fe80:4::1.123 *.* udp6 0 0 ::1.123*.* udp4 0 0 127.0.0.1.123 *.* udp6 0 0 fe80:1::2d0:59ff.123 *.* udp6 0 0 *.123 *.* udp4 0 0 *.123 *.* I don't get it. It's almost like it's trying to start twice, or forking at the wrong time, or something. Those ports for listening look pretty resonable, but it doesn't work, and it gives that error message. Very odd. It's definitely broke. Who wants to send in the PR? -- John Lind [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems since upgrading to 5.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 January 2005 01:09, John wrote: On Mon, Jan 17, 2005 at 12:49:00PM -0600, John wrote: On Mon, Jan 17, 2005 at 12:22:48PM -0600, John wrote: On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote: Ian Moore wrote: Hi, Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been getting the following error on boot: ntpd[380]: bind() fd 7, family 28, port 123, addr fe80:1 ::204:61ff:fe46:be89, in6_is_addr_multicast=0 flags=0 fails: Can't :: assign requested address ntpd seems to be working from what I can see in it's log file, but I can't do anything with ntpq to check it. Wether I run it as my normal user or as root, running ntpq -p always gives: ntpq: write to localhost.foo.com failed: Permission denied Try to add disable auth to your ntp.conf. I had once a problem with ntpd, when also running named. Some hostname resolution failed, because the servers were started in the wrong order. Are you also running named? Here is my ntpd entries in rc.conf: ntpd_enable=YES # Run ntpd Network Time Protocol (or NO). ntpd_program=/usr/sbin/ntpd # path to ntpd, if you want a different one. ntpd_flags=-c /etc/ntp.conf -p /var/run/ntpd.pid I use: ntpd_enable=YES ntpd_flags=-g and the contents of ntp.conf: server 210.48.130.204 server augean.eleceng.adelaide.edu.au driftfile /var/db/ntpd.drift logfile /var/log/ntpd And here I use: driftfile /var/db/ntpd.drift pidfile /var/run/ntpd.pid server nr1.time.server server nr2.time.server server nr3.time.server OK - this is interesting! I have identical ntp.conf files on my 5.2.1 system and my 5.3-STABLE system. Guess what? The 5.2.1 system works, and the 5.3-STABLE system doesn't. Not only that, but the clock on my 5.3-STABLE system is RACING. It is going at almost twice as fast as real time. Here's the ntp.conf file: # stratum 3 time server server 192.168.1.1 driftfile /var/db/ntp.drift In both cases, name resolution is working. On the 5.2.1 system, ntpdc shows: ntpdc peers remote local st poll reach delay offsetdisp === *dexter.starfire 192.168.1.52 3 64 377 0.00073 0.060184 0.00093 ntpdc On the 5.3-STABLE system, it ntpdc shows: ntpdc peers remote local st poll reach delay offsetdisp === =dexter.starfire 192.168.1.5316 640 0.0 0.00 0.0 ntpdc This shows that DNS is working fine, as the remote name is being correctly resolved. (I know I'm showing some of my IP numbers, but it's all NAT). I'm afraid something is broke! Oh, and ntpdate works on the 5.3 system just fine (when ntpd isn't running, of course). The system that is running 5.3-STABLE was a good time keeper before this update (4.9-STABLE). OK. An update. I ran ntpdate 192.168.1.1 ; ntpdate 192.168.1.1 ; ntpdate 192.168.1.1 and suddenly, I'm keeping time MUCH better! My current theory is that whatever is going wrong with adjkerntz, it messed up the kernel time keeping adjustment, and when I ran ntpdate close enough together that it was able to use adjtime rather than stepping the time, that helped things out greatly. ntpd still doesn't work, but my system is keeping time much better! MUCH better! Stranger and stranger. Well, since ntp kept RUNNING, I neglected to check the logs. Shame on me. This is what goes into the log: Jan 17 18:04:29 pearl ntpd[838]: ntpd 4.2.0-a Sun Jan 9 10:58:59 CST 2005 (1) Jan 17 18:04:29 pearl ntpd[838]: bind() fd 7, family 2, port 123, addr 0.0.0.0,in_classd=0 flags=8 fails: Address already in use HOWEVER, when I do a netstat -na | grep \.12 before running it, there is no matches. After running it (and getting the error, but it stays running, and non-functional), I get: udp4 0 0 192.168.1.53.123 *.* udp6 0 0 fe80:5::206:25ff.123 *.* udp6 0 0 fe80:4::1.123 *.* udp6 0 0 ::1.123*.* udp4 0 0 127.0.0.1.123 *.* udp6 0 0 fe80:1::2d0:59ff.123 *.* udp6 0 0 *.123 *.* udp4 0 0 *.123 *.* I don't get it. It's almost like it's trying to start twice, or forking at the wrong time, or something. Those ports for listening look pretty resonable, but it doesn't work, and it gives that error message. Very odd. It's definitely broke. Who wants to send in the PR? Hi, I also had some problems with ntpd, when I
Re: ntpd problems since upgrading to 5.3
Christian Hiris wrote: On the server ntp.matrix.net I run ntpd with the following config files (This machine still runs 5.3-BETA-4): # cat /etc/rc.conf | grep ntp ntpdate_flags=-b clock.netcetera.dk tick.keso.fi ntpdate_enable=YES ntpd_enable=YES - - No need for ntpdate -b. Following has same effect, using the time servers from ntp.conf: xntpd_enable=YES xntpd_flags=-g At least, that's how I use it. Rob. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
