topic Re: Error in /var/adm/syslog.log in Operating System - HP-UX

Error in /var/adm/syslog.log

Isaac_4 — Thu, 20 Sep 2001 21:17:45 GMT

Please, some person had seen this error found in /var/adm/syslog.log
they have some idea in this respect
Sep 16 11:16:35 scrco xntpd[1303]: offset 0.000000 freq 0.00000 comp 2
Sep 16 12:16:03 scrco named[921]: NSTATS 1000664163 1000653363 A=1101
SOA=362 PT
R=496 MX=27 33=2 ANY=172
Isaac Smith

Re: Error in /var/adm/syslog.log

Santosh Nair_1 — Thu, 20 Sep 2001 21:39:00 GMT

this is not an error...this is just XNTP doing its thing, i.e. synching time with a time server.

-Santosh

Re: Error in /var/adm/syslog.log

eran maor — Thu, 20 Sep 2001 21:40:29 GMT

Hi

i saw two message so i will reply on both .

the first message is about ntp .
i think that you didnt config the ntp ( Network Time Protocol)

go to www.docs.com for details if you want to config the ntp .

about the second message

its a DNS message . you can disable is with
this actions :

1. install DNS patch or replacement.
[PHNE_20618/PACHRDME/English] : s700_800 10.X BIND 4.9.7 components
2. run named command with -X option.
# named -X
* To set option in boot file,
# vi /etc/rc.config.d/namesv

Re: Error in /var/adm/syslog.log

Sridhar Bhaskarla — Thu, 20 Sep 2001 21:47:07 GMT

As long as offset is less than 128ms, you are ok and it was only the log from your ntp server. The second one is the debugging stats from your name server daemon.

Try using ntpq for checking the sync status.

-Sri

Re: Error in /var/adm/syslog.log

Isaac_4 — Fri, 21 Sep 2001 15:13:08 GMT

Thanks for your assistance

Isaac Smith

Re: Error in /var/adm/syslog.log

Robert Binkley — Fri, 21 Sep 2001 17:59:47 GMT

When the xntpd daemon is started on a system, it will look at the the
/etc/ntp.conf configuration file present on the system. If that file
contains the entry

driftfile file_name

then the xntpd daemon will check for this file called file_name and
attempt to read it to determine what the last drift value was that was
seen when the xntpd daemon was last running.

If this file is empty or does not exist, the error will be seen. If
xntpd on this system has never been sync'd up to a NTP server yet, then
its very likely that this message can be seen, and in this case should be
ignored. The xntpd daemon will begin to place information in this file
1 hour after it finally syncs up with a NTP server, and every hour after
that it will update the entry in the file with the current drift value.

There should only be concern if the error is seen while the xntpd daemon
is up and running and after its sync'd up to a server. Use the command

ntpq -p

to check on the ntp synchronization status for this system.