OpenNTPD isnt syncing correctly!

ninjaprawn · 2009-03-01 17:28:37

hi

not sure if it is just me, but my OpenNTPD isnt setting the time correctly! my config file has these uncommented only;

server 0.uk.pool.ntp.org
server 1.uk.pool.ntp.org
server 2.uk.pool.ntp.org
server 4.uk.pool.ntp.org

Last edited by ninjaprawn (2009-04-08 22:08:20)

wonder · 2009-03-01 17:37:19

did your timezone in rc.conf is corectly?

Last edited by wonder (2009-03-01 17:38:36)

ninjaprawn · 2009-03-01 18:44:03

wonder wrote:

did your timezone in rc.conf is corectly?

my rc.conf is;

LOCALE="en_GB.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="London/Britain"

wonder · 2009-03-01 18:56:40

timezone should be Europe/London

ninjaprawn · 2009-03-01 21:05:04

ok, i changed it to "London/Europe", still not giving me the correct time! (i have rebooted since)

Last edited by ninjaprawn (2009-03-01 21:05:25)

wonder · 2009-03-01 21:13:42

check again how do i wrote it.

fukawi2 · 2009-03-01 21:51:54

wonder wrote:

Europe/London

ninjaprawn wrote:

London/Europe

ninjaprawn · 2009-03-03 00:24:06

LOCALE="en_GB.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/London"

everything i compare my system time to is out by 2 mins!

whukes · 2009-03-03 07:29:11

Maybe you live in the future?

try 'ntpd -sd' in console and see if your time is correct.

byte · 2009-03-03 08:40:33

Have a look at /var/log/daemon.log. Do you see lines with "ntpd[$pid]: adjusting local clock by 1.234567s"?
If so, it is working. My guess is that openntpd favors "slewing" (adjtime syscall) over hard steps (settimeofday), so it might take a while until you see the correct time.
Any reason why you don't use "servers uk.pool.ntp.org"?

whompus · 2009-03-03 12:21:27

I had openntpd backgrounded in rc.conf and it wasn't starting correctly, changed my network and openntpd to not background now everything is fine. Looking at the daemon.log it took 3 days to get the correct time.

ninjaprawn · 2009-03-21 21:59:04

ok, i solved my problem! the issue was that im an idiot, and created a file called ntpd.conf instead of ntp.conf!

ninjaprawn · 2009-04-08 22:14:31

hmmmm.........
i thought i had fixed the problem, still the same though!!
ntpd -sd;

reply from 213.40.20.1: offset -89.226282 delay 0.015050, next query 6s
reply from 80.87.128.243: offset -89.227121 delay 0.020608, next query 5s
reply from 80.87.128.243: offset -89.227282 delay 0.021440, next query 30s
reply from 213.40.20.1: offset -89.227186 delay 0.015050, next query 33s
reply from 91.186.12.87: offset -89.226195 delay 0.016679, next query 31s
reply from 78.129.196.4: offset -89.228505 delay 0.014683, next query 31s
reply from 80.87.128.243: offset -89.222597 delay 0.039122, next query 32s
reply from 91.186.12.87: offset -89.230331 delay 0.017020, next query 30s
reply from 213.40.20.1: offset -89.231178 delay 0.016257, next query 33s
reply from 78.129.196.4: offset -89.231749 delay 0.016855, next query 30s
adjusting local clock by -89.225778s
reply from 91.194.67.1: offset -89.224172 delay 0.014305, next query 8s
reply from 91.186.12.87: offset -89.220278 delay 0.017695, next query 31s
reply from 80.87.128.243: offset -89.221499 delay 0.022728, next query 34s
reply from 91.194.67.1: offset -89.220478 delay 0.015896, next query 7s
reply from 78.129.196.4: offset -89.221098 delay 0.016661, next query 33s
reply from 213.40.20.1: offset -89.219870 delay 0.015241, next query 32s
peer 91.194.67.1 now valid
reply from 91.194.67.1: offset -89.218981 delay 0.013977, next query 8s

as you can see, ntp realises the system is out of sync by 89.?? seconds, trys to adjust, but nothing changes!

my rc.conf;

LOCALE="en_GB.utf8"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/London"

i read a few that running hwclock --hctosys should help, but nope!

fukawi2 · 2009-04-08 22:53:15

Do you have opennptd in your DAEMONS array in rc.conf?

brebs · 2009-04-09 10:04:26

I recommend you use ntp instead of openntp. Some reasons are in that thread and its links.

brazzmonkey · 2009-04-09 10:11:41

I tried openntpd myself, but it's been adjusting time very slowly. It would take several days to get correct time. ntp worked at once.

ninjaprawn · 2009-04-10 07:58:29

fukawi2 wrote:

Do you have opennptd in your DAEMONS array in rc.conf?

Yeah, and I read that it is not good to have it backgrounded, so when I boot up, all my DAEMONS get backgrounded, then I have to wait a few seconds for opennptd to start unbackgrounded.

I left my pc off for a couple of hours, when I booted up, my clock was out by ~30mins, but the opennptd had started up fine. I then ran nptd from urxvt and my clock instantly updated correctly.

I am a little confused. Opennptd seems to work absolutly fine now, but doesnt start at boot correctly.

Arch Linux

#1 2009-03-01 17:28:37

OpenNTPD isnt syncing correctly!

#2 2009-03-01 17:37:19

Re: OpenNTPD isnt syncing correctly!

#3 2009-03-01 18:44:03

Re: OpenNTPD isnt syncing correctly!

#4 2009-03-01 18:56:40

Re: OpenNTPD isnt syncing correctly!

#5 2009-03-01 21:05:04

Re: OpenNTPD isnt syncing correctly!

#6 2009-03-01 21:13:42

Re: OpenNTPD isnt syncing correctly!

#7 2009-03-01 21:51:54

Re: OpenNTPD isnt syncing correctly!

#8 2009-03-03 00:24:06

Re: OpenNTPD isnt syncing correctly!

#9 2009-03-03 07:29:11

Re: OpenNTPD isnt syncing correctly!

#10 2009-03-03 08:40:33

Re: OpenNTPD isnt syncing correctly!

#11 2009-03-03 12:21:27

Re: OpenNTPD isnt syncing correctly!

#12 2009-03-21 21:59:04

Re: OpenNTPD isnt syncing correctly!

#13 2009-04-08 22:14:31

Re: OpenNTPD isnt syncing correctly!

#14 2009-04-08 22:53:15

Re: OpenNTPD isnt syncing correctly!

#15 2009-04-09 10:04:26

Re: OpenNTPD isnt syncing correctly!

#16 2009-04-09 10:11:41

Re: OpenNTPD isnt syncing correctly!

#17 2009-04-10 07:58:29

Re: OpenNTPD isnt syncing correctly!

Board footer