From nobody Wed Sep 27 22:17:50 2023 X-Original-To: ports-bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Rwrb26ZwJz4v4GF for ; Wed, 27 Sep 2023 22:17:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Rwrb25Ynkz4VF0 for ; Wed, 27 Sep 2023 22:17:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1695853070; a=rsa-sha256; cv=none; b=DsylPGfVHmRMFs+dp9vP3kXiitDDzL/TKqP2wxhFyL874R+z3JLPyc7ogqnCeeRSEptDgj vLHA6zNIMTDLUBWNPVN60kjW2I2udl3aXNnH36JG2xDtaPYYyt0a4v03dpD+m54ie1APak H+OoYUIL26vZsvXZJxVt9tdR+HSP+SWmUPJotY/Wqse/xNMzIPKGBdcOvAMLpPknfaG6Ui JZBv1nN/VFoUFPeltmOuX8Y48ueNlNgeZdjwjHPmmOR1U8n/mBX6QV5iU0B7N9n2If5/oK 0nxqI/WTGDxDnI3llx+kdLSX0kW31Jul+mFuhvsiVr2/5S/s6r4pG3FQuDNREQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1695853070; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=lvRiJjDi1sGWh106KbubcHJr//FPmjtrs1wnLx2/Qzw=; b=GJAg5/1Bk69noPThlnA6lAMYCQjFi3af9wngW1UegIdYih/WmjYjHPbr8qz0+KeGQLIMkt cZ0xqxOEjYzNUlhdq66s4yjTDRaXtTVW/yzjCOhMFJg3P4V6XDOFbF5fnM7YtxstQt8CRj zlud4wypqGgdVQS7VGIWEwjzBX2rsDoZBMpmyccbYtBMKfq0bPRvFJVl9gNiYfE+MMJVG2 glhH46nTO/7kK5sYJLqSvKuEbLVvDaJg2U0mMl2C3q1bCOCFZ/b2b/dOiMWCHt1WSazAzc odEO5nGuHXUe6P33ZP1+qxaMu56agMkgtpC1UewTkFnHJ40iBtbEHVaUkaNS1Q== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Rwrb24YX4zwjy for ; Wed, 27 Sep 2023 22:17:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 38RMHoIU070315 for ; Wed, 27 Sep 2023 22:17:50 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 38RMHoxu070314 for ports-bugs@FreeBSD.org; Wed, 27 Sep 2023 22:17:50 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 274135] lang/php81: php-fpm processes fail to fork cleanly and procfs needed Date: Wed, 27 Sep 2023 22:17:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ports@thelanman.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bofh@freebsd.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Ports bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-ports-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports-bugs@freebsd.org X-BeenThere: freebsd-ports-bugs@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D274135 Bug ID: 274135 Summary: lang/php81: php-fpm processes fail to fork cleanly and procfs needed Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: bofh@freebsd.org Reporter: ports@thelanman.net Assignee: bofh@freebsd.org Flags: maintainer-feedback?(bofh@freebsd.org) I opened the below a few weeks back: https://github.com/php/php-src/issues/12157 However, I wanted to open a bug here as well. I maintain a custom poudriere package repo and sometime after April 2023 the PHP port seems to have gone a little wonky. I don't know if this is the fault of poudriere, 13.2, the PHP port, or PHP proper but I'm out of ideas. I've been running PHP5.4x+ and FreeBSD11+ with more or less the same setup for a loooong time. I update the lang/phpXY options and lang/phpXY-extensions options files (trying to keep = them more or less the same) as we roll forward builds and we're now on php81. See the github post for my PHP configs, but we basically run PHP-FPM via lo= cal sockets and each site gets its own "pool" user and talk over sockets with Apache. Older servers will have 1 master "root" process and 100s of PHP-FPM processes spread across 20-50 UIDs depending on server load. 1) PHP FPM processes started looking for /procfs for some reason. I ended up having to add "USE_PROCFS=3Dno" to my poudriere.conf build to get it to not= do that. This is a undocumented (it seems) option that I just happened to run across via GoogleFu. It does fix that problem, but what changed in FreeBSD = 13.2 or the port that it even started to build like that??? I made zero changes outside of updating FreeBSD, poudriere and my ports tree since I built 8.1.x sometime in April and this has never been exhibited in the 5+ years I've be= en doing PHP builds. 2) the bigger issue is that the PHP-FPM master seems to partially fork a process and it gets stuck as a new "master" PHP process and starts consuming 100% CPU. Once I get 5+ or so of these over a few days it starts to impact services and I either re-start PHP-FPM or kill the non-actual "master" processes. The odd thing is the PHP-FPM debug logs show it forking a process for the right user, but it just doesn't "switch" to that user. If I "kill -9 PID" the wonky process then PHP-FPM will immediately start a new process wi= th the right UID/GID no matter the server's actual traffic load or requirements which leads me to believe it's either a bug caused by malicious requests (I can't find anything) or a "race condition" in the fork code. Thoughts? Ideas? --=20 You are receiving this mail because: You are the assignee for the bug.=