Hi all, I have troubles with a server getting time right. On boot the time is synchronized with the ntp-server of my ISP (xntpd is started at boot). After that nothing seems to be done any more. This machine has a clock, that runs about half an hour behind in 24 hours, so timesync is something, that could be usefull :-) What do I miss?? Leen.
Leen de Braal wrote:
I have troubles with a server getting time right. On boot the time is synchronized with the ntp-server of my ISP (xntpd is started at boot). After that nothing seems to be done any more. This machine has a clock, that runs about half an hour behind in 24 hours, so timesync is something, that could be usefull :-)
What do I miss??
Could be a link typo I discovered a while back. Search for ntp in the Dec 2003 archives for the entire post. -------------------------- The following shows the typo: space:/var/lib/ntp # pwd /var/lib/ntp space:/var/lib/ntp # ls -l drwxr-xr-x 2 ntp nogroup 80 2003-12-04 08:59 drift drwxr-xr-x 2 root root 104 2003-11-20 12:37 etc drwxr-xr-x 4 root root 96 2003-11-12 16:15 var space:/var/lib/ntp # ls -l var/lib/ lrwxrwxrwx 1 root root 4 2003-11-12 16:15 BADntp -> ../. lrwxrwxrwx 1 root root 5 2003-12-03 17:49 ntp -> ../.. Notice that BADntp is a link to ../. while the fix links to ../.. That's two dots after the slash. With the link set to ../.. it works as described in the manual.
At 15:07 29-1-2004 -0700, Gary Hodges wrote:
Leen de Braal wrote:
I have troubles with a server getting time right. On boot the time is synchronized with the ntp-server of my ISP (xntpd is started at boot). After that nothing seems to be done any more. This machine has a clock, that runs about half an hour behind in 24 hours, so timesync is something, that could be usefull :-)
What do I miss??
Could be a link typo I discovered a while back. Search for ntp in the Dec 2003 archives for the entire post.
-------------------------- The following shows the typo:
space:/var/lib/ntp # pwd /var/lib/ntp space:/var/lib/ntp # ls -l drwxr-xr-x 2 ntp nogroup 80 2003-12-04 08:59 drift drwxr-xr-x 2 root root 104 2003-11-20 12:37 etc drwxr-xr-x 4 root root 96 2003-11-12 16:15 var space:/var/lib/ntp # ls -l var/lib/ lrwxrwxrwx 1 root root 4 2003-11-12 16:15 BADntp -> ../. lrwxrwxrwx 1 root root 5 2003-12-03 17:49 ntp -> ../..
Notice that BADntp is a link to ../. while the fix links to ../.. That's two dots after the slash. With the link set to ../.. it works as described in the manual.
I did not have a BADntp link at all (suse9). I made one like above. But I did have the ntp link, and this one had ../. (so one dot). I also changed this, and have also been putting a second server in the ntp.conf. I restarted, we will see tomorrow if this is kept up to date. Txs
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
The Friday 2004-01-30 at 19:28 +0100, Leen de Braal wrote:
At 15:07 29-1-2004 -0700, Gary Hodges wrote:
lrwxrwxrwx 1 root root 4 2003-11-12 16:15 BADntp -> ../. lrwxrwxrwx 1 root root 5 2003-12-03 17:49 ntp -> ../..
I did not have a BADntp link at all (suse9).
Of course not. :-) He renamed the old ntp link to BADntp, because it is bad, and created a new correct one. -- Cheers, Carlos Robinson
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 29 Jan 2004 21:58:32 +0100 Leen de Braal <ldb@braha.nl> wrote:
Hi all,
I have troubles with a server getting time right. On boot the time is synchronized with the ntp-server of my ISP (xntpd is started at boot). After that nothing seems to be done any more. This machine has a clock, that runs about half an hour behind in 24 hours, so timesync is something, that could be usefull :-) The first thing to to is to check your logs: /var/log/ntp. This might give you an indication of the problem.
You probably should have more than one ntp server selected. Normally, at boot time, the system runs ntpdate to set your date, then while the system is operational it runs ntpd. Make sure that /usr/sbin/ntpd or /usr/sbin/xntpd is running. You can use the run level editor to enable this service. - -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAGmyk+wA+1cUGHqkRAnfEAJ97VUPNy5+BSzuIo6Z7H+CnnL/RmACeLdyr u4tVeY6PGUEFwZ7OQjuFLgk= =SAP4 -----END PGP SIGNATURE-----
On Thursday 29 January 2004 8:58 pm, Leen de Braal wrote:
Hi all,
I have troubles with a server getting time right. On boot the time is synchronized with the ntp-server of my ISP (xntpd is started at boot). After that nothing seems to be done any more. This machine has a clock, that runs about half an hour behind in 24 hours, so timesync is something, that could be usefull :-)
What do I miss??
You may be interested in this article on how to set up an ntp sevice for your LAN... <http://networking.earthweb.com/netsysm/article.php/10954_3302411_1> | Keeping Accurate Time on Linux | January 22, 2004 | By Carla Schroder rather timely shall we say??? One thing, did you create a driftfile for your service to calculate drift rate??? and the other, are you on dialup and are not running ntpdate everytime you connect to the internet??? the article will tell you how and why...
At 21:59 30-1-2004 +0000, Paul Cooke wrote:
On Thursday 29 January 2004 8:58 pm, Leen de Braal wrote:
Hi all,
I have troubles with a server getting time right. On boot the time is synchronized with the ntp-server of my ISP (xntpd is started at boot). After that nothing seems to be done any more. This machine has a clock, that runs about half an hour behind in 24 hours, so timesync is something, that could be usefull :-)
What do I miss??
You may be interested in this article on how to set up an ntp sevice for your LAN...
<http://networking.earthweb.com/netsysm/article.php/10954_3302411_1> | Keeping Accurate Time on Linux | January 22, 2004 | By Carla Schroder
rather timely shall we say???
One thing, did you create a driftfile for your service to calculate drift rate??? and the other, are you on dialup and are not running ntpdate everytime you connect to the internet???
the article will tell you how and why...
Indeed really helpfull. And the suggestion Gary gave by saying that it might be a firewall issue hit the nail: udp123 was open on the outside, but not from inside-out. Opening up made the peers appear. The article helps to tweak the system. I think it works OK now. Thank you guys :-)
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (5)
-
Carlos E. R. -
Gary Hodges -
Jerry Feldman -
Leen de Braal -
Paul Cooke