Crs-1726 Process Failed To Run In Real-time Priority (2025-2027)

crsctl set resourceattr <res_name> -attr "REAL_TIME_PRIORITY=0" -update (Only do this after confirming no negative impact.) crsctl stat res -t tail -f $GRID_HOME/log/`hostname`/crsd/crsd.log | grep -i "1726" If the error disappears, the fix worked. If not, check OS logs ( dmesg , audit.log ) for denied sched_setscheduler calls.

docker run --cap-add=SYS_NICE ... If the cluster runs fine and you don't need strict real-time guarantees, you can ignore it. To suppress the message, set: crs-1726 process failed to run in real-time priority

setenforce 0 crsctl stop crs && crsctl start crs If error disappears, adjust SELinux policy (allow sched_setscheduler ). Grant CAP_SYS_NICE capability: If the cluster runs fine and you don't

grid soft rtprio unlimited grid hard rtprio unlimited oracle soft rtprio unlimited oracle hard rtprio unlimited Also ensure these lines exist for memlock (often required together): It typically appears in the crsd

CRS-1726 is an Oracle Clusterware (Grid Infrastructure) error. It typically appears in the crsd.log or when manually starting/stopping resources. The full message usually looks like: CRS-1726: Process 'string' failed to run in real-time priority. Cause Oracle Clusterware attempts to run its critical processes (e.g., oraagent , orarootagent , cssdmonitor ) with real-time (RT) scheduling policy (SCHED_FIFO or SCHED_RR) to achieve low latency and predictable performance.