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.

After apache upgrades core.* files are filling up public_html

Discussion in 'EasyApache' started by Francisco, Nov 26, 2007.

  1. Francisco

    Francisco Well-Known Member

    Joined:
    Jun 3, 2003
    Messages:
    99
    Likes Received:
    0
    Trophy Points:
    6
    Anyone experiencing this?
     
  2. ToddShipway

    ToddShipway Well-Known Member

    Joined:
    Nov 13, 2006
    Messages:
    300
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Houston, TX
    This means something is causing apache to segfault. Look in /usr/local/apache/logs/error_log for any information that may lead you to the cause. This is most likely due to php being corrupt after the upgrade or a module isn't compatible with options you have selected during the build causing php to segfault. Be sure to check all php configuration as well.

    If all else fails, rebuild with the default options to make sure the issue doesn't continue in a default state.
     
  3. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    Todd assists individuals with these issues more often than I do, however also don't discount the possibility of a malfunctioning PHP script. If you recently changed a PHP script, it may be malfunctioning to the point of causing a core dump. I know myself, at one time I built a PHP script at one point which frequently requested data from external URLs and the script generated core files routinely.

    While the server will continue functioning, I would recommend investigating possible causes for the core files so they do not fill up your disk space and so you can fix whatever is causing these issues in the first place.
     
  4. VeZoZ

    VeZoZ Well-Known Member

    Joined:
    Dec 14, 2002
    Messages:
    248
    Likes Received:
    0
    Trophy Points:
    16
    cPanel Access Level:
    DataCenter Provider
    I saw this when cPanel installed Zend 3.3.0 on my PHP4 install in easyapache. I had to install 3.2.2 to avoid the core files from being generated.
     
  5. Infopro

    Infopro cPanel Sr. Product Evangelist
    Staff Member

    Joined:
    May 20, 2003
    Messages:
    14,478
    Likes Received:
    203
    Trophy Points:
    63
    Location:
    Pennsylvania
    cPanel Access Level:
    Root Administrator
    Twitter:
  6. Infopro

    Infopro cPanel Sr. Product Evangelist
    Staff Member

    Joined:
    May 20, 2003
    Messages:
    14,478
    Likes Received:
    203
    Trophy Points:
    63
    Location:
    Pennsylvania
    cPanel Access Level:
    Root Administrator
    Twitter:
  7. mtindor

    mtindor Well-Known Member

    Joined:
    Sep 14, 2004
    Messages:
    1,281
    Likes Received:
    37
    Trophy Points:
    48
    Location:
    inside a catfish
    cPanel Access Level:
    Root Administrator
    Had exactly the same problem about two weeks ago, and it was Zend 3.3 for me as well - I had to revert to 3.2.2

    Mike
     
  8. darren.nolan

    darren.nolan Well-Known Member

    Joined:
    Oct 4, 2007
    Messages:
    259
    Likes Received:
    0
    Trophy Points:
    16
    There's a problem with Zend 3.3.0???? :O

    I saw core files on one of my clients public_html area also. But it never happened before Zend was installed. Zend somehow disallows PHP opening a URL file, which caused apache to have heart-attacks... :| I changed his script to use file.php rather than http://www.hisdomain.com/file.php in includes.
     
Loading...

Share This Page