Find the answer to your Linux question:
Results 1 to 4 of 4
Folks: I've been trying to fix my time settings on OpenSUSE 12, but nothing works. Every time I reboot, it's always off by 4 - 5 hours. I've set the ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2011
    Posts
    28

    Time always resets after reboot in OpenSUSE 12.1/KDE 4.6


    Folks: I've been trying to fix my time settings on OpenSUSE 12, but nothing works.

    Every time I reboot, it's always off by 4 - 5 hours. I've set the timezone to New York (EST), and the BIOS is right. But still it will not keep the right time. I've used the command line to set the date, time and timezone (Sun Mar 11 18:12:06 EST 2012) So it's set right, but instead of 18h, it's nearly 23h as I write this.

    In the settings/date & Time - system settings, I tell it to set date and time automatically, using the north-America.pool.ntp.org server.

    But every time I reboot, it's the same problem. The time is at least 4 hours to 5 hours wrong. The little clock widget on KDE 4.6 also shows the same time as the command line time.

    Oddly enough even Windows on the same machine has had problems. I have a little program that resets the time via an internet connection under Windows, but Linux will not work.

    Anyone know how to fix this for good?

  2. #2
    Just Joined! charleseddy's Avatar
    Join Date
    Mar 2012
    Location
    France
    Posts
    27
    There should be some information as to what's not working in your log files. First check if it's logging statistics:

    Code:
    grep log /etc/ntp.conf
    If it's logging (no pound symbol in front), check the log file it gives you and find out what the errors are, and bring them back here!

    If it's not logging, edit the file

    Code:
    sudo nano /etc/ntp.conf
    and remove the pound symbol so you can have some logging and know what's going wrong with ntp.

  3. #3
    Just Joined! charleseddy's Avatar
    Join Date
    Mar 2012
    Location
    France
    Posts
    27
    I forgot, you might also get lucky and find something in /var/log/messages or /var/log/daemon.log concerning NTP.

  4. #4
    Just Joined!
    Join Date
    Aug 2012
    Posts
    2
    Quote Originally Posted by charleseddy View Post
    There should be some information as to what's not working in your log files. First check if it's logging statistics:

    Code:
    grep log /etc/ntp.conf
    If it's logging (no pound symbol in front), check the log file it gives you and find out what the errors are, and bring them back here!

    If it's not logging, edit the file

    Code:
    sudo nano /etc/ntp.conf
    and remove the pound symbol so you can have some logging and know what's going wrong with ntp.
    Code:
     2 Aug 20:52:07 ntpd[5971]: ntpd exiting on signal 15
     2 Aug 17:53:00 ntpd[1918]: bind(21) AF_INET6 fe80::22cf:30ff:fef0:e62c%2#123 flags 0x11 failed: Cannot assign requested address
     2 Aug 17:53:00 ntpd[1918]: unable to create socket on eth0 (5) for fe80::22cf:30ff:fef0:e62c#123
     2 Aug 17:53:00 ntpd[1918]: failed to init interface for address fe80::22cf:30ff:fef0:e62c
     2 Aug 17:53:04 ntpd[1918]: Listen normally on 6 eth0 192.168.1.5 UDP 123
     2 Aug 17:53:04 ntpd[1918]: Listen normally on 7 eth0 fe80::22cf:30ff:fef0:e62c UDP 123
     2 Aug 17:53:04 ntpd[1918]: peers refreshed
     2 Aug 17:53:04 ntpd[1918]: new interface(s) found: waking up resolver
     2 Aug 18:38:30 ntpd[1918]: ntpd exiting on signal 15
     3 Aug 20:54:26 ntpd[8214]: ntpd exiting on signal 15
    Quote Originally Posted by charleseddy View Post
    I forgot, you might also get lucky and find something in /var/log/messages or /var/log/daemon.log concerning NTP.
    not found

Posting Permissions

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