Linux Server / Boot, systemd & Service Recovery
Find a Linux service core dump before restarting away evidence
A process crash may leave a core record that explains the failure better than a generic service exit code.
Environment and inputs: Linux server baseline · Ubuntu 24.04 LTS / RHEL 9-style systems. Use the specified distribution, init system and installed tool; service names, privileges and supported options can differ.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
coredumpctl list --since '2 hours ago'
Read the result
On systems using systemd-coredump with authorized access, this lists recorded dumps in the recent window. Retention and resource policy may mean the full core is unavailable.
Resolve and verify
Match the process, executable version and time with the service failure. Preserve a bounded approved diagnostic artifact and analyze it with the application owner.
Before changing production
Core files can contain credentials and user data. Do not upload them to unapproved external tools.