Red Hat Bugzilla – Bug 858832
Sanlock service cannot start due to SELinux
Last modified: 2012-09-24 09:22:39 EDT
Created attachment 614528 [details]
Logs from messages and audit.log
Description of problem:
Sanlock tries to start but then fails. The problem seems to be caused by selinux, because if it is in permissive state, the service starts properly.
Version-Release number of selected component (if applicable):
Any time, if SELinux is in enforcing mode
Steps to Reproduce:
1. Set SELinux to enforcing mode
2. Start sanlock service
Service does not start
Sanlock service up and running
See logs attached.
i also get an error while trying to start sanlock service:
service sanlock status shows:
sanlock daemon started 2.4 aio 1 10 renew 20 80 host 885008f5-17dc...348127889
set scheduler RR|RESET_ON_FORK priority 99 failed: Operation not permitted
wdmd connect failed for watchdog handling
I'd check if there is a newer selinux build you could try out.
You can refer to bug 831908 where we're getting the selinux policy fixed in RHEL. Similar changes will probably be needed here.
I just tested these selinux-policy packages new version and my problem is fixed: