PHP-FPM Signal 13 (SIGPIPE) #15872
Comments
|
When looking at my development server's logs, which is on PHP 8.3.11, is also running into the error. |
speaking of this, what would be those extensions ? ie |
|
[PHP Modules] [Zend Modules] *striking through what has remained the same since a build that does not contain these crashes |
|
Thanks. It might be because of xdebug. Would it be possible to disable it, for a while at least, and sees what happens ? |
|
In production there is no Xdebug, and that's where I found the error originally. The above is from my dev server that is now running 8.3.11. |
|
While I am programming in PHP for decades (since version 3), I still don't know how to debug these kind of crashes. |
|
Thanks for the clarifications. Would debugging/launching fpm with GDB be an option ? I won t have time to look into it only later today, but having a backtrace of the calls would help I think. |
|
How do I do that? Can I do that with my current setup, or do I need to build with certain flags enabled? |
|
Once FPM is launched, you might be able to attach a gdb instance per child worker. ie |
|
I may come up with other ideas in the meantime unless someone else beat me to it :-) |
|
Thanks so far, I am building a new container with |
And I still get: |
|
I see. Did you try adding |
To be honest, I don't get it. There is no reference to a specific library or extension. Why did this suddenly become a problem? |
|
SIGPIPE, strange... that means the file descriptor is closed on the other end... |
|
My guess it is a change in Alpine Linux between 3.18.8 -> 3.18.9 and 3.19.3 -> 3.19.4. I lack the knowledge to know where to look for. |
|
Because of my suspicion I have created an issue in Alpine too. |
|
Running into the same issue here. Would upgrading to alpine 3.20 solve it? |
|
Ideally we get something like a Docker image with some code so we can reproduce it on our systems, so far we don't have enough information to know what's going on. |
I don't know. I imagined it could also be related to a (Docker) host update, in my case Ubuntu 22.04.
That's totally understandable. Until we find out what is causing this, I do think this is the location the issue needs to be reported. |
I understand, for us the error starts popping up after around 15 minutes after a deployment on production. |
|
In case this helps anyone, we have seen this quite a lot yesterday and today I've changed alpine to 3.20 and the warning is no longer showing |
|
@kgogolek That is helpful. Then I am going to apply the 3.20 update too, and see if the error will return, or not. Also, I have reported your findings in the Alpine issue. |
Description
Today I started seeing crashes on one of my PHP-FPM 8.2.23 servers with a SIGPIPE message.
This server was using a fresh (Docker) build that was created 2 days ago. Another PHP 8.2.23 server that was created directly after its release was not seeing the issues.
My guess is that a version of another linked library or extension was upgraded in the meanwhile and that this causes the newer build to crash whereas the older one does not. When I downgraded the crashing server to a 8.2.22 build of one month ago, the errors disappeared.
So I wondered what library or extension might be causing the trouble. The only result I found online on the SIGPIPE error was related to an update in libxml. Maybe I am running into this problem or a similar one too. I will continue investigating and report what I find.
PHP Version
8.2.23 / 8.3.11
Operating System
Alpine 3.18 (8.2.23) / 3.19 (8.3.11)
The text was updated successfully, but these errors were encountered: