ERROR : <MACHINE> has state: STILL ALIVE AFTER REBOOT HAS BEEN INITIATED
(Doc ID 2712735.1)
Last updated on JANUARY 21, 2022
Applies to:
Oracle Exadata Storage Server Software - Version 20.0.0.0.0 to 20.0.0.0.0 [Release 20.0]Information in this document applies to any platform.
Symptoms
Customer is patching the database nodes
The DB node 1 was patched w/o trouble then they attempted to update nodes 2,3 and 4. patchmgr reported nodes 2 and 3 were not bounced, when
in fact the nodes were rebooted:
2020-08-01 17:16:28 -0400 :ERROR : Node(s) is still alive after 10 minutes of timeout: <MACHINE2>,<MACHINE3>
2020-08-01 17:16:28 -0400 :ERROR : An error occurred during the reboot of <MACHINE2>,<MACHINE3>.
2020-08-01 17:16:28 -0400 :ERROR : Contact Oracle Support to investigate if a safe manual reboot or power cycle can be performed.
2020-08-01 17:16:28 -0400 :ERROR : Waiting to ensure node(s) is down before reboot.
....
2020-08-01 17:16:28 -0400 :ERROR : <MACHINE2> has state: STILL ALIVE AFTER REBOOT HAS BEEN INITIATED
2020-08-01 17:16:28 -0400 :ERROR : <MACHINE3> has state: STILL ALIVE AFTER REBOOT HAS BEEN INITIATED
2020-08-01 17:40:03 -0400 : : <MACHINE4> has state: SUCCESS
2020-08-01 17:16:28 -0400 :ERROR : An error occurred during the reboot of <MACHINE2>,<MACHINE3>.
2020-08-01 17:16:28 -0400 :ERROR : Contact Oracle Support to investigate if a safe manual reboot or power cycle can be performed.
2020-08-01 17:16:28 -0400 :ERROR : Waiting to ensure node(s) is down before reboot.
....
2020-08-01 17:16:28 -0400 :ERROR : <MACHINE2> has state: STILL ALIVE AFTER REBOOT HAS BEEN INITIATED
2020-08-01 17:16:28 -0400 :ERROR : <MACHINE3> has state: STILL ALIVE AFTER REBOOT HAS BEEN INITIATED
2020-08-01 17:40:03 -0400 : : <MACHINE4> has state: SUCCESS
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |