Phpselector + litespeed new suexec + switch back to apache ?
Forum
  1. Forums
  2. CloudLinux and Control Panels
  3. CloudLinux and cPanel
  1. Richard Hordern
  2. 31.10.2013
  3.  Subscribe via email
Hello,

In a couple of weeks we will be updating litespeed to 4.2.5 which should allow us to use phpselector.

Will Cloudlinux\'s PHPSelector work out of the box ? or should I wait for CloudLinux to test it with Litespeed\'s new suexec per acount deamon mode ?

Currently with the native version of PHP, easy apache compiles it\'s version then litespeed compiless it\'s version based ton the easyapache version with lsphp support.

If I switch back to Apache for cPanel support because there are two versions everything continues to work fine albeit a bit slower.

If I\'m using phpselector with litespeed how will this work ?

Does phpselector install two versions of PHP one for apache and the other for Apache ? Woud sites stop working for sites with a phpselector PHP version if I switched back to Apache ?

Thanks !
Rate this post:
  1. 31.10.2013 10:10:48
  2. # 1
Igor Seletskiy Accepted Answer
Posts: 1201
Joined: 09.02.2010
0
Votes
Undo
People were using PHP Selector with LiteSpeed for ~4-5 months now. 
Few settings needs to be adjusted though:
http://docs.cloudlinux.com/index.html?litespeed_support.html
  1. 31.10.2013 16:10:25
  2. # 2
Richard Hordern Accepted Answer
Posts: 219
Joined: 19.03.2011
0
Votes
Undo
Hello,

It doesn't give me any information about the compatibility of switching back to apache without causing issues with PHP Selector.

I'm not sure how PHPSelctor manages the lsapi part as it wouldn't know if it's being run by Apache or by litespeed…

Also I would be using the new Suexec deamon per account mode and not the old CGI mode.
  1. 31.10.2013 17:10:11
  2. # 3
Igor Seletskiy Accepted Answer
Posts: 1201
Joined: 09.02.2010
0
Votes
Undo
As you might have noticed -- there is not thing to do from CL side when you switch to LiteSpeed --> so there is no difference when you switch back -- nothing needs to be done.

daemon per account mode does sound interesting.
  1. 01.11.2013 09:11:13
  2. # 4
Richard Hordern Accepted Answer
Posts: 219
Joined: 19.03.2011
0
Votes
Undo
Hello Igor, that's precisly what I don't understand.

PHP has to be built with LSAPI and needs LSAPI to be updated for new features.

For example litspeed 4.2.5 requires LSAPI  6.4 in order to detect 508 errors.

When you build PHP from source you have to first download the latest version of LSAPI and replace PHP's old version of LSAPI before manually compiling with the --with-litespeed option.

Because of this I don't see how it's possible for it to work without a litespeed compatible version of PHP… 

Thanks :)
  1. 01.11.2013 14:11:59
  2. # 5
Richard Hordern Accepted Answer
Posts: 219
Joined: 19.03.2011
0
Votes
Undo
Hello again,

If I understand correctly, based on litespeeds answer about this question group install alt-php installs both php rpms and lsphp rpms ?

If this is the case I presume we just have to wait for an update to the alt-php packages to get the latest lsapi version ?
  1. 04.11.2013 12:11:51
  2. # 6
Richard Hordern Accepted Answer
Posts: 219
Joined: 19.03.2011
0
Votes
Undo
Hello,

Just got my answer from your latest php-alt update announcement :

updated LSAPI to 6.3, PEAR extensions, PECL extensions

I guess I\'ll wait for an update with 6.4 before re-activating php-selector. :)

Thanks
  • Page :
  • 1


There are no replies made for this post yet.
Be one of the first to reply to this post!
Guest
Submit Your Response
Upload files or images for this discussion by clicking on the upload button below. Supports gif,jpg,png,zip,rar,pdf
• Insert • Remove Upload Files (Maximum File Size: 2 MB)
Captcha
To protect the site from bots and unauthorized scripts, we require that you enter the captcha codes below before posting your question.