CloudLinux - CloudLinux Blog - Beta: mod_lsapi updated
RSS

Beta: mod_lsapi updated

Beta: mod_lsapi updated

The new updated mod_lsapi packages for CloudLinux 6 and 7 as well as for Apache 2.4 (CloudLinux 6) and EasyApache 4 (CloudLinux 6 and 7) are available for download from our updates-testing repository.

Changelog:

mod_lsapi 1.1-12

ea-apache24-mod_lsapi 1.1-12

httpd24-mod_lsapi 1.1-12

  • MODLS-419: implemented the script for switching lsapi from the old mechanism (--enable-global, --enable-domain) to the new (lsapi via web-interface of cPanel).

Explanation of changes:

Normally, after updating ea-apache24-mod_lsapi, all the domains are switched to default handler. To turn on mod_lsapi back it is necessary to enable lsapi handler through MultiPHP manager. We have noticed that it is not very convenient to enable lsapi handler through MultiPHP manager after updating and automating the process.

So, if you update ea-apache24-mod_lsapi from the stable repo or ea-apache24-mod_lsapi-1.1-9 or lower from beta, after update you should run /usr/bin/switch_mod_lsapi --setup to add lsapi handler to MultiPHP Manager.

After this, you will be asked to enable lsapi handler for proper PHP versions, depending on how you used mod_lsapi before (--enable-global, --enable-domain), and then restart Apache.

We should repeat that the following options were disabled for ea-apache24-mod_lsapi:

/usr/bin/switch_mod_lsapi --enable-domain

/usr/bin/switch_mod_lsapi --disable-domain

/usr/bin/switch_mod_lsapi --enable-global

/usr/bin/switch_mod_lsapi --disable-global

You can manage your domains with PHP version and lsapi handler from MultiPHP Manager.

Example 1:

  1. ea-apache24-mod_lsapi-1.0-30 installed and globally enabled.

  2. The command yum update ea-apache24-mod_lsapi --enablerepo=cloudlinux-updates-testing --enablerepo=cl-ea4-testing executed.

  3. If switch_mod_lsapi --setup is not called, mod_lsapi will work as before.

  4. switch_mod_lsapi --setup will return:

Instruction: http://docs.cloudlinux.com/index.html?apache_mod_lsapi.html

patching file apache.pm

Patch was applied correctly...

Added hook for System::upcp to hooks registry

mod_lsapi switched to turning on and off through the MultiPHP Manager(/Home/Software/MultiPHP Manager)

You are using enabled globally mod_lsapi. Do you want to enable mod_lsapi through MultiPHP Manager?

Current PHP will be switched to lsapi handler:

ea-php53 SAPI: suphp

ea-php54 SAPI: suphp

ea-php55 SAPI: cgi

ea-php56 SAPI: suphp

ea-php70 SAPI: cgi

ea-php71 SAPI: suphp

If you type no then mod_lsapi will be disabled and you can enable it again from MultiPHP Manager.

Do you want to proceed? [y/N]

 

5. If N chosen, then mod_lsapi moves to the new type of integration with cPanel and restores php.conf and suphp.conf files. mod_lsapi will be disabled.

6. If Y chosen, then all installed versions will be moved to LSAPI handler.

Setting ea-php53 to lsapi handler...

Setting ea-php54 to lsapi handler...

Setting ea-php55 to lsapi handler...

Setting ea-php56 to lsapi handler...

Setting ea-php70 to lsapi handler...

Setting ea-php71 to lsapi handler...

 

 

Example 2:

  1. ea-apache24-mod_lsapi-1.0-30 was installed and enabled only for one domain but all the other domains have the same version of ea-php56.

  2. The command yum update ea-apache24-mod_lsapi --enablerepo=cloudlinux-updates-testing --enablerepo=cl-ea4-testing executed.

  3. If switch_mod_lsapi --setup is not called, mod_lsapi will work as before.

  4. switch_mod_lsapi --setup will return:

Instruction: http://docs.cloudlinux.com/index.html?apache_mod_lsapi.html
patching file apache.pm
Patch was applied correctly...
Added hook for System::upcp to hooks registry
Domains that handled by ea-php56:
tstdomain01.com - lsapi
tstdomain02.com - suphp
There are domains which are using mod_lsapi through --enable-domain option.
This option is deprecated for EA4 and mod_lsapi switched to turning on and off through
the MultiPHP Manager(/Home/Software/MultiPHP Manager)
Do you want to enable mod_lsapi through MultiPHP Manager for ea-php56?
Domains which are using suphp will be switched to lsapi handler too.
If you type N then mod_lsapi will remain enabled on these domains.
However, enabling mod_lsapi for new domains is now possible only through MultiPHP Manager.
Do you want to proceed? [y/N] y
Setting ea-php56 to lsapi handler...
Built /etc/apache2/conf/httpd.conf OK
Reconfiguration completed

5. If N chosen, then mod_lsapi moves to the new type of integration with cPanel and restores php.conf and suphp.conf files. mod_lsapi will still be enabled for domains like tstdomain01.com through .htaccess file in example.

6. If Y chosen, then displayed PHP version will be moved to LSAPI handler. According to the example, tstdomain01.com and tstdomain02.com using ea-php56 will be switched to lsapi handler.

To update:

cPanel & RPM Based

$ yum update liblsapi liblsapi-devel --enablerepo=cloudlinux-updates-testing
$ yum update mod_lsapi --enablerepo=cloudlinux-updates-testing
$ service httpd restart

DirectAdmin

$ yum update liblsapi liblsapi-devel --enablerepo=cloudlinux-updates-testing
$ cd /usr/local/directadmin/custombuild
$ ./build set cloudlinux_beta yes
$ ./build update
$ ./build mod_lsapi

To install follow the instructions on the link:

http://docs.cloudlinux.com/index.html?installation_mod_lsapi.html

For EasyApache 4

To update: 

$ yum update liblsapi liblsapi-devel ea-apache24-mod_lsapi --enablerepo=cl-ea4-testing --enablerepo=cloudlinux-updates-testing
$ service httpd restart

To install:

$ yum-config-manager --enable cl-ea4-testing
$ yum update liblsapi liblsapi-devel --enablerepo=cloudlinux-updates-testing

readhttp://docs.cloudlinux.com/index.html?cpanel_easyapache_4.html

$ yum-config-manager --disable cl-ea4-testing

Go to MultiPHP Manager and enable mod_lsapi for your domains through lsapi handler.

http24 for CloudLinux 6

For installation/update run:

$ yum update liblsapi liblsapi-devel --enablerepo=cloudlinux-updates-testing
$ yum install httpd24-mod_lsapi --enablerepo=cloudlinux-updates-testing
Major vulnerability: The Stack Clash security issu...
Issues caused by the latest KernelCare update and ...
 

By accepting you will be accessing a service provided by a third-party external to https://www.cloudlinux.com/