I have a centos server that recently needed a fsck repair on it's main hard drive. After fixing a bunch of inode issues (booting from a system rescue disk), the box booted clean. Most of the services are running fine, however the sshd service immediately core dumps when I try to start it.
I am making a testing script to compile (via make) and run a bunch of tests. I have a series of cat, grep and sed commands that organizes the results of all the tests nicely, however core-dumps are the exception. Let's say I have a program called test.
I've followed instructions from many locations online on how to get a core dump from apache when it is producing a segfault, but it still refuses to generate the dump.
Added the CoreDumpDirectory directive into the httpd.conf file and set it to /tmp
ulimit -c unlimited
Provided the pattern for dumps using
echo '/tmp/core-%e.%p' > /proc/sys/kernel/core_pattern
When I search for the files the event log mentions they are not there. Well, the bottom one is there but there's no helpful information in that file. This event was created by the Windows Error Reporting mechanism. What do I need to do in order to get my hands on the dumps so I can look at them with windbg or something?
Also, this particular event was caused because of an AppPool crashing...