On 22 Kwi, 09:44, Ashok Sangra <aksan...@gmail.com> wrote:
> On Apr 21, 8:02 pm, Marcin.Tabinow...@gmail.com wrote:
>
>
>
>
>
> > Hi
>
> > I have an annoying problem with ntp on AIX 5.3 TL7. This is what I
> > did:
> > 1. I have enabled start of xntpd in /etc/rc.tcpip
> > 2. /etc/ntp.conf looks like this:
>
> > server <my ntp server ip>
> > broadcastclient
>
> > driftfile /etc/ntp.drift
> > tracefile /etc/ntp.trace
>
> > 3. I run ntpdate <my ntp server ip>
> > 4. Finally, I run startsrc -s xntpd
>
> > The subsystem has started and runs just fine without a crash. The time
> > is correct, the date is correct, the time zone is good (I set it
> > earlier). There is no error regarding to xntp src. But...
> > The xntpd does not start after reboot. After reboot the date and time
> > are still correct and seem to be synchronized. But xntpd subsystem is
> > inoperative. After every reboot I have to start it manually. Then I
> > run ntpq -p and the output is like this:
>
> > remote refid st t when poll reach delay
> > offset disp
> > ================================================== =========================--===
> > *x.x.x.x x.x.x.x 4 u 94 128 377 1.16 -0.367
> > 0.12
>
> > So the offset is not the issue. After reboot there is no error in
> > errorlog and after starting src manually ntp runs just fine without
> > the crash.
> > Am I doing something wrong or what? Why xntpd doesn't start after
> > reboot? I have thi issue on all my LPARs in p595 server, firmware
> > version SF240_320. I will appreciate any help, thanks in advance
>
> Try strating the xntpd daemon at system boot by putting the following
> entry in /etc/inittab
> xntp:2nce:/usr/bin/startsrc -s xntpd > /dev/console 2>&1
> I suppose xntpd doesn't get initialized through rc.tcpip. Pls correct
> if I am wrong.
> HTH
> Ashok Sangra- Ukryj cytowany tekst -
>
> - Poka¿ cytowany tekst -

Conslog is clear, adding xntp:2nce:/usr/bin/startsrc -s xntpd > /dev/
console 2>&1 to inittab makes no effect, hovever when I put xntp:
2:respawn:/usr/bin/startsrc -s xntpd > /dev/console 2>&1 to inittab
and restart, the message has occured in /var/adm/ras/conslog:

INIT: Command is respawning too rapidly. Check for possible errors.
id: xntp "/usr/bin/startsrc -s xntpd /dev/console 2>&1"

The xntp subsystem was still inoperative. So, it seems the xntp is
starting and stopping very fast. But whty is it stopping? I put all
facilities in all priority levels in syslog but after restart there is
no entry in log file. There also are no errors in bootlog or errorlog.
After starting inoperative system manually the entry shows in syslog:

Apr 22 11:07:36 piwmbtdev daemon:notice xntpd[327904]: 3.4y
Apr 22 11:07:36 piwmbtdev daemon:notice xntpd[327904]: 3.4y
Apr 22 11:07:36 piwmbtdev daemon:notice xntpd[327904]: tickadj = 1000,
tick = 10000, tvu_maxslew = 99000
Apr 22 11:07:36 piwmbtdev daemon:notice xntpd[327904]: tickadj = 1000,
tick = 10000, tvu_maxslew = 99000
Apr 22 11:07:36 piwmbtdev daemon:info xntpd[327904]: precision = 6
usec

But I see no errors here either Is that possible the xntp starts at
reboot time, synchronizes the time with ntp server and then stops
normally? I think I run out of ideas abouthis silly problem :P