fix: use journalctl -t fapolicyd to get fapolicyd log messages #41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Cause: On EL10, using `journalctl -u fapolicyd` does not work - sometime during fapolicyd startup, the `UNIT` field is dropped from the journald log entries, which is what `-u` uses. Consequence: The fapolicyd role never sees the journald log message that says fapolicyd is listening for connections. The role fails saying that the trustdb could not be updated. Fix: Use `journalctl -t fapolicyd` instead. This uses the journald field SYSLOG_IDENTIFIER which is stable and works on all supported platforms. Result: The role can tell when fapolicyd is up and listening. The role can successfully update the trust db. Signed-off-by: Rich Megginson <[email protected]>
|
[citest] |
|
[citest bad] |
spetrosi
approved these changes
Aug 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cause: On EL10, using
journalctl -u fapolicyddoes not work - sometimeduring fapolicyd startup, the
UNITfield is dropped from the journaldlog entries, which is what
-uuses.Consequence: The fapolicyd role never sees the journald log message that
says fapolicyd is listening for connections. The role fails saying that
the trustdb could not be updated.
Fix: Use
journalctl -t fapolicydinstead. This uses the journald fieldSYSLOG_IDENTIFIER which is stable and works on all supported platforms.
Result: The role can tell when fapolicyd is up and listening. The role
can successfully update the trust db.
Signed-off-by: Rich Megginson [email protected]