Installed 5.0RC1 and CPU usage exploded

Discussion in 'General' started by jdeg, Mar 27, 2014.

  1. jdeg

    jdeg New Member

    I realize that installing a RC on a production server is probably a bad idea, but I did want to see how 5.0 would run. Unfortunately the number of lsphp5 processes jumped to about 50 and the load went through the roof. I didn't have it installed long enough to figure out why. I didn't change any settings. Any ideas why?
  2. jdeg

    jdeg New Member

    ah, a clue:

    At [26/Mar/2014:21:32:23 -0400], web server with pid=11170 received unexpected signal=6, 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.0RC1 Enterprise
    OS: Linux
    Release: 2.6.32-431.el6.x86_64
    Version: #1 SMP Fri Nov 22 03:15:09 UTC 2013
    Machine: x86_64


    I forwarded the core file
  3. NiteWave

    NiteWave Administrator

    please do
    #yum install gdb

    so the debug info will be more detailed and help to fix a bug.
  4. jdeg

    jdeg New Member

    here we go:

    At [27/Mar/2014:13:17:02 -0400], web server with pid=16347 received unexpected signal=6, 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.0RC1 Enterprise
    OS: Linux
    Release: 2.6.32-431.el6.x86_64
    Version: #1 SMP Fri Nov 22 03:15:09 UTC 2013
    Machine: x86_64

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

    [New Thread 16347]
    [New Thread 16348]
    [New Thread 16349]
    [Thread debugging using libthread_db enabled]
    Core was generated by `litespeed'.
    Program terminated with signal 6, Aborted.
    #0 0x000000367f032925 in raise () from /lib64/libc.so.6
    #0 0x000000367f032925 in raise () from /lib64/libc.so.6
    #1 0x000000367f034105 in abort () from /lib64/libc.so.6
    #2 0x000000367f02ba4e in __assert_fail_base () from /lib64/libc.so.6
    #3 0x000000367f02bb10 in __assert_fail () from /lib64/libc.so.6
    #4 0x000000000048e8fb in HttpRespHeaders::add (this=0x2678410, headerIndex=HttpRespHeaders::H_LOCATION, pName=0x754d5a "Location", nameLen=8, pVal=0x754d59 "", valLen=0, method=1) at /home/gwang/release/litespeed/src/http/httprespheaders.cpp:201
    #5 0x000000000048d94b in HttpResp::addLocationHeader (this=0x2678410, pReq=0x2677fe0) at /home/gwang/release/litespeed/src/http/httpresp.cpp:84
    #6 0x000000000048daac in HttpResp::prepareHeaders (this=0x2678410, pReq=0x2677fe0, rangeHeaderLen=0) at /home/gwang/release/litespeed/src/http/httpresp.cpp:136
    #7 0x0000000000463515 in HttpConnection::buildErrorResponse (this=0x2677fc0, errMsg=0x0) at /home/gwang/release/litespeed/src/http/httpconnection.cpp:2196
    #8 0x00000000004633d5 in HttpConnection::sendHttpError (this=0x2677fc0, pAdditional=0x0) at /home/gwang/release/litespeed/src/http/httpconnection.cpp:2164
    #9 0x0000000000468db0 in HttpConnection::httpError (this=0x2677fc0, code=14, pAdditional=0x0) at /home/gwang/release/litespeed/src/http/httpconnection.h:317
    #10 0x00000000004638b2 in HttpConnection::eek:nReadEx (this=0x2677fc0) at /home/gwang/release/litespeed/src/http/httpconnection.cpp:2305
    #11 0x000000000049e060 in NtwkIOLink::eek:nRead (pThis=0x2685a30) at /home/gwang/release/litespeed/src/http/ntwkiolink.cpp:627
    #12 0x000000000049d02b in NtwkIOLink::handleEvents (this=0x2685a30, evt=1) at /home/gwang/release/litespeed/src/http/ntwkiolink.cpp:257
    #13 0x000000000051730c in epoll::waitAndProcessEvents (this=0x27ceb30, iTimeoutMilliSec=100) at /home/gwang/release/litespeed/src/edio/epoll.cpp:271
    #14 0x0000000000457938 in EventDispatcher::run (this=0x2689418) at /home/gwang/release/litespeed/src/http/eventdispatcher.cpp:225
    #15 0x000000000041267f in HttpServerImpl::start (this=0x26893f0) at /home/gwang/release/litespeed/src/main/httpserver.cpp:506
    #16 0x00000000004159ed in HttpServer::start (this=0x9d9430) at /home/gwang/release/litespeed/src/main/httpserver.cpp:1971
    #17 0x000000000040bd37 in LshttpdMain::main (this=0x2688b20, argc=1, argv=0x7fff157e8b48) at /home/gwang/release/litespeed/src/main/lshttpdmain.cpp:1808
    #18 0x000000000040783f in main (argc=1, argv=0x7fff157e8b48) at /home/gwang/release/litespeed/src/main.cpp:139
  5. jdeg

    jdeg New Member

    I forwarded that to the bug email address, btw...

    What happens to the bug report from there?
  6. Michael

    Michael Administrator Staff Member

    Generally, one of our developers takes a look into it, tries to reproduce it, figures out what went wrong, and fixes it. Then we include it in the next build with a short explanation of the bug that was fixed. (If it were a problem with a specific feature you were trying to use, we'd let you know as soon as it had been fixed, but this seems like more of a general problem.)

    Cheers,

    m
  7. jdeg

    jdeg New Member

    thanks for explaining :)

Share This Page