-
Notifications
You must be signed in to change notification settings - Fork 493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Symfony application error : readv() failed (104: Connection reset by peer) while reading upstream #522
Comments
Sorry, I can't reproduce that. The FPM config seems not to be causing this issue. Are there any other logs. Usually that error is caused by a SIGSEGV of PHP. |
Thanks for your reply. We tested the same application with an old image we still have in our cache with this configuration and it works perfectly :
The new image and new configuration raises the issue :
|
I'm quite sure the nginx version has nothing to do with it. The FastCGI request lost the connection that happens if PHP-FPM breaks. Which is most of the times a SIGSEGV. Please check the other lines of the log before and after |
We do have a SIGSEGV but no more logs of the cause of this SIGSEGV. (We do not have one with the version webdevops/php-nginx:8.3@sha256:3c215733f28569cbd2da1449788c7bc097112e534ef926425722b593fa0880f9)
By the Way, is it possible to give me a valid sha256 from 2 weeks ago for image Thanks |
Hello, i have the same issue with webdevops/php-nginx-dev:8.3 but not with webdevops/php-nginx:8.3
EDIT: |
I can also verify it, for me it's happening only under Sonata admin controllers, not in some very basic simple Controllers I have for the front-end. And I can also verify that with |
Not sure if these are related, but disabling ioncube resolved the issue for me: #523 |
I'm developing a Symfony application from base image
webdevops/php-nginx-dev:8.3
and everything was going well until the end of last week when i've rebuild my containers.Now we have our app not responding to any request, because of the following issue :
Our local configuration of our env dev did not change recently and i didn't understand why this issue is coming now.
These is our nginx config file the replace the one in the container :
Here is my custom DockerFile :
Thanks for your inputs
The text was updated successfully, but these errors were encountered: