Date: Mon, 12 Aug 2024 14:07:11 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 280775] lang/php81 lots of SIGPIPE warnings in php-fpm.log Message-ID: <bug-280775-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280775 Bug ID: 280775 Summary: lang/php81 lots of SIGPIPE warnings in php-fpm.log Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: bofh@freebsd.org Reporter: freebsdbugs@filis.org Assignee: bofh@freebsd.org Flags: maintainer-feedback?(bofh@freebsd.org) After upgrading to the latest version of the port, we're seeing a lot of SIGPIPE warnings in the php-fpm.log: [12-Aug-2024 15:56:27] WARNING: [pool www] child 13282 exited on signal 13 (SIGPIPE) after 5.575445 seconds from start [12-Aug-2024 15:56:27] NOTICE: [pool www] child 13325 started [12-Aug-2024 15:56:33] WARNING: [pool www] child 13325 exited on signal 13 (SIGPIPE) after 5.099562 seconds from start [12-Aug-2024 15:56:33] NOTICE: [pool www] child 13328 started [12-Aug-2024 15:57:08] WARNING: [pool www] child 11939 exited on signal 13 (SIGPIPE) after 216.912813 seconds from start [12-Aug-2024 15:57:08] NOTICE: [pool www] child 13674 started even on systems that aren't crazy busy, this happens. We don't see user-fac= ing errors in the logs, though. Sometimes nginx logs a 499 error, probably duri= ng the child restart. Any clues on where that could come from? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280775-7788>