FedoraForum.org - Fedora Support Forums and Community
Page 1 of 2 12 LastLast
Results 1 to 15 of 30
  1. #1
    Join Date
    Oct 2006
    Posts
    44
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    time on server advances very slowly

    I have a fedora 12 server on which the time is advancing very slowly, 1 sec every 20 sec .
    Does anyone have an idea what is wrong?

    Thanks,
    F.

  2. #2
    Join Date
    Oct 2005
    Location
    GMT
    Posts
    3,242
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    It may be slowing down to synchronize with a NTP server... Have you setup NTP recently? Or it maybe a problem with an old CMOS battery that needs replacement
    Asus K55VD, i5 3230M - Productivity/Programming (F28)
    Asus M32CD - i7-6700, Asus STRIX-GTX970-DC2OC-4GD, 1x8 GB Sk Hynix 2133 MHz DDR4 - Gaming (W10)

  3. #3
    Join Date
    Oct 2006
    Posts
    44
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    The time advances slowly, synchronized or not to an NTP server. It is probably the battery then. Il will change it.

    Thanks,
    F

  4. #4
    Join Date
    Oct 2005
    Location
    GMT
    Posts
    3,242
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Just to clarify my question: Synchronization to a NTP server is done in small steps, accelerating or slowing down the system clock until it is synchronized with the NTP server. This is to prevent some programs that rely on system time to malfunction if the time changes suddenly.
    Asus K55VD, i5 3230M - Productivity/Programming (F28)
    Asus M32CD - i7-6700, Asus STRIX-GTX970-DC2OC-4GD, 1x8 GB Sk Hynix 2133 MHz DDR4 - Gaming (W10)

  5. #5
    Join Date
    Oct 2006
    Posts
    44
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Well, I synchronized to an NTP server probably end of January or beginning of February.

    I just changed the battery and the time seems to advance normally. I'll check again tomorrow.

    F.

  6. #6
    Join Date
    Oct 2006
    Posts
    44
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I bought a new battery and put it in my server yesterday at 09:00 AM. I rebooted it. The time was synchronized to an NTP server. Since then, my server lost 10 min until now (11:46 AM).

    What can possibly slow down the time like that?

    Fujisan

  7. #7
    Join Date
    Oct 2005
    Location
    GMT
    Posts
    3,242
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Is ntpd running? Please post the output of
    Code:
    ps -ef |grep ntpd |grep -v grep
    If it is, that is, you get something like
    Code:
    ntp       8927     1  0 15:36 ?        00:00:00 ntpd -u ntp:ntp -p /var/run/ntpd.pid -g
    what does
    Code:
    ntpq -p
    give? If it's something like
    Code:
         remote           refid      st t when poll reach   delay   offset  jitter
    ==============================================================================
     ntp1.inrim.it   .INIT.          16 u    -   64    0    0.000    0.000   0.000
     ntp2.inrim.it   .INIT.          16 u    -   64    0    0.000    0.000   0.002
    (i.e. all zeros) then you've probably have a firewall somewhere stopping the protocol from going through.
    If the server is not running (i.e. you don't get any output from first command), run
    Code:
    su -c "service ntpd start"
    Asus K55VD, i5 3230M - Productivity/Programming (F28)
    Asus M32CD - i7-6700, Asus STRIX-GTX970-DC2OC-4GD, 1x8 GB Sk Hynix 2133 MHz DDR4 - Gaming (W10)

  8. #8
    Join Date
    Oct 2006
    Posts
    44
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    ntpd is up and running:

    Code:
    # ps -ef |grep ntpd |grep -v grep
    ntp       1459     1  0 12:03 ?        00:00:00 ntpd -u ntp:ntp -p /var/run/ntpd.pid -g
    # ntpd -q
    #
    ntpd -q gives nothing.

    I have a firewall. here is the log:

    Code:
     Date/Time	Source Address/Port	Destination Address/Port	Translated Source Address/Port	Translated Destination Address/Port	Service	Duration	Bytes Sent	Bytes Received
    2010-03-02 16:38:05	10.0.21.17:123	91.121.45.45:123	10.0.21.17:123	91.121.45.45:123	NETWORK TIME	62 sec.	94	98
    2010-03-02 16:37:59	10.0.21.17:123	81.93.183.116:123	10.0.21.17:123	81.93.183.116:123	NETWORK TIME	59 sec.	94	98
    2010-03-02 16:37:43	10.0.21.17:123	88.191.108.178:123	10.0.21.17:123	88.191.108.178:123	NETWORK TIME	62 sec.	94	98
    2010-03-02 16:37:13	10.0.21.17:123	193.55.167.2:123	10.0.21.17:123	193.55.167.2:123	NETWORK TIME	61 sec.	94	98
    F.

  9. #9
    Join Date
    Oct 2005
    Location
    GMT
    Posts
    3,242
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    It's the other way round
    Code:
    ntpq -p
    Asus K55VD, i5 3230M - Productivity/Programming (F28)
    Asus M32CD - i7-6700, Asus STRIX-GTX970-DC2OC-4GD, 1x8 GB Sk Hynix 2133 MHz DDR4 - Gaming (W10)

  10. #10
    Join Date
    Oct 2006
    Posts
    44
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    In /var/log/messages, I have:
    Code:
    Mar  2 12:03:07  ntpd[1459]: precision = 1000.499 usec
    Mar  2 12:03:07  ntpd[1459]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
    Mar  2 12:03:07  ntpd[1459]: Listening on interface #1 wildcard, ::#123 Disabled
    Mar  2 12:03:07  ntpd[1459]: Listening on interface #2 eth0, fe80::206:5bff:fefc:bd96#123 Enabled
    Mar  2 12:03:07  ntpd[1459]: Listening on interface #3 lo, ::1#123 Enabled
    Mar  2 12:03:07  ntpd[1459]: Listening on interface #4 lo, 127.0.0.1#123 Enabled
    Mar  2 12:03:07  ntpd[1459]: Listening on interface #5 eth0, 10.0.21.17#123 Enabled
    Mar  2 12:03:07  ntpd[1459]: Listening on routing socket on fd #22 for interface updates
    Mar  2 12:03:07  ntpd[1459]: kernel time sync status 0040
    Mar  2 12:03:07  ntpd[1459]: frequency initialized 499.647 PPM from /var/lib/ntp/drift
    Mar  2 12:06:20  ntpd[1459]: synchronized to LOCAL(0), stratum 5
    Mar  2 12:06:20  ntpd[1459]: kernel time sync status change 0001
    Mar  2 12:07:25  ntpd[1459]: synchronized to 88.191.108.178, stratum 2
    Mar  2 12:10:39  ntpd[1459]: synchronized to 91.121.45.45, stratum 2
    Mar  2 12:10:42  ntpd[1459]: synchronized to 88.191.108.178, stratum 2
    Mar  2 12:21:28  ntpd[1459]: synchronized to 91.121.45.45, stratum 2
    Mar  2 12:22:30  ntpd[1459]: time reset -5.077425 s
    Mar  2 12:26:00  ntpd[1459]: synchronized to LOCAL(0), stratum 5
    Mar  2 12:26:58  ntpd[1459]: synchronized to 81.93.183.116, stratum 2
    Mar  2 12:33:24  ntpd[1459]: synchronized to 91.121.45.45, stratum 2
    Mar  2 12:35:12  ntpd[1459]: synchronized to LOCAL(0), stratum 5
    Mar  2 12:35:31  ntpd[1459]: synchronized to 88.191.108.178, stratum 2
    Mar  2 12:36:15  ntpd[1459]: synchronized to LOCAL(0), stratum 5


    ---------- Post added at 03:59 PM CST ---------- Previous post was at 03:54 PM CST ----------

    Sorry,
    but this gives me the help message.

    Code:
    # ntpd -p
    ntpd: option `pidfile' requires an argument
    ntpd - NTP daemon program - Ver. 4.2.4p7
    USAGE:  ntpd [ -<flag> [<val>] | --<name>[{=| }<val>] ]...
      Flg Arg Option-Name    Description
       -4 no  ipv4           Force IPv4 DNS name resolution
       -6 no  ipv6           Force IPv6 DNS name resolution
       -a no  authreq        Require crypto authentication
       -A no  authnoreq      Do not require crypto authentication
       -b no  bcastsync      Allow us to sync to broadcast servers
       -c Str configfile     configuration file name
       -d no  debug-level    Increase output debug message level
       -D Str set-debug-level Set the output debug message level
       -f Str driftfile      frequency drift file name
       -g no  panicgate      Allow the first adjustment to be Big
       -i Str jaildir        Jail directory
       -I Str interface      Listen on interface
       -k Str keyfile        path to symmetric keys
       -l Str logfile        path to the log file
       -L no  novirtualips   Do not listen to virtual IPs
       -n no  nofork         Do not fork
       -N no  nice           Run at high priority
       -p Str pidfile        path to the PID file
       -P Num priority       Process priority
       -q no  quit           Set the time and quit
       -r Str propagationdelay Broadcast/propagation delay
       -U Num updateinterval interval in seconds between scans for new or dropped interfaces
       -s Str statsdir       Statistics file location
       -t Str trustedkey     Trusted key number
       -u Str user           Run as userid (or userid:groupid)
       -v Str var            make ARG an ntp variable (RW)
       -V Str dvar           make ARG an ntp variable (RW|DEF)
       -x no  slew           Slew up to 600 seconds
       -m no  mlock          Lock memory
       -v opt version        Output version information and exit
       -? no  help           Display usage information and exit
       -! no  more-help      Extended usage information passed thru pager
    
    Options are specified by doubled hyphens and their name
    or by a single hyphen and the flag character.
    
    please send bug reports to:  http://bugs.ntp.org, bugs@ntp.org
    and if i run
    Code:
    ntpd -p /var/run/ntpd.pid
    I get this in /var/log/messages:
    Code:
    Mar  2 15:54:38  ntpd[2278]: precision = 1000.500 usec
    Mar  2 15:54:38  ntpd[2278]: unable to bind to wildcard socket address 0.0.0.0 - another process may be running - EXITING

    Quote Originally Posted by giulix
    It's the other way round
    Code:
    ntpq -p

  11. #11
    Join Date
    Oct 2005
    Location
    GMT
    Posts
    3,242
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    It's still (wrong)
    Code:
    ntpd -p
    and not (right)
    Code:
    ntpq -p
    Try also
    Code:
    su -c ntpdate
    Asus K55VD, i5 3230M - Productivity/Programming (F28)
    Asus M32CD - i7-6700, Asus STRIX-GTX970-DC2OC-4GD, 1x8 GB Sk Hynix 2133 MHz DDR4 - Gaming (W10)

  12. #12
    Join Date
    Oct 2006
    Posts
    44
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I definitely need a rest.

    Code:
    # ntpq -p
         remote           refid      st t when poll reach   delay   offset  jitter
    ==============================================================================
    *LOCAL(0)        .LOCL.           5 l   32   64  377    0.000    0.000   0.977
     ntp1.adviseo.ne 195.66.241.2     2 u   32  128  377   19.104  77084.3 2675.96
     ns.gansta93.com 192.93.2.20      2 u   36  128  377   19.838  77084.6 2675.62
     eth0-casterlyro 207.3.130.6      2 u   32  128  377   18.811  77085.8 2675.45
     matterhorn.arbo 193.190.230.65   2 u   93  128  377   22.770  77119.0 3122.65


    ---------- Post added at 04:08 PM CST ---------- Previous post was at 04:07 PM CST ----------

    aah?
    Code:
    # ntpdate
     2 Mar 16:06:18 ntpdate[2318]: no servers can be used, exiting

  13. #13
    Join Date
    Aug 2006
    Location
    /dev/realm/{Abba,Carpenters,...stage}
    Posts
    3,285
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by fujisan
    In /var/log/messages, I have:
    Code:
    Mar  2 12:03:07  ntpd[1459]: precision = 1000.499 usec
    Mar  2 12:03:07  ntpd[1459]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
    Mar  2 12:03:07  ntpd[1459]: Listening on interface #1 wildcard, ::#123 Disabled
    Mar  2 12:03:07  ntpd[1459]: Listening on interface #2 eth0, fe80::206:5bff:fefc:bd96#123 Enabled
    Mar  2 12:03:07  ntpd[1459]: Listening on interface #3 lo, ::1#123 Enabled
    Mar  2 12:03:07  ntpd[1459]: Listening on interface #4 lo, 127.0.0.1#123 Enabled
    Mar  2 12:03:07  ntpd[1459]: Listening on interface #5 eth0, 10.0.21.17#123 Enabled
    Mar  2 12:03:07  ntpd[1459]: Listening on routing socket on fd #22 for interface updates
    Mar  2 12:03:07  ntpd[1459]: kernel time sync status 0040
    Mar  2 12:03:07  ntpd[1459]: frequency initialized 499.647 PPM from /var/lib/ntp/drift
    Mar  2 12:06:20  ntpd[1459]: synchronized to LOCAL(0), stratum 5
    Mar  2 12:06:20  ntpd[1459]: kernel time sync status change 0001
    Mar  2 12:07:25  ntpd[1459]: synchronized to 88.191.108.178, stratum 2
    Mar  2 12:10:39  ntpd[1459]: synchronized to 91.121.45.45, stratum 2
    Mar  2 12:10:42  ntpd[1459]: synchronized to 88.191.108.178, stratum 2
    Mar  2 12:21:28  ntpd[1459]: synchronized to 91.121.45.45, stratum 2
    Mar  2 12:22:30  ntpd[1459]: time reset -5.077425 s
    Mar  2 12:26:00  ntpd[1459]: synchronized to LOCAL(0), stratum 5
    Mar  2 12:26:58  ntpd[1459]: synchronized to 81.93.183.116, stratum 2
    Mar  2 12:33:24  ntpd[1459]: synchronized to 91.121.45.45, stratum 2
    Mar  2 12:35:12  ntpd[1459]: synchronized to LOCAL(0), stratum 5
    Mar  2 12:35:31  ntpd[1459]: synchronized to 88.191.108.178, stratum 2
    Mar  2 12:36:15  ntpd[1459]: synchronized to LOCAL(0), stratum 5


    It's synchronized alright. Do you run your server in a virtual machine ?
    For safer browsing, use OpenDNS nameservers 208.67.222.222 and 208.67.220.220

    SELinux User Guide

    AutoPager

  14. #14
    Join Date
    Oct 2006
    Posts
    44
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    No, the server is Fedora 10, native.

  15. #15
    Join Date
    Oct 2006
    Posts
    44
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    It says it is synchronized, but still the time on my server is not the correct time compared to the time on my desktop.

    ---------- Post added at 09:42 AM CST ---------- Previous post was at 09:30 AM CST ----------

    I pulled out all the ntpd messages from /var/log/messages on my server and my desktop:

    Server:
    Code:
    Mar  2 11:43:23 ntpd[2299]: ntpd exiting on signal 15
    Mar  2 11:43:23 ntpd[1331]: ntpd 4.2.4p7@1.1607-o Wed Dec  9 11:59:30 UTC 2009 (1)
    Mar  2 11:43:23 ntpd[1332]: precision = 1000.499 usec
    Mar  2 11:43:23 ntpd[1332]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
    Mar  2 11:43:23 ntpd[1332]: Listening on interface #1 wildcard, ::#123 Disabled
    Mar  2 11:43:23 ntpd[1332]: Listening on interface #2 eth0, fe80::206:5bff:fefc:bd96#123 Enabled
    Mar  2 11:43:23 ntpd[1332]: Listening on interface #3 lo, ::1#123 Enabled
    Mar  2 11:43:23 ntpd[1332]: Listening on interface #4 lo, 127.0.0.1#123 Enabled
    Mar  2 11:43:23 ntpd[1332]: Listening on interface #5 eth0, 10.0.21.17#123 Enabled
    Mar  2 11:43:23 ntpd[1332]: Listening on routing socket on fd #22 for interface updates
    Mar  2 11:43:23 ntpd[1332]: kernel time sync status 0040
    Mar  2 11:43:24 ntpd[1332]: frequency initialized 499.647 PPM from /var/lib/ntp/drift
    Mar  2 11:46:36 ntpd[1332]: synchronized to LOCAL(0), stratum 5
    Mar  2 11:46:36 ntpd[1332]: kernel time sync status change 0001
    Mar  2 11:53:11 ntpd[1332]: ntpd exiting on signal 15
    Mar  2 12:03:07 ntpd[1458]: ntpd 4.2.4p7@1.1607-o Wed Dec  9 11:59:30 UTC 2009 (1)
    Mar  2 12:03:07 ntpd[1459]: precision = 1000.499 usec
    Mar  2 12:03:07 ntpd[1459]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
    Mar  2 12:03:07 ntpd[1459]: Listening on interface #1 wildcard, ::#123 Disabled
    Mar  2 12:03:07 ntpd[1459]: Listening on interface #2 eth0, fe80::206:5bff:fefc:bd96#123 Enabled
    Mar  2 12:03:07 ntpd[1459]: Listening on interface #3 lo, ::1#123 Enabled
    Mar  2 12:03:07 ntpd[1459]: Listening on interface #4 lo, 127.0.0.1#123 Enabled
    Mar  2 12:03:07 ntpd[1459]: Listening on interface #5 eth0, 10.0.21.17#123 Enabled
    Mar  2 12:03:07 ntpd[1459]: Listening on routing socket on fd #22 for interface updates
    Mar  2 12:03:07 ntpd[1459]: kernel time sync status 0040
    Mar  2 12:03:07 ntpd[1459]: frequency initialized 499.647 PPM from /var/lib/ntp/drift
    Mar  2 12:06:20 ntpd[1459]: synchronized to LOCAL(0), stratum 5
    Mar  2 12:06:20 ntpd[1459]: kernel time sync status change 0001
    Mar  2 12:07:25 ntpd[1459]: synchronized to 88.191.108.178, stratum 2
    Mar  2 12:10:39 ntpd[1459]: synchronized to 91.121.45.45, stratum 2
    Mar  2 12:10:42 ntpd[1459]: synchronized to 88.191.108.178, stratum 2
    Mar  2 12:21:28 ntpd[1459]: synchronized to 91.121.45.45, stratum 2
    Mar  2 12:22:30 ntpd[1459]: time reset -5.077425 s
    Mar  2 12:26:00 ntpd[1459]: synchronized to LOCAL(0), stratum 5
    Mar  2 12:26:58 ntpd[1459]: synchronized to 81.93.183.116, stratum 2
    Mar  2 12:33:24 ntpd[1459]: synchronized to 91.121.45.45, stratum 2
    Mar  2 12:35:12 ntpd[1459]: synchronized to LOCAL(0), stratum 5
    Mar  2 12:35:31 ntpd[1459]: synchronized to 88.191.108.178, stratum 2
    Mar  2 12:36:15 ntpd[1459]: synchronized to LOCAL(0), stratum 5
    Mar  2 15:39:48 ntpd[2186]: ntpd 4.2.4p7@1.1607-o Wed Dec  9 11:59:30 UTC 2009 (1)
    Mar  2 15:39:48 ntpd[2186]: precision = 1000.500 usec
    Mar  2 15:39:48 ntpd[2186]: unable to bind to wildcard socket address 0.0.0.0 - another process may be running - EXITING
    Mar  2 15:46:29 ntpd[2202]: ntpd 4.2.4p7@1.1607-o Wed Dec  9 11:59:30 UTC 2009 (1)
    Mar  2 15:46:29 ntpd[2203]: precision = 1000.500 usec
    Mar  2 15:46:29 ntpd[2203]: unable to bind to wildcard socket address 0.0.0.0 - another process may be running - EXITING
    Mar  2 15:49:01 ntpd[1459]: ntpd exiting on signal 15
    Mar  2 15:49:01 ntpd[2254]: ntpd 4.2.4p7@1.1607-o Wed Dec  9 11:59:30 UTC 2009 (1)
    Mar  2 15:49:01 ntpd[2255]: precision = 1000.500 usec
    Mar  2 15:49:01 ntpd[2255]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
    Mar  2 15:49:01 ntpd[2255]: Listening on interface #1 wildcard, ::#123 Disabled
    Mar  2 15:49:01 ntpd[2255]: Listening on interface #2 eth0, fe80::206:5bff:fefc:bd96#123 Enabled
    Mar  2 15:49:01 ntpd[2255]: Listening on interface #3 lo, ::1#123 Enabled
    Mar  2 15:49:01 ntpd[2255]: Listening on interface #4 lo, 127.0.0.1#123 Enabled
    Mar  2 15:49:01 ntpd[2255]: Listening on interface #5 eth0, 10.0.21.17#123 Enabled
    Mar  2 15:49:01 ntpd[2255]: Listening on routing socket on fd #22 for interface updates
    Mar  2 15:49:01 ntpd[2255]: kernel time sync status 0040
    Mar  2 15:49:01 ntpd[2255]: frequency initialized 500.000 PPM from /var/lib/ntp/drift
    Mar  2 15:52:16 ntpd[2255]: synchronized to LOCAL(0), stratum 5
    Mar  2 15:52:16 ntpd[2255]: kernel time sync status change 0001
    Mar  2 15:53:21 ntpd[2255]: synchronized to 81.19.16.225, stratum 2
    Mar  2 15:54:23 ntpd[2255]: synchronized to 88.191.101.34, stratum 2
    Mar  2 15:54:25 ntpd[2255]: synchronized to LOCAL(0), stratum 5
    Mar  2 15:54:27 ntpd[2255]: synchronized to 91.121.104.170, stratum 2
    Mar  2 15:54:37 ntpd[2277]: ntpd 4.2.4p7@1.1607-o Wed Dec  9 11:59:30 UTC 2009 (1)
    Mar  2 15:54:38 ntpd[2278]: precision = 1000.500 usec
    Mar  2 15:54:38 ntpd[2278]: unable to bind to wildcard socket address 0.0.0.0 - another process may be running - EXITING
    Mar  2 15:55:33 ntpd[2255]: synchronized to LOCAL(0), stratum 5
    Mar  3 09:14:52 ntpd[5329]: ntpd 4.2.4p7@1.1607-o Wed Dec  9 11:59:30 UTC 2009 (1)
    Mar  3 09:14:52 ntpd[5330]: precision = 1000.500 usec
    Mar  3 09:14:52 ntpd[5330]: unable to bind to wildcard socket address 0.0.0.0 - another process may be running - EXITING
    Desktop:
    Code:
    Feb 28 20:37:41 ntpd[1884]: synchronized to 91.121.104.170, stratum 2
    Mar  1 04:01:46 ntpd[1884]: synchronized to 91.121.138.81, stratum 2
    Mar  1 21:06:04 ntpd[1884]: synchronized to 91.121.104.170, stratum 2
    Mar  1 22:27:25 ntpd[1884]: synchronized to 91.121.138.81, stratum 2
    Mar  2 10:21:33 ntpd[1884]: ntpd exiting on signal 15
    Mar  2 10:22:56 ntpd[1994]: ntpd 4.2.4p8@1.1612-o Wed Dec  9 11:49:11 UTC 2009 (1)
    Mar  2 10:22:56 ntpd[1995]: precision = 0.093 usec
    Mar  2 10:22:56 ntpd[1995]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
    Mar  2 10:22:56 ntpd[1995]: Listening on interface #1 wildcard, ::#123 Disabled
    Mar  2 10:22:56 ntpd[1995]: Listening on interface #2 lo, ::1#123 Enabled
    Mar  2 10:22:56 ntpd[1995]: Listening on interface #3 lo, 127.0.0.1#123 Enabled
    Mar  2 10:22:56 ntpd[1995]: Listening on routing socket on fd #20 for interface updates
    Mar  2 10:22:56 ntpd[1995]: kernel time sync status 2040
    Mar  2 10:22:56 ntpd[1995]: frequency initialized -188.912 PPM from /var/lib/ntp/drift
    Mar  2 10:22:58 ntpd_initres[2013]: host name not found: 0.fedora.pool.ntp.org
    Mar  2 10:22:58 ntpd_initres[2013]: host name not found: 1.fedora.pool.ntp.org
    Mar  2 10:22:58 ntpd_initres[2013]: host name not found: 2.fedora.pool.ntp.org
    Mar  2 10:22:59 ntpd[1995]: Listening on interface #4 eth0, fe80::221:9bff:fe6a:a574#123 Enabled
    Mar  2 10:22:59 ntpd[1995]: Listening on interface #5 eth0, 10.0.21.200#123 Enabled
    Mar  2 10:27:25 ntpd[1995]: synchronized to 95.130.9.63, stratum 3
    Mar  2 10:27:25 ntpd[1995]: time reset -0.429370 s
    Mar  2 10:27:25 ntpd[1995]: kernel time sync status change 2001
    Mar  2 10:36:07 ntpd[1995]: synchronized to 87.98.188.218, stratum 2
    Mar  2 11:03:29 ntpd[1995]: synchronized to 91.121.149.114, stratum 2
    Mar  2 12:01:27 ntpd[1995]: synchronized to 87.98.188.218, stratum 2
    Mar  2 13:58:22 ntpd[1995]: synchronized to 91.121.149.114, stratum 2
    Mar  2 14:37:33 ntpd[1995]: synchronized to 87.98.188.218, stratum 2
    Mar  2 21:13:45 ntpd[1995]: synchronized to 91.121.149.114, stratum 2
    Mar  3 08:16:21 ntpd[1995]: synchronized to 87.98.188.218, stratum 2
    The last time my server was synchronized was on Mar 2 15:54:27, my desktop was last synchronized this morning.

    What can explain that?

    F.

Page 1 of 2 12 LastLast

Similar Threads

  1. server time
    By pppswing in forum Using Fedora
    Replies: 1
    Last Post: 13th November 2007, 05:19 PM
  2. SAMBA - File server for images - loading slowly from WinXP
    By Airmister in forum Servers & Networking
    Replies: 0
    Last Post: 22nd June 2007, 07:12 PM
  3. NET TIME - "Could not locate a time server"
    By mark.dixon in forum Servers & Networking
    Replies: 0
    Last Post: 15th March 2005, 12:44 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •