LiteSpeed Technologies
Download Download     Blog Blog     Wiki Wiki     Forum Forum     Store     Contact Contact    

Go Back   LiteSpeed Support Forums > LiteSpeed Web Server > Bug Reports > Litespeed exited on signal 11

Reply
 
Thread Tools Display Modes
  #1  
Old 01-11-2010, 12:47 PM
raphidae raphidae is offline
Senior Member
 
Join Date: Apr 2008
Posts: 59
Default Litespeed exited on signal 11

I have just installed a server, downloaded and installed lsws std, and tried to start it.

The result is the following in /usr/local/lsws/logs/lsws.log:

Code:
2010-01-11 21:40:41.468 [NOTICE] Loading LiteSpeed/4.0.12 Standard ...
2010-01-11 21:40:41.474 [NOTICE] [ADMIN] server socket: uds://usr/local/lsws/admin/tmp/admin.sock.7645
2010-01-11 21:40:41.474 [NOTICE] Loading configuration from /usr/local/lsws/conf/httpd_config.xml ...
2010-01-11 21:40:41.488 [NOTICE] The maximum number of file descriptor limit is set to 7178.
Then it apparently dies:

Code:
Jan 11 21:40:41 satanael kernel: pid 1641 (lshttpd.4.0.12), uid 0: exited on signal 11
FreeBSD satanael.darkness-reigns.net 9.0-CURRENT FreeBSD 9.0-CURRENT #4: Mon Jan 11 18:53:20 CET 2010 terrence@satanael.darkness-reigns.net:/usr/obj/usr/src/sys/BELIAL-SMP amd64

COMPAT_FREEBSD6 and COMPAT_FREEBSD7 in kernel and compat packages installed.

Please advise.
Reply With Quote
  #2  
Old 01-11-2010, 12:57 PM
mistwang mistwang is offline
LiteSpeed Staff
 
Join Date: May 2003
Location: New Jersey
Posts: 7,583
If you can get a core file, please try dump the call stack back trace with GDB.
I think the Freebsd6 compatibility layer in Freebsd 9 does not work that well. Maybe file a bug report to FreeBSD group.
Reply With Quote
  #3  
Old 01-11-2010, 01:33 PM
raphidae raphidae is offline
Senior Member
 
Join Date: Apr 2008
Posts: 59
Quote:
Originally Posted by mistwang View Post
If you can get a core file, please try dump the call stack back trace with GDB.
I think the Freebsd6 compatibility layer in Freebsd 9 does not work that well. Maybe file a bug report to FreeBSD group.
How do I get a core? There's none in /tmp/lshttpd.

Also, I've been using FreeBSD since version 3 and I have never seen the backwards compatibility fail. FreeBSD is really anal about regression testing.

If you want I can downgrade to 8-STABLE, but I can almost guarantee that the same happens with that version as the change between 8-STABLE and 9-CURRENT is minimal (they just cut RELENG_8). This can also be seen in the lack of COMPAT_FREEBSD8 currently.
Reply With Quote
  #4  
Old 01-11-2010, 01:52 PM
mistwang mistwang is offline
LiteSpeed Staff
 
Join Date: May 2003
Location: New Jersey
Posts: 7,583
You can check kernel configuration
kern.sugid_coredump

Core file may not under /tmp/lshttpd, some system can explicitly configure where to put the core file.

Run "lshttpd" with parameter "-d" under GDB, should give you the stack back trace as well.
Reply With Quote
  #5  
Old 01-11-2010, 02:03 PM
raphidae raphidae is offline
Senior Member
 
Join Date: Apr 2008
Posts: 59
Code:
(gdb) bt
#0  0x080fed83 in GSockAddr::ntop (pAddr=0x800, pBuf=0xffff9100 "\004\0202\b\004\0202\b(\221&#255;&#255;<t\020\b`C+\b&#240;\223&#255;&#255;T\002", len=80) at /usr/home/gwang/release/httpd/httpd/socket/gsockaddr.cpp:284
#1  0x08066317 in HttpServerBuilder::detectIP (this=0x830f000, family=28 '\034', str=0xffff93f0 "", pEnd=0xffffb3e0 "") at /usr/home/gwang/release/httpd/httpd/main/httpserverbuilder.cpp:5615
#2  0x08066b55 in HttpServerBuilder::initAdmin (this=0x830f000, pNode=0x831f0d0) at /usr/home/gwang/release/httpd/httpd/main/httpserverbuilder.cpp:5759
#3  0x08063b18 in HttpServerBuilder::configServer (this=0x830f000, reconfig=0) at /usr/home/gwang/release/httpd/httpd/main/httpserverbuilder.cpp:4783
#4  0x0806411e in HttpServerBuilder::initServer (this=0x830f000, reconfig=0) at /usr/home/gwang/release/httpd/httpd/main/httpserverbuilder.cpp:4941
#5  0x0804ddf2 in LshttpdMain::config (this=0x82fc000) at /usr/home/gwang/release/httpd/httpd/main/lshttpdmain.cpp:1139
#6  0x0804e5c7 in LshttpdMain::init (this=0x82fc000, argc=1, argv=0xffffdc74) at /usr/home/gwang/release/httpd/httpd/main/lshttpdmain.cpp:1548
#7  0x0804e923 in LshttpdMain::main (this=0x82fc000, argc=1, argv=0xffffdc74) at /usr/home/gwang/release/httpd/httpd/main/lshttpdmain.cpp:1678
#8  0x0804b2c5 in main (argc=1, argv=0xffffdc74) at /usr/home/gwang/release/httpd/httpd/main.cpp:121
Reply With Quote
  #6  
Old 01-12-2010, 12:39 PM
mistwang mistwang is offline
LiteSpeed Staff
 
Join Date: May 2003
Location: New Jersey
Posts: 7,583
Looks like net_rt_iflist() system call return something invalid.
Are you using 32bit binary on 64bit freebsd? If yes, can you please try the 64bit binary with a trial key?
Reply With Quote
  #7  
Old 01-13-2010, 02:32 AM
raphidae raphidae is offline
Senior Member
 
Join Date: Apr 2008
Posts: 59
Quote:
Originally Posted by mistwang View Post
Looks like net_rt_iflist() system call return something invalid.
Are you using 32bit binary on 64bit freebsd? If yes, can you please try the 64bit binary with a trial key?
That is correct. The x64 enterprise version does not have the problem.
Reply With Quote
  #8  
Old 02-05-2010, 08:33 AM
raphidae raphidae is offline
Senior Member
 
Join Date: Apr 2008
Posts: 59
So, now my trial has run out. What's the workaround/fix for Std?
Reply With Quote
  #9  
Old 02-05-2010, 02:16 PM
mistwang mistwang is offline
LiteSpeed Staff
 
Join Date: May 2003
Location: New Jersey
Posts: 7,583
This is fixed in the latest 4.0.12 i386-freebsd6 build.
Reply With Quote
  #10  
Old 02-05-2010, 02:38 PM
raphidae raphidae is offline
Senior Member
 
Join Date: Apr 2008
Posts: 59
I'm confused a bit. Are there different versions of 4.0.12?

If so, how to differentiate?
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 02:02 AM.



- Archive - Top
© Copyright 2003-2011 LiteSpeed Technologies, Inc. All rights reserved. Privacy Policy.