4.0.2: web server with pid=xxxx received unexpected signal=11

#1
Dear support,

I received hundreds of these messages every once in a while, sometimes in a very short span (almost every minute now).

Note that this started to happen after I upgraded to 4.0.1, after hundreds of restart messages I reverted back to 3.3.24 and it's 503 all over. I have to switch back to 4.0.1 then upgrade to 4.0.2; the problem persists.

It was my poor judgment to upgrade after it became available in auto update. More so because I have paid for the Enterprise version and my other server is running smoothly with 3.3.24 standard without a speck of problem. Perhaps I don't have to upgrade to Enterprise at all :(

Can you please check if this can be fixed or should I reinstall the standard version and get a refund (if possible).

Here is one the messages that I received close to a thousand messages of this today! I don't think it's possible to send all of them to you or post them here.

Lek


At [28/Apr/2009:16:54:42 +0700], web server with pid=9377 received unexpected signal=11, a core file is created. A new instance of web server will be started automatically!

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

Server: LiteSpeed/4.0.2 Enterprise
OS: Linux
Release: 2.6.9-55.0.6.ELsmp
Version: #1 SMP Tue Sep 4 21:36:00 EDT 2007
Machine: i686

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

Using host libthread_db library "/lib/tls/libthread_db.so.1".
Core was generated by `lshttpd'.
Program terminated with signal 11, Segmentation fault.
#0 0x080a9801 in EventReactor::resetRevent (this=0x850f378, event=4)
at /home/gwang/release/httpd/httpd/edio/eventreactor.h:55
in /home/gwang/release/httpd/httpd/edio/eventreactor.h
#0 0x080a9801 in EventReactor::resetRevent (this=0x850f378, event=4)
at /home/gwang/release/httpd/httpd/edio/eventreactor.h:55
#1 0x080e5d84 in EdStream::write (this=0x850f378, buf=0xbffff7d0 "LS\002",
len=8) at /home/gwang/release/httpd/httpd/edio/ediostream.h:103
#2 0x080f6a25 in LsapiConn::sendAbortReq (this=0x850f378)
at /home/gwang/release/httpd/httpd/extensions/lsapi/lsapiconn.cpp:225
#3 0x080f6997 in LsapiConn::abort (this=0x850f378)
at /home/gwang/release/httpd/httpd/extensions/lsapi/lsapiconn.cpp:214
#4 0x080c6c29 in HttpExtConnector::abortReq (this=0x82fef90)
at /home/gwang/release/httpd/httpd/http/httpextconnector.cpp:288
#5 0x080c64e0 in HttpExtConnector::cleanUp (this=0x82fef90, pConn=0x8409cf0)
at /home/gwang/release/httpd/httpd/http/httpextconnector.cpp:66
#6 0x080bc671 in HttpConnection::cleanUpHandler (this=0x8409cf0)
at /home/gwang/release/httpd/httpd/http/httpconnection.cpp:1659
#7 0x080bc6e0 in HttpConnection::closeConnection (this=0x8409cf0, cancelled=0)
at /home/gwang/release/httpd/httpd/http/httpconnection.cpp:1674
#8 0x080a6cdb in HttpIOLink::handleEvents (this=0x8409cf0, evt=25)
- Hide quoted text -
at /home/gwang/release/httpd/httpd/http/httpiolink.cpp:169
#9 0x08105f9c in PollfdReactor::processAllEvents (this=0x82ece30)
at /home/gwang/release/httpd/httpd/edio/pollfdreactor.h:143
#10 0x08105d24 in Poller::waitAndProcessEvents (this=0x82ece28,
iTimeoutMilliSec=100) at /home/gwang/release/httpd/httpd/edio/poller.cpp:69
#11 0x0809e8b0 in EventDispatcher::run (this=0x82d6924)
at /home/gwang/release/httpd/httpd/http/eventdispatcher.cpp:217
#12 0x080657ae in HttpServerImpl::start (this=0x82d6910)
at /home/gwang/release/httpd/httpd/main/httpserver.cpp:348
#13 0x08068218 in HttpServer::start (this=0x82961b0)
at /home/gwang/release/httpd/httpd/main/httpserver.cpp:1656
#14 0x0804f565 in LshttpdMain::main (this=0x82d6700, argc=1, argv=0xbffffa64)
at /home/gwang/release/httpd/httpd/main/lshttpdmain.cpp:1614
#15 0x0804be71 in main (argc=1, argv=0xbffffa64)
at /home/gwang/release/httpd/httpd/main.cpp:121
 
#3
Thanks, but the link you have provided is a standard version. Should I downgrade from the Enterprise version or download 4.0.3-ent instead?
 

mistwang

LiteSpeed Staff
#4
Yes, you should download the enterprise version, however, the bug may not be fixed, please follow up with our staff to investigate your issue.
 
Top