Segmentation fault (11)

Discussion in 'Apache' started by fvanlaere, Jul 6, 2010.

  1. #1
    Hello everyone,

    Yesterday my apache/php configuration was working perfectly. I noticed that there was a notification that my save_path (/var/lib/php/session) had some issues, so I changed the group from root to apache. I tried rerunning the script, and I noticed that the problems were still there. So I (for testing purposes) set the chmod to 777 and the notification disappeared. Unfortunately, this was the moment where I realized that my web pages weren't loading anymore.

    I went to the httpd error log (/var/log/httpd/error_log) and this is what it showed:
    
    [Tue Jul 06 00:15:26 2010] [notice] child pid 27379 exit signal Segmentation fault (11)
    [Tue Jul 06 00:16:15 2010] [notice] child pid 27345 exit signal Segmentation fault (11)
    [Tue Jul 06 00:16:19 2010] [notice] child pid 27338 exit signal Segmentation fault (11)
    [Tue Jul 06 00:16:30 2010] [notice] child pid 27409 exit signal Segmentation fault (11)
    [Tue Jul 06 00:16:45 2010] [notice] child pid 27265 exit signal Segmentation fault (11)
    [Tue Jul 06 00:16:55 2010] [notice] child pid 27380 exit signal Segmentation fault (11)
    ...
    
    Code (markup):
    So I tried restarting the httpd service, and once I did that the faults came coming back. I restarted the server, I set the path of the session.save_path variable to /tmp/, changed it back to how it was. Even set all the settings as it was before, nothing helps.
    Everytime I restart the httpd service, I now get these normal messages:

    
    [Tue Jul 06 10:25:08 2010] [notice] caught SIGTERM, shutting down
    [Tue Jul 06 10:30:32 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [Tue Jul 06 10:30:32 2010] [notice] Digest: generating secret for digest authentication ...
    [Tue Jul 06 10:30:32 2010] [notice] Digest: done
    [Tue Jul 06 10:30:33 2010] [notice] Apache/2.2.9 (Unix) DAV/2 PHP/5.2.9 mod_ssl/2.2.9 OpenSSL/0.9.8g configured -- resuming normal operations
    
    Code (markup):
    And nothing after that. The access_log shows nothing, the php log shows nothing.

    I have reinstalled httpd and php with yum, doesn't help. When browsing the site you just get an empty screen.
    So I thought that the problem might just be with php, so I loaded up a jpg file, but it doesn't show it either...
    It shouldn't be a DNS issue, because when you go to the site directly, you get nothing.

    I can still execute scripts from server side, but not from client side. Is there some sort of backlog so I can find out where it goes wrong?

    Thank you for your replies,
     
    Last edited: Jul 6, 2010
    fvanlaere, Jul 6, 2010 IP
  2. fvanlaere

    fvanlaere Peon

    Messages:
    2
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #2
    This is fixed. It turned out to be a class file that was included with require_once, and made the entire eAccelerator plugin go nuts.
     
    fvanlaere, Jul 6, 2010 IP