Process Crash Recipe

1. On POSIX-based operating systems:
   1. Ensure the process was started with unlimited core and file ulimits.
2. On Linux:
   1. Ensure core piping is configured properly or disabled.
   2. Review the system log (e.g. journalctl) to see if the crash was caused by the Linux OOM killer.
3. Load the core dump in the operating system debugger and review the stack trace of the crashing thread.
4. Check if the RAM is non-ECC RAM in which case the cause may have been due to atmospheric radiation. Non-ECC RAM is more common in consumer hardware rather than production hardware.
5. Review the possibility of mercurial CPU cores.

Previous Section (Troubleshooting Operating System Recipes) | Next Section (Looping Shell Script Recipe) | Back to Table of Contents