CMS Made Simple Forums

Recently, my CMSMS v1.6.4 began generating huge core.#### dump files. I upgraded to v1.6.5 and no change.  I don't know what module is causing the issue, but I'm thinking it is the MySQL dump module that I used for the first time a couple of weeks ago. Can anyone assist me with finding out how to resolve this issue? It is consuming vast amounts storage space. I am currently running CMSMS v1.6.5 on Linux with PHP 5.2.6 and MySQL 4.1.22-Standard.

-Jab

jab wrote: Recently, my CMSMS v1.6.4 began generating huge core.#### dump files. ... I am currently running CMSMS v1.6.5 on Linux with PHP 5.2.6 and MySQL 4.1.22-Standard.
...

Hi,

Do you have shell access to your server?  You can find out what program dumped a core file (and why) by running the "file" command on it.
For example:

   file core.1234

You might run the "file" command on one of your core files and then post the output to this thread.

Fred

I've been experiencing segfaults and other problems with php 5.2.x and CMSMS quite regularly.... though I am having grief trying to setup a temporary debug environment so that I can find out what's causing them.

A stack trace from each of these core dumps would be useful.

Here's how you get a gdb backtrace:

http://bugs.php.net/bugs-generating-backtrace.php

Also, we'll need the PHP version.

Thanks - I am not 100% sure, but I think the problem may have been with the settings in the Archiver module being set to unlimited archive. When I change the settings it appears that I am no longer getting dump files. My hosting company provided the following to indicate that the problem was with the index.php page. I asked them to evaluate one of the core.xxxx files that I left on the site. If the problem returns, I will see if I can provide information from the actual core.xxxx file.

-------------------------------------------------------------
-bash-3.00# php -e -f index.php > /dev/null
zend_mm_heap_corrupted
-------------------------------------------------------------

Thanks,
Jab

I had my hosting company run gdb on the core.xxxx files and they got the following result indicating the moduleinterface.php file was generating the core dump.

