-
Notifications
You must be signed in to change notification settings - Fork 67
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
upstream timed out (110: Connection timed out) while reading response header from upstream #605
Comments
I updated to last version (released after this issue), now I saw that php fpm is upgraded to 8.2, but I have the same error. |
Not sure #615 will fix the issue but you can test with
|
I've also faced timeout that I fixed with a higher memory footprint (100mb) in php-fpm configuration (control panel in the webadmin). |
In my /etc/php/8.2/fpm/pool.d/nextcloud.conf i have: The problem is still here. |
Could be a problem with a bug in nextcloud that was maintaining process in worker, so at the end process limit was reched for each worker, and it doesn't respond anymore. I had this issue in the past, and it seems i recently get something similar. This kind of issue is difficult cause it crash not so often (each 1 or 2 weeks...). Last year i have used a work around to define a process timeout in php config, don't remember the exact change i made. |
Describe the bug
After some time while service running fine, it stopped working, some timeout errors are inside nginx logs.
If you restart the php8.1-fpm.service it works again, but after some other time it freezes again.
Context
Steps to reproduce
Start the service and wait until it freeze.
Expected behavior
Nextcloud running without problems.
Logs
2023/10/07 08:45:44 [error] 742812#742812: *11722 upstream timed out (110: Connection timed out) while reading response header from upstream, client: x.x.x.x, server: yyyy.zzz, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/var/run/php/php8.1-fpm-nextcloud.sock", host: "yyyy.zzz"
The text was updated successfully, but these errors were encountered: