Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Capture and upload oscap coredump #50

Closed
comps opened this issue Aug 2, 2023 · 1 comment
Closed

Capture and upload oscap coredump #50

comps opened this issue Aug 2, 2023 · 1 comment

Comments

@comps
Copy link
Contributor

comps commented Aug 2, 2023

oscap crashing is frequent enough for this to be a sensible thing to do - detect exit code 139 and generate a backtrace (somehow, possibly via coredumpctl) and upload it into logs.

This would likely need its own utility function, as it requires using debuginfo-install openscap or something similar, to get usable symbols for the oscap binary, along with dnf/yum installing gdb. Unless systemd can produce a backtrace just via coredumpd.
@comps
Copy link
Contributor Author

comps commented Oct 4, 2024

Probably covered by #264 even if not for every oscap run.

@comps comps closed this as completed Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@comps