Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've been getting some 500 internal server errors on my website every so often, so I had a look at the error log.

I am using lighttpd with Kloxo (lxadmin) installed. I have xcache enabled.

2011-04-14 04:57:05: (mod_cgi.c.588) cgi died, pid: 14160
2011-04-14 04:57:12: (mod_cgi.c.588) cgi died, pid: 15363
2011-04-14 04:57:19: (mod_cgi.c.588) cgi died, pid: 15492
2011-04-14 04:57:19: (mod_cgi.c.1287) cleaning up CGI: process died with signal 11
2011-04-14 04:57:28: (mod_cgi.c.588) cgi died, pid: 15846
2011-04-14 04:57:28: (mod_cgi.c.588) cgi died, pid: 15845
2011-04-14 04:57:28: (mod_cgi.c.588) cgi died, pid: 15849
2011-04-14 04:57:32: (mod_cgi.c.588) cgi died, pid: 15914
2011-04-14 04:58:07: (mod_cgi.c.588) cgi died, pid: 17758
2011-04-14 04:58:25: (mod_cgi.c.1287) cleaning up CGI: process died with signal 11
2011-04-14 04:59:57: (mod_cgi.c.588) cgi died, pid: 20103
2011-04-14 05:00:05: (mod_cgi.c.588) cgi died, pid: 20363

My error log is full of this. Any clues on what's going on?

share|improve this question

closed as off-topic by HopelessN00b Apr 9 '15 at 19:29

  • This question does not appear to be about server, networking, or related infrastructure administration within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

The only possible conclusion from that log is that the CGI is dying. And from something pretty serious (signal 11 = segmentation fault). You should look at the CGI logs and see if you can debug and find what is making him die so badly.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.