System time not correct

[styno]

None of the previous outputs shows that your time is updated correctly, hence the manual force.

 

[Rilo Ravestein]

No, but the service is restarted anyway. But I just tried it nonetheless, no success.

 

[styno]

ntpdate <> ntpd, you have to stop the ntpd service to be able to run the ntpdate command.

It would be good to see the actual output of the command.

 

[Rilo Ravestein]

Turns out that for whatever servers i try, after the ntpdate command, i get: no server suitable for synchronization found. Weird that in the GUI i never get an error or warning at all.
if i use the -d option:

Code:

[root@nas] ~# ntpdate -d 172.30.35.1
22 May 15:55:28 ntpdate[28265]: ntpdate 4.2.8p6-a (1)
transmit(172.30.35.1)
receive(172.30.35.1)
transmit(172.30.35.1)
receive(172.30.35.1)
transmit(172.30.35.1)
receive(172.30.35.1)
transmit(172.30.35.1)
receive(172.30.35.1)
server 172.30.35.1, port 123
stratum 2, precision -22, leap 00, trust 000
refid [172.30.35.1], delay 0.02573, dispersion 0.00000
transmitted 4, in filter 4
reference time:    daec14d0.ce0429cb  Sun, May 22 2016 13:21:52.804
originate timestamp: daec1c9e.db28bfd3  Sun, May 22 2016 13:55:10.856
transmit timestamp:  daec38d6.e612d1bb  Sun, May 22 2016 15:55:34.898
filter delay:  0.02577  0.02573  0.02573  0.02573
         0.00000  0.00000  0.00000  0.00000
filter offset: -7224.04 -7224.04 -7224.04 -7224.04
         0.000000 0.000000 0.000000 0.000000
delay 0.02573, dispersion 0.00000
offset -7224.042761

22 May 15:55:34 ntpdate[28265]: step time server 172.30.35.1 offset -7224.042761 sec

But still results in the wrong time.

 

[styno]

-d will print a lot of info but NOT adjust the time. With the offset being off by 7000 sec I highly doubt that ntpd would've been able to adjust this on its own.

 

[Rilo Ravestein]

I know. It was just to show that there's nothing wrong with the ntp server(s) itself.

 

[styno]

What happens if you set the correct time manually just once with the date command and then start ntpd? The gap would be minimal and ntpd should be able to correct it.
But yeah it is a workaround. Ntpdate should just work.

 

[Rilo Ravestein]

I've changed the time manually and the time & timezone is shown correctly in the GUI. However, i still get the error "no server suitable for synchronization found." with the command ntpdate <timeserver>. So i wonder now it it's actually synchronizing, even though i get no error in the GUI when updating timeservers.

 

[Rilo Ravestein]

Well, it even survived a reboot. I'm still not sure things are synchronizing correctly....

Code:

[root@nas] ~# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
pfSense.home    .INIT.          16 u    -   64    0    0.000    0.000   0.000

Code:

[root@nas] ~# ntpq -c as

ind assid status  conf reach auth condition  last_event cnt
===========================================================
  1 16110  8011   yes    no  none    reject    mobilize  1

 

[styno]

Code:

[root@yourfreenas~]# ntpq
ntpq> peers
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+ntp.katho.be    193.190.230.65   2 u  262 1024  377   15.700    1.662   2.778
+ssh2.ulyssis.st 193.79.237.14    2 u  124 1024  377   12.040    1.740   1.866
*213.189.188.3.i 193.190.230.65   2 u  342 1024  377   12.968    1.235   2.413
ntpq>

 

[Rilo Ravestein]

That is the same command i used ;) So it seems like things are still not working as they should.

 

[styno]

Don't you hate forum edits and browser cache ;)
What are your dns settings?

 

[Rilo Ravestein]

Yeah, sometimes i click "submit" too fast
DNS settings are the same as the NTP settings, my pfSense box

 

[Rilo Ravestein]

Anyone any more ideas?

 

[Mirfster]

Only thing I can think of is to file a bug for the TZ and see what the devs say. I would mention what you said about UTC being fine, but not your desired TZ.