使用者在重啟伺服器後,發現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,問題解決