I really really need to disable these core dumps

F

felosi

Well-Known Member
#1
#1
I know you said was a php issue before but its not doing it on apache, same php version and everything.
The thing is now I have servers that are running out of disk space nightly due to hundreds of these huge core files. Some of them even using enough disk space where I have to restart the box

I have
* soft core 0
* hard core 0

In my limits config file but its still doing it.

Please help me find a way to keep lsapi php from dumping these, its becoming a huge problem on a number of servers.
 
M

mistwang

LiteSpeed Staff
#2
#2
You need to check what causes the core files using GDB.

gdb <path_to_lsphp> corefile
bt

You can try disable core dump from admin console.
 
F

felosi

Well-Known Member
#3
#3
mistwang said:
You need to check what causes the core files using GDB.

gdb <path_to_lsphp> corefile
bt

You can try disable core dump from admin console.
Click to expand...
all of them are like this
Core was generated by `lsphp -c /usr/local/lib'.
Program terminated with signal 25, File size limit exceeded.
#0 0xb2ccb410 in __kernel_vsyscall ()
 
T

ts77

Well-Known Member
#4
#4
some file has more than the maximum filesize, I think mostly thats 2GB. find that file, delete/rename it and php will run without problems (at least until that file has reached that size again).

if you log php-errors/warnings to a file it will be probably that error-log from php.
 
M

mistwang

LiteSpeed Staff
#5
#5
felosi said:
all of them are like this
Core was generated by `lsphp -c /usr/local/lib'.
Program terminated with signal 25, File size limit exceeded.
#0 0xb2ccb410 in __kernel_vsyscall ()
Click to expand...
It is not a good idea to let your customer process large file at will. It could bring down the server. There are many ways to limit this, in php.ini, in LSWS "Max request body size", etc.
 
F

felosi

Well-Known Member
#6
#6
mistwang said:
It is not a good idea to let your customer process large file at will. It could bring down the server. There are many ways to limit this, in php.ini, in LSWS "Max request body size", etc.
Click to expand...

Yeah the other ones Ive found were all this

Program terminated with signal 11, Segmentation fault.
#0 0xa3f44b86 in ?? ()

I will try to do some tinkering. I do notice though this happens on servers with grsecurity kernel more often then with rhel stock kernel
 
F

felosi

Well-Known Member
#8
#8
Ok, seems its something with zend. Ive tried switching versions to no avail. Here is the bt from a core, I dont know why its executing things in /usr/src though

Code: 
Program terminated with signal 11, Segmentation fault.
#0  zend_str_tolower (str=0x578 <Address 0x578 out of bounds>, length=8)
    at /usr/src/php/Zend/zend_operators.c:1871
1871                    *p = zend_tolower((int)*p);
(gdb) bt
#0  zend_str_tolower (str=0x578 <Address 0x578 out of bounds>, length=8)
    at /usr/src/php/Zend/zend_operators.c:1871
#1  0x000038c779fb3f08 in zend_nop2_handler ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#2  0x000038c779fb5933 in zend_nop2_handler ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#3  0x000038c779fa7a24 in _uew82 ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#4  0x000038c779faa790 in _zval_dup ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#5  0x000038c779fa31ab in _sdu3mndf ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#6  0x000038c779f9f067 in ioncube_include_wrapper_handler ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#7  0x000038c779f43b98 in _ntime ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#8  0x000038c779f9d530 in _su3jdmx ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#9  0x000038c779fa195b in _osdn21 ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#10 0x000000000078b99b in zend_do_fcall_common_helper_SPEC (
    execute_data=0x7f0bae3245a0) at /usr/src/php/Zend/zend_vm_execute.h:200
#11 0x000000000078aa93 in execute (op_array=0x168a060)
---Type <return> to continue, or q <return> to quit---
    at /usr/src/php/Zend/zend_vm_execute.h:92
#12 0x000038c77c871623 in zend_oe ()
   from /usr/local/Zend/lib/Optimizer-3.2.2/php-5.2.x/ZendOptimizer.so
#13 0x000038c779f9f5b0 in ioncube_include_wrapper_handler ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#14 0x000038c779f43b98 in _ntime ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#15 0x000038c779f9d530 in _su3jdmx ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#16 0x000038c779fa195b in _osdn21 ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#17 0x000000000078b99b in zend_do_fcall_common_helper_SPEC (
    execute_data=0x7f0bae324ba0) at /usr/src/php/Zend/zend_vm_execute.h:200
#18 0x000000000078aa93 in execute (op_array=0x1697198)
    at /usr/src/php/Zend/zend_vm_execute.h:92
#19 0x000038c77c871623 in zend_oe ()
   from /usr/local/Zend/lib/Optimizer-3.2.2/php-5.2.x/ZendOptimizer.so
#20 0x000038c779f9f5b0 in ioncube_include_wrapper_handler ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#21 0x000038c779f43b98 in _ntime ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#22 0x000038c779f9d530 in _su3jdmx ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
---Type <return> to continue, or q <return> to quit---
#23 0x000038c779fa195b in _osdn21 ()
   from /usr/local/lib/php/ioncube/ioncube_loader_lin_5.2.so
#24 0x000000000078b99b in zend_do_fcall_common_helper_SPEC (
    execute_data=0x7f0bae325940) at /usr/src/php/Zend/zend_vm_execute.h:200
#25 0x000000000078aa93 in execute (op_array=0x1309d28)
    at /usr/src/php/Zend/zend_vm_execute.h:92
#26 0x000038c77c871623 in zend_oe ()
   from /usr/local/Zend/lib/Optimizer-3.2.2/php-5.2.x/ZendOptimizer.so
#27 0x000000000076b823 in zend_execute_scripts (type=8, retval=0x580,
    file_count=3) at /usr/src/php/Zend/zend.c:1215
#28 0x000000000072990b in php_execute_script (primary_file=0x7f0bae327e10)
    at /usr/src/php/main/main.c:2025
#29 0x00000000007e69ae in lsapi_module_main (show_source=0)
    at /usr/src/php/sapi/litespeed/lsapi_main.c:356
#30 0x00000000007e6db4 in processReq ()
    at /usr/src/php/sapi/litespeed/lsapi_main.c:404
#31 0x00000000007e71e3 in main (argc=1, argv=0x0)
    at /usr/src/php/sapi/litespeed/lsapi_main.c:791
 
M

mistwang

LiteSpeed Staff
#9
#9
The problem is more likely reside in ioncube loader. you can submit a bug report to them, and check if there is any new release available.
 
N

nick-a

New Member
#10
#10
Have you got a solution for this yet? I'm ending up with 20Gb of core dumps a day, and cant figure out how to stop it. Only got a few days left of trial too so I'd appreciate it if it can be sorted before I decide to buy it!
 
M

mistwang

LiteSpeed Staff
#11
#11
If your core dump looks exactly like above, it is a ioncube loader problem, there is nothing we can do other than file a bug report to the source.
 
T

ts77

Well-Known Member
#15
#15
a coredump simply means that your php is *crashing*. it doesn't help to simply turn them off! you need to fix the cause why its crashing.
 
V

valera

Member
#16
#16
I am running litespeed 4 core enterprise and have been getting core dump files. On average I get one core dump per few million php requests, and this frequency seems to increase somewhat exponentially when server is under heavier load.

I've checked the core dumps using gdb and all of them show:

Program terminated with signal 7, Bus error.

What exactly does this mean and how can it be solved?
 
You must log in or register to reply here.
Top