ntp

Tue Feb 28 15:50:42 UTC 2012

On Mon, 2012-02-27 at 22:15 +0000, Patrick Dupre wrote: 
> On Mon, 27 Feb 2012, Patrick Dupre wrote:
> 
> > Hello,
> >
> > My machine (fedora 16) does not synchronize its time.
> > ntpd is running, but ntpdate 0.fedora.pool.ntp.org
> > generate an error:
> > 27 Feb 21:44:29 ntpdate[3184]: the NTP socket is in use, exiting
> >
> > Here is my ntp.conf
> >
> >
> > # For more information about this file, see the man pages
> > # ntp.conf(5), ntp_acc(5), ntp_auth(5), ntp_clock(5), ntp_misc(5), 
> > ntp_mon(5).
> >
> > driftfile /var/lib/ntp/drift
> >
> > # Permit time synchronization with our time source, but do not
> > # permit the source to query or modify the service on this system.
> > restrict default kod nomodify notrap nopeer noquery
> > restrict -6 default kod nomodify notrap nopeer noquery
> >
> > # Permit all access over the loopback interface.  This could
> > # be tightened as well, but to do so would effect some of
> > # the administrative functions.
> > restrict 127.0.0.1
> > restrict -6 ::1
> >
> > # Hosts on local network are less restricted.
> > #restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap
> >
> > # Use public servers from the pool.ntp.org project.
> > # Please consider joining the pool (http://www.pool.ntp.org/join.html).
> > server 0.fedora.pool.ntp.org iburst
> > server 1.fedora.pool.ntp.org iburst
> > server 2.fedora.pool.ntp.org iburst
> > server 3.fedora.pool.ntp.org iburst
> >
> > #broadcast 192.168.1.255 autokey	# broadcast server
> > #broadcastclient			# broadcast client
> > #broadcast 224.0.1.1 autokey		# multicast server
> > #multicastclient 224.0.1.1		# multicast client
> > #manycastserver 239.255.254.254		# manycast server
> > #manycastclient 239.255.254.254 autokey # manycast client
> >
> > # Undisciplined Local Clock. This is a fake driver intended for backup
> > # and when no outside source of synchronized time is available.
> > #server	127.127.1.0	# local clock
> > #fudge	127.127.1.0 stratum 10
> >
> > # Enable public key cryptography.
> > #crypto
> >
> > includefile /etc/ntp/crypto/pw
> >
> > # Key file containing the keys and key identifiers used when operating
> > # with symmetric key cryptography.
> > keys /etc/ntp/keys
> >
> > # Specify the key identifiers which are trusted.
> > #trustedkey 4 8 42
> >
> > # Specify the key identifier to use with the ntpdc utility.
> > #requestkey 8
> >
> > # Specify the key identifier to use with the ntpq utility.
> > #controlkey 8
> >
> > # Enable writing of statistics records.
> > #statistics clockstats cryptostats loopstats peerstats
> >
> > =================================================================
> > This is part of the message file:
> >
> >
> >
> > Feb 27 21:22:55 Homere ntpd[2144]: ntpd 4.2.6p4 at 1.2324-o Thu Oct  6 15:37:57 
> > UTC 2011 (1)
> > Feb 27 21:22:55 Homere ntpd[2144]: proto: precision = 0.076 usec
> > Feb 27 21:22:55 Homere ntpd[2144]: 0.0.0.0 c01d 0d kern kernel time sync 
> > enabled
> > Feb 27 21:22:55 Homere ntpd[2144]: Listen and drop on 0 v4wildcard 0.0.0.0 
> > UDP 123
> > Feb 27 21:22:55 Homere ntpd[2144]: Listen and drop on 1 v6wildcard :: UDP 123
> > Feb 27 21:22:55 Homere ntpd[2144]: Listen normally on 2 lo 127.0.0.1 UDP 123
> > Feb 27 21:22:55 Homere ntpd[2144]: Listen normally on 3 p5p1 134.99.120.46 
> > UDP 123
> > Feb 27 21:22:55 Homere ntpd[2144]: Listen normally on 4 p5p1 
> > fe80::225:22ff:fecb:b91a UDP 123
> > Feb 27 21:22:55 Homere ntpd[2144]: Listen normally on 5 lo ::1 UDP 123
> > Feb 27 21:22:55 Homere ntpd[2144]: peers refreshed
> > Feb 27 21:22:55 Homere ntpd[2144]: Listening on routing socket on fd #22 for 
> > interface updates
> > Feb 27 21:22:55 Homere ntpd[2144]: 0.0.0.0 c016 06 restart
> > Feb 27 21:22:55 Homere ntpd[2144]: 0.0.0.0 c012 02 freq_set kernel 0.000 PPM
> > Feb 27 21:22:55 Homere ntpd[2144]: 0.0.0.0 c011 01 freq_not_set
> > Feb 27 21:24:15 Homere ntpd[2144]: ntpd exiting on signal 15
> > Feb 27 21:24:15 Homere ntpd[2147]: ntpd 4.2.6p4 at 1.2324-o Thu Oct  6 15:37:57 
> > UTC 2011 (1)
> > Feb 27 21:24:15 Homere ntpd[2147]: proto: precision = 0.243 usec
> > Feb 27 21:24:15 Homere ntpd[2147]: 0.0.0.0 c01d 0d kern kernel time sync 
> > enabled
> > Feb 27 21:24:15 Homere ntpd[2147]: Listen and drop on 0 v4wildcard 0.0.0.0 
> > UDP 123
> > Feb 27 21:24:15 Homere ntpd[2147]: Listen and drop on 1 v6wildcard :: UDP 123
> > Feb 27 21:24:15 Homere ntpd[2147]: Listen normally on 2 lo 127.0.0.1 UDP 123
> > Feb 27 21:24:15 Homere ntpd[2147]: Listen normally on 3 p5p1 134.99.120.46 
> > UDP 123
> > Feb 27 21:24:15 Homere ntpd[2147]: Listen normally on 4 p5p1 
> > fe80::225:22ff:fecb:b91a UDP 123
> > Feb 27 21:24:15 Homere ntpd[2147]: Listen normally on 5 lo ::1 UDP 123
> > Feb 27 21:24:15 Homere ntpd[2147]: peers refreshed
> > Feb 27 21:24:15 Homere ntpd[2147]: Listening on routing socket on fd #22 for 
> > interface updates
> > Feb 27 21:24:15 Homere ntpd[2147]: 0.0.0.0 c016 06 restart
> > Feb 27 21:24:15 Homere ntpd[2147]: 0.0.0.0 c012 02 freq_set kernel 0.000 PPM
> > Feb 27 21:24:15 Homere ntpd[2147]: 0.0.0.0 c011 01 freq_not_set
> > Feb 27 21:24:19 Homere ntpd[2147]: ntpd exiting on signal 15
> > Feb 27 21:24:19 Homere ntpd[2149]: ntpd 4.2.6p4 at 1.2324-o Thu Oct  6 15:37:57 
> > UTC 2011 (1)
> > Feb 27 21:24:19 Homere ntpd[2149]: proto: precision = 0.278 usec
> > Feb 27 21:24:19 Homere ntpd[2149]: 0.0.0.0 c01d 0d kern kernel time sync 
> > enabled
> > Feb 27 21:24:19 Homere ntpd[2149]: Listen and drop on 0 v4wildcard 0.0.0.0 
> > UDP 123
> > Feb 27 21:24:19 Homere ntpd[2149]: Listen and drop on 1 v6wildcard :: UDP 123
> > Feb 27 21:24:19 Homere ntpd[2149]: Listen normally on 2 lo 127.0.0.1 UDP 123
> > Feb 27 21:24:19 Homere ntpd[2149]: Listen normally on 3 p5p1 134.99.120.46 
> > UDP 123
> > Feb 27 21:24:19 Homere ntpd[2149]: Listen normally on 4 p5p1 
> > fe80::225:22ff:fecb:b91a UDP 123
> > Feb 27 21:24:19 Homere ntpd[2149]: Listen normally on 5 lo ::1 UDP 123
> > Feb 27 21:24:19 Homere ntpd[2149]: peers refreshed
> > Feb 27 21:24:19 Homere ntpd[2149]: Listening on routing socket on fd #22 for 
> > interface updates
> > Feb 27 21:24:19 Homere ntpd[2149]: 0.0.0.0 c016 06 restart
> > Feb 27 21:24:19 Homere ntpd[2149]: 0.0.0.0 c012 02 freq_set kernel 0.000 PPM
> > Feb 27 21:24:19 Homere ntpd[2149]: 0.0.0.0 c011 01 freq_not_set
> >
> >
> 
> I can that if I run system-config-date
> If I check the synchronize date and time over the network
> then it kill the ntpd server and vice et versa.
> 
> What is wrong?
As yo were told., you can't run chrony and ntpd at the same time. And be
sure in the Time Zone display of system-config-date you chose the UTC
option.


-- 
=======================================================================
All God's children are not beautiful. Most of God's children are, in
fact, barely presentable. -- Fran Lebowitz, "Metropolitan Life"
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam at sbcglobal.net