My WordPress used a period of time, developed a theme, after installing a number of plug-ins, the performance of the site declined, so it is intended to open the Opcache, but after the opening, the site is completely unresponsive (after the request immediately empty response), The Apache server also does not log any error logs.
Server Software versions: CentOS, php5.4, wordpress4.5, apache2.2
Web Server Runtime Environment: Apache runs PHP using the modfcgi module
Tried method:
在没有完全重装wp的情况下,停用或删除所有插件,使用wp自带的主题,删除整个数据库,重新安装wp数据库,更新wp到最新版本。都无效果。完全重装(即是重新下载安装包安装)后,就没问题。所以这也可以得出此问题跟操作系统和apache应该是无关的。
The following are the responses to Chrome's access to the problematic WP:
The configuration of the Opcache in PHP.ini is as follows (the entire INI file was intended to be sent out, but the length of the article allowed):
zend_extension="/usr/local/php/lib/php/extensions/no-debug-non-zts-20100525/opcache.so";opcache.blacklist_filename="/etc/php/opcache/blacklists"opcache.memory_consumption=256opcache.interned_strings_buffer=16
Reply content:
My WordPress used a period of time, developed a theme, after installing a number of plug-ins, the performance of the site declined, so it is intended to open the Opcache, but after the opening, the site is completely unresponsive (after the request immediately empty response), The Apache server also does not log any error logs.
Server Software versions: CentOS, php5.4, wordpress4.5, apache2.2
Web Server Runtime Environment: Apache runs PHP using the modfcgi module
Tried method:
在没有完全重装wp的情况下,停用或删除所有插件,使用wp自带的主题,删除整个数据库,重新安装wp数据库,更新wp到最新版本。都无效果。完全重装(即是重新下载安装包安装)后,就没问题。所以这也可以得出此问题跟操作系统和apache应该是无关的。
The following are the responses to Chrome's access to the problematic WP:
The configuration of the Opcache in PHP.ini is as follows (the entire INI file was intended to be sent out, but the length of the article allowed):
zend_extension="/usr/local/php/lib/php/extensions/no-debug-non-zts-20100525/opcache.so";opcache.blacklist_filename="/etc/php/opcache/blacklists"opcache.memory_consumption=256opcache.interned_strings_buffer=16
Have found the cause of the problem, not WP's pot, but because php.ini in the Zend Guard and ioncube This two PHP code encryption extension reasons.