-
Notifications
You must be signed in to change notification settings - Fork 675
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
App breaks when php max children reached #3116
Comments
I have the same issue. I'm trying out a default AiO install (with Nextcloud 27) on an old laptop with 4GB RAM and a dual-core processor (Celeron 2955U). After opening some of the sample files with the admin account on two different clients, my Nextcloud also got blocked in a matter of minutes. My
From a quick search, it seems that there are multiple related issues:
It's probably worthwhile to play with the configuration values mentioned there, but I don't know directly where they should be configured in AiO. |
Hi, can you upgrade to v7.0.0 Beta and check if that resolves things? See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel |
Nope, that does not really help - only change, nextcloud not completely shuts down forever, but recovers after 5min. PS: a bit weird to close as completed without waiting if it is actually solved? |
How much ram do you have and which optional addons do you have enabled? |
2GB, 2 CPUS Only imaginary is active |
Hm.. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Steps to reproduce
The issue seems to be, that all the preview generation request start new php processes with own database connections.
This will fast reach the max_children settings.
Guess that is ok, but after this limit is reached, it seems like the connections are never released and thus the database is blocked indefinitely.
Nextcloud is now not accessible anymore and the only way to get it running again is to restart the container.
That seems not acceptable (badly formulated, sorry) - I think it needs to be made sure that it will always recover from errors like this.
Expected behavior
Nextcloud should always recover from errors
Actual behavior
Nextcloud does not recover and needs to be restarted
Host OS
Ubuntu 22.04
Nextcloud AIO version
7.4.0
Current channel
latest
Other valuable info
Nextcloud container log
DB container log:
The text was updated successfully, but these errors were encountered: