spausedd service logs error "Operation not permitted (1): Can't set SCHED_RR" at startup

Solution In Progress - Updated -

Issue

  • spausedd.service fails to set real-time scheduling priority.

    [root@HSVWDP01 tmp]# systemctl status spausedd.service
    ● spausedd.service - Scheduler Pause Detection Daemon
       Loaded: loaded (/usr/lib/systemd/system/spausedd.service; enabled; vendor preset: disabled)
       Active: active (running) since Wed 2020-11-11 09:30:19 +07; 5s ago
         Docs: man:spausedd
      Process: 26943 ExecStart=/usr/bin/spausedd -D (code=exited, status=0/SUCCESS)
     Main PID: 26946 (spausedd)
        Tasks: 1
       Memory: 1.1M
       CGroup: /system.slice/spausedd.service
               └─26946 /usr/bin/spausedd -D
    
    Nov 11 09:30:19 HSVWDP01 systemd[1]: Starting Scheduler Pause Detection Daemon...
    Nov 11 09:30:19 HSVWDP01 systemd[1]: Started Scheduler Pause Detection Daemon.
    Nov 11 09:30:19 HSVWDP01 spausedd[26946]: Operation not permitted (1): Can't set SCHED_RR
    Nov 11 09:30:19 HSVWDP01 spausedd[26946]: Using VMGuestLib
    Nov 11 09:30:19 HSVWDP01 spausedd[26946]: Running main poll loop with maximum timeout 200 and steal threshold 100%
    
  • Note: A segmentation fault masks this issue, and fixes for both issues should be released at the same time. The error shown above and in the title of this solution can only be observed when the segmentation fault bug is fixed, so you will likely never see this exact error in an official release of the spausedd package. Nonetheless, this issue is one possible error underlying a segmentation fault and crash.

Environment

  • Red Hat Enterprise Linux 7 (with the High Availability Add-on)
  • Red Hat Enterprise Linux 8 (with the High Availability Add-on)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In