Cluster Failed to Start Due to Problem With Socket Pipe npohasd
(Doc ID 1612325.1)
Last updated on DECEMBER 25, 2019
Applies to:Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
CRS stack not coming up on one node.
Sockets permission issue with Grid Infrastructure and CRS stack fails to come up with crsctl start crs after the server reboot.
tusc output -> seems stuck in sleeping.
test-133:(root)/>/hpk/tusc -faep -T %H:%M:%S -p 28680
( Attached to process 28680 ("/oracle/app/11.2.0/grid/bin/ohasd.bin reboot") [64 -bit] ) 19:03:42  open(0x40000000007789b0, O_WRONLY|0x800, 023240) [sleeping] tusc: ttrace(TT_PROC_STOP, 0, 0, 0, 0, 0): Permission denied
Problem Started after patching failed and the server rebooted.
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