Cluster Ready Services Processes and Log dirs

Here is a short description of each of the CRS daemon processes:

CRSD:
- Engine for HA operation
- Manages 'application resources'
- Starts, stops, and fails 'application resources' over
- Spawns separate 'actions' to start/stop/check application resources
- Maintains configuration profiles in the OCR (Oracle Configuration Repository)
- Stores current known state in the OCR.
- Runs as root
- Is restarted automatically on failure
OCSSD:
- OCSSD is part of RAC and Single Instance with ASM
- Provides access to node membership
- Provides group services
- Provides basic cluster locking
- Integrates with existing vendor clusteware, when present
- Can also runs without integration to vendor clustware
- Runs as Oracle.
- Failure exit causes machine reboot.
--- This is a feature to prevent data corruption in event of a split brain.
EVMD:
- Generates events when things happen
- Spawns a permanent child evmlogger
- Evmlogger, on demand, spawns children
- Scans callout directory and invokes callouts.
- Runs as Oracle.
- Restarted automatically on failure

CRS LOG DIRECTORIES-------------------
When troubleshooting CRS problems, it is important to review the directoriesunder the CRS Home.
$ORA_CRS_HOME/crs/log
- This directory includes traces for CRS resources that arejoining, leaving, restarting, and relocating as identified by CRS.
$ORA_CRS_HOME/crs/init
- Any core dumps for the crsd.bin daemon should be writtenhere. Note 1812.1 could be used to debug these.
$ORA_CRS_HOME/css/log
- The css logs indicate all actions such as reconfigurations, missed checkins , connects, and disconnects from the clientCSS listener . In some cases the logger logs messages with the category of (auth.crit) for the reboots done by oracle. This could be used for checking the exact time when the reboot occured.
$ORA_CRS_HOME/css/init
- Core dumps from the ocssd primarily and the pid for the css daemon whose death is treated as fatal are located here. If there are abnormal restarts for css then the core files will have the formats of core.. Note 1812.1 could be used to debug these.
$ORA_CRS_HOME/evm/log
- Log files for the evm and evmlogger daemons. Not usedas often for debugging as the CRS and CSS directories.
$ORA_CRS_HOME/evm/init
- Pid and lock files for EVM. Core files for EVM shouldalso be written here. Note 1812.1 could be used to debug these.
$ORA_CRS_HOME/srvm/log
- Log files for OCR.

****************************************************
keywords CRS crs dir process
****************************************************