4.0b3 release

M

mistwang

LiteSpeed Staff
#1
#1
Finally, here comes 4.0b3 release. :)

New features are:
  • mod_security 2.x rule support
  • Improved mod_security audit log, compatible with cPanel mod_security plugin.
  • reorganized real-time status page
  • Large file support for 32bit Linux
  • All bug fixes from 3.3.x releases
To enable cache for vhost configured through Apache httpd.conf, directive

CacheEnable ...

should be set for the vhost or from .htaccess


only linux package is available now

i386-std package
http://www.litespeedtech.com/packages/4.0/lsws-4.0b3-std-i386-linux.tar.gz

i386-ent package
http://www.litespeedtech.com/packages/4.0/lsws-4.0b3-ent-i386-linux.tar.gz

x86_64-ent package
http://www.litespeedtech.com/packages/4.0/lsws-4.0b3-ent-x86_64-linux.tar.gz
 
M

mistwang

LiteSpeed Staff
#3
#3
It will be addressed along with the new server status page. This release is only a make up, did not change the way it works or add something new.

We'd like to have another beta release, then go through two or three Release Candidate releases before the official release. Hopefully, we will move faster than current pace. :)
 
M

mistwang

LiteSpeed Staff
#5
#5
Release candidates should be pretty stable. For the beta releases, only the new features are not considered stable, as it has not been widely tested.
 
K

kc8yds

Active Member
#6
#6
i installed this on both of my servers and got these errors after it started running & it was really slow loading the panel

2008-11-23 21:54:58.419 WARN [AutoRestarter] forking too frequently, suspend for a while!
2008-11-23 21:56:02.306 WARN [AutoRestarter] forking too frequently, suspend for a while!
2008-11-23 21:57:03.414 WARN [AutoRestarter] forking too frequently, suspend for a while!


installed on centos (5) no control panel -- same on both servers



if you need any other info just ask
 
C

closet geek

Well-Known Member
#7
#7
Now that mod_sec v2 compatibility has been added I'm keen to test it. We are using LiteSpeed directly using it's own configuration files i.e. not importing from Apache. How do we set each VirtualHost to use a global mod_sec.conf rules file?
 
Last edited:
M

mistwang

LiteSpeed Staff
#8
#8
closet geek said:
Now that mod_sec v2 compatibility has been added I'm keen to test it. We are using LiteSpeed directly using it's own configuration files i.e. not importing from Apache. How do we set each VirtualHost to use a global mod_sec.conf rules file?
Click to expand...
Just set the security rule at server level.
 
M

mistwang

LiteSpeed Staff
#9
#9
kc8yds said:
i installed this on both of my servers and got these errors after it started running & it was really slow loading the panel

2008-11-23 21:54:58.419 WARN [AutoRestarter] forking too frequently, suspend for a while!
2008-11-23 21:56:02.306 WARN [AutoRestarter] forking too frequently, suspend for a while!
2008-11-23 21:57:03.414 WARN [AutoRestarter] forking too frequently, suspend for a while!


installed on centos (5) no control panel -- same on both servers



if you need any other info just ask
Click to expand...
The best option is to let us login to your server and take a look. If it is not possible, you can send us the core files under /tmp/lshttpd/bak_core directory.
 
M

mistwang

LiteSpeed Staff
#13
#13
kc8yds said:
i installed this on both of my servers and got these errors after it started running & it was really slow loading the panel

2008-11-23 21:54:58.419 WARN [AutoRestarter] forking too frequently, suspend for a while!
2008-11-23 21:56:02.306 WARN [AutoRestarter] forking too frequently, suspend for a while!
2008-11-23 21:57:03.414 WARN [AutoRestarter] forking too frequently, suspend for a while!
Click to expand...
This problem should have been fixed with the latest build of 4.0b3 package, please download it and give it a try.
 
D

Dru

Member
#16
#16
Had a problem this morning with 4.0b3, I restarted the webserver and it wouldn't come back up, I had to rollback to 3.3.22 manually (since the web interface didn't work).

If I try to upgrade to it again, then it works fine until it's restarted and then it fails again, a little snippet from the error log is below,

2008-12-03 10:03:16.209 [NOTICE] Loading LiteSpeed/4.0b3 Standard ...
2008-12-03 10:03:16.322 [NOTICE] [ADMIN] server socket: uds://opt/lsws/admin/tmp/admin.sock.7414
2008-12-03 10:03:16.322 [NOTICE] Loading configuration from /opt/lsws/conf/httpd_config.xml ...
2008-12-03 10:03:16.324 [INFO] old priority: 0, new priority: 0
2008-12-03 10:03:16.324 [INFO] [config:server:basic] For better obscurity, server version number is hidden in the response header.
2008-12-03 10:03:16.666 [ERROR] HttpListener::start(): Can't listen at address adminListener: Address already in use!
2008-12-03 10:03:16.666 [ERROR] HttpServer::addListener(adminListener) failed to create new listener
2008-12-03 10:03:16.666 [ERROR] [config:admin:listener:adminListener] failed to start listener on address *:7080!
2008-12-03 10:03:16.666 [ERROR] [config:admin:listener] No listener is available for admin virtual host!
2008-12-03 10:03:16.667 [ERROR] Fatal error in configuration, exit!
 
C

closet geek

Well-Known Member
#17
#17
Dru,

I believe we also had this error, it may be related to the fix mistwang has introduced in beta 3. It was a silent fix, so you need to download beta 3 again and install it if you haven't already.

By the way am I the only person who isn't able to restart via the admin interface? It simply fails to load again? I have to restart via the shell in order for LiteSpeed to actually come back up after a restart.
 
M

mistwang

LiteSpeed Staff
#18
#18
Thank your for the bug report.
"The problem with graceful restart from web console" has been fixed in the latest 4.0b3 release package (today).
 
You must log in or register to reply here.
Top