LSWS Crashing?

G

GOT

Well-Known Member
#1
#1
I've got a couple of servers that are seeing Litespeed die. lsphp5 processes are orphaned off and the processes for litespeed look like this

6272 ? S 0:31 litespeed (lshttpd)
6273 ? S 0:02 \_ httpd (lscgid)
24582 ? S 0:00 \_ sh -c gdb --batch --command=/opt/lsws//admin/misc/gdb-bt /opt/lsws//bin/litespeed /tmp/lshttpd/core* >> /tmp/m-OE75lq
24583 ? S 0:00 \_ gdb --batch --command=/opt/lsws//admin/misc/gdb-bt /opt/lsws//bin/litespeed /tmp/lshttpd/core.20483

I have to manually kill off the processes and then i can restart litespeed.

Any idea what could be causing this and how I fix it?
 
N

NiteWave

Administrator
#2
#2
what's your lsws version ?
please force-upgrade to latest 5.0.17 latest build, to ensure if latest version latest build will have the same issue:

#/opt/lsws/admin/misc/lsup.sh -f -v 5.0.17
 
L

Long

Guest
#4
#4
With the latest build, did you still get the same issue? Under what condition did it happen?
 
G

GOT

Well-Known Member
#5
#5
We had .17 installed already but I reinstalled it. We saw it with .16 as well. I do not know what conditions caused it, it just happened. Its a pretty high traffic site running on two app servers.
 
G

GOT

Well-Known Member
#7
#7
The system error log doesn't have anything, but i am seeing a ton of these in the stderr.log

2016-05-19 09:43:34.441 [STDERR] Child process with pid: 26930 was killed by signal: 6, core dump: 128
*** glibc detected *** lsphp5: free(): invalid pointer: 0x00007fbaa523ed98 ***
2016-05-19 09:43:35.236 [STDERR] ======= Backtrace: =========
2016-05-19 09:43:35.236 [STDERR] /lib64/libc.so.6[0x320e075f4e]
2016-05-19 09:43:35.237 [STDERR] /lib64/libc.so.6[0x320e078cad]
2016-05-19 09:43:35.237 [STDERR] lsphp5(destroy_zend_class+0x23d)[0x79aced]
2016-05-19 09:43:35.237 [STDERR] lsphp5(zend_hash_clean+0x73)[0x7b02e3]
2016-05-19 09:43:35.237 [STDERR] /usr/lib64/extensions/no-debug-non-zts-20100525/apc.so(apc_interned_strings_shutdown+0x20)[0x7fbaa4b966e0]
2016-05-19 09:43:35.237 [STDERR] /usr/lib64/extensions/no-debug-non-zts-20100525/apc.so(apc_module_shutdown+0x12a)[0x7fbaa4b8ec7a]
2016-05-19 09:43:35.237 [STDERR] /usr/lib64/extensions/no-debug-non-zts-20100525/apc.so(+0xa5ff)[0x7fbaa4b855ff]
2016-05-19 09:43:35.237 [STDERR] lsphp5[0x7a94c5]
2016-05-19 09:43:35.237 [STDERR] lsphp5[0x7afc4f]
2016-05-19 09:43:35.237 [STDERR] lsphp5(zend_hash_graceful_reverse_destroy+0x18)[0x7afee8]
2016-05-19 09:43:35.237 [STDERR] lsphp5[0x7a3d85]
2016-05-19 09:43:35.237 [STDERR] lsphp5(php_module_shutdown+0x2a)[0x748a5a]
2016-05-19 09:43:35.237 [STDERR] lsphp5[0x84944f]
2016-05-19 09:43:35.237 [STDERR] /lib64/libc.so.6(__libc_start_main+0xfd)[0x320e01ed5d]
2016-05-19 09:43:35.237 [STDERR] lsphp5[0x42e7d9]

Followed by a memory map.
 
L

Long

Guest
#8
#8
If you disable apc see how it will be?
But php error shouldn't kill the server process.
How often did the server die happen?
Did you get any thing from dmesg?
Or check /var/log/messages, see whether you can get any hint.

If possible please gdb bt the core dump file for lshttpd and send the output to bug@litespeedtech.com
 
G

GOT

Well-Known Member
#9
#9
It hasn't happened again since I reisntalled but it only would happen every few days. If/when it happens again I will try to collect more info.
 
You must log in or register to reply here.
Top