Originally posted by: SystemAdmin

Hi, I was asked to look into a problem with our time servers. Both of them p520s, both running AIX 5.3 and the version for xntp is "xntpdc version=3.4y". My ntp.conf file as follows:
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 and 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
#AIX-Forum

Originally posted by: bassemir

Not sure but would this note help from the command reference?

Note: When operating in a client mode running AIX 4.2.1 or later, the xntpd daemon will exit with an error if no configured servers are within 1000 seconds of local system time. Use the date or ntpdate command to set the time of a bad skewed system before starting xntpd.

Rich
#AIX-Forum

Originally posted by: SystemAdmin

Hi Rich,

That is something I looked into already. I scoured the posts, internet sites, ibm documentation before I posted. I gave that one (and many others) a try. When I do the "/usr/sbin/ntpdate -s -b time.nist.gov" on the running node it is fine. However, I cannot get this one up and running (it's system clock is within a second of the one it is trying to sync with). The real stumper to me is that both boxes are exactly the same (hardware, os, software levels etc). I am beginning to wonder about kernel corruption and am going to open up a service request. Can't spend any more hours pounding my head against the wall. However I will update and close this post when I have an answer. I want to be a responsible poster. Besides nothing is more frustrating than to see someone who had the exact same problem as you, and you finally track down their post, and then they never return to tell how to fix it. ARGH! I already found one of those.......

Regards,
Jen
#AIX-Forum

Originally posted by: SystemAdmin

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
#AIX-Forum

Originally posted by: SystemAdmin

I established we did not reboot when we should have:

root@vantsmsvr01:/home/root lslpp -w `which xntpd`
File Fileset Type
<hr />
/usr/sbin/xntpd bos.net.tcp.client File

root@vantsmsvr01:/home/root lslpp -h bos.net.tcp.client
Fileset Level Action Status Date Time
<hr />
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

IBM recommended we:

sync; sync; sync;
shutdown -r

I did just that and everything came up roses. Problem resolved.

Regards,
Jen
#AIX-Forum