LiteSpeed Support Forums

LiteSpeed Support Forums (http://www.litespeedtech.com/support/forum/index.php)
-   LiteSpeed Cache (http://www.litespeedtech.com/support/forum/forumdisplay.php?f=30)
-   -   [solved] LiteSpeed Caching Error (http://www.litespeedtech.com/support/forum/showthread.php?t=4961)

NC-Designs 05-08-2011 11:14 AM

[solved] LiteSpeed Caching Error
 
Typically an error has occured since updating to 4.1

Quote:

At [08/May/2011:19:10:10 +0100], web server with pid=7836 received unexpected signal=11, a core file is created. A new instance of web server will be started automatically!

Please forward the following debug information to bug@litespeedtech.com.
Environment:

Server: LiteSpeed/4.1 Enterprise
OS: Linux
Release: 2.6.18-194.17.1.el5
Version: #1 SMP Wed Sep 29 12:50:31 EDT 2010
Machine: x86_64

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

Core was generated by `litespeed'.
Program terminated with signal 11, Segmentation fault.
#0 0x0000000000484ad5 in ?? ()
#0 0x0000000000484ad5 in ?? ()
#1 0x0000000000000004 in ?? ()
#2 0x0000000100000000 in ?? ()
#3 0x0000000013375000 in ?? ()
#4 0x000000001320e210 in ?? ()
#5 0x000000001320e210 in ?? ()
#6 0x0000000000000000 in ?? ()
Please could you get back to me about this.

Thanks.

NiteWave 05-08-2011 07:08 PM

can you install the debug version
http://www.litespeedtech.com/package...nux-dbg.tar.gz
and reproduce the issue

NC-Designs 05-09-2011 12:34 AM

Quote:

Originally Posted by NiteWave (Post 25968)
can you install the debug version
http://www.litespeedtech.com/package...nux-dbg.tar.gz
and reproduce the issue

It seems I cannot reproduce this issue with the debug version no.

NiteWave 05-09-2011 02:34 AM

can you switch to the latest 4.1 build(if not yet), see if can reproduce?

NC-Designs 05-09-2011 02:37 AM

Quote:

Originally Posted by NiteWave (Post 25976)
can you switch to the latest 4.1 build(if not yet), see if can reproduce?

Have done this and it seems to be fine, I guess it was a bug that has been ironed out already.

Regards,
Chris.


All times are GMT -7. The time now is 11:30 PM.