Litespeed exited on signal 11

R

raphidae

Well-Known Member
#1
#1
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.
 
M

mistwang

LiteSpeed Staff
#2
#2
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.
 
R

raphidae

Well-Known Member
#3
#3
mistwang said:
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.
Click to expand...
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.
 
M

mistwang

LiteSpeed Staff
#4
#4
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.
 
R

raphidae

Well-Known Member
#5
#5
Code: 
(gdb) bt
#0  0x080fed83 in GSockAddr::ntop (pAddr=0x800, pBuf=0xffff9100 "\004\0202\b\004\0202\b(\221ÿÿ<t\020\b`C+\bð\223ÿÿ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
 
M

mistwang

LiteSpeed Staff
#6
#6
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?
 
You must log in or register to reply here.
Top