 | | | No logins after several days | No logins after several days 2006-02-13 - By Paul Krizak
Back
Hmmm...I doubt that anything in /etc/exports is your culprit. Next time
you have this problem, run a ps auxwwwww and see if your processes are
going into disk-wait state (D). If so, you can try and run lsof on
those processes (or run mount) to see what mount (if any) is hanging.
This could be a total wild-goose-chase, but here at AMD 99% of the time
a system locks up in this manner, it's due to some kind of problem with
network-mounted file systems, or something like NIS/LDAP not responding.
Of course your problem *could* be those crappy Xeons you're running ;-)
Paul Krizak 5900 E. Ben White Blvd. MS 625
Advanced Micro Devices Austin, TX 78741
Linux/Unix Systems Engineering Phone: (512) 602-8775
Microprocessor Solutions Sector
Thom Paine wrote:
> I had a few mounts listed in /etc/exports, but I can remove them and
> see if that clears it up. I wasn't automounting anything. I think I
> just have local mounts defined like the share for the FC4 & FC5T2
> images.
>
> Thanks.
>
> On 2/13/06, Paul Krizak <paul.krizak@(protected)> wrote:
>> Are you NFS-automounting anything? Generally when we see a system do
>> something like that it's because the automounter is hosed and new mounts
>> aren't happening. Result: processes go into a "D" state (ps auxwwwwww)
>> as they wait on NFS I/O but nothing happens, and the load average goes
>> through the roof.
>>
>> Paul Krizak 5900 E. Ben White Blvd. MS 625
>> Advanced Micro Devices Austin, TX 78741
>> Linux/Unix Systems Engineering Phone: (512) 602-8775
>> Microprocessor Solutions Sector
>>
>>
>> D Canfield wrote:
>>> We're having a problem with one of our RHEL3 test boxes in that after a
>>> few days, the login system starts hanging. Any established ssh sessions
>>> run fine. Any running processes continue just fine. CPU load
>>> percentages and iowait displayed via top are nominal, but the load
>>> number starts growing steadily and it any attempt to login via ssh or
>>> the console accepts the username and password and then hangs with no
>>> further response. A reboot fixes this, but it occurs again every few days.
>>>
>>> Anyone have any suggestions as to where I can begin to figure out what's
>>> happening? I usually open a few root sessions on the console after each
>>> reboot so that I can poke around once it happens, but I've not found
>>> anything thus far.
>>>
>>>
>>> Thanks
>>> DC
>>>
>>> --
>>> Taroon-list mailing list
>>> Taroon-list@(protected)
>>> https://www.redhat.com/mailman/listinfo/taroon-list
>> --
>> Taroon-list mailing list
>> Taroon-list@(protected)
>> https://www.redhat.com/mailman/listinfo/taroon-list
>>
>
>
> --
> -=/>Thom
>
> --
> Taroon-list mailing list
> Taroon-list@(protected)
> https://www.redhat.com/mailman/listinfo/taroon-list
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
|