Shyam and I looked a bit into the searchd crashing issue, but I think Trevor might have a better handle of this. I looked into the settings for searchd and didn't see anything immediately obvious that would allow it to give us more debugging information - other than running it in --console mode in a screen session - we could try that just for preview. There's no rush on this, since it's never (knock on wood) affected production, but it's definitely a curiosity we should try to figure out.
Nothing obvious for output from a crash. Next time it crashes we'll have a core to run gdb against. The production daemon has crashed before but never where both hosts were down at once.
Of course, once we're watching it stops crashing... leaving core dumps on but closing this for now.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.