2.0.1 as stable as 2.0?

[ts77]

as I'm putting a bit more load on litespeed-webserver I just got this:
---
At [10/Apr/2005:16:52:32 +0200], web server with pid=7340 received unexpected signal=6, no core file is created. A new instance of web server will be started automatically!
---
... running 2.0.2 .

Does anyone know what could cause a "signal 6" ?
Thats running kernel 2.4.28 on a debian-stable.


Thanks,

thomas

[zellster]

Signal 6 is SIGABRT, which is typically triggered by a false assert() or a direct call to abort().

[ts77]

ok, thanks.
so the question to the litespeed-developers remains,
where in the litespeed-code could that happen?
I wasn't really able to reproduce this ... just got it two times yesterday.

[mistwang]

Yes, that's cause by assert() calls, assert() are used somewhere to guard against something not suppose to happen.
I can pin-point the location if you can send me a core dump, just enable core dump from the admin interface.

Thanks.

[ts77]

damned, I just go this again but still even though I had enabled core-dumps in the admin I didn't get one. The same for a segfault I had two days ago.

does anyone know how to convince a grsec-enabled kernel to produce core-files?

[mistwang]

I think there is no easy way to allow it other than recompiling the kernel with corresponding patch removed, at least for a redhat kernel.

However, the failed conditions are logged into stderr.log for assert() failures, so please search your stderr.log and let me know the related output. If it is a "POLLOUT" related failure, it has been fixed in current 2.1RC1.

[ts77]

ah, that gave some mesages .
message to bugs is on its way.

[mistwang]

Please try updated 2.1RC1.