Forum
  1. Forums
  2. Imunify360
  3. Imunify360 and Imunify Sensor
  1. Hector
  2. Wednesday, May 24, 2017
  3.  Subscribe via email
Hi,

I had Opcache running, installed through cPanel's Easy Apache 4. After installing Imunify's "Hardened PHP" opcache became unavailable. Installing it again through Easy Apache aparently overwrites your hardened PHP entirely back again. So it is an endless loop of one overwriting the other.

Imunify also installed all versions of PHP, which were not present in the original config.

In short, it appears that your hardened php does not have any connection with its previous settings? For the time being, and to keep opcache, I have given priority to EasyApache but the ideal solution is to have a hardened version of the setup that I had originally chosen. For example, choose which hardened modules and extensions to install? Or that Imunify reads EA config and even update whenever EA provisions a new config. This is how Litespeed interfaces with EA4, for example.
Rate this post:
  1. 26.05.2017 13:05:14
  2. # 1
Oleksiy Shchukin Accepted Answer
Posts: 9
Joined: 16.03.2017
0
Votes
Undo
Thank you for your report. From this point we noted that our hardened php apache profile is missing opcache and we are working on adding opcache back to hardened php profile. As soon as you activate hardened php via Imunify360, your ea-php *any profile* packages will be upgraded with hardened php as far hardened php ones have higher rpm package epoch. Thus feel free to switch back to your regular ea-php profile after hardened php activation.

In a next release we are adding a change to avoid switching from existing ea-php profile to hardened php (jira id DEF-1997). That step will not be required.

Kind regards,
Imunify360 developer
  1. 30.05.2017 11:05:28
  2. # 2
Oleksiy Shchukin Accepted Answer
Posts: 9
Joined: 16.03.2017
0
Votes
Undo
Here is another finding: ZendGuard starting from php5.5 obsoletes opcache package and brings on it's own opcache.so [http://www.zend.com/en/products/guard/release-notes]. That is why 'yum update -y "ea-php*' log may look like this -

# yum update -y "ea-php*
May 30 12:43:56 Updated: 1:ea-php55-runtime-5.5.38-1.el6.cloudlinux.x86_64
May 30 12:43:57 Updated: 1:ea-php55-php-common-5.5.38-11.el6.cloudlinux.x86_64
May 30 12:43:59 Updated: 1:ea-php55-php-pdo-5.5.38-11.el6.cloudlinux.x86_64
....
May 30 12:44:30 Updated: 1:ea-php55-php-gmp-5.5.38-11.el6.cloudlinux.x86_64
May 30 12:44:30 Updated: 1:ea-php55-php-fileinfo-5.5.38-11.el6.cloudlinux.x86_64
May 30 12:44:31 Installed: 1:ea-php55-php-zendguard-3.3-6.el6.cloudlinux.x86_64
....
May 30 12:44:57 Erased: ea-php55-php-opcache
  • 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
• Remove Upload Files (Maximum File Size: 2 MB)
You may insert polls into your post. The poll would then appear in the post.
Vote Options
Captcha
To protect the site from bots and unauthorized scripts, we require that you enter the captcha codes below before posting your question.