broadcastclient
driftfile /etc/ntp.drift
tracefile /etc/ntp.trace
server time.nist.gov prefer
server 192.43.244.18
One server starts up fine, the other gives an error and closes right
away. Here is the error from the /var/adm/daemon.log file:
Feb 4 15:09:52 vantsmsvr01 daemon:notice xntpd893098: 3.4y
Feb 4 15:09:52 vantsmsvr01 daemon:err|error xntpd893098: tickadj or
tick unknown, exiting
So, anyone have any ideas? I don't know what it is.
Regards,
Jen
Hi,
IBM has recommended a reboot of the server after running this command:
bosboot -ad /dev/ipldevice
I have ran the command and am now waiting for a reboot window on the
server. After all the research and comments I read out there, the most
useful one was a translated page from German that told me my server
was high... Too funny. But it mentioned a broken connection to a
kernel module that was probably done during a patch or upgrade that
wasn't rebooted after the install (which IBM concurred on). Could be,
I have only been here a few months and from the history of this
server, ntp has never successfully worked. I will update this link
after I reboot.
Jen
Yes everything was successful. I was able to confirm that we had
updated xntpd but had not rebooted since:
[root@vantsmsvr01:/home/root] lslpp -w `which xntpd`
File Fileset
Type
----------------------------------------------------------------------------
/usr/sbin/xntpd bos.net.tcp.client
File
[root@vantsmsvr01:/home/root] lslpp -h bos.net.tcp.client
Fileset Level Action Status Date
Time
----------------------------------------------------------------------------
Path: /usr/lib/objrepos
bos.net.tcp.client
5.3.0.50 COMMIT COMPLETE 09/10/07
16:37:30
5.3.0.55 COMMIT COMPLETE 09/10/07
16:49:38
Path: /etc/objrepos
bos.net.tcp.client
5.3.0.50 COMMIT COMPLETE 09/10/07
16:38:21
5.3.0.55 COMMIT COMPLETE 09/10/07
16:49:38
[root@vantsmsvr01:/home/root] who -b
. system boot Mar 09 15:32
so I ran sync 3 times and then did a shutdown -r. All is good.
Jen