-
Notifications
You must be signed in to change notification settings - Fork 11
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] checkrr is stuck in running state after SIGSEGV, OoMKiller invocation, or other calls to kill() for checkrr's pid #91
Comments
Checkrr periodically writes to a table in the db file with the "current stats" and that's one of the states that is tracked with that write. There's a stop function that sets running to false and the button is only enabled when running is set to false. If checkrr never writes You can try clearing the state by hitting checkrr's API for run: If you can't for some reason send a post request to that endpoint, if you delete the DB file, recreate it with the touch command again, it should free up checkrr to run again, though it will lose it's hashes of the current files. |
This issue has been open a few months with no reply. I'll close it now, if you are still having issues, just reply and I'll reopen it. |
The post request worked. |
reopening to patch this in bug in 3.4.0. |
Patch will be in 3.4.0.
|
I have installed Checkrr in Docker container on Unraid (via CA). To start with, I have only set up connection with Radarr.
After starting the docker, I hit "run now" in the GUI. It seems to work and it identifies a few bad files and seems to have scanned my whole library. So far, so good!
However, it doesn't seem to stop and doesn't allow me to restart. GUI always says "running" and "run now" is greyed out. Even after restarting the docker, this doesn't change. No info in docker log and log file.
Any thoughts what I can try to troubleshoot?
The text was updated successfully, but these errors were encountered: