Re: Time Synchronisation

 
SOLVED
Go to solution
Donald Thaler
Super Advisor

Re: Time Synchronisation

how do i trouble shoot 'Your server cannot talk NTP to 10.2.2.28. Until this is fixed, the rest of the steps will be ineffective.'
i'm still getting "Can't assign requested address" ?


Bill Hassell
Honored Contributor

Re: Time Synchronisation

> i'm still getting "Can't assign requested address" ?

Did you simply type the command: ntpq -p? If so, this is normal because you told ntpq to query xntpd on your local server and it is not running, or not running correctly. Be sure you type the command completely:

ntpq -p 10.2.2.28

Once you get a good response, change your ntp.conf file as mentioned above and stop/restart xntpd:

/sbin/init.d/xntpd stop
/sbin/init.d/xntpd start

then look at the end of syslog.log:

tail /var/adm/syslog/syslog.log

which will show what happened when ntpdate was run to set the current time.


Bill Hassell, sysadmin
Suraj K Sankari
Honored Contributor

Re: Time Synchronisation

Hi,

Did you check whether your xntpd demon is running or not ?
Are you using drift file ? if not then try with drift file restart the demon

/sbin/init.d/xntpd stop
/sbin/init.d/xntpd start

after restart give
ntpd â q

Then check you /var/adm/syslog/syslog.log

Still problem then post last 100 line of your syslog.log

Suraj
Fadia Almarei
Super Advisor

Re: Time Synchronisation

attached file is steps how to configure the ntp on hp-ux and you have then to restart the servers and wait on them to take the effect
fadia.marei
Donald Thaler
Super Advisor

Re: Time Synchronisation

following fadia's suggestion i get this in the syslog.log files

from client

Dec 22 09:40:02 apollo xntpd[450]: tickadj = 625, tick = 10000, tvu_maxslew = 61875
Dec 22 09:40:02 apollo xntpd[450]: precision = 6 usec

from server

Dec 22 09:45:49 artemis xntpd[3269]: refclock_open: /dev/hpgps1: No such file or directory
Dec 22 09:45:49 artemis xntpd[3269]: configuration of 127.127.26.1 failed
Dec 22 09:47:43 artemis xntpd[3405]: tickadj = 625, tick = 10000, tvu_maxslew = 61875
Dec 22 09:47:43 artemis xntpd[3405]: precision = 6 usec
Dec 22 09:47:43 artemis xntpd[3405]: refclock_open: /dev/hpgps1: No such file or directory
Dec 22 09:47:43 artemis xntpd[3405]: configuration of 127.127.26.1 failed
Dec 22 09:49:48 artemis xntpd[3456]: tickadj = 625, tick = 10000, tvu_maxslew = 61875
Dec 22 09:49:48 artemis xntpd[3456]: precision = 25 usec
Dec 22 09:49:48 artemis xntpd[3456]: refclock_open: /dev/hpgps1: No such file or directory
Dec 22 09:49:48 artemis xntpd[3456]: configuration of 127.127.26.1 failed

there is not ntp.drift file on either server?

the ntpq -p 10.2.2.28 now returns this on the client
# ntpq -p 10.2.2.28
remote refid st t when poll reach delay offset disp
==============================================================================
*LOCAL(0) LOCAL(0) 3 l 66m 64 377 0.00 0.000 10.01
artemis.lccc.ed 0.0.0.0 16 - - 64 0 0.00 0.000 16000.0

the time on the client remains 5 minutes faster than the time on the server



Donald Thaler
Super Advisor

Re: Time Synchronisation

on the client:
after stopping and starting xntpd...
Dec 22 14:15:11 apollo xntpd[23525]: synchronized to 10.2.2.28, stratum=4
Dec 22 14:15:11 apollo xntpd[23525]: time error -3918.453608 is way too large (set clock manually)

nothing shows up in the ntp.drift on the client, on the server the value is 0.0.0..

can i specify a smaller value in the ntp.drift file file on the client, and see if the client time changes ?
TTr
Honored Contributor

Re: Time Synchronisation

Now it appears that the client is connecting to the server but the time correction is too large to change the clock. Shutdown the ntp service on the client and adjust the time manually first. Either use the date command, the "date -a" command or the "ntpdate -B ntpserver" command and after the client has adjusted then restart the ntp service on the client.
Donald Thaler
Super Advisor

Re: Time Synchronisation

by issuing a 'date -a -360' on the client, i was able to slow the clock down so that the time which was 5 minutes faster than the ntp server is now about 30 seconds slower, i started up xntpd on the client. I'm assuming the problem i was having was due to the fact that the client was originally faster than the server and xntpd doesn't change the time backwards ?
Donald Thaler
Super Advisor

Re: Time Synchronisation

i notice that on the client if i run the xntpd start, and then wait about 5-10 mins and try the xntpd stop i get the message "Unable to stop xntpd (cannot find pid)..."

if i do the xntpd stop soon after the xntpd start then i don't get the error message.

on the ntp server i never get the error message when trying to do the xntpd stop...




James R. Ferguson
Acclaimed Contributor

Re: Time Synchronisation

Hi (again) Donald:

> i notice that on the client if i run the xntpd start, and then wait about 5-10 mins and try the xntpd stop i get the message "Unable to stop xntpd (cannot find pid)..."

> if i do the xntpd stop soon after the xntpd start then i don't get the error message.

This behavior is consistent with the 'xntpd' dying after it is started. This is likely the result of too large a time difference between your server and client.

Did you ever verify that the UTC time for your server is correct as I originally suggested?

# date -u

...should return a value very close to the correct time if NTP is going to begin to synchronize.

Regards!

...JRF...