[RESOLVED] Openntpd fail but Ntpd functions

[slycat]

I haven't ran an update on my PPPro since all the hoopla about initscripts being phased out. An just last week I had openntpd initialize without a problem after running a backup. However, this morning after its automated backup I noticed my logs began at Jan 1 1970 again.

Force starting openntpd didn't work. Reinstalling the current version on the machine didn't work. Running `ntpd -s -d` does but then requires a force quit afterwards.

Though I did not run an update on my machine, did something get changed in my initscripts? Also, how can I now implement the direct ntpd command without needing to force quit (for rc.local script to work as openntpd in DAEMONS does not work anymore)?
All other programs in the DAEMONS list works, however. Openntpd is the only one showing signs of problems. I was able to ping the pool server it is set to look up in ntpd.conf so I know it isn't that.

[Geoff]

I still have openntpd working fine, so you should be able to get it working again. I imagine you might have a DNS problem that prevents it finding the time servers when it starts up.

[ejblom]

These are my notes for the pogoplug v3. I had the same on my pogoplug(s) and it will not be changed instantly after reboot but after a while

pacman -S ntp
ntpd -qg
pacman -Sy polkit
reboot

ON V2:
timedatectl status
timedatectl set-timezone Europe/Amsterdam
systemctl enable ntpd.service

ON V3
mcedit /etc/rc.conf
timezone -> Europe/Amsterdam
daemons -> change opnntpd ntpd
reboot and wait

Perhaps somewhat useful

[slycat]

$this->bbcode_second_pass_quote('Geoff', 'I') imagine you might have a DNS problem that prevents it finding the time servers when it starts up.