OpenLiteSpeed 1.5.2 segfaults

[zEitEr]

Hello,

Probably it has been already reported and you are on a way to fix it. Or should I provide details of the recent segfaults in OpenLiteSpeed 1.5.2?

segfault at 0 ip 00007f871cbe8137 sp 00007ffc71c30d78 error 4 in libc-2.17.so[7f871cb4b000+1c2000]

Last 3 nights brought a challenge when litespeed caused an abnormal high load on a server.

Directadmin running on the server reported "New Message: Warning: The system load average is 1570.87" and only a hard reboot could help.

Regards,
Alex.

 

[David]

Yes, please give me more detail about the crash.
In your errorlog, there is a BUILD TIME about your running version, can you also paste here?
Thanks.

 

[zEitEr]

The same issue happened last night with 1.4.49 (after downgrade) already:

# /usr/local/lsws/bin/openlitespeed -v
LiteSpeed/1.4.49 Open (built: Fri Jun 28 15:24:10 UTC 2019)
        module versions:
        modpagespeed 2.2-1.11.33.4
        cache 1.61
        modinspector 1.1
        uploadprogress 1.1
        mod_security 1.1

For now I have only this backtrace:

# gdb /usr/local/lsws/bin/openlitespeed ./coredump
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-114.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/local/lsws/bin/openlitespeed...done.

warning: core file may not match specified executable file.
[New LWP 19548]

warning: .dynamic section for "/lib64/libc.so.6" is not at the expected address (wrong library or version mismatch?)
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `openlitespee'.
Program terminated with signal 11, Segmentation fault.
#0  __strcat_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:622
622             mov     %edx, 3(%rdi)
(gdb) frame 0
#0  __strcat_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:622
622             mov     %edx, 3(%rdi)
(gdb) bt full
#0  __strcat_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:622
No locals.
#1  0x00000000004dbb42 in HttpServerImpl::checkOLSUpdate() ()
No symbol table info available.
#2  0x00000000004dbd39 in HttpServerImpl::onTimer60Secs() ()
No symbol table info available.
#3  0x00000000004db10f in HttpServerImpl::onTimer30Secs() ()
No symbol table info available.
#4  0x00000000004db0ab in HttpServerImpl::onTimer10Secs() ()
No symbol table info available.
#5  0x00000000004dbda1 in HttpServerImpl::onTimer() ()
No symbol table info available.
#6  0x00000000004e4492 in HttpServer::onTimer() ()
No symbol table info available.
#7  0x000000000050fcec in processTimerNew() ()
No symbol table info available.
#8  0x000000000050fddb in EventDispatcher::run() ()
No symbol table info available.
#9  0x00000000004d98a2 in HttpServerImpl::start() ()
No symbol table info available.
#10 0x00000000004e43ae in HttpServer::start() ()
No symbol table info available.
#11 0x00000000004d6668 in LshttpdMain::main(int, char**) ()
No symbol table info available.
#12 0x00000000004a4869 in main ()
No symbol table info available.
(gdb) frame 0
#0  __strcat_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:622
622             mov     %edx, 3(%rdi)
(gdb)

I have these versions installed:

glibc-2.17-260.el7_6.5.x86_64
glibc-common-2.17-260.el7_6.5.x86_64
glibc-debuginfo-2.17-260.el7_6.5.x86_64
glibc-debuginfo-common-2.17-260.el7_6.5.x86_64
glibc-devel-2.17-260.el7_6.5.x86_64
glibc-headers-2.17-260.el7_6.5.x86_64

If you need anything else please let me know.

Regards,
Alex.

 

[David]

Thanks.
This is an error reported also by others just now and it is fixed.
Please try to use the newly build 1.4.49 or 1.5.2 to replace your current running binaries.
you can use
/usr/local/lsws/admin/misc/testbeate.sh -d 1.4.49
to get the latest 1.4.49.
Any question, please just let us know.

 

[zEitEr]

Seems to be fixed. Thanks.

# /usr/local/lsws/bin/litespeed -v
LiteSpeed/1.4.49 Open (built: Sat Jul  6 12:45:47 UTC 2019) (DEBUG)
        module versions:
        modpagespeed 2.2-1.11.33.4
        cache 1.61
        modinspector 1.1
        uploadprogress 1.1
        mod_security 1.1

 

[David]

Nice.
We will officially release it soon.

 

[papa zulu]

Hi,
I am running an older version of OpenLitespeed and just experienced a similar issue.
If I understand correctly, this was resolved in newer versions, specifically in version 1.4.49.
But as I can't yet upgrade the OpenLitespeed web server, does anyone know what was causing this issue?
Someone on Google Forums mentioned that they experienced when they had a bad vhost config.

I am looking for this just so that I can bypass this issue on my specific version of the OpenLitespeed web server, which is 1.4.46.

 

[Cold-Egg]

@papa zulu
If possible, please try to upgrade to the new version since v1.4 is outdated.