Re: xnptd insane after reboot

From: Dave Stewart (dstewart_at_AQUAFLO.COM)
Date: 04/07/05

  • Next message: Bob Booth - CITES: "Re: xnptd insane after reboot" 
    Date:         Thu, 7 Apr 2005 10:09:21 -0700
To: aix-l@Princeton.EDU

    On Apr 5, 2005, at 9:01 PM, Bob Booth offered this insight:

    > When it is nuts, use the xntpdc program to check to make sure that it
    > does
    > have peers. One problem may be that the system time is way out of
    > wack with
    > the time servers, and ntpd can't correct that fast, so you stay at S16
    > instead
    > of what you are supposed to be.
    >
    > When you come up, before you start xntpd, you might want to do an
    > 'ntpdate'
    > against one of your 'solid' timeservers to get the time in sync.
    >
    > hth,
    >
    > bob

    Thanks Bob, it did help somewhat. At least to find the source of the
    problem, which has now changed ...

    The other admin guy here typically does the reboots of this machine and
    didn't tell me that each time he has to smitty tcpip and reset the
    default gateway to the current value (it's somehow resetting itself
    with the old gateway value after each reboot). This sure caught me off
    guard yesterday when I did a reboot and found it couldn't get back on
    the network.

    My guess is this is causing the problems with ntp on reboots. ;-)

    (Direct answers: the time isn't that far off unless I don't notice it
    for a few weeks and then setting the date works like perfectly. I also
    discovered that when the machine is restarted xntpd can't find it's
    data, so the xntpdc command doesn't return much other than "can find
    data". When the gateway is reset to the correct values via smitty, then
    the xntpdc command returns the correct peers and stopping/restarting
    xntpd via smitty works like a charm.)

    Next question, why does this server (IBM E20 running AIX 5.1) keep
    resetting it's gateway on a reboot? Where *could* it be caching this
    old gateway value?

    Dave Stewart
    Aqua~Flo Supply (Goleta CA)
    dstewart at aquaflo dot com

    There are 10 kinds of people in the world:
    Those who understand binary and those who don't.

  • Next message: Bob Booth - CITES: "Re: xnptd insane after reboot"

    Relevant Pages

    • Re: Kein Netzwerk nach Xubuntu 8.10 update
      ... Dann solltest Du nach dem Reboot zumindest dich selber, das Gateway und die Rechner im Netz anpingen können - wenn Gateway und die anderen Rechner auf "ping" reagieren. ... Im Fall von "inet static" muss dann noch in die /etc/resolv.conf ein Nameserver rein: ...
      (de.comp.os.unix.linux.misc)
    • Re: What now?
      ... machine would reboot. ... I sent the computer back to Gateway. ... nor Tiger Direct have offered to help me any ... I'm sure the problem is the mobo. ...
      (alt.comp.hardware.pc-homebuilt)
    • Can not change default gateway(URGENT!!!)
      ... Everytime after reboot my PC, the default gateway is set to 10.64.x.x in the ... TCP/IP properities(correct default gateway should be 10.128.x.1). ... program will overwrite the default gateway every time at Windows startup ...
      (microsoft.public.windowsxp.network_web)
    • Re: [opensuse] screwy time
      ... Bob S wrote: ... Every time I reboot my computrer it loses 4 hours exactly. ... Regardless, if you will ever boot windows, then you need to set your hwclock ... On my single boot box with hwclock set to UTC, ...
      (SuSE)
    • Re: Gateway reset on reboot (was: xnptd insane after reboot)
      ... if you do a 'smitty tcpip' to set the hostname/primary IP address ... which will persist through a reboot because it gets put in the ODM. ... Subject: Gateway reset on reboot ... Some of these CuAt entries look right, ...
      (AIX-L)