compaq server stop responding using RedHat AS 2.1

From: Lovro VRE© (lovro_at_kopa.si)
Date: 10/27/03


Date: Mon, 27 Oct 2003 09:34:41 +0100

Hi,

I installed RedHat Linux Advanced Server 2.1 on Compaq Proliant 370 DL. It
works fine for a time, but suddenly it stops to respond.

Ping still works fine, but I'm not able to connect throug telnet or any
other network service, also the console is dead. The only solution is to
power off the machine.

After reboot I lways checked all logs, but there is nothing helpful in logs.
I also checked sar logs, but there is nothing strange inthere. sar also
stops making any additional records in its log when the problem occured.

The same problems occured on another Compaq Server ML 580.

Is there any idea, how can I solve the problem or how can I discover what
cause the problem?

Regards,
Lovro



Relevant Pages

  • compaq server stop responding using RedHat AS 2.1
    ... I installed RedHat Linux Advanced Server 2.1 on Compaq Proliant 370 DL. ... After reboot I lways checked all logs, but there is nothing helpful in logs. ... stops making any additional records in its log when the problem occured. ...
    (alt.os.linux.redhat)
  • Re: compaq server stop responding using RedHat AS 2.1
    ... >> After reboot I lways checked all logs, but there is nothing helpful in ... >> stops making any additional records in its log when the problem occured. ... > it was some dma bug with the cdroms, so after turning off dma on the ... > cdroms everything was ok. ...
    (linux.redhat)
  • Re: compaq server stop responding using RedHat AS 2.1
    ... > After reboot I lways checked all logs, but there is nothing helpful in logs. ... > stops making any additional records in its log when the problem occured. ... it was some dma bug with the cdroms, so after turning off dma on the ... cdroms everything was ok. ...
    (alt.os.linux.redhat)
  • Re: compaq server stop responding using RedHat AS 2.1
    ... > After reboot I lways checked all logs, but there is nothing helpful in logs. ... > stops making any additional records in its log when the problem occured. ... it was some dma bug with the cdroms, so after turning off dma on the ... cdroms everything was ok. ...
    (linux.redhat)