Re: Gateway reset on reboot (was: xnptd insane after reboot) *SOLVED*

• Previous message: Green, Simon: "Re: lsof: can't figure out how to show open files"
• In reply to: Dave Stewart: "Re: Gateway reset on reboot (was: xnptd insane after reboot) *SOLVED*"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date:         Tue, 24 May 2005 12:37:12 -0400
To: aix-l@Princeton.EDU

Yep, Dave, a lack of memory will wreak havoc on your system; e.g.: You
can't configure
TCP/IP with no physical memory available. The reboot would have scrubbed
all the
memory you have, so it's free at the moment. You probably want to do some
history and definitely have a look at those "vmtune"-ables, to prevent the
same thing
from happening in the future.

Mark Ray
IBM Global Services

                                                                           
             Dave Stewart
             <dstewart@AQUAFLO
             .COM> To
             Sent by: IBM AIX aix-l@Princeton.EDU
             Discussion List cc
             <aix-l@Princeton.
             EDU> Subject
                                       Re: Gateway reset on reboot (was:
                                       xnptd insane after reboot) *SOLVED*
             05/24/2005 12:04
             PM
                                                                           
                                                                           
             Please respond to
                  IBM AIX
              Discussion List
                                                                           
                                                                           

Hi list, I think I resolved my issue!

I was messing around with this machine yesterday and put it in a state
where nothing would work ... ps and ls wouldn't work with messages
about not enough memory. Same thing this morning, so I figured I'd
reboot it ...

Turns out that seems to have been the key. After the reboot this
morning, this machine just came back. Network was still down, but when
I did smitty tcpip, THE PROPER GATEWAY SHOWED UP (it's always showed
the old gateway value after a reboot, that was the issue I was trying
to address)! After verifying the settings and letting smitty run, the
network came right back.

I think I still have some kinks to iron out (it's not yet doing name
resolution - BIND must have not been happy about being down for so
long), but it SEEMS to have worked itself out.

I can't thank you all enough for your patience and support, especially
Hercom who made this sound so easy. I guess it didn't hate me after
all, it just needed a short nap.

On May 23, 2005, at 9:00 PM, I offered this insight:

>
> On May 20, 2005, at 9:02 PM, hercom offered this insight:
>
>> Don`t worry yourself so much... since you only removed the network
>> interface
>> (en0, en1, etc) the device is in a intermediate state, if you feel
>> confident
>> doing it, remove the device entirely (rmdev -dl ent0), put the first
>> AIX CD
>> on the drive, run smitty cfgmgr and set the path to /dev/cd0 (or the
>> device
>> name in your system).
>
> OK, cool. This doesn't sound so bad, but I think I'm tripping over some
> other problem ...
>
> #rmdev -dl ent0
> ent0 removed
> #smitty cfgmgr (set to cdrom device found in the <F4> list)
> This command returned "OK", but with the following messages:
> method error (/etc/methods/cfgrcon -l rcon0):
> 0514-038 error loading kernel extension
>
> Trying to reconfigure the network interfaces (smitty tcpip -> minimum
> configuration & startup) gives the same errors as before (see below).
>
> I did notice that my production server does not have any device named
> "rcon0" and I have no idea what this is (although it has the same files
> in /etc/methods in both machines, including cfgrcon). Anyone? How do I
> make it go away (assuming I don't really want it - I might if I knew
> what in blazes it was!)
>
>> As with any major change, a full backup of the system
>> could be handy if something goes wrong....
>
> This sounded reasonable enough, so I gave it a whirl (even though the
> machine is "messed up"). Unfortunately, all I get is failure about too
> many simlinks to resolve and a link in /usr/lib/methods/chgfcparray
> *THAT POINTS TO ITSELF*. Removing that link and rerunning gives the
> same result (so I think it's "smitty savevg" that's creating the link).
>
> I'm starting to think this machine hates me ...
> ;-)
>

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

A computer lets you make more mistakes
faster than any invention in human history
with the possible exceptions of handguns and tequila.

• Previous message: Green, Simon: "Re: lsof: can't figure out how to show open files"
• In reply to: Dave Stewart: "Re: Gateway reset on reboot (was: xnptd insane after reboot) *SOLVED*"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]