My Oracle Support Banner

A cluster node hung and was unexpectedly rebooted (Doc ID 2328894.1)

Last updated on MAY 21, 2020

Applies to:

Oracle Cloud Infrastructure - Version N/A and later
Linux OS - Version Oracle Linux 5.11 and later
Information in this document applies to any platform.

Symptoms

The system, which was part of a cluster, became non-responsive, and then rebooted unexpectedly.
The following errors were logged to multiple nodes within the cluster immediately prior to the affected server rebooting.

Sep 15 21:23:55 localhost kernel: sd 1:0:1:41: timing out command, waited 60s
Sep 15 21:23:55 localhost kernel: sd 1:0:1:42: timing out command, waited 60s
Sep 15 21:23:55 localhost kernel: sd 1:0:1:45: timing out command, waited 60s
Sep 15 21:23:55 localhost kernel: sd 1:0:1:34: timing out command, waited 60s
Sep 15 21:23:55 localhost kernel: sd 1:0:1:32: timing out command, waited 60s
Sep 15 21:23:55 localhost kernel: sd 1:0:1:20: timing out command, waited 60s


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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.