Bug #67141 [Com]: PHP FPM vhost pollution
Edit report at https://bugs.php.net/bug.php?id=67141&edit=1
ID: 67141
Comment by: public+php dot net at bastelstu dot be
Reported by: power2all at gmail dot com
Summary: PHP FPM vhost pollution
Status: Open
Type: Bug
Package: FPM related
Operating System: ubuntu 14.04
PHP Version: 5.5.11
Block user comment: N
Private report: N
New Comment:
Did you try setting 'opcache.revalidate_freq=0'? Forcing opcache to revalidate the file on
every request circumvented the issue for me.
But I agree that this should be fixed in opcache (e.g. by including the inode or the fpm pool name)
Previous Comments:
------------------------------------------------------------------------
[2014-04-28 10:45:59] power2all at gmail dot com
Description:
------------
PHP Version: 5.5.9-1ubuntu4 (Ubuntu 14.04 apt version)
Description:
When using 1 master process and multiple pool processes, when using chroot and prefix options, the
pools individually will pollute each other.
A website with phpBB3 will eventually read out a website with wordpress in between.
A possible inter-exchange of variables might occure, or something similar.
For example:
PHP message: PHP Fatal error: require_once(): Failed opening required
'/public_html/wp-includes/pomo/mo.php'
(include_path='.:/usr/share/php:/usr/share/pear') in /public_html/wp-includes/load.php on
line 731" while reading response header from upstream, client: 80.82.71.7, server: anirena.com,
request: "GET / HTTP/1.0", upstream: "fastcgi://127.0.0.1:5002", host:
"www.anirena.com"
This site runs phpBB3 and not Wordpress.
When you refresh the website, sometimes it loads fine, and sometimes it doesn't.
Even with all modules disabled, it does this problem.
Here my configurations:
http://p.ngx.cc/84c66229a899aae5
I made some changes as to apply this:
prefix = /home/anirena
chroot = $prefix
chdir = /
The fastcgi_params file has a small modification to allow it to load properly chrooted content.
Site does load, but with multiple pools, it gets polluted.
Expected result:
----------------
Only work-around right now, is having multiple master processes with 1 pool linked to it.
This ain't a good fix, but it works for now, until the pool pollution issue is found and fixed,
or if I made a configuration error.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=67141&edit=1
Thread (6 messages)