-
Notifications
You must be signed in to change notification settings - Fork 117
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
[Bug]: Nextcloud Server gets unusably slow if external services like Collabora Server are not reachable #3347
Comments
I remember a similar report at help.nextcloud.com a while ago. Back then, I could trace it down to richdocuments/lib/AppInfo/Application.php Lines 98 to 101 in 64045b5
richdocuments/lib/Service/CapabilitiesService.php Lines 160 to 190 in 64045b5
The app is already using the capabilities service in the app boostrapping. By default, we have a timeout of 45 seconds for the collabora capabilties endpoint. If we cannot fetch the capabilities, we keep the current state only for 60 seconds instead of one hour. All together, that's not ideal. What could help, here in server, is to extend TemplateManager.getTypes to handle a null value from the registerTemplateFileCreator callback. Therefore, we could move the "expensive" capabilties query to the actual moment when we need to register the template file creator. Sorry, I had in mind to send a pull request or write a proper bug ticket for the office team but forgot it. |
Are you using the built-in code server? I'm wondering if running that might be something that is blocked by the hosting provider. Or are you using an external collabora server. |
Ah sorry just noticed that you use an external collabora server. Can you check the log if there is any error trace mentioning the request to the COllabora server? Would be curious where that is triggered then, as far as I remember we should only perform those queries for the built-in server on page load (which is also something that should be fixed) |
|
If there is no more elegant way to solve this problem, the bare minimum should be to (temporarily) auto disable the document server to at least be able to login and use the rest of nextcloud again. |
Bug description
Nextcloud Server gets unusably slow if external services like Collabora Server are not reachable. I am not 100% if this belongs here on in the Collabora issues, but i guess NC itself should have measures to function when external services and plugins are not reachable.
This causes the the hosted Nextcloud to be basically unreachable. Just loading the Homepage takes 2-3 minutes. Loading any other page again takes 2-3 minutes.
Steps to reproduce
Expected behavior
I guess there should be a resonable timeout handling in NC when it comes to externally connected services, no matter if connected through plugins or from NC itself. Unreachable external services should not slow NC to a halt.
Installation method
Community Web installer on a VPS or web space
Nextcloud Server version
27
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.0
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: