[SOLVED] Wrong time from NTP

[Guest zin105]

I keep getting the wrong time from NTP. I've tried many different NTP servers and the time zone in the GUI is set correctly, but still it adds 2 extra hours. BIOS time is correct aswell. Both ESXI and pfSense gets the right time but not unRAID. Tried reboot.

 

Also I can't disable NTP in the GUI, it goes back to Yes automatically. Related issue?

 

 

Edited April 11, 2017 by zin105

[Frank1940]

First thing.  Please tell us what time zone you are in.

 

Second thing.  Double check that you have setup the Time and Date options correctly in your BIOS. I seem to recall that there was a case or two where this type of problems were traced to issues with that. 

Edited April 11, 2017 by Frank1940

[Guest zin105]

10 minutes ago, Frank1940 said:

First thing.  Please tell us what time zone you are in.

 

Second thing.  Double check that you have setup the Time and Date options correctly in your BIOS. I seem to recall that there was a case or two where this type of problems were traced to issues with that. 

 

I'm in UTC+01.00 Stockholm.

 

BIOS time is correct.

 

Stopping NTP daemon.../etc/rc.d/rc.ntpd: line 44: kill: (2005) - No such process

That's what my log says when I try and disable NTP for example. Maybe it's any help.

Edited April 11, 2017 by zin105

[Frank1940]

Now let's see what experiences other folks in that same time zone have had.  (Sometimes, the 'rules' are wrong but I doubt that this is the case here since it appears that most of Western Continental Europe is in that time zone.)

 

EDIT:  Post up manufacturer and model number of Motherboard. 

Edited April 11, 2017 by Frank1940

[gubbgnutten]

11 minutes ago, zin105 said:

I'm in UTC+01.00 Stockholm.

 

BIOS time is correct.

 

By correct, do you mean that it is set to UTC time?

 

And isn't Stockholm +2 compared to UTC due to daylight savings?

[Frank1940]

I believe that the 'rules' associated with the Time Zone in the options account for (what we call in the USA) 'Daylight Savings Time'.  The problem often is that sometimes 'Local' custom/regulation superseded the general rules and thus the automatic adjustment will result in the wrong time. 

[Guest zin105]

31 minutes ago, gubbgnutten said:

 

By correct, do you mean that it is set to UTC time?

 

And isn't Stockholm +2 compared to UTC due to daylight savings?

 

You're probably correct. BIOS time should not be the actual time including daylight savings I'm guessing?

[gubbgnutten]

No, the system clock should be the consistent actual time (UTC). That way a sensible operating system can easily compensate for time zones and daylight savings and derive the appropriate local time.

[Guest zin105]

Gonna mark this thread as solved, and me as stupid

Edited April 11, 2017 by zin105

[Frank1940]

Please don't feel that way.  This whole issue can be confusing and you are not the first one (and you won't be the last one) to have problems.  I am glad that you have it straighten out now. 

[JonathanM]

1 hour ago, zin105 said:

Gonna mark this thread as solved, and me as stupid

Like @Frank1940 said, you aren't stupid. Microsoft has been stubbornly doing it wrong for a LONG time. It's not exactly a settled issue. Now you know that time is relative, lunchtime doubly so.

[vyshnav]

HI I am facing issue in ntpd . randomly I am getting 2 minutes delay in device compare to system time .I am using ntpd -p pool.ntp.org -q.