一節點啟動不起來(ocssd)
日誌報錯:
[cssd(28117)]CRS-1603:CSSD on node rztjdb2 shutdown by user.
2017-04-19 22:37:07.426:
[ohasd(27732)]CRS-2765:Resource 'ora.cssdmonitor' has failed on server 'rztjdb2'.
2017-04-19 22:37:08.940:
[cssd(3684)]CRS-1713:CSSD daemon is started in clustered mode
2017-04-19 22:37:10.617:
[ohasd(27732)]CRS-2767:Resource state recovery not attempted for 'ora.diskmon' as its target state is OFFLINE
2017-04-19 22:37:14.537:
[cssd(3684)]CRS-1707:Lease acquisition for node rztjdb2 number 2 completed
2017-04-19 22:37:15.785:
[cssd(3684)]CRS-1605:CSSD voting file is online: ORCL:OCR_VOT; details in /u01/app/11.2.0.4/grid/log/rztjdb2/cssd/ocssd.log.
2017-04-19 22:47:08.022:
[/u01/app/11.2.0.4/grid/bin/cssdagent(3617)]CRS-5818:Aborted command 'start' for resource 'ora.cssd'. Details at (:CRSAGF00113:) {0:0:2} in /u01/app/11.2.0.4/grid/log/rztjdb2/agent/ohasd/oracssdagent_root//oracssdagent_root.log.
2017-04-19 22:47:08.022:
[cssd(3684)]CRS-1656:The CSS daemon is terminating due to a fatal error; Details at (:CSSSC00012:) in /u01/app/11.2.0.4/grid/log/rztjdb2/cssd/ocssd.log
2017-04-19 22:47:08.022:
[cssd(3684)]CRS-1603:CSSD on node rztjdb2 shutdown by user.
2017-04-19 22:47:13.135:
[ohasd(27732)]CRS-2765:Resource 'ora.cssdmonitor' has failed on server 'rztjdb2'.
2017-04-19 22:47:13.182:
[ohasd(27732)]CRS-2807:Resource 'ora.asm' failed to start automatically.
2017-04-19 22:47:13.182:
[ohasd(27732)]CRS-2807:Resource 'ora.cluster_interconnect.haip' failed to start automatically.
2017-04-19 22:47:13.182:
[ohasd(27732)]CRS-2807:Resource 'ora.crsd' failed to start automatically.
2017-04-19 22:47:13.182:
[ohasd(27732)]CRS-2807:Resource 'ora.cssd' failed to start automatically.
2017-04-19 22:47:13.182:
[ohasd(27732)]CRS-2807:Resource 'ora.ctssd' failed to start automatically.
2017-04-19 22:47:13.182:
[ohasd(27732)]CRS-2807:Resource 'ora.evmd' failed to start automatically.
2017-04-19 22:47:13.185:
[mdnsd(28030)]CRS-5602:mDNS service stopping by request.
2017-04-19 22:47:15.930:
[gpnpd(28040)]CRS-2329:GPNPD on node rztjdb2 shutdown.
解決:
初步判斷是由於心跳出現問題導致,後排查機房,發現心跳線鬆動,解決之後正常啟動
[cssd(28117)]CRS-1603:CSSD on node rztjdb2 shutdown by user.
2017-04-19 22:37:07.426:
[ohasd(27732)]CRS-2765:Resource 'ora.cssdmonitor' has failed on server 'rztjdb2'.
2017-04-19 22:37:08.940:
[cssd(3684)]CRS-1713:CSSD daemon is started in clustered mode
2017-04-19 22:37:10.617:
[ohasd(27732)]CRS-2767:Resource state recovery not attempted for 'ora.diskmon' as its target state is OFFLINE
2017-04-19 22:37:14.537:
[cssd(3684)]CRS-1707:Lease acquisition for node rztjdb2 number 2 completed
2017-04-19 22:37:15.785:
[cssd(3684)]CRS-1605:CSSD voting file is online: ORCL:OCR_VOT; details in /u01/app/11.2.0.4/grid/log/rztjdb2/cssd/ocssd.log.
2017-04-19 22:47:08.022:
[/u01/app/11.2.0.4/grid/bin/cssdagent(3617)]CRS-5818:Aborted command 'start' for resource 'ora.cssd'. Details at (:CRSAGF00113:) {0:0:2} in /u01/app/11.2.0.4/grid/log/rztjdb2/agent/ohasd/oracssdagent_root//oracssdagent_root.log.
2017-04-19 22:47:08.022:
[cssd(3684)]CRS-1656:The CSS daemon is terminating due to a fatal error; Details at (:CSSSC00012:) in /u01/app/11.2.0.4/grid/log/rztjdb2/cssd/ocssd.log
2017-04-19 22:47:08.022:
[cssd(3684)]CRS-1603:CSSD on node rztjdb2 shutdown by user.
2017-04-19 22:47:13.135:
[ohasd(27732)]CRS-2765:Resource 'ora.cssdmonitor' has failed on server 'rztjdb2'.
2017-04-19 22:47:13.182:
[ohasd(27732)]CRS-2807:Resource 'ora.asm' failed to start automatically.
2017-04-19 22:47:13.182:
[ohasd(27732)]CRS-2807:Resource 'ora.cluster_interconnect.haip' failed to start automatically.
2017-04-19 22:47:13.182:
[ohasd(27732)]CRS-2807:Resource 'ora.crsd' failed to start automatically.
2017-04-19 22:47:13.182:
[ohasd(27732)]CRS-2807:Resource 'ora.cssd' failed to start automatically.
2017-04-19 22:47:13.182:
[ohasd(27732)]CRS-2807:Resource 'ora.ctssd' failed to start automatically.
2017-04-19 22:47:13.182:
[ohasd(27732)]CRS-2807:Resource 'ora.evmd' failed to start automatically.
2017-04-19 22:47:13.185:
[mdnsd(28030)]CRS-5602:mDNS service stopping by request.
2017-04-19 22:47:15.930:
[gpnpd(28040)]CRS-2329:GPNPD on node rztjdb2 shutdown.
解決:
初步判斷是由於心跳出現問題導致,後排查機房,發現心跳線鬆動,解決之後正常啟動
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29802484/viewspace-2137634/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- MySQL資料庫當機,啟動不起來,教你一招搞定!MySql資料庫
- unix cm單節點啟動
- Hadoop 啟動namenode節點失敗Hadoop
- RAC二節點啟動異常
- 【RAC】Oracle19.13之後的grid,節點重啟後不會自動驅動Oracle
- [Kubernetes]node節點pod無法啟動/節點刪除網路重置
- 一起來梳理JVM知識點JVM
- 為什麼移動辦公APP火不起來APP
- Jenkins 節點已啟動,但是一直顯示未線上?Jenkins
- docker-swarm容器固定到node節點啟動DockerSwarm
- Oracle 19c rac安裝,只能啟動一個節點的ASMOracleASM
- 如何判斷LInux程式完全啟動起來的呢Linux
- w10安裝後啟動不起來怎麼辦_w10安裝後無法啟動的解決方法
- MySQL安裝後在服務裡找不到或者服務啟動不起來解決方法MySql
- 12.2新特性之ADG多節點啟動MRP程式
- RAC節點啟動失敗--ASM無法連線ASM
- Python學習起來難不難?Python
- thinkphp6專案起不來PHP
- 上海下雨了,不來點函式防抖、節流壓壓驚?函式
- 一款讓照片動起來的SDK
- 【GoLang 那點事】gRPC-Server 啟動原始碼分析,一起弄懂它(八)GolangRPCServer原始碼
- 火不起來的桌遊,差點消失的展會,和一個東北人的求生之路
- GraalVM和Spring Native嚐鮮,一步步讓Springboot啟動飛起來,66ms完成啟動LVMSpring Boot
- 谷歌雲遊戲來了?抱歉,香不起來谷歌遊戲
- 2021 都捲成這樣了,眨眼迎來 2022 還不趕緊動起來?
- oracle兩節點RAC,由於gipc導致某節點crs無法啟動問題分析Oracle
- 【劉文彬】EOS多節點組網:商業場景分析以及節點啟動時序
- grid軟體複製到另外的節點啟動crs
- 記一次oracle 19c RAC叢集重啟單節點DB啟動異常(二)Oracle
- MacBook 電腦 nginx 執行不起來MacNginx
- Solaris叢集節點重啟
- 移動端適配不會,千萬別點進來
- CSS——讓“盒子”動起來:① 浮動CSS
- rac二節點例項redo故障無法啟動修復
- Activiti5.2 自動完成第一節點流程
- 呀!ASM例項起不來可咋整ASM
- 內部論壇緣何火不起來
- HDFS動態新增節點
- hadoop動態摘除節點Hadoop