System time not correct

[Rilo Ravestein]

Hi there,

Since 9.10, the system time on my FreeNAS system is not correct, in the web GUI as well as in the SSH console. It shows 2 hours later. All other devices on the network use the same NTP server (on my pfSense box) and every other device works just fine with that. I also tried some pool.ntp.org ones, just to be sure.

FreeNAS-9.10-STABLE-201605021851
In the BIOS, (date &) time is correct
In the web GUI system information, the time is +2 hours
In the SSH console, the 'date' command shows +2 hours
Timezone in general system settings is Europe/Amsterdam
NTP servers: 0.nl.pool.ntp.org, 1.nl.pool.ntp.org, 2.nl.pool.ntp.org, 3.nl.pool.ntp.org

 

[Mirfster]

What about trying "time.nist.gov" as NTP?

 

[Rilo Ravestein]

Why would that be different, since the problem only occures on FreeNAS and no other systems in my network, which all use the same NTP servers? Furthermore, it has always been fine up until now. With the same NPT server (my own on the pfSense box). I only tried the external ones for testing purposes, I want to keep using my own NTP.

 

[Mirfster]

Not saying it really would, just trying a different NTP. Perhaps there is simply an issue with the "Europe/Amsterdam" Timezone in FreeNas.

 

[Rilo Ravestein]

Tried it. No change.

The only way i can get it to report the correct time, is if i set the date/timezone to "UTC"

 

[Mirfster]

Interesting, well then I would think that the time offset for "Europe/Amsterdam" is for sure incorrect. Think I will poke around and see where that is actually set. /Just for my curiosity ;)

 

[styno]

Fyi, Europe/Brussels results in the correct time and uses CEST in the shell.

Code:

# date
Fri May 20 15:52:37 CEST 2016

# date "+%Z"
CEST

# date "+%z"
+0200

 

[Rilo Ravestein]

Fyi, Europe/Brussels results in the correct time and uses CEST in the shell.

Not for me.

 

[styno]

Not for me.

Just to be 100% sure: did you open a new ssh connection when you checked? What is the output of those date commands on your box?

And for more tests, my ntp settings:

Code:

# cat /etc/ntp.conf
server 0.freebsd.pool.ntp.org iburst maxpoll 10 minpoll 6
server 1.freebsd.pool.ntp.org iburst maxpoll 10 minpoll 6
server 2.freebsd.pool.ntp.org iburst maxpoll 10 minpoll 6
restrict default limited kod nomodify notrap nopeer noquery
restrict -6 default limited kod nomodify notrap nopeer noquery
restrict 127.0.0.1
restrict -6 ::1
restrict 127.127.1.0

 

[Rilo Ravestein]

Code:

[root@nas ~]# date                                                          
Fri May 20 18:56:58 CEST 2016                                               
[root@nas ~]# date "+%Z"                                                    
CEST                                                                        
[root@nas ~]# date "+%z"                                                    
+0200

Code:

[root@nas ~]# cat /etc/ntp.conf 
server 172.30.35.1 iburst maxpoll 10 minpoll 6                              
restrict default limited kod nomodify notrap nopeer noquery                 
restrict -6 default limited kod nomodify notrap nopeer noquery              
restrict 127.0.0.1                                                          
restrict -6 ::1                                                             
restrict 127.127.1.0

With other NTP server:

Code:

[root@nas ~]# date                                                           
Fri May 20 19:00:14 CEST 2016                                                
[root@nas ~]# date "+%Z"                                                     
CEST                                                                         
[root@nas ~]# date "+%z"                                                     
+0200

Code:

[root@nas ~]# cat /etc/ntp.conf                                              
server 0.nl.pool.ntp.org iburst maxpoll 10 minpoll 6                         
restrict default limited kod nomodify notrap nopeer noquery                  
restrict -6 default limited kod nomodify notrap nopeer noquery               
restrict 127.0.0.1                                                           
restrict -6 ::1                                                              
restrict 127.127.1.0

With yours:

Code:

[root@nas ~]# date                                                            
Fri May 20 19:03:16 CEST 2016                                                 
[root@nas ~]# date "+%Z"                                                      
CEST                                                                          
[root@nas ~]# date "+%z"                                                      
+0200

Code:

[root@nas ~]# cat /etc/ntp.conf                                               
server 0.freebsd.pool.ntp.org iburst maxpoll 10 minpoll 6                     
restrict default limited kod nomodify notrap nopeer noquery                   
restrict -6 default limited kod nomodify notrap nopeer noquery                
restrict 127.0.0.1                                                            
restrict -6 ::1                                                               
restrict 127.127.1.0

 

[styno]

Looks like your ntp config is not pointing to the correct ntp server.
I am not sure that it will make the 2hr leap immediately when you correct it or that it will do it gradually.

(172.30.35.1 is something internal on your network?)

 

[Rilo Ravestein]

Looks like your ntp config is not pointing to the correct ntp server.
172.30.35.1 is something internal on your network?

It is. It's my own server. I've been using that for quite a while now, and works fine on every other device on my network. But as you can see, all other servers result in the same problem.

 

[Mirfster]

172.30.35.1 is something internal on your network?

Think it is this:

All other devices on the network use the same NTP server (on my pfSense box) and every other device works just fine with that

 

[styno]

My apologies, I guess I should blame the lack of or too much coffee now ;)

What can happen is that ntp refuses to make big leaps in time at once, on Linux I would force it with ntpdate but not sure about FreeNas/BSD.

 

[Mirfster]

Just out of curiosity, this system is not a Domain Member is it?

 

[Rilo Ravestein]

Just out of curiosity, this system is not a Domain Member is it?

Nope.

 

[Mirfster]

K, just a shot in the dark

 

[Rilo Ravestein]

Well, I appreciate any suggestion. I really have no clue whatsoever on where this is coming from.

 

[styno]

any suggestion

This should force an update:

Code:

# service ntpd stop
# ntpdate 0.freebsd.pool.ntp.org
# service ntpd start

 

[Rilo Ravestein]

This should force an update:

Code:

# service ntpd stop
# ntpdate 0.freebsd.pool.ntp.org
# service ntpd start

An update of the ntp servers already results in a restart of the ntpd service (you can check the log for that). And as shown in earlier commands and their output, it updates correctly.