After migrating to Amazon, segmentation fault 11 was haunting me. It happened about every 30 minutes. When it happened, a few consecutive segmentation faults could be seen at /var/log/apache2/error.log.
[Mon Jan 07 13:08:46 2013] [notice] child pid 1593 exit signal Segmentation fault (11)
[Mon Jan 07 13:08:47 2013] [notice] child pid 1471 exit signal Segmentation fault (11)
[Mon Jan 07 13:08:47 2013] [notice] child pid 1503 exit signal Segmentation fault (11)
[Mon Jan 07 13:08:47 2013] [notice] child pid 1590 exit signal Segmentation fault (11)
[Mon Jan 07 13:08:47 2013] [notice] child pid 1591 exit signal Segmentation fault (11)
The annoying thing was, subsequent access to any Serendipity page will be timeout, and more Segmentation faults will be thrown. The problem will rectify itself after a while. But this would happen again after some time.
Tried a lot of things. The faults did not occur if I disable Serendipity. But I could not afford to disable Serendipity.
Finally, I guess I had the answer. Serendipity seems NOT working well with APC. Occasionally, the following error is observed.
PHP Warning: include(): GC cache entry 'serendipity_event_trackexits.php' was on gc-list for 3607 seconds in Smarty.class.php on line 1263
After the GC cache entry error is observed, a request to any Serendipity page will cause the Segmentation fault.
Thus, solution is to disable APC until either Serendipity or APC fix the problem.
- PHP Version : 5.3.10
- APC Version : 3.1.7
- Serendipity Version : 1.5.2 to 1.6.2