My Oracle Support Banner

Grid Infrastructure Fails to Start on Linux 7 After Node Reboot with OHASD Timed out Waiting for init.ohasd to be Started (Doc ID 2389622.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Linux x86-64
Can occur on:
Oracle Linux 7
Red Hat Enterprise 7

Symptoms

After the Cluster node rebooted, Oracle Clusterware fails to start automatically because the init.ohasd process fails to start successfully.

Clusterware alert.log from <oracle base>/diag/crs/<hostname>/crs/trace location (12.1 version and above): 

2018-03-16 14:26:47.404 [OHASD(14525)]CRS-8500: Oracle Clusterware OHASD process is starting with operating system process ID 14525

2018-03-16 14:26:47.405 [OHASD(14525)]CRS-0715: Oracle High Availability Service has timed out waiting for init.ohasd to be started.

2018-03-16 14:37:20.647 [OHASD(27441)]CRS-8500: Oracle Clusterware OHASD process is starting with operating system process ID 27441

2018-03-16 14:37:20.648 [OHASD(27441)]CRS-0715: Oracle High Availability Service has timed out waiting for init.ohasd to be started.

ohasd.trc inside <oracle base>/diag/crs/<hostname>/crs/trace location (12.1 version and above): 

CLSB:4190694976: Argument count (argc) for this daemon is 2

CLSB:4190694976: Argument 0 is: /u01/app/12.1.0/grid/bin/ohasd.bin

CLSB:4190694976: Argument 1 is: reboot

2018-03-16 14:37:20.648725 : default:4190694976: Created alert : (:OHAS00117:) : TIMED OUT WAITING FOR OHASD MONITOR 

Status check display as below: 

 

Changes

Hostname and/or /etc/hostname file was changed at Operating System Level

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!


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