simnom's avatar

OPcache issues

Hey,

Seem to be having an issue with OPcache and Laravel 5 in my production environment. In short, the application just dies with nothing being written in the access_log, error_log or application log files but zend_mm_heap corrupted being written to the top level apache error_log.

I can resolve this by disabling OPcache with php_flag opcache.enable Off in the .htaccess flag but I'm not sure that this should really be necessary.

Any one come across this before?

Thanks

Simon

0 likes
4 replies
bashy's avatar

Sure PHP has been installed properly? All sites running on the server having issues?

simnom's avatar

Yeah, seems to be fine generally and all other sites are running fine. This is the only L5 site running on the server. Currently thing I'm looking at is the PHP version which is 5.5.11, there seems to be a few segmentation bug fixes up to 5.5.22.

5.5.22 runs fine in my vagrant dev environment so I'm just deciding whether to bite the bullet and push up to that on the server. Weird one though and really hard to debug as there's nothing to work with in terms of logging.

bashy's avatar

Could well be the PHP version. I too use 5.5.22 as well as PHP 5.6.5 with OPcache v7.0.4-dev

simnom's avatar
simnom
OP
Best Answer
Level 1

Just as a closing note for anyone stumbling across this. It was indeed a PHP/OPcache issue and updating the software versions to 5.5.22 and OPCache 7.0.4-dev resolves the segmentation issues.

Please or to participate in this conversation.