Hi all.
Two days ago a server got freezed, not responding at console or by LAN. I noticed both caps lock and scroll lock LEDs at the keyboard flashing.
I think this could be a hardware problem, but I don't recall where I read about this flashing indicators.
The hardware is an Intel based white box PC running CentOS 3.5 fully updated.
Anybody knows what the flashing LEDs means?
Regards.
Hugo Perez Casanova wrote:
Hi all.
Two days ago a server got freezed, not responding at console or by LAN. I noticed both caps lock and scroll lock LEDs at the keyboard flashing.
I think this could be a hardware problem, but I don't recall where I read about this flashing indicators.
The hardware is an Intel based white box PC running CentOS 3.5 fully updated.
Anybody knows what the flashing LEDs means?
Regards.
The last time I saw flashing LEDs was during a kernel panic. This usually is a hardware issue (it has been for me). YMMV
HTH,
Alex
Thanks everybody.
Yes, it seems to be a hardware issue.
Regards.
On Fri, 2005-08-19 at 08:54, Alex White wrote:
Hugo Perez Casanova wrote:
Hi all.
Two days ago a server got freezed, not responding at console or by LAN. I noticed both caps lock and scroll lock LEDs at the keyboard flashing.
I think this could be a hardware problem, but I don't recall where I read about this flashing indicators.
The hardware is an Intel based white box PC running CentOS 3.5 fully updated.
Anybody knows what the flashing LEDs means?
Regards.
The last time I saw flashing LEDs was during a kernel panic. This usually is a hardware issue (it has been for me). YMMV
HTH,
Alex _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
----- IEE José Hugo Pérez Casanova Gerente de Sistemas Linux Soluciones Integrales www.linux-si.com
It may not!!
I have the same issue with CentOS 3.x The box freezes if I leave auditd enabled.
Once I killed auditd my problems were over (I too suspected hardware). Now I get lots of laus(y) errors in my syslogd but the freezes are gone.
Never found out what the problem was, just live with it
On Fri, 19 Aug 2005, Hugo Perez Casanova wrote:
Thanks everybody.
Yes, it seems to be a hardware issue.
Regards.
On Fri, 2005-08-19 at 08:54, Alex White wrote:
Hugo Perez Casanova wrote:
Hi all.
Two days ago a server got freezed, not responding at console or by LAN. I noticed both caps lock and scroll lock LEDs at the keyboard flashing.
I think this could be a hardware problem, but I don't recall where I read about this flashing indicators.
The hardware is an Intel based white box PC running CentOS 3.5 fully updated.
Anybody knows what the flashing LEDs means?
Regards.
The last time I saw flashing LEDs was during a kernel panic. This usually is a hardware issue (it has been for me). YMMV
HTH,
Alex _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
IEE José Hugo Pérez Casanova Gerente de Sistemas Linux Soluciones Integrales www.linux-si.com
On 8/21/05, Remco Barendse redhat@barendse.to wrote:
It may not!!
I have the same issue with CentOS 3.x The box freezes if I leave auditd enabled.
Once I killed auditd my problems were over (I too suspected hardware). Now I get lots of laus(y) errors in my syslogd but the freezes are gone.
Never found out what the problem was, just live with it
I also had a problem with auditd on Cent3. I noticed I could not login a few days ago and cron had not run for over a week. I was able to get in through webmin and do some tasks. After rebooting I had the same problem. I set most services to not start on boot up and started each one separately. When I started auditd, the problem came back.
On Mon, 22 Aug 2005, Dave wrote:
On 8/21/05, Remco Barendse redhat@barendse.to wrote:
It may not!!
I have the same issue with CentOS 3.x The box freezes if I leave auditd enabled.
Once I killed auditd my problems were over (I too suspected hardware). Now I get lots of laus(y) errors in my syslogd but the freezes are gone.
Never found out what the problem was, just live with it
I also had a problem with auditd on Cent3. I noticed I could not login a few days ago and cron had not run for over a week. I was able to get in through webmin and do some tasks. After rebooting I had the same problem. I set most services to not start on boot up and started each one separately. When I started auditd, the problem came back.
Heh :) At least I now know it's not me going crazy :)
Did you manage to get rid of those stupid laus errors?
On Mon, 22 Aug 2005, Dave wrote:
On 8/21/05, Remco Barendse redhat@barendse.to wrote:
It may not!!
I have the same issue with CentOS 3.x The box freezes if I leave auditd enabled.
Once I killed auditd my problems were over (I too suspected hardware). Now I get lots of laus(y) errors in my syslogd but the freezes are gone.
Laus errors -- update vixie-cron to fix, had same problem on RHEL3.1 box
On Wed, 24 Aug 2005, Sean O Sullivan wrote:
On Mon, 22 Aug 2005, Dave wrote:
On 8/21/05, Remco Barendse redhat@barendse.to wrote:
It may not!!
I have the same issue with CentOS 3.x The box freezes if I leave auditd enabled.
Once I killed auditd my problems were over (I too suspected hardware). Now I get lots of laus(y) errors in my syslogd but the freezes are gone.
Laus errors -- update vixie-cron to fix, had same problem on RHEL3.1 box
When looking for the fix I found that this has been fixed by RedHat
</stupid question mode on> why isn't this update in the standard repository? </stupid question mode off>
I prefer not to install stuff outside the standard repos to prevent that I miss important updated stuff
-
Alex White -
Dave -
Hugo Perez Casanova -
Remco Barendse -
Sean O Sullivan