Upgraded to 3.3.8 and Litespeed stoped working

[fastproxy]

Hi,

Just upgraded to lastest version and litespeed stoped working.

And now i am not sure how to reverse to last version beside resintalling from source.
Any idea?

In the mean while i am using Apache now.

btw, the server running CENTOS5 with Plesk

 

[ffeingol]

you should be able to go into the version manager and revert back to the previous release.

 

[mistwang]

Hi,

Just upgraded to lastest version and litespeed stoped working.

And now i am not sure how to reverse to last version beside resintalling from source.
Any idea?

In the mean while i am using Apache now.

btw, the server running CENTOS5 with Plesk

Are you using the new Apache binary wrapper? Or, just a upgrade? from which version?

 

[fastproxy]

I upgraded from 3.3.7 then after the upgrade Litespeed restarted and never go back. I used the command line to restart but it says started successfully but it just does not work.

I could not get the the admin panel so could not reverse back.

I had to installed 3.3.7 manually again.

 

[mistwang]

You can switch to another version with command line tool: /opt/lsws/admin/misc/mgr_ver.sh

If you find core file under /opt/lsws/bin or /tmp/lshttpd, please forward to bug @ .... ,
Are you using 64 bit?

 

[fastproxy]

No i am using 32bit

 

[fastproxy]

btw, i accidently entered the command lshttpd -m.

Now the key is created and ready to move. How do i cancel this?

 

[mistwang]

lsws/bin/lshttpd -r
cp lsws/license.key conf

 

[jkeegan]

I just tried to upgrade from 3.3.7 to 3.3.8 on a Plesk VPS running CentOS and I experienced the same issue. On restart, Litespeed never came back and would not restart via the shell. I had to revert to 3.3.7 via command line in order to get Litespeed back.

Tried twice and got the same thing both times. Definitely an issue for at least this Centos+Plesk combo... 3.3.8 is not working...

 

[mistwang]

Is that possible to PM me temp root access to that box, I will take a look and have it fixed ASAP.

 

[mistwang]

Or, you can send us core files created under /tmp/lshttpd or /opt/lsws/bin directory, it will help us fixing the issue.

 

[mistwang]

OK, it should be fixed in our latest 3.3.9 build, which has been tested on jkeegan's server.

 

[jkeegan]

OK, it should be fixed in our latest 3.3.9 build, which has been tested on jkeegan's server.

Thanks so much - I'm happy to help!

 

[anewday]

So, I should wait until 3.3.9 is released before trying it on my production server?

 

[mistwang]

It only affect Plesk users.