Support

andreas · #11 05-11-2011, 07:38 AM

Keeps happening constantly now... back to 4.0.20.

MikeDVB · #12 05-11-2011, 03:27 PM

Indeed, the only way I've found to prevent the spinlock is to set the maximum connections (http) to something like 50k and then the spinlock never happens. On 4.0 you could set it to something conservative like 2k (the default) and you would be fine but if you upgrade to 4.1 and leave it at 2k you'll inevitably hit this spinlock eventually.

Pipert · #13 05-12-2011, 12:01 AM

Quote:

Originally Posted by MikeDVB

Indeed, the only way I've found to prevent the spinlock is to set the maximum connections (http) to something like 50k and then the spinlock never happens. On 4.0 you could set it to something conservative like 2k (the default) and you would be fine but if you upgrade to 4.1 and leave it at 2k you'll inevitably hit this spinlock eventually.

I've had Litespeed 4.1 randomly crash on me a couple of times. I've now downgraded to 4.0.20 and I haven't had any issues with it.

MikeDVB · #14 05-12-2011, 12:17 AM

Quote:

Originally Posted by Pipert

I've had Litespeed 4.1 randomly crash on me a couple of times. I've now downgraded to 4.0.20 and I haven't had any issues with it.

When it crashed, did you have to manually intervene? The issue with this spin lock is that it doesn't kill itself off and start a new process automatically. It will sit and do nothing but spin lock for 5 to 15 minutes before it gets a signal 11.

MikeDVB · #15 05-12-2011, 11:20 AM

On the latest debug version I'm getting a lot of this:

Code:

root@echo [/tmp/lshttpd/bak_core]# gdb /usr/local/lsws/bin/lshttpd core.829851
GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-32.el5_6.2)
Copyright (C) 2009 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/lshttpd...(no debugging symbols found)...done.

warning: core file may not match specified executable file.
[New Thread 829853]
[New Thread 829852]
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Failed to read a valid object file image from memory.
Core was generated by `litespeed'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000036f867c2e3 in ?? ()
(gdb) bt
Cannot access memory at address 0x7fffaeabaf98

The one from yesterday is the same:

root@echo [/tmp/lshttpd/bak_core]# gdb /usr/local/lsws/bin/lshttpd core.624673
GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-32.el5_6.2)
Copyright (C) 2009 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/lshttpd...(no debugging symbols found)...done.

warning: core file may not match specified executable file.
[New Thread 624678]
[New Thread 624677]
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Failed to read a valid object file image from memory.
Core was generated by `litespeed'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000036f867c321 in ?? ()
(gdb) bt
Cannot access memory at address 0x7fff48bf21b8