On Saturday 08 September 2007, Andrew Junev wrote: >Saturday, September 8, 2007, 12:37:01 PM, you wrote: >> And that fairly screams that its an selinux problem, one that setting it >> to permissive mode does NOT fix in my experience. > >I disabled selinux already during the installation. > >> Append to the end of the kernel arguments line in your grub.conf, >> 'selinux=0' without the quotes and reboot. If that fixes it, throw it >> back at the selinux mailing list where Stephen Smalley hangs out. > >Hmmm... Although I disabled selinux, I didn't have 'selinux=0' in my >grub.conf. Probably it gets disabled somewhere else. No, that is the only way to shut it completely off. This is a known FC7 problem. Setting it to be permissive as you did in the install is not sufficient to allow ntp to work. >Anyway, I added >this parameter and rebooted the system. Still no changes in ntpd >behavior. > >Sep 8 12:56:10 frontend_light ntpdate[1943]: step time server 66.187.233.4 > offset -65.237699 sec Sep 8 12:56:10 frontend_light ntpd[1945]: ntpd > 4.2.4p2@xxxxxxxx Tue Aug 21 14:07:56 UTC 2007 (1) Sep 8 12:56:10 > frontend_light ntpd[1946]: precision = 1.000 usec >Sep 8 12:56:10 frontend_light ntpd[1946]: Listening on interface #0 > wildcard, 0.0.0.0#123 Disabled Sep 8 12:56:10 frontend_light ntpd[1946]: > Listening on interface #1 wildcard, ::#123 Disabled Sep 8 12:56:10 > frontend_light ntpd[1946]: Listening on interface #2 lo, ::1#123 Enabled > Sep 8 12:56:10 frontend_light ntpd[1946]: Listening on interface #3 eth0, > fe80::230:5ff:fe22:857#123 Enabled Sep 8 12:56:10 frontend_light > ntpd[1946]: Listening on interface #4 lo, 127.0.0.1#123 Enabled Sep 8 > 12:56:10 frontend_light ntpd[1946]: Listening on interface #5 eth0, > 172.23.0.133#123 Enabled Sep 8 12:56:10 frontend_light ntpd[1946]: kernel > time sync status 0040 Sep 8 12:56:11 frontend_light ntpd[1946]: frequency > initialized 0.000 PPM from /var/lib/ntp/drift > > >On my Fedora 6 machine ntpd is working fine: > > 6 Sep 23:13:05 ntpd[2770]: synchronized to 128.10.252.10, stratum 2 > 7 Sep 03:20:43 ntpd[2770]: synchronized to 130.89.164.77, stratum 2 > 7 Sep 04:46:10 ntpd[2770]: synchronized to 128.10.252.10, stratum 2 > 7 Sep 06:47:57 ntpd[2770]: synchronized to 130.89.164.77, stratum 2 > 7 Sep 07:53:58 ntpd[2770]: synchronized to 128.10.252.10, stratum 2 > > >[root@frontend_light ~]# ntpq -p > remote refid st t when poll reach delay offset > jitter > =========================================================================== >=== balthazar.tihld 192.36.144.22 2 u 15 64 377 41.875 -3341.6 > 1648.40 bbs.csie.ncyu.e 220.130.158.71 3 u 13 64 377 364.927 > -3354.8 1646.82 hobbes.macvaerk 193.162.142.71 3 u 14 64 377 > 128.439 -3332.9 1608.39 [root@frontend_light ~]# ntpstat >unsynchronised > time server re-starting And why is it restarting? I don't know the answer there, but someplace in a log, there should be a clue. > polling server every 64 s >[root@frontend_light ~]# -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Never underestimate the bandwidth of a station wagon full of tapes. -- Dr. Warren Jackson, Director, UTCS
