received unexpected signal=11

M

MattW

Well-Known Member
#1
#1
I've just upgraded @dethfire 's server to 5.0

Every couple of minutes, we are getting the below

At [24/Apr/2015:09:07:43 -0500], web server with pid=732 received unexpected signal=11, a core file has been created. A new instance of web server will be started automatically!

Please forward the following debug information to bug@litespeedtech.com.
Environment:

Server: LiteSpeed/5.0 Enterprise
OS: Linux
Release: 2.6.32-504.12.2.el6.x86_64
Version: #1 SMP Wed Mar 11 22:03:14 UTC 2015
Machine: x86_64

There is no core file being created.
 
P

Pong

Administrator
Staff member
#2
#2
Please try the latest build to see how it can be resolved. Let us know if the problem persists.

/usr/local/lsws/admin/misc/lsup.sh -f -v 5.0
 
M

MattW

Well-Known Member
#3
#3
Unless the issue has been addresses and fixed in the last 25 minutes, then the server is already running the latest build.
 
M

MattW

Well-Known Member
#7
#7
I've just had the same crash report on my own server:
Code: 
At [27/Apr/2015:14:53:29 +0100], web server with pid=11399 received unexpected signal=11, a core file has been created. A new instance of web server will be started automatically!

Please forward the following debug information to bug@litespeedtech.com.
Environment:

Server: LiteSpeed/5.0 Enterprise
OS: Linux
Release: 2.6.32-32-pve
Version: #1 SMP Thu Aug 21 08:50:19 CEST 2014
Machine: x86_64

If the call stack information does not show up here, please compress and forward the core file located in /tmp/lshttpd/.
 
T

theRKF

Well-Known Member
#10
#10
+1 for this report, multiple and frequent restarts due to segfaults (reported via email as well) using Build 2.

Since Build 3 breaks our sites I didn't keep it running long enough to crash.
 
You must log in or register to reply here.
Top