Download Print this page

Node Continuously Reboots; Crs Fails To Start When You Reboot The Nodes, Or After Entering /Etc/Init.d/Init.crs Start - Dell PowerEdge Troubleshooting Manual

Oracle database on enterprise linux x86_64
Hide thumbs Also See for PowerEdge:

Advertisement

Available languages
  • EN

Available languages

  • ENGLISH, page 1

Node continuously reboots

Node reboots continuously when the node does not have access to the
quorum disk on shared storage.
Perform the following steps:
Start Linux in single-user mode and enter the following command:
a
/etc/init.d/init.crs disable
Verify that the quorum disk is available and the private interconnect
b
is alive.
Reboot and type: /etc/init.d/init.crs enable
c
If the private interconnect is down:
Start Linux in single-user mode.
a
Enter the following command:
b
/etc/init.d/init.crs disable
Verify that the node can ping over the private interconnect to the
c
remaining nodes in the cluster.
Enter the following command:
d
/etc/init.d/init.crs enable
Reboot the system. In some cases, the network has a latency of up to
30 seconds before it can ping the remaining nodes in the cluster after
reboot. If this situation occurs, add the following line to the beginning of
your /etc/inet.d/init.crs file and reboot your system: /bin/sleep 30.
CRS fails to start when you reboot the nodes, or after entering
/etc/init.d/init.crs start
1 Change /etc/iscsi/iscsid.conf
node.session.timeo.replacement_timeout = 144
to
node.session.timeo.replacement_timeout = 30
2 Logout from the existing iscsi sessions, rediscover, and re-login to set the
change in timeout.
14
Troubleshooting

Advertisement

loading

This manual is also suitable for:

Poweredge series