I've read dozens of ntpdate posts and have not been able to find a working fix for this problem. When I start up my server, ntpdate complains:
Like most posters, I am able to manually set the time using ntpdate with the -u option:
ntpdate is started after the nics. I'm thinking it's a firewall between my server and the internet that is blocking well-known ports
So, I tried this and rebooted:
but that didn't change the outcome.
Is it possible to get the ntpdate daemon to use the behind a firewall logic during bootup?
Code:
29 Jun 13:45:55 ntpdate[515]: no server suitable for synchronization found
Like most posters, I am able to manually set the time using ntpdate with the -u option:
Code:
ntpdate -u pool.ntp.org
29 Jun 13:53:47 ntpdate[790]: step time server 129.250.35.250 offset -0.890322 sec
ntpdate is started after the nics. I'm thinking it's a firewall between my server and the internet that is blocking well-known ports
So, I tried this and rebooted:
Code:
sudo sysrc -f /etc/rc.conf ntpdate_args="-u"
but that didn't change the outcome.
Is it possible to get the ntpdate daemon to use the behind a firewall logic during bootup?