Timeline for SELINUX_ERR op=security_bounded_transition
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 9, 2020 at 16:48 | vote | accept | dafydd | ||
| Mar 21, 2017 at 22:44 | answer | added | dafydd | timeline score: 0 | |
| Mar 21, 2017 at 21:06 | history | edited | dafydd | CC BY-SA 3.0 |
added 632 characters in body
|
| Mar 21, 2017 at 20:13 | answer | added | Jakuje | timeline score: 2 | |
| Mar 21, 2017 at 19:56 | history | edited | dafydd | CC BY-SA 3.0 |
added 396 characters in body
|
| Mar 21, 2017 at 19:44 | history | edited | dafydd | CC BY-SA 3.0 |
added 223 characters in body
|
| Mar 21, 2017 at 17:57 | comment | added | dafydd |
After trying that, journalctl only captures the start of the service manager, which comes up okay. The Service Manager then starts the Agent, and the Agent fails because it can't open its keystore. I'll work on an edit to the OP to clarify that distinction. I don't think this is a systemctl thing, really. Calling this a "service manager starting the agent under SELinux" thing is more accurate.
|
|
| Mar 21, 2017 at 17:50 | comment | added | supriady | Run # journalctl -xlf for troubleshooting. | |
| Mar 21, 2017 at 17:47 | history | asked | dafydd | CC BY-SA 3.0 |