After apache upgrades core.* files are filling up public_html

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.

 

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.

 

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.

 

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

 

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.