Re: HP Trap Alerts
- From: redhat@xxxxxxxxxxxxxx
- Date: Thu, 27 Jul 2006 21:59:26 -0600
If you are using up2date, hopefully your config does not remove the old
kernel when it updates to the new kernel, most likely this is not the
case. The default setup should allow you to do as the other posters
suggested. Although it will not help you this time, you may want to
consider enabling rollbacks if you are using up2date. Then when
something like this happens you can simply rollback to the previous
state. It takes a little more disk space and updates are a little
slower, but it has saved me a few times.
On Thu, 27 Jul 2006 11:56:29 -0500, "Paul Crittenden"
<paul.crittenden@xxxxxxxxxxx> said:
We are running RHE 4.0 on an HP DL385. Up until a week ago we had no
problems. Since last Thursday and periodically since then the server has
rebooted with HP ASR trap alerts being the only indication that it
happened. The only thing that changed is that on Friday, July 14, I
updated the server with patches from Redhat. I know that a new kernel
was part of this update and am assuming that may be the problem. I know
we used to be able to choose which kernel to boot, although I don't know
for sure if it was available in RHE 4.0. How can I go back to an older
kernel and see if this fixes my problem? Does anyone have any other
suggestions.
Paul Crittenden
Computer Systems Manager
Simpson College
Phone: 515-961-1680
Email: paul.crittenden@xxxxxxxxxxx
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
- References:
- HP Trap Alerts
- From: Paul Crittenden
- HP Trap Alerts
- Prev by Date: Re: HP Trap Alerts
- Next by Date: RE: automatic logout
- Previous by thread: Re: HP Trap Alerts
- Index(es):
Relevant Pages
|
|
