I have a problem keeping xntpd going, any ideas on what is wrong?
# oslevel -s
5300-04-02

root# ntpdate -v 10.55.130.24
2 Aug 14:47:37 ntpdate[439026]: 3.4y
2 Aug 14:47:37 ntpdate[439026]: adjust time server 10.55.130.24 offset
0.000498

root# startsrc -s xntpd
0513-059 The xntpd Subsystem has been started. Subsystem PID is 578230.


root# ps -ef|grep ntp
<note, /usr/sbin/xntpd not in
process queue>
root# ps -ef |grep 578230
<note, /usr/sbin/xntpd not in
process queue>


root# grep server /etc/ntp.conf
server 10.55.130.24 prefer
server 10.73.130.24

root# ntptrace 10.55.130.24
gp55hr01.example.com stratum 1, offset -0.000073, synch distance
0.00000, refid 'GPS '

takarov2003@yahoo.com wrote:
> I have a problem keeping xntpd going, any ideas on what is wrong?
> # oslevel -s
> 5300-04-02
>
> root# ntpdate -v 10.55.130.24
> 2 Aug 14:47:37 ntpdate[439026]: 3.4y
> 2 Aug 14:47:37 ntpdate[439026]: adjust time server 10.55.130.24 offset
> 0.000498
>
> root# startsrc -s xntpd
> 0513-059 The xntpd Subsystem has been started. Subsystem PID is 578230.
>
>
> root# ps -ef|grep ntp
> <note, /usr/sbin/xntpd not in
> process queue>
> root# ps -ef |grep 578230
> <note, /usr/sbin/xntpd not in
> process queue>
>
>
> root# grep server /etc/ntp.conf
> server 10.55.130.24 prefer
> server 10.73.130.24
>
> root# ntptrace 10.55.130.24
> gp55hr01.example.com stratum 1, offset -0.000073, synch distance
> 0.00000, refid 'GPS '

takarov2003@yahoo.com wrote:
> I have a problem keeping xntpd going, any ideas on what is wrong?
> # oslevel -s
> 5300-04-02
>
> root# ntpdate -v 10.55.130.24
> 2 Aug 14:47:37 ntpdate[439026]: 3.4y
> 2 Aug 14:47:37 ntpdate[439026]: adjust time server 10.55.130.24 offset
> 0.000498
>
> root# startsrc -s xntpd
> 0513-059 The xntpd Subsystem has been started. Subsystem PID is 578230.
>
>
> root# ps -ef|grep ntp
> <note, /usr/sbin/xntpd not in
> process queue>
> root# ps -ef |grep 578230
> <note, /usr/sbin/xntpd not in
> process queue>
>
>
> root# grep server /etc/ntp.conf
> server 10.55.130.24 prefer
> server 10.73.130.24
>
> root# ntptrace 10.55.130.24
> gp55hr01.example.com stratum 1, offset -0.000073, synch distance
> 0.00000, refid 'GPS '

Is this a client or a server?

I'll guess that it is client. Here is my client set up:
root@unxr1:/etc>root@unxr1:/etc>oslevel -s
5300-04-03

root@unxr1:/etc>grep xntpd *
rc.tcpip:start /usr/sbin/xntpd "$src_running" -a "-x"

root@unxr1:/etc>cat /etc/ntp.conf
#broadcastclient
driftfile /etc/ntp.drift
tracefile /etc/ntp.trace
server 10.113.210.202

root@unxr1:/etc>pgrep ntp
UID PID PPID STIME TTY TIME CMD
root 233688 229466 0 Jul 30 - 0:05 /usr/sbin/xntpd -a
root@unxr1:/etc>

If you run syslogd, ntp errors should be logged there.

Miles

miles wrote:
> takarov2003@yahoo.com wrote:
> > I have a problem keeping xntpd going, any ideas on what is wrong?
> > # oslevel -s
> > 5300-04-02
> >
> > root# ntpdate -v 10.55.130.24
> > 2 Aug 14:47:37 ntpdate[439026]: 3.4y
> > 2 Aug 14:47:37 ntpdate[439026]: adjust time server 10.55.130.24 offset
> > 0.000498
> >
> > root# startsrc -s xntpd
> > 0513-059 The xntpd Subsystem has been started. Subsystem PID is 578230.
> >
> >
> > root# ps -ef|grep ntp
> > <note, /usr/sbin/xntpd not in
> > process queue>
> > root# ps -ef |grep 578230
> > <note, /usr/sbin/xntpd not in
> > process queue>
> >
> >
> > root# grep server /etc/ntp.conf
> > server 10.55.130.24 prefer
> > server 10.73.130.24
> >
> > root# ntptrace 10.55.130.24
> > gp55hr01.example.com stratum 1, offset -0.000073, synch distance
> > 0.00000, refid 'GPS '
>
> Is this a client or a server?
>
> I'll guess that it is client. Here is my client set up:
> root@unxr1:/etc>root@unxr1:/etc>oslevel -s
> 5300-04-03
>
> root@unxr1:/etc>grep xntpd *
> rc.tcpip:start /usr/sbin/xntpd "$src_running" -a "-x"
>
> root@unxr1:/etc>cat /etc/ntp.conf
> #broadcastclient
> driftfile /etc/ntp.drift
> tracefile /etc/ntp.trace
> server 10.113.210.202
>
> root@unxr1:/etc>pgrep ntp
> UID PID PPID STIME TTY TIME CMD
> root 233688 229466 0 Jul 30 - 0:05 /usr/sbin/xntpd -a
> root@unxr1:/etc>
>
> If you run syslogd, ntp errors should be logged there.

Thanks, the problem turned out to be a bad link for /unix. fixed that
and things are fine.

>
> Miles