Friday, September 7, 2007, 10:23:49 PM, you wrote:
> Did you do a "service ntpd restart"?
Sure!
> Yes, ntpdate requires you to pass it a clock server. I made a minor
> boo-boo in saying the /etc/rc.d/init.d/ntpd script uses the clock
> sources from ntpservers...it uses step-tickers. If you see the startup
> message "Synchronizing with time server:", then it's trying the ntpdate
> command. If it comes up with "[OK]", then it succeeded and the ntpd
> daemon SHOULD be able to keep you in sync (unless your clock is REALLY
> fast...in which case you have other problems).
> The actual ntpd daemon startup is indicated by the startup message
> "Starting ntpd".
I get everywhere 'OK', but it still doesn't work...
Here's the log, I was just typing the commands one by one:
[root@frontend ~]# date
Fri Sep 7 23:21:29 MSD 2007
[root@frontend ~]# service ntpd restart
Shutting down ntpd: [ OK ]
ntpd: Synchronizing with time server: [ OK ]
Starting ntpd: [ OK ]
[root@frontend ~]# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
andromeda.cs.pu .CDMA. 1 u 6 64 1 187.712 -46.448 0.002
banana.irc.gr 192.36.134.25 2 u 5 64 1 160.135 -67.667 0.002
b.pool.ntp.uq.e 130.102.152.7 2 u 4 64 1 550.855 4.548 0.002
[root@frontend ~]# ntpstat
unsynchronised
time server re-starting
polling server every 64 s
[root@frontend ~]# date
Fri Sep 7 23:21:59 MSD 2007
[root@frontend ~]#
Here's the corresponding part of /var/log/messages:
Sep 7 23:21:35 frontend ntpd[4088]: ntpd exiting on signal 15
Sep 7 23:21:39 frontend ntpdate[4115]: step time server 66.187.224.4 offset -0.344342 sec
Sep 7 23:21:39 frontend ntpd[4117]: ntpd 4.2.4p2@xxxxxxxx Tue Aug 21 14:07:56 UTC 2007 (1)
Sep 7 23:21:39 frontend ntpd[4118]: precision = 2.000 usec
Sep 7 23:21:39 frontend ntpd[4118]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Sep 7 23:21:39 frontend ntpd[4118]: Listening on interface #1 wildcard, ::#123 Disabled
Sep 7 23:21:39 frontend ntpd[4118]: Listening on interface #2 lo, ::1#123 Enabled
Sep 7 23:21:39 frontend ntpd[4118]: Listening on interface #3 eth0, fe80::230:5ff:fe22:857#123 Enabled
Sep 7 23:21:39 frontend ntpd[4118]: Listening on interface #4 lo, 127.0.0.1#123 Enabled
Sep 7 23:21:39 frontend ntpd[4118]: Listening on interface #5 eth0, 172.23.0.133#123 Enabled
Sep 7 23:21:39 frontend ntpd[4118]: kernel time sync status 0040
Sep 7 23:21:39 frontend ntpd[4118]: frequency initialized 0.000 PPM from /var/lib/ntp/drift
> Just for your info, here are my files:
> [root@golem3 ~]# cat /etc/ntp/ntpservers
> clock.redhat.com
> clock2.redhat.com
> [root@golem3 ~]# cat /etc/ntp/step-tickers
> clock.redhat.com
> clock2.redhat.com
> Works fine for me.
I have the same now. And it doesn't work. And I see no reason...
> You do have port 123 open on your firewall, right?
I have my firewall disabled at all. So all ports are open.
And other PCs on my home LAN are syncing just fine, so it's not a
provider's fault.
Uhhh...
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
