CRS-0184: CannotcommunicatewiththeCRSdaemo diagnostics

CRS-0184: CannotcommunicatewiththeCRSdaemo diagnostics

CRS-0184: Cannot communicate with the CRS daemo diagnostics

After restarting the server, the user finds that a node in RAC cannot view the RAC status.
An error occurred while checking the RAC status.
./Crs_stat-t
CRS-0184: Cannot communicate with the CRS daemo
Because it cannot communicate with crs, check the crs health status first.
[Oracle @ oms bin] $./crsctl check crs
Failure 1 contacting CSS daemon
Cannot communicate with CRS
Cannot communicate with EVM
Crs is not started. This problem may be related to the failure of background processes.

View crs Processes
[Oracle @ oms ~] $ Ps-ef | grep crs
Root 5142 1 0? 00:00:00/bin/sh/etc/init. d/init. crsd run
Root 19033 5370 0? 00:00:00/bin/su-l oracle-c/u01/app/oracle/crs/bin/crsctl check boot>/tmp/crsctl.5370
Oracle 19034 19033 0? 00:00:00-bash-c/u01/app/oracle/crs/bin/crsctl check boot>/tmp/crsctl.5370
Root 19052 5234 0? 00:00:00/bin/su-l oracle-c/u01/app/oracle/crs/bin/crsctl check boot>/tmp/crsctl.5234
Oracle 19053 19052 0? 00:00:00-bash-c/u01/app/oracle/crs/bin/crsctl check boot>/tmp/crsctl.5234
Oracle 19097 19053 0? 00:00:00/u01/app/oracle/crs/bin/crsctl. bin check boot
Oracle 19101 19034 0? 00:00:00/u01/app/oracle/crs/bin/crsctl. bin check boot
Oracle 19184 19143 0 00:00:00 pts/1 grep crs
Locate the error log trace based on the process information and view the related crs log file.
[Oracle @ oms bin] $ cat/tmp/crsctl.5370
Failed 3 to bind listening endpoint: (ADDRESS = (PROTOCOL = tcp) (HOST = oms-priv ))
According to the above prompt, Lenovo is mostly related to network configuration. First, check the network configuration file.
[Root @ oms init. d] # ll/etc/hosts
-Rw-r -- 2 root 263 Dec 25 2011/etc/hosts
Check that this file has no permission for optical communication.
[Root @ oms init. d] # cat/etc/hosts
# Do not remove the following line, or various programs
# That require network functionality will fail.
127.0.0.1 localhost. localdomain localhost
192.168.17.139 oms. localdomain
192.168.17.138 dbsv. localdomain dbsv

-------------------------------------- Split line --------------------------------------

Related reading:

VIP cannot be started properly, error CRS-1006

How RAC starts Resources in the UNKNOWN state & PRKS-1009, CRS-1028, CRS-0223

Oracle 11g RAC after starting rac report CRS-0184: Cannot communicate with the CRS daemon.

Analysis and Handling of CRS CRS-2409 alarm information

CRS-0184/PRCR-1070 when Oracle 11g RAC executes root. sh

-------------------------------------- Split line --------------------------------------

Obviously, the host name in the configuration file does not correspond to the Host Name of the node host. Obviously, this is because the configuration file has not been changed for different purposes, and the RAC cannot be started after restart, find the corresponding resource, talk about the error correction in the hosts file, restart RAC, and solve the problem