[--snip--]
> What kind of hard drive? If the hard drive is having a read error when
> attempting to grab a chunk of virtual memory stored on the swap partition,
> that is a critical error which will freeze any process or thread relying on
> that chunk of memory. Your WWW server may be running just fine because it's
> currently retained in RAM and not swapped out.
Thanks alot for your great tips.
It's an old FUJITSU MPC3032AT at about 2Gb.
If it's an harddrive error, wouldn't the logs say something about
Drive SeekError { xxxxxxx } as it "should" be when the harddrive is
damaged?
Cheers,
Martin
> Download a hard drive utility from the hard drive manufacturer and boot to
> an old DOS disk to run it.
>
> You could alternately boot Linux to single user mode, unmount the swap
> partition and try to run an extensive fsck check against it.
>
> I would try this both now and right after the problem occurs.
>
> You could also disable your swap partition (/etc/fstab) since you have a
> fair amount of RAM just to prove if it's the hard drive or other problem. I
> disagree with earlier posting that your RAM could be the problem. That would
> show other critical errors that would be unrelated to virtual memory. While
> waiting to see if a problem occurs, keep another machine telnetted into your
> server running the "top" process so that you get a snapshot of the RAM and
> process running just before the freeze occurs.
>
>
>
>
>
> ------------------------------------------------------------------------
> To unsubscribe email security-discuss-request@linuxsecurity.com
> with "unsubscribe" in the subject of the message.
>
>
------------------------------------------------------------------------
To unsubscribe email security-discuss-request@linuxsecurity.com
with "unsubscribe" in the subject of the message.
