LSWS 5.0.2 - received unexpected signal - automatically restarted

L

LiteSpeeder

Well-Known Member
#1
#1
Hello,

I've been receiving emails regarding "automatic restarts" since i upgraded from LSWS 4.2.23 to LSWS 5.0.1. Then i switched back to 4.2.23 version, no more emails. I wanted to give a second try when LSWS 5.0.2 was released, same emails again:

Web server web1.xxx.net on web1.xxx.net automatically restarted

At [10/Jul/2015:14:40:43 +0300], web server with pid=8455 received unexpected signal=11, no core file created. A new instance of web server will be started automatically!

Is this a bug?
 
P

Pong

Administrator
Staff member
#2
#2
May need more error log info on why restart happened. Any other info before the restart notice line in your error log?

yes, please upgrade to 5.0.2 and test again.
 
M

mistwang

LiteSpeed Staff
#3
#3
LiteSpeeder said:
At [10/Jul/2015:14:40:43 +0300], web server with pid=8455 received unexpected signal=11, no core file created. A new instance of web server will be started automatically!

Is this a bug?
Click to expand...
Yes, it is a bug, we may need temp root access to investigate. Please contact bug@litespeed...
 
M

mistwang

LiteSpeed Staff
#7
#7
It only crash once, and does not create a core dump, so we could not figure anything out of it.
No need to downgrade as it does not happen frequently.
 
M

MOtorHead

Member
#8
#8
Im on 5.0.4 and sometimes this happens quite frequently as of late.

Code: 
At [15/Aug/2015:14:39:39 +0500], web server with pid=1158 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.4 Enterprise
OS: Linux
Release: 2.6.32-042stab104.1
Version: #1 SMP Thu Jan 29 12:58:41 MSK 2015
Machine: i686

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

[New Thread 1158]
[New Thread 1159]
[New Thread 1160]
[Thread debugging using libthread_db enabled]
Core was generated by `litespeed'.
Program terminated with signal 11, Segmentation fault.
#0  0xb7641033 in __memmove_ssse3_rep () from /lib/libc.so.6
#0  0xb7641033 in __memmove_ssse3_rep () from /lib/libc.so.6
#1  0x0811506d in ChunkOutputStream::fillChunkBuf (this=0xa06a3b8, pBuf=0xb5f25758 "\322-N\031\303\346!\006\b.\350\004#u", size=-5976) at /home/gwang/release/litespeed/src/http/chunkoutputstream.cpp:74
#2  0x08115299 in ChunkOutputStream::write (this=0xa06a3b8, pBuf=0xb5f25758 "\322-N\031\303\346!\006\b.\350\004#u", size=2216) at /home/gwang/release/litespeed/src/http/chunkoutputstream.cpp:199
#3  0x080a97dd in HttpSession::writeRespBody (this=0xa2e0b88, pBuf=0xb5f23758 "̝K\016\303 \f\005\317\324\024\210\224+\365\376\373\022\361\261UuQ\251\263\230#\214L\310\350ـeޡ\344\333\371\200\231\244\205*\314\a˸\333\357\240\376\061\033\325\227\017ި\244\017\356\005\354Sߎ\212\372\340B\025\372`\201}p\243\n\253\n\345\202\023\261'<\257\031)ivފJR\273\312<d!\034\252먠$\311QII\262\243r\222\224H\215\237*y\b5P\205\203:u\204fϊl\300\362\365KJ\222\035\025\224$\371\002&\233\250\201*\034\200\255\243\211z0\003\017\251\252\302\035\030ގ\204\325l\250\017\366G\261\274>\330QA\037\224\243\222>\030\250\302~q\373|\270\342Ǿ\372\327\b\337^"..., size=2216) at /home/gwang/release/litespeed/src/http/httpsession.cpp:3689
#4  0x080a9c02 in HttpSession::sendDynBody (this=0xa2e0b88) at /home/gwang/release/litespeed/src/http/httpsession.cpp:3849
#5  0x080aa8ad in HttpSession::flushDynBody (this=0xa2e0b88) at /home/gwang/release/litespeed/src/http/httpsession.cpp:4146
#6  0x080aa9b8 in HttpSession::flushBody (this=0xa2e0b88) at /home/gwang/release/litespeed/src/http/httpsession.cpp:4177
#7  0x080aacc8 in HttpSession::flush (this=0xa2e0b88) at /home/gwang/release/litespeed/src/http/httpsession.cpp:4248
#8  0x080a7ddb in HttpSession::doWrite (this=0xa2e0b88) at /home/gwang/release/litespeed/src/http/httpsession.cpp:3114
#9  0x080a8137 in HttpSession::onWriteEx (this=0xa2e0b88) at /home/gwang/release/litespeed/src/http/httpsession.cpp:3183
#10 0x080e9a7e in NtwkIOLink::doWrite (this=0xa339ae0) at /home/gwang/release/litespeed/src/http/ntwkiolink.cpp:152
#11 0x080e7b64 in NtwkIOLink::onWriteT (pThis=0xa339ae0) at /home/gwang/release/litespeed/src/http/ntwkiolink.cpp:1049
#12 0x080e5e96 in NtwkIOLink::handleEvents (this=0xa339ae0, evt=4) at /home/gwang/release/litespeed/src/http/ntwkiolink.cpp:324
#13 0x08160074 in epoll::waitAndProcessEvents (this=0xa083918, iTimeoutMilliSec=100) at /home/gwang/release/litespeed/src/edio/epoll.cpp:274
#14 0x0809991b in EventDispatcher::run (this=0xa06ccfc) at /home/gwang/release/litespeed/src/http/eventdispatcher.cpp:227
#15 0x08056861 in HttpServerImpl::start (this=0xa06cce8) at /home/gwang/release/litespeed/src/main/httpserver.cpp:515
#16 0x08059e96 in HttpServer::start (this=0x84e6870) at /home/gwang/release/litespeed/src/main/httpserver.cpp:2090
#17 0x0805034c in LshttpdMain::main (this=0xa06ca68, argc=1, argv=0xbfd6ab34) at /home/gwang/release/litespeed/src/main/lshttpdmain.cpp:1818
#18 0x0804c123 in main (argc=1, argv=0xbfd6ab34) at /home/gwang/release/litespeed/src/main.cpp:140
 
You must log in or register to reply here.
Top