Core was generated by `/public_html/admin/moduleinterface.php'.
Program terminated with signal 11, Segmentation fault.
#0  0x0838432e in mtx_append (stream=0x88d2360, mailbox=0xb50f3b88 " 30 03", af=0xbfff9ff8, data=0x8385c7d) at mtx.c:1045
1045    mtx.c: No such file or directory.
        in mtx.c
(gdb) bt
#0  0x0838432e in mtx_append (stream=0x88d2360, mailbox=0xb50f3b88 " 30 03", af=0xbfff9ff8, data=0x8385c7d) at mtx.c:1045
#1  0x083853ab in mtx_expunge (stream=0x1a41ff4, sequence=0xb50f3b78 "�B 01�", options=-1073766344) at mtx.c:763
#2  0x08385c7d in mtx_parse (stream=0xb50f3b78) at mtx.c:1198

I am still getting the huge core dump files. Below is the stack trace for the index.php file. the moduleinterface.php file also cause a core dump to the admin folder whenever an edit is made in the admin panel. Hopefully someone can help me.  These files are huge and they are consuming my storage space quickly and have to purged a couple times a day.

Core was generated by `/public_html/index.php'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libstdc++.so.6...done.
Loaded symbols for /usr/lib/libstdc++.so.6
Reading symbols from /lib/libcrypt.so.1...done.
Loaded symbols for /lib/libcrypt.so.1
Reading symbols from /opt/xslt/lib/libexslt.so.0...done.
Loaded symbols for /opt/xslt/lib/libexslt.so.0
Reading symbols from /lib/tls/libm.so.6...done.
Loaded symbols for /lib/tls/libm.so.6
Reading symbols from /usr/lib/libexpat.so.0...done.
Loaded symbols for /usr/lib/libexpat.so.0
Reading symbols from /opt/tidy/lib/libtidy-0.99.so.0...done.
Loaded symbols for /opt/tidy/lib/libtidy-0.99.so.0
Reading symbols from /usr/lib/libaspell.so.15...done.
Loaded symbols for /usr/lib/libaspell.so.15
Reading symbols from /usr/lib/libpspell.so.15...done.
Loaded symbols for /usr/lib/libpspell.so.15
Reading symbols from /opt/mhash/lib/libmhash.so.2...done.
Loaded symbols for /opt/mhash/lib/libmhash.so.2
Reading symbols from /opt/libmcrypt/lib/libmcrypt.so.4...done.
Loaded symbols for /opt/libmcrypt/lib/libmcrypt.so.4
Reading symbols from /usr/lib/libltdl.so.3...done.
Loaded symbols for /usr/lib/libltdl.so.3
Reading symbols from /lib/libssl.so.4...done.
Loaded symbols for /lib/libssl.so.4
Reading symbols from /lib/libcrypto.so.4...done.
Loaded symbols for /lib/libcrypto.so.4
Reading symbols from /lib/libpam.so.0...done.
Loaded symbols for /lib/libpam.so.0
Reading symbols from /usr/lib/libfreetype.so.6...done.
Loaded symbols for /usr/lib/libfreetype.so.6
Reading symbols from /usr/X11R6/lib/libX11.so.6...done.
Loaded symbols for /usr/X11R6/lib/libX11.so.6
Reading symbols from /usr/X11R6/lib/libXpm.so.4...done.
Loaded symbols for /usr/X11R6/lib/libXpm.so.4
Reading symbols from /usr/lib/libpng12.so.0...done.
Loaded symbols for /usr/lib/libpng12.so.0
Reading symbols from /usr/lib/libjpeg.so.62...done.
Loaded symbols for /usr/lib/libjpeg.so.62
Reading symbols from /usr/lib/libbz2.so.1...done.
Loaded symbols for /usr/lib/libbz2.so.1
Reading symbols from /lib/libresolv.so.2...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libnsl.so.1...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /usr/lib/libgssapi_krb5.so.2...done.
Loaded symbols for /usr/lib/libgssapi_krb5.so.2
Reading symbols from /usr/lib/libkrb5.so.3...done.
Loaded symbols for /usr/lib/libkrb5.so.3
Reading symbols from /usr/lib/libk5crypto.so.3...done.
Loaded symbols for /usr/lib/libk5crypto.so.3
Reading symbols from /lib/libcom_err.so.2...done.
Loaded symbols for /lib/libcom_err.so.2
Reading symbols from /opt/curlssl/lib/libcurl.so.4...done.
Loaded symbols for /opt/curlssl//lib/libcurl.so.4
Reading symbols from /usr/lib/libidn.so.11...done.
Loaded symbols for /usr/lib/libidn.so.11
Reading symbols from /lib/tls/librt.so.1...done.
Loaded symbols for /lib/tls/librt.so.1
Reading symbols from /lib/tls/libpthread.so.0...done.
Loaded symbols for /lib/tls/libpthread.so.0
Reading symbols from /opt/xslt/lib/libxslt.so.1...done.
Loaded symbols for /opt/xslt/lib/libxslt.so.1
Reading symbols from /opt/xml2/lib/libxml2.so.2...done.
Loaded symbols for /opt/xml2/lib/libxml2.so.2
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/tls/libc.so.6...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /usr/lib/libz.so.1...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libaudit.so.0...done.
Loaded symbols for /lib/libaudit.so.0
Reading symbols from /usr/X11R6/lib/libXext.so.6...done.
Loaded symbols for /usr/X11R6/lib/libXext.so.6
Reading symbols from /usr/local/IonCube/ioncube_loader_lin_5.2.so...done.
Loaded symbols for /usr/local/IonCube/ioncube_loader_lin_5.2.so
Reading symbols from /usr/local/Zend/lib/ZendExtensionManager.so...done.
Loaded symbols for /usr/local/Zend/lib/ZendExtensionManager.so
Reading symbols from /usr/local/lib/php/extensions/no-debug-non-zts-20060613/eaccelerator.so...done.
Loaded symbols for /usr/local/lib/php/extensions/no-debug-non-zts-20060613/eaccelerator.so
Reading symbols from /lib/libnss_files.so.2...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /usr/local/Zend/lib/Optimizer-3.3.3/php-5.2.x/ZendOptimizer.so...done.
Loaded symbols for /usr/local/Zend/lib/Optimizer-3.3.3/php-5.2.x/ZendOptimizer.so
Reading symbols from /usr/lib/gconv/ISO8859-1.so...done.
Loaded symbols for /usr/lib/gconv/ISO8859-1.so
#0  0x0838432e in zend_mm_remove_from_free_list ()
(gdb) /Hangup detected on fd 0
Error detected on fd 0
error detected on stdin

