OPCache Warnings
News and General
I see that RS Cloud Sites has made changes related to the OP-code cache. Now when I save changes on the General Config page in CP, I get the following warnings. I’m not sure what to do about this on my many, many, EE sites. I have a ticket in with RS, but thought I’d look for input here too. Any help or advice would be appreciated.
A PHP Error was encountered Severity: Warning Message: Zend OPcache API is restricted by “restrict_api” configuration directive Filename: core/EE_Config.php Line Number: 1217
A PHP Error was encountered Severity: Warning Message: Cannot modify header information - headers already sent by (output started at /mnt/stor6-wc1-dfw1/669788/www.blueskyrecording.com/web/content/brssys/codeigniter/system/core/Exceptions.php:170) Filename: core/EE_Input.php Line Number: 213
A PHP Error was encountered Severity: Warning Message: Cannot modify header information - headers already sent by (output started at /mnt/stor6-wc1-dfw1/669788/www.blueskyrecording.com/web/content/brssys/codeigniter/system/core/Exceptions.php:170) Filename: libraries/Functions.php Line Number: 446
Sounds like they are not segregating users’ environments very well, which I guess is to be expected with Rackspace’s “Cloud Sites” implementation. Looks like they have disabled a number of standard PHP opcache_* methods since their configuration would cause your opcache clearing to affect other users as well.
It’s a little annoying since we do first check that if (function_exists('opcache_invalidate')) is TRUE before trying to use it. It does present the possibility that changes you make to your PHP files, including the config, will not be reflected in subsequent requests. For some situations this might be a minor issue. For things like performing updates, this could cause some critical failures.
If I’m being flat honest, we have not had a good experience with Rackspace “Cloud Sites”. Their other offerings, including the normal “Rackspace Cloud” are fine. But Cloud Sites has not proven in our experience to be a good environment for any dynamic PHP/MySQL application, including ExpressionEngine.
Thanks for the input. Very helpful as I prepare for many EE3 updates.
I have the same issue as this, I was wondering if there is a solution even if temporary as it is causing issues with saving settings etc for users.
Hi Brandon, unfortunately this is out of ExpressionEngine’s control, as it’s restricted at the environmental level, affecting all PHP apps, and in a way that is mis-reporting function availability to PHP apps. My recommendation would be to move to a more suitable hosting environment as soon as you are able.
In my case, I found that the settings actually are saved in-spite of the warnings, which seems to be buying me some time as I take Derek’s advise, one site at a time.