'signal Segmentation fault' due to comment module

deepesh - February 11, 2008 - 11:45

If I enable comment module and any node with comments is accessed a blank page is shown and following error appears in apache logs:

[Mon Feb 11 00:36:28 2008] [notice] child pid 5751 exit signal Segmentation fault (11)
[Mon Feb 11 00:36:29 2008] [notice] child pid 14333 exit signal Segmentation fault (11)
[Mon Feb 11 00:36:31 2008] [notice] child pid 5750 exit signal Segmentation fault (11)
[Mon Feb 11 00:38:15 2008] [notice] child pid 30220 exit signal Segmentation fault (11)
[Mon Feb 11 00:38:18 2008] [notice] child pid 30225 exit signal Segmentation fault (11)
[Mon Feb 11 00:38:30 2008] [notice] child pid 14318 exit signal Segmentation fault (11)

Disabling comment module serves the pages fine.

Since, comment is a core module this needs urgent attention !!

» Login or register to post comments

We are experiencing the same

ambi - February 11, 2008 - 19:24

Somehow we are also experiencing this issue as of yesterday.

We are running Apache/2.0.52 (Red Hat) with Drupal 5.6, 2008-01-10, MySQL: 4.1.20, PHP 5.2.5.

Restarting apache solves the seg faults.

Seg faults occur on pages with commented blogs, as far as we can tell.

Any help will be appreciated!

Thanks
Ambi

Restarting apache resolves

deepesh - February 12, 2008 - 00:19

Restarting apache resolves the fault but does it re-occurs ?? also, this could be due to op-code accelerators as discussed here, pls. second my comment there to get a fast response - http://2bits.com/articles/php-op-code-caches-accelerators-a-must-for-a-l...

Shalini Agarwal,
http://MegaLeecher.Net/

we turned off e-accelerator and seg faults went away

ambi - February 12, 2008 - 21:09

We turned off e-accelerator and installed apc instead.
somehow all is well so far.

Ambi

Restarting Apache also resolved this issue for us

hintbw - April 15, 2009 - 17:57

We also had white pages on nodes with comments (as well as white pages on ec mail and the list of views - strangely enough). Restarting apache resolved the issue and we did have eaccelerator installed.

We are exploring the automatic detection and apache restart scripts that were highlighted above, as well as possibly switching accelerators.

Also getting this issue using

robinduckett - June 25, 2009 - 10:34

Also getting this issue using XCache,

But happens randomly. Sometimes on the frontpage, sometimes on the Node admin pages. Restart of Apache always works.

I have updated to the latest version of all modules and core and going to wait and see if it breaks again.