Hide Forgot
Description of problem: When selinux is relabeling filesystem, it is being aborted by an incorrect watchdog behavior of systemd. Version-Release number of selected component (if applicable): systemd-229-7.fc24.x86_64 selinux-policy-3.13.1-180.fc24.noarch kernel-4.5.0-302.fc24.x86_64 How reproducible: don't know Steps to Reproduce: 1. as root, create /.autorelabel 2. reboot 3. watch Actual results: After about 10 minutes, system reboots. A look into syslogs reveals that the system ran into a watchdog timeout. Expected results: Systemd must not abort selinux relabeling filesystems.
What watchdog? There are watchdogs both for services and for systemd itself. Your description does not clarify which watchdog fires. Maybe you could paste the logs.
Created attachment 1144593 [details] last 20 lines from journal before system rebooted plus some lines before that (In reply to Zbigniew Jędrzejewski-Szmek from comment #1) > What watchdog? There are watchdogs both for services and for systemd itself. > Your description does not clarify which watchdog fires. Maybe you could > paste the logs. I don't know, but I've attached a log file. selinux was relabeling files (nothing logged to syslog).
Apr 06 09:33:32 hostname systemd[1]: Shutting down. Apr 06 09:33:32 hostname systemd[1]: Hardware watchdog 'INTCAMT', version 0 Apr 06 09:33:32 hostname systemd[1]: Set hardware watchdog to 10min. Apr 06 09:33:32 hostname systemd-shutdown[1]: Sending SIGTERM to remaining processes... This just means that systemd sets the watchdog for shutdown to 10min. It doesn't specify the reason for shutdown. Can you attach the whole logs?
> Can you attach the whole logs? Sorry, I can't. They are gone and I don't understand why. (In reply to Zbigniew Jędrzejewski-Szmek from comment #3) > This just means that systemd sets the watchdog for shutdown to 10min. It > doesn't specify the reason for shutdown. Ok, then I might be seeing something completely different. Systemd might not even be related. Still I don't understand why the system was rebooting after some time of restoring context, it should just have continued booting. I'll try to reproduce.
Oh, it reboots automatically after the relabel is finished. That is expected.
(In reply to Zbigniew Jędrzejewski-Szmek from comment #5) > Oh, it reboots automatically after the relabel is finished. That is expected. And that's exactly what is specified in section "File Labeling" in man 8 selinux, I must have overread that. Sorry for wasting your time.
NP, good that we got that cleared.