SELINUX enforcing mode stuck - Failed to initialize SELinux context: Permission denied
0
I have Ubuntu 18 and followed basic installations :
- apt-get install selinux
- apt-get install selinux-basics
we create a lot of custom modules
NOW, we DO NOT have anymore AVC denials, but still when we switch to enforce - it doesn't goes through the boot properly.
In the journalctl we see the following errors:
> systemd-udevd[504]: Failed to initialize
> SELinux context: Permission denied
> systemd-udevd[504]: could not initialize labelling: Permission denied
> systemd-udevd[507]: Failed to initialize
> SELinux context: Permission denied
> systemd-udevd[507]: could not initialize labelling: Permission denied
> systemd-udevd[510]: Failed to initialize
> SELinux context: Permission denied
> udevadm[482]: Failed to initialize SELinux context: Permission denied
> systemd-udevd[510]: could not initialize labelling: Permission denied
While booting, we see the following errors:
(looks like the udev Kernel Device Manager doesn't start)
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[ OK ] Started Monitoring of LVM2 mirrors,…sing dmeventd or progress polling.
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[ OK ] Started nftables.
[ OK ] Started Load Kernel Modules.
[FAILED] Failed to start udev Kernel Device Manager.caldomain)
18.04 selinux
asked Mar 13 at 15:53
reut zeevireut zeevi
11
add a comment |
0
I have Ubuntu 18 and followed basic installations :
- apt-get install selinux
- apt-get install selinux-basics
we create a lot of custom modules
NOW, we DO NOT have anymore AVC denials, but still when we switch to enforce - it doesn't goes through the boot properly.
In the journalctl we see the following errors:
> systemd-udevd[504]: Failed to initialize
> SELinux context: Permission denied
> systemd-udevd[504]: could not initialize labelling: Permission denied
> systemd-udevd[507]: Failed to initialize
> SELinux context: Permission denied
> systemd-udevd[507]: could not initialize labelling: Permission denied
> systemd-udevd[510]: Failed to initialize
> SELinux context: Permission denied
> udevadm[482]: Failed to initialize SELinux context: Permission denied
> systemd-udevd[510]: could not initialize labelling: Permission denied
While booting, we see the following errors:
(looks like the udev Kernel Device Manager doesn't start)
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[ OK ] Started Monitoring of LVM2 mirrors,…sing dmeventd or progress polling.
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[ OK ] Started nftables.
[ OK ] Started Load Kernel Modules.
[FAILED] Failed to start udev Kernel Device Manager.caldomain)
18.04 selinux
asked Mar 13 at 15:53
reut zeevireut zeevi
11
add a comment |
0
0
0
I have Ubuntu 18 and followed basic installations :
- apt-get install selinux
- apt-get install selinux-basics
we create a lot of custom modules
NOW, we DO NOT have anymore AVC denials, but still when we switch to enforce - it doesn't goes through the boot properly.
In the journalctl we see the following errors:
> systemd-udevd[504]: Failed to initialize
> SELinux context: Permission denied
> systemd-udevd[504]: could not initialize labelling: Permission denied
> systemd-udevd[507]: Failed to initialize
> SELinux context: Permission denied
> systemd-udevd[507]: could not initialize labelling: Permission denied
> systemd-udevd[510]: Failed to initialize
> SELinux context: Permission denied
> udevadm[482]: Failed to initialize SELinux context: Permission denied
> systemd-udevd[510]: could not initialize labelling: Permission denied
While booting, we see the following errors:
(looks like the udev Kernel Device Manager doesn't start)
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[ OK ] Started Monitoring of LVM2 mirrors,…sing dmeventd or progress polling.
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[ OK ] Started nftables.
[ OK ] Started Load Kernel Modules.
[FAILED] Failed to start udev Kernel Device Manager.caldomain)
18.04 selinux
asked Mar 13 at 15:53
reut zeevireut zeevi
11
I have Ubuntu 18 and followed basic installations :
- apt-get install selinux
- apt-get install selinux-basics
we create a lot of custom modules
NOW, we DO NOT have anymore AVC denials, but still when we switch to enforce - it doesn't goes through the boot properly.
In the journalctl we see the following errors:
> systemd-udevd[504]: Failed to initialize
> SELinux context: Permission denied
> systemd-udevd[504]: could not initialize labelling: Permission denied
> systemd-udevd[507]: Failed to initialize
> SELinux context: Permission denied
> systemd-udevd[507]: could not initialize labelling: Permission denied
> systemd-udevd[510]: Failed to initialize
> SELinux context: Permission denied
> udevadm[482]: Failed to initialize SELinux context: Permission denied
> systemd-udevd[510]: could not initialize labelling: Permission denied
While booting, we see the following errors:
(looks like the udev Kernel Device Manager doesn't start)
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[ OK ] Started Monitoring of LVM2 mirrors,…sing dmeventd or progress polling.
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[ OK ] Started nftables.
[ OK ] Started Load Kernel Modules.
[FAILED] Failed to start udev Kernel Device Manager.caldomain)
18.04 selinux
18.04 selinux
asked Mar 13 at 15:53
reut zeevireut zeevi
11
asked Mar 13 at 15:53
reut zeevireut zeevi
11
asked Mar 13 at 15:53
reut zeevireut zeevi
11
asked Mar 13 at 15:53
reut zeevireut zeevi
11
asked Mar 13 at 15:53
reut zeevireut zeevi
11
11
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1125364%2fselinux-enforcing-mode-stuck-failed-to-initialize-selinux-context-permission%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1125364%2fselinux-enforcing-mode-stuck-failed-to-initialize-selinux-context-permission%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
