-
Notifications
You must be signed in to change notification settings - Fork 27
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
SetupCheck is taking too long / Detect and log slow running setup checks #1170
Comments
Should also build a check into the server code, that it logs an warning (> 5/10 seconds) or error (> 60 seconds) when a setupcheck is taking too long |
@nickvergessen Note that there is already a log line for this purpose: |
I can't really enable debug on production :D |
You can on a single occ run with env var |
yeah, anyway error logging very long running setupchecks sounds still good :) |
#1179 should speed things up a bunch |
Hi, Is this issue fixed? When going to the admin -> overview I get Thanks for looking into this! |
This issue was fixed for logreader with PR #1178 |
I updated to 29.0.8 and it is solved! |
@Mat-DB It's alright. The issue is still sitting open so it's understandable. :) Seems we could close this with #1178 and #1179 being in place. I think this is still open to remind us about the idea to add automated detection and non-debug level logging of overly slow running setup checks here: to be kind of like we already do here, as @nickvergessen mentioned: |
On our instance the setup check did almost not finish.
I added
var_dump(time() . $setupCheck->getService());
in the SetupCheckManager to find out it's actually the log reader taking all the time.Our nextcloud.log.1 and nextcloud.log files are ~101MB both and the SetupCheck takes almost 20 minutes:
1.159 seconds = 19 minutes and 19 seconds...
This is not really acceptable.
I think we should skip the setupcheck when the file is bigger then 5 MB or something (home server level size), or we need to change it to simply
grep | wc -l
, but looping over the file in PHP and json decoding each line does not scale.The text was updated successfully, but these errors were encountered: