-
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
Nextcloud 18.0.2 uses a lot of ressources #300
Comments
Could you try to upgrade to 18.0.3 ? (or maybe testing with 18.0.4 is you wish) |
Thank you @lapineige |
Oh that's correct, sorry, the PR wasn't merged yet. It's almost about to be merged, yet it's maybe safer to first check if the error comes from somewhere else than a 18.0.2 bug. You can't stop an app like that. Yep you can stop php7.3, if nextcloud is the only one to use it. Did you take a look at the logs ? (from Nextcloud admin interface for instance) |
@Thatoo a few question
This PR fix a "regression" that actually overload the CPU when an user connect to Nextcloud. |
How can I know if nextcloud is the only one using php7.3 when I don't even know that it is itself using php7.3? :-) When I go to yunohost's admin > applications > nextcloud > debug, I have logs for php7.0-fpm not php7.3-fpm is not normal? However, in Services, I have a php7.3-fpm service running. You were right, there are a lot of debug coming in the nextcloud logs, mostly this one: |
No, a Core2Duo
No, about 5 I guess that use time to time (mostly syncing)
Yes
Constant, I actually didn't notice it at first. I thought it was coming from Synapse as I was experimenting a lot of disconnection with matrix but that was not making sense as synapse has not been updating for weeks. When I saw the result of glances, and I saw all this 8 nextcloud processus going crazy, it then made sense as I've just updated nextcloud.
1 min | 10.31 |
Indeed, you're quite overloaded... To put a core2duo on its knee, nextcloud should really be overwhelmed ! |
and |
sudo doesn't help. |
Should I stop name_of_user 's Davx5 sync? |
Huh yep sorry I mean the log of nextcloud ;) But, do your 5 users sync their calendars on nextcloud ? |
yes they do and it has never been a problem in the last 2 years... In all the log I checked, it was always the same user mention. Could it come from his android phone? his Davx5? Should I remake the sync from start on his phone? |
Same with this log, USER_1 is the same user all the time and the same I mentioned earlier. It is like something is wrong for him
|
Not sure about how caldav protocol works, but I know that it does connect with the credentials. It's quite easy, you just have to edit EDIT:
|
I have updated Davx5 on the phone of USER_1 and Charge CPU Let's see if it lasts with time, if not, I'll try the fix about argon2, what do you think? |
I think you're free to do as you prefer 😉 I don't know if that fix will solve anything for you. Now you know how do to it, feel free to try it if you want. |
Thank you very much @maniackcrudelis and @lapineige for your help. I'm not sure I would have find out that my issue was coming from an android phone without your guidance on where to look. |
Too bad, so sad, problem isn't solved apparently... |
I really hope this #274 , updating to 18.0.4 will solve my issue. |
I still have pbm with "hashing_default_password"
|
My mistake, I wrote |
I guess it was that and only that because it suddenly drop to a load below 0 and I don't have any new log for more than 10 minutes. Thanks again. |
Nope, sorry for closing/opening but after I remove the "," I didn't get any log or heavy load because nextcloud was down....
right? |
So I decided to do a |
@Thatoo, I updated my previous comment. A fucking fake quote sneaked its way into my comment... |
And sorry to hear that it wasn't actually fixed... |
and no , after true? |
Yep there's a , at the end, like the others line in the file. |
ok. I'll try and let you know. |
Bingo, 24h has passed and no more problem! |
I guess its glances screenshot will summarize better than I would.
Before I update to 18.0.2, nextcloud wasn't taking much ressources, only synapse and the whole server was running below 50% charge of CPU.
Since I updated to 18.0.2 (2 days ago), I experienced a lot of problem reaching synapse or nextcloud services and I discovered why this morning.
The text was updated successfully, but these errors were encountered: