用户在重启服务器后，发现RAC中某节点无法查看RAC状态
查看RAC状态时报错
./crs_stat -t
CRS-0184: Cannot communicate with the CRS daemo
由于无法与crs通信，首先查看crs健康状况
[Oracle@oms bin]$ ./crsctl check crs
Failure 1 contacting CSS daemon
Cannot communicate with CRS
Cannot communicate with EVM
发现crs未启动，出现此问题可能和后台进程没有启动有关。
查看crs相关进程
[oracle@oms ~]$ ps -ef|grep crs
root 5142 1 0 16:31 ? 00:00:00 /bin/sh /etc/init.d/init.crsd run
root 19033 5370 0 17:59 ? 00:00:00 /bin/su -l oracle -c /u01/app/oracle/crs/bin/crsctl check boot > /tmp/crsctl.5370
oracle 19034 19033 0 17:59 ? 00:00:00 -bash -c /u01/app/oracle/crs/bin/crsctl check boot > /tmp/crsctl.5370
root 19052 5234 0 17:59 ? 00:00:00 /bin/su -l oracle -c /u01/app/oracle/crs/bin/crsctl check boot > /tmp/crsctl.5234
oracle 19053 19052 0 17:59 ? 00:00:00 -bash -c /u01/app/oracle/crs/bin/crsctl check boot > /tmp/crsctl.5234
oracle 19097 19053 0 17:59 ? 00:00:00 /u01/app/oracle/crs/bin/crsctl.bin check boot
oracle 19101 19034 0 17:59 ? 00:00:00 /u01/app/oracle/crs/bin/crsctl.bin check boot
oracle 19184 19143 0 18:00 pts/1 00:00:00 grep crs
根据相关进程信息找到报错的日志痕迹，查看相关crs日志文件
[oracle@oms bin]$ cat /tmp/crsctl.5370
Failed 3 to bind listening endpoint: (ADDRESS=(PROTOCOL=tcp)(HOST=oms-priv))
根据上面提示联想多半是和网络配置有关，首先查看网络配置文件
[root@oms init.d]# ll /etc/hosts
-rw-r--r-- 2 root root 263 Dec 25 2011 /etc/hosts
检查这个文件并无权限光管问题
[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 oms.localdomain
192.168.17.138 dbsv.localdomain dbsv
--------------------------------------分割线 --------------------------------------
相关阅读：
VIP不能正常启动，报错CRS-1006
RAC如何启动状态为UNKNOWN的资源&&PRKS-1009,CRS-1028,CRS-0223
Oracle 11g RAC 停机之后启动rac 时报 CRS-0184: Cannot communicate with the CRS daemon.
CRS报CRS-2409告警信息问题分析与处理
Oracle 11g RAC 执行root.sh时遭遇 CRS-0184/PRCR-1070
--------------------------------------分割线 --------------------------------------
显然，配置文件中的主机名和节点主机的主机名不对应，很明显这是不同相关人员为实现不同目的未沟通对配置文件进行了更改，造成RAC 重启后无法启动，找到相应资源，讲hosts文件中的错误修正后，重启RAC，问题解决
：