mirror of
https://github.com/Cleanuparr/Cleanuparr.git
synced 2026-02-04 12:21:33 -06:00
[BUG] latest 1.5.18 won't start, endless restart loop #119
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ssuess on GitHub.
Before submitting a bug report, I have:
What is the behavior?
First, thanks for creating cleanuperr I really appreciate the work that went into this.
My current issue is that I just see this in an endless loop in the docker container logs:
Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.This did not happen with any previous version. I am running 1.5.17 with no issues.
Which operating system do you use?
MacOS
What type of deployment do you use?
Docker container
Relevant log output
Anything else?
No response
@ssuess commented on GitHub:
https://pastebin.com/icMrjeTr
@ssuess commented on GitHub:
Not that I can think of: M1 mac mini with 16GB of RAM, running qbittorrent-vpn, sonarr, radarr, jackett, and cleanuperr in docker. I update from the command line getting
:latestof all of these from time to time.Docker desktop info is this:
@Flaminel commented on GitHub:
I'm only publishing 2 types of containers: one for AMD64 processors and one for ARM64 processors, and they both seem to work on my end. Is there anything particular about your setup?
@Flaminel commented on GitHub:
Thank you!
I've just tried it on a MacBook with an ARM64 processor and it seems fine. Is your setup different?
@Flaminel commented on GitHub:
Can you please share your configuration, excluding sensitive information?
https://pastebin.com/
@ssuess commented on GitHub:
I just fixed it! I ran these two commands to make sure the local image was deleted:
docker image rm ghcr.io/flmorg/cleanuperr:latestdocker image rm ghcr.io/flmorg/cleanuperr:1.5.18and then re-ran:
docker pull ghcr.io/flmorg/cleanuperr:latestand then finally:
docker compose up -dAnd for whatever reason, it now works! So I guess that download was initially corrupted somehow?
Anyway, thanks for your help!
@ssuess commented on GitHub:
Thanks so much for looking into this I appreciate it. I have no idea what is different between 1.5.17 and 1.5.18, but I have upgraded and downgraded several times, and re-pulled all images but still have this issue. I don't know what else to check. I guess I should comb through the source code line by line and try to see what is different that could be related...
@ssuess commented on GitHub:
I just tried to upgrade again, and same issue, cleanuperr keeps trying to restart in an endless loop, displaying only this in the logs over and over:
@Flaminel commented on GitHub:
I still can't reproduce it on an M4 MacBook, with neither
latestnor1.5.18tags. I've tried it from both Docker Desktop and the terminal. Any other suggestions on how I could reproduce this?@Flaminel commented on GitHub:
Great job! It's very weird though. While that error you had can be a valid one, I can't think of any reasons for it to appear. As far as I remember, v1.5.18 was built only once, so it doesn't really make sense for your first version to crash.