FS#34051 - [watchdog] Starting watchdog via systemd results in a cannot set scheduler error.

Attached to Project: Arch Linux
Opened by Jameson Pugh (ImNtReal) - Wednesday, 27 February 2013, 17:40 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 06 October 2017, 02:31 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Starting watchdog via systemd results in a cannot set scheduler error. According to https://bugzilla.redhat.com/show_bug.cgi?id=915270, simply adding ControlGroup=cpu:/ to the unit file will correct the problem.

Additional info:
* watchdog 5.13-1
* watchdog[29871]: cannot set scheduler (errno = 1 = 'Operation not permitted')


Steps to reproduce:
1. # pacman -S watchdog
2. # systemctl start watchdog.service
3. # systemctl status watchdog.service
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 06 October 2017, 02:31 GMT
Reason for closing:  Fixed
Comment by Thomas Bächler (brain0) - Wednesday, 29 May 2013, 09:17 GMT
I don't know if this is a good idea - I guess that setting realtime priority on the watchdog process conflicts with the idea of cpu control groups, so this change should be fine.
Comment by David Kowis (BeepDog) - Sunday, 15 March 2015, 20:23 GMT
So I can't find anywhere in any of the systemd documentation about ControlGroup=cpu:/ any longer, and this doesn't work on the latest version of archlinux :(

The problem remains that systemd cannot set the scheduler...
Comment by mattia (nTia89) - Wednesday, 04 October 2017, 16:50 GMT
I cannot reproduce the bug.

is this issue still valid?
Comment by David Kowis (BeepDog) - Wednesday, 04 October 2017, 23:05 GMT
I no longer use ArchLinux for this purpose, so it can probably be closed, if it can no longer be reproduced.

Loading...