Closed rauschgiftengel closed 1 year ago
We offer our own docker container first of all: mrcas/mind:latest
.
Secondly, with this amount of information, I won't be able to fix it. Is it constant? Or only at startup? Can you use the web-ui while this happens? Does it have this kind of usage when there are no reminders in your library?
Hey Casvt,
sorry for the lack of information: with your input i´ve tested again - with the provided docker container everything is working fine, no more high cpu load.
To answer your questions (for the self builded version): The high load was constantly, no matter if theres a job or not. web-ui was useable all the time.
But i´ll use the provided container from now on ;)
Sorry to re-open this one, but I'm in a scenario where as soon as it has to send a notification it goes 100% CPU usage and never goes back to 0.
Situation:
mrcas/mind:latest
Additional information:
On top of that, I am only receiving one notification out of the 3 I set up.
I don't know what else to add to this issue since docker logs -f mind
does not really have a lot to show.
Portainer screenshot of activity:
I've released a new version of MIND, V1.2.1, which fixes a bug with repeated reminders. Maybe, the bug that has now been fixed has been causing this high cpu load? Please pull the new docker image (mrcas/mind:latest
) and check if the problem still persists.
You say that the load starts when the notification gets sent. So there is some sort of bug in the code for sending the notification.
The docker logs don't show anything because proper logging hasn't been added yet (I should).
The new version fixed it! Thank you 😁 I have retried all my scenarii and they are successful this time, I have my 3 notifications apart and no more 100% high-load CPU.
Thank you for the explanation and for the quick fix. Ticket can officially be closed now 👍
Description of the bug Have a high CPU load on my docker host. See screenshot. Running via latest docker on latest Ubunto. Self compiled via cloning your repo.
To Reproduce
Run the container - high load. Stop the container - load gone
Expected behaviour no high load ;)
Screenshots
Version info
Additional context