I verified the following in my Ubuntu 8.04 VM. So, hopefully should also be accurate for a natively-installed system.
1 – Verify that ntpd is running:
ps -Af | grep ntp
sudo netstat -nap | grep ntp
Verify that ntpd is running and listening on port 123.
2 – Verify the following lines within /etc/ntp.conf:
server 127.127.1.0
fudge 127.127.1.0 stratum 13
There may be an additional server line preceding these lines, depending on whether the user has used eV to configure NTP.
3 – Start ntpd if not already started:
sudo /etc/init.d/ntpd start
Then use ps to verify that ntpd is running – don’t just assume so because initscript didn’t display any errors.
4 – Test NTP server with local command-line client:
sudo ntpdate -q localhost
The “-q” means just query, don’t change anything.
You will likely get initial output resembling:
server 127.0.0.1, stratum 16, offset -0.000007, delay 0.02563
23 Feb 13:39:57 ntpdate[12987]: no server suitable for synchronization found
After nearly 5 minutes (perhaps less, but definitely more than a couple), you’ll start getting output resembling:
server 127.0.0.1, stratum 14, offset -0.000006, delay 0.02563
23 Feb 13:43:57 ntpdate[13001]: adjust time server 127.0.0.1 offset -0.000006 sec
The apparent necessary delay in #4 above was *really* interesting.
So first, it appeared that ntpd was NOT running on the customer’s system, so we started it while I was at Gary’s desk. Then, you tried rebooting the Axis camera, but got the ntp failure in the camera’s log. I suggest allowing up to 5 minutes, verify on the Linux system itself with ntpdate as I described above, and then if that looks good, THEN reboot the Axis camera and see if you get better results in the camera’s log.
