Bug #67141 [Asn]: PHP FPM vhost pollution

From: Date: Sun, 17 Sep 2023 15:50:59 +0000
Subject: Bug #67141 [Asn]: PHP FPM vhost pollution
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-245391@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=67141&edit=1 ID: 67141 Updated by: bukka@php.net Reported by: power2all at gmail dot com Summary: PHP FPM vhost pollution Status: Assigned Type: Bug Package: FPM related Operating System: ubuntu 14.04 PHP Version: 5.5.11 Assigned To: bukka Block user comment: N Private report: N New Comment: I have had a look on this and think this is primarily because the opache shared memory is also shared between pools - I think the optimal solution would be to introduce a pool manager as suggested in https://github.com/php/php-src/issues/11723 . Then we could make sure that things work as they should. In terms of tagging, it would have to somehow get that info from the pool or do it per child but that would not be really effective. Passing pool info would require some extra info / API. There are however other issues (specially when different pool users / groups are configured) so it would be better to separate it completely so might not be worth to spend time on that. Previous Comments: ------------------------------------------------------------------------ [2020-02-13 11:20:57] mustang at miswave dot com From 5.6.29, 7.0.14, and 7.1.0 looks like this can now be solved with: opcache.validate_root=1 ------------------------------------------------------------------------ [2017-10-20 14:39:08] nicolas dot girardet at gmail dot com Same issue with the following configuration: PHP Version: 7.1.10 OS: Debian 4.9.30 Apache: 2.4.24 ------------------------------------------------------------------------ [2016-09-08 10:41:51] mustang at gmail dot com Just hit this nasty. "opcache.revalidate_freq=0" does seem to be working for now (only tested briefly), although it's not really a very good solution. I saw mention in #72521 that a cache prefix would probably work, how could I set this up? Or does such a feature not exist yet. Would be nice if this could be looked into as per user pools are basically useless at the moment. ------------------------------------------------------------------------ [2016-06-30 09:09:56] requinix@php.net Related To: Bug #68965 ------------------------------------------------------------------------ [2016-06-30 09:08:08] requinix@php.net Related To: Bug #72521 ------------------------------------------------------------------------ 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=67141 -- Edit this bug report at https://bugs.php.net/bug.php?id=67141&edit=1

« previous php.bugs (#245391) next »