[AutoRestarter] child process with pid=3264 received signal=11, a core file is created

P

paulozlx

Member
#1
#1
Hey

One of my server is constantly crashing and restarting OpenLiteSpeed. In the last night, it sent 4500 emails to me about the crash

Code: 
2019-10-24 09:55:37.173539 [NOTICE] Child: 3264] Core dump is enabled.
2019-10-24 09:55:37.260419 [NOTICE] [Child: 3264] Setup swapping space...
2019-10-24 09:55:37.260715 [NOTICE] [Child: 3264] LiteSpeed/1.5.7 Open
    module versions:
    modpagespeed 2.2-1.11.33.4
    cache 1.61
    modinspector 1.1
    uploadprogress LSIAPI_VERSION_STRING
    mod_security 1.1
 starts successfully!
2019-10-24 09:55:38.131846 [NOTICE] [AutoRestarter] child process with pid=3264 received signal=11, a core file is created!
2019-10-24 09:55:38.132072 [NOTICE] [*****] Debug version running, will create core file.
2019-10-24 09:55:39.100029 [NOTICE] [AutoRestarter] cleanup children processes and unix sockets belong to process 3264 !
2019-10-24 09:55:39.200725 [NOTICE] [AutoRestarter] new child process with pid=3299 is forked!
2019-10-24 09:55:39.203758 [NOTICE] [child: 3299] Successfully change current user to www-data
2019-10-24 09:55:39.206527 [NOTICE] Child: 3299] Core dump is enabled.
2019-10-24 09:55:39.296702 [NOTICE] [Child: 3299] Setup swapping space...
2019-10-24 09:55:39.296906 [NOTICE] [Child: 3299] LiteSpeed/1.5.7 Open
    module versions:
    modpagespeed 2.2-1.11.33.4
    cache 1.61
    modinspector 1.1
    uploadprogress LSIAPI_VERSION_STRING
    mod_security 1.1
 starts successfully!
2019-10-24 09:55:40.145847 [NOTICE] [AutoRestarter] child process with pid=3299 received signal=11, a core file is created!
2019-10-24 09:55:40.146040 [NOTICE] [*****] Debug version running, will create core file.
^C
root@ip-45-33-24-45:/usr/local/lsws/logs# tail -f error.log
    modpagespeed 2.2-1.11.33.4
    cache 1.61
    modinspector 1.1
    uploadprogress LSIAPI_VERSION_STRING
    mod_security 1.1
 starts successfully!
2019-10-24 09:56:44.633950 [WARN] [AutoRestarter] forking too frequently, suspend for a while!
2019-10-24 09:56:45.103351 [NOTICE] [AutoRestarter] child process with pid=3766 received signal=11, a core file is created!
2019-10-24 09:56:45.103376 [NOTICE] [*****] Debug version running, will create core file.
2019-10-24 09:56:46.030693 [NOTICE] [AutoRestarter] cleanup children processes and unix sockets belong to process 3766 !
Should I send bak_core/core zipped to somewhere not public?
 
D

David

Active Member
#2
#2
Can you check your email if you have gotten such an email about the backtrace of the core file?
If not, can you do (you need to install gdb)
/>gdb /usr/local/lsws/bin/openlitespeed /tmp/lshttpd/bak_core/core.xxxxx
and type bt, you will get the backtrace and send us it.
 
P

paulozlx

Member
#3
#3
Code: 
Server: LiteSpeed/1.5.7 Open
        module versions:
        modpagespeed 2.2-1.11.33.4
        cache 1.61
        modinspector 1.1
        uploadprogress LSIAPI_VERSION_STRING
        mod_security 1.1

OS: Linux
Release: 4.18.16-x86_64-linode118
Version: #1 SMP PREEMPT Mon Oct 29 15:38:25 UTC 2018
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 LWP 8800]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `openlitesp'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __strcmp_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:31
#0  __strcmp_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:31
#1  0x00000000005a5df1 in ExtWorker::generateRTReport (this=0x28ebaa0, fd=75, pTypeName=0x833109 "LSAPI") at extworker.cpp:465
#2  0x00000000005afd51 in ExtAppSubRegistry::generateRTReport (this=0xc1dca0 <s_registry+160>, fd=75, type=4) at registry/extappregistry.cpp:233
#3  0x00000000005b0463 in ExtAppRegistry::generateRTReport (fd=75) at registry/extappregistry.cpp:377
#4  0x00000000004e6a2e in HttpServerImpl::generateRTReport (this=0x280aa90) at httpserver.cpp:654
#5  0x00000000004e7519 in HttpServerImpl::onTimerSecond (this=0x280aa90) at httpserver.cpp:893
#6  0x00000000004e839e in HttpServerImpl::onTimer (this=0x280aa90) at httpserver.cpp:1127
#7  0x00000000004f171c in HttpServer::onTimer (this=0x280aa70) at httpserver.cpp:4626
#8  0x000000000051d734 in processTimerNew () at eventdispatcher.cpp:213
#9  0x000000000051d823 in EventDispatcher::run (this=0x280aab8) at eventdispatcher.cpp:243
#10 0x00000000004e5d7c in HttpServerImpl::start (this=0x280aa90) at httpserver.cpp:507
#11 0x00000000004f1638 in HttpServer::start (this=0x280aa70) at httpserver.cpp:4584
#12 0x00000000004e233a in LshttpdMain::main (this=0x280a820, argc=1, argv=0x7ffcd55ac098) at lshttpdmain.cpp:1073
#13 0x00000000004acf39 in main (argc=1, argv=0x7ffcd55ac098) at main.cpp:109
 
You must log in or register to reply here.
Top