Database - RAC/Scalability (MOSC)

MOSC Banner

V490 rebooted repeatedly suspecting Oprocd cause system to reboot

edited Oct 3, 2013 5:45AM in Database - RAC/Scalability (MOSC) 3 commentsAnswered
 Hi 

Pls advise below logs cause system to reboot.

* Oprocd – Cluster fencing module
* Cssd – Cluster sychronization module which manages node membership
* Oclsomon – Cssd monitor which will monitor for cssd hangs

Further checking on kedb2's CSSD log (as attached):

[    CSSD]2013-09-29 06:07:48.743 [18] >WARNING: clssnmPollingThread: node kedb1 (1) at 50 2.123747e-314artbeat fatal, eviction in 14.544 seconds
[    CSSD]2013-09-29 06:07:48.743 [18] >TRACE:   clssnmPollingThread: node kedb1 (1) is impending reconfig, flag 1039, misstime 15456
[    CSSD]2013-09-29 06:07:48.743 [18] >TRACE:   clssnmPollingThread: diskTimeout set to (27000)ms impending reconfig status(1)
[    CSSD]2013-09-29 06:07:49.753 [18] >WARNING: clssnmPollingThread: node kedb1 (1) at 50 2.123747e-314artbeat fatal, eviction in 13.534 seconds
[    CSSD]2013-09-29 06:07:55.812 [18] >WARNING: clssnmPollingThread: node kedb1 (1) at 75 2.123747e-314artbeat fatal, eviction in 7.474 seconds

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center