The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Segmentation fault

Discussion in 'EasyApache' started by NovemberRain, Mar 8, 2014.

  1. NovemberRain

    NovemberRain Well-Known Member

    Joined:
    Sep 24, 2003
    Messages:
    93
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    İstanbul
    cPanel Access Level:
    Root Administrator
    I'm running apache 2.4.7 and php 5.4.25 with mod_ruid and my apache error log is also full of segmentation faults but the homeloader.so option is already disabled on my server.

    [core:notice] [pid 2475] AH00052: child pid 22590 exit signal Segmentation fault (11)
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,678
    Likes Received:
    654
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    Feel free to open a support ticket using the link in my signature so we can take a closer look. You can post the ticket number here so we can update this thread with the outcome.

    Thank you.
     
  3. NovemberRain

    NovemberRain Well-Known Member

    Joined:
    Sep 24, 2003
    Messages:
    93
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    İstanbul
    cPanel Access Level:
    Root Administrator
    I had already opened a ticket for this but support told me it looks like a server issue, I should hire a server administrator etc. It was also crashing my server at least once a day.

    However I fixed it by downgrading to apache 2.2 Everything is fine now.
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,678
    Likes Received:
    654
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    It's difficult to say for sure what may have been the cause without the ticket number, but I am happy to hear the issue is now resolved. Feel free to let us know if you experience the issue again when upgrading to Apache 2.4 in the future.

    Thank you.
     
Loading...

Share This Page