Help...
Jab

jab wrote: I am still getting the huge core dump files. Below is the stack trace for the index.php file. the moduleinterface.php file also cause a core ...

Core was generated by `/public_html/index.php'.
Program terminated with signal 11, Segmentation fault.
...
Reading symbols from /usr/local/Zend/lib/ZendExtensionManager.so...done.
Loaded symbols for /usr/local/Zend/lib/ZendExtensionManager.so
Reading symbols from /usr/local/lib/php/extensions/no-debug-non-zts-20060613/eaccelerator.so...done.
Loaded symbols for /usr/local/lib/php/extensions/no-debug-non-zts-20060613/eaccelerator.so
...
Reading symbols from /usr/local/Zend/lib/Optimizer-3.3.3/php-5.2.x/ZendOptimizer.so...done.
Loaded symbols for /usr/local/Zend/lib/Optimizer-3.3.3/php-5.2.x/ZendOptimizer.so
Reading symbols from /usr/lib/gconv/ISO8859-1.so...done.
Loaded symbols for /usr/lib/gconv/ISO8859-1.so
#0  0x0838432e in zend_mm_remove_from_free_list ()
(gdb) /Hangup detected on fd 0
Error detected on fd 0
error detected on stdin

Help...

Hi Jab,

The short answer is that I don't know what is causing your core dumps.   Sorry.

That said, if all else fails, here are a few things you and/or your hosting company might explore:

1)  Try disabling "optional" PHP facilities (e.g., eaccelerator, optimizers, etc.) one by one.  If disabling a facility causes your page(s) to start working, then that might indicate a configuration "problem" (or even a bug) in that facility.

2)  Review known bugs in your version of PHP that cause segfaults similar to what you are seeing.  Here is a sample of what I found with a quick web search; perhaps they are relevant:
  a. PHP Bug #46300  php crash in high load
        http://bugs.php.net/bug.php?id=46300
  b. PHP Bug #47533  php crash when it is compile without --enable-debug
        http://bugs.php.net/bug.php?id=47533

3)  Your host *might* be able to temporarily reduce your user 'core dump size' resource limit to something small.  That won't fix your problem, but it would keep your processes from creating new (huge) core dumps while you're debugging the core dumps you already have.  Note: this might not be possible; it depends upon how your web server is configured to run.

4)  Search PHP-related forums for similar segfault problems.  I'm not convinced this is a "bug" in CMSMS core or modules.

Hope this helps,
Fred

Thanks - I appreciate your support.

I have five sites running CMSMS.

When I upgraded them all to 1.6.4, one of them started giving me core dumps. I contacted the site host about the problem. After some discussion the solution was for them to rebuild php5 and apache. The core dumps have stopped.

The sites are all running v1.6.6 now but my core dump problem wasn't with CMSMS. Just thought I would share this.

Hi:

I'm experiencing a similar problem.  I have several clients running CMSMS, but only one seems to be generating huge core files.  I have copied the suggested provided here to the host in the hope that he can read the core files and perform a gdb - whatever that is..

Server details:

• linux server
• server API =  cgi
• PHP v5.2.8
• safe)mode: off
• register_globals: off
• disabled function: shell_exec, system, proc_open

modules installed are:
CMSMS v1.6.6
CMSMailer  1.73.14
FileManager  1.0.1
MenuManager  1.6.2
ModuleManager  1.3.1
nuSOAP  1.0.1
Printing  1.0.4
Search  1.6.1
ThemeManager  1.1.1
FCKeditorX  1.1.0
PageBlocks  0.1.5
TinyMCE  2.5.5
CGSimpleSmarty  1.3.1

has anyone else found a concrete reason why this is happening and is willing to share the solution?

I have spent hours diagnosing these issues.  they were all related to bad php versions.
Upgrade to php 5.2.12 or better.

Thanks Robert.  Apparently these files were generated when the host upgraded to PHP 5.2.8.  this has been fixed.  thanks again.