Edit report at https://bugs.php.net/bug.php?id=66460&edit=1
ID: 66460
Comment by: spam2 at rhsoft dot net
Reported by: spam2 at rhsoft dot net
Summary: PHP 5.5.7 and 5.5.8 horrible unstable
Status: Open
Type: Bug
Package: opcache
Operating System: Linux
PHP Version: 5.5.8
Block user comment: N
Private report: N
New Comment:
take tar "ext/opcache" from 5.5.6 tarball, unpack the 5.5.8 tarball, replace the folder
with the older opcache, make a tarball and feed rpmbuild, after that you are done, have a stable
webserver without known security issues or degraded performance
[root@asterisk:~]$ rpm -q --changelog php
* Sa Jan 11 2014
- replace "ext/opcache" in 5.5.8 tarball with sources from 5.5.6
because PHP 5.5.7/5.5.8 are completly unstable with opcache
* Fr Jan 10 2014
- update to 5.5.8
Previous Comments:
------------------------------------------------------------------------
[2014-01-11 13:33:04] spam2 at rhsoft dot net
confirmed
changes in "opcache.enable_file_override" and "opcache.revalidate_path" change
things only unpredictable and far away from get the server stable
opcache.enable=0 for sure disables the bytecode-cache and the segfaults of httpd-workers are going
away - so opcache *is broken* and the changelog of 5.5.7 and 5.5.8 are shoing *both* changes in
opcache, 5.5.8 is even more broken then 5.5.7 because with 5.5.7 on my workstation it was mostly
useable, with 5.5.8 and opcache no way
why you would downgrade to 5.5.5 is unclear for me
5.5.6 is clean and stable with opcache
5.5.7 is the first broken release
------------------------------------------------------------------------
[2014-01-11 12:17:30] spam008 at evil dot net dot pl
Setting opcache.revalidate_path = 1 didn`t help. I will try 5.5.8 without loading opcache. Just to
be 100% sure it is opcache issue.
------------------------------------------------------------------------
[2014-01-11 12:17:29] spam008 at evil dot net dot pl
Setting opcache.revalidate_path = 1 didn`t help. I will try 5.5.8 without loading opcache. Just to
be 100% sure it is opcache issue.
------------------------------------------------------------------------
[2014-01-10 19:21:34] spam2 at rhsoft dot net
crap - on the machine in front of me it makes no
differnce how i configure opcache, it crashed right after restart
and never generated a single page of our self-developed cms, after
restart httpd and open phpMyAdmin i wondered that this did not
crash and after that for now it appears that my cms-page also runs
stable
this is completly unpredictable and i doubt that the other reporter
which confirmed this behavior and me are the only persons facing this
whatever changes are done to "opcache" they are broken
[zend]
zend_extension = "/usr/lib64/php/modules/opcache.so"
opcache.enable = 1
opcache.enable_cli = 0
opcache.load_comments = 0
opcache.save_comments = 0
opcache.use_cwd = 1
opcache.validate_timestamps = 1
opcache.revalidate_freq = 5
opcache.revalidate_path = 1
opcache.max_accelerated_files = 1000
opcache.memory_consumption = 128
opcache.interned_strings_buffer = 8
opcache.max_file_size = 262144
opcache.enable_file_override = 0
opcache.fast_shutdown = 1
opcache.error_log = "/var/log/php_error.log"
opcache.log_verbosity_level = 1
------------------------------------------------------------------------
[2014-01-10 19:05:26] spam008 at evil dot net dot pl
I have EXEACLY same observation. It only happens on three vhosts running Typo3 (multiple versions).
It happens on both of my WWW servers. Im going back to 5.5.5 right now. Im using
opcache too.
PHP-FPM self compiled on Slackware64 14.1.
One of my opcache`s config:
zend_extension = "opcache.so"
opcache.memory_consumption = 256
opcache.interned_strings_buffer = 8
opcache.max_accelerated_files = 10000
opcache.revalidate_freq = 0
opcache.validate_timestamps = On
opcache.fast_shutdown = Off
opcache.enable = On
opcache.enable_cli = Off
opcache.max_file_size = 0
opcache.use_cwd = On
opcache.log_verbosity_level = 2
opcache.load_comments = On
opcache.save_comments = On
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=66460--
Edit this bug report at https://bugs.php.net/bug.php?id=66460&edit=1