Skip to content
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

Closed
steve1977 opened this issue Feb 10, 2024 · 5 comments
Labels
bug Something isn't working
Milestone

Comments

@steve1977
Copy link

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?

@steve1977 steve1977 added the bug Something isn't working label Feb 10, 2024
@aetaric
Copy link
Owner

aetaric commented Feb 10, 2024

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 running: false to that table, the button will not re-enable. (this could occur if checkrr is killed by OOMKiller or SIGKILL before it can write that state)

You can try clearing the state by hitting checkrr's API for run: curl -X POST http://address.to.checkrr.web:port/api/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.

@aetaric aetaric added invalid This doesn't seem right support A user needs help, but it doesn't look like a bug and removed bug Something isn't working labels Apr 12, 2024
@aetaric
Copy link
Owner

aetaric commented Apr 12, 2024

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.

@aetaric aetaric closed this as completed Apr 12, 2024
@anthony0030
Copy link

The post request worked.
You can send it via the UNRAID terminal if you are on a device like a phone with no easy post

@aetaric
Copy link
Owner

aetaric commented Oct 8, 2024

reopening to patch this in bug in 3.4.0.

@aetaric aetaric reopened this Oct 8, 2024
@aetaric aetaric changed the title Runs forever [BUG] checkrr is stuck in running state after SIGSEGV, OoMKiller invocation, or other calls to kill() for checkrr's pid Oct 8, 2024
@aetaric aetaric added bug Something isn't working and removed invalid This doesn't seem right support A user needs help, but it doesn't look like a bug labels Oct 8, 2024
@aetaric aetaric added this to the 3.4.0 milestone Oct 8, 2024
@aetaric
Copy link
Owner

aetaric commented Oct 8, 2024

Patch will be in 3.4.0.

[1]  + 48670 killed     ./checkrr -c test-noarr.yaml                                                                                                  
➜  checkrr git:(main) ✗ ./checkrr -c test-noarr.yaml

            _|                               _|
   _|_|_|   _|_|_|       _|_|       _|_|_|   _|  _|     _|  _|_|   _|  _|_|
 _|         _|    _|   _|_|_|_|   _|         _|_|       _|_|       _|_|
 _|         _|    _|   _|         _|         _|  _|     _|         _|
   _|_|_|   _|    _|     _|_|_|     _|_|_|   _|    _|   _|         _|
Checkrr version development
 Commit: 
 Built On: 
 Built By: 
INFO[0000] Using config file: test-noarr.yaml           
WARN[0000] Cleaing up previous crash or improper termination of checkrr.  startup=true
[GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.

[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.

@aetaric aetaric closed this as completed in 58827e0 Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants