[BUG] latest 1.5.18 won't start, endless restart loop #119

Closed
opened 2025-10-09 16:58:39 -05:00 by giteasync · 10 comments
Owner

Originally created by @ssuess on GitHub.

Before submitting a bug report, I have:

  • Reviewed the documentation.
  • Ensured I am using ghcr.io/flmorg/cleanuperr docker repository.
  • Ensured I am using the latest version.
  • Enabled verbose logging.

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

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.

File name: 'System.Runtime, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

Anything else?

No response

Originally created by @ssuess on GitHub. ### Before submitting a bug report, I have: - [x] Reviewed the documentation. - [x] Ensured I am using ghcr.io/flmorg/cleanuperr docker repository. - [x] Ensured I am using the latest version. - [x] Enabled verbose logging. ### 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 ```shell 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. File name: 'System.Runtime, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' ``` ### Anything else? _No response_
giteasync added the
bug
label 2025-10-09 16:58:39 -05:00
Author
Owner

@ssuess commented on GitHub:

Can you please share your configuration, excluding sensitive information? https://pastebin.com/

https://pastebin.com/icMrjeTr

@ssuess commented on GitHub: > Can you please share your configuration, excluding sensitive information? https://pastebin.com/ https://pastebin.com/icMrjeTr
Author
Owner

@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 :latest of all of these from time to time.

Docker desktop info is this:

Image
@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 `:latest` of all of these from time to time. Docker desktop info is this: <img width="682" alt="Image" src="https://github.com/user-attachments/assets/3210290d-a6aa-4885-9912-1e5cdd33e00c" />
Author
Owner

@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: 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?
Author
Owner

@Flaminel commented on GitHub:

First, thanks for creating cleanuperr I really appreciate the work that went into this.

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: > First, thanks for creating cleanuperr I really appreciate the work that went into this. Thank you! I've just tried it on a MacBook with an ARM64 processor and it seems fine. Is your setup different?
Author
Owner

@Flaminel commented on GitHub:

Can you please share your configuration, excluding sensitive information?
https://pastebin.com/

@Flaminel commented on GitHub: Can you please share your configuration, excluding sensitive information? https://pastebin.com/
Author
Owner

@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:latest
docker image rm ghcr.io/flmorg/cleanuperr:1.5.18

and then re-ran:

docker pull ghcr.io/flmorg/cleanuperr:latest

and then finally:

docker compose up -d

And for whatever reason, it now works! So I guess that download was initially corrupted somehow?

Anyway, thanks for your help!

@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:latest` `docker image rm ghcr.io/flmorg/cleanuperr:1.5.18` and then re-ran: `docker pull ghcr.io/flmorg/cleanuperr:latest` and then finally: `docker compose up -d` And for whatever reason, it now works! So I guess that download was initially corrupted somehow? Anyway, thanks for your help!
Author
Owner

@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: 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...
Author
Owner

@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:

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.

File name: 'System.Runtime, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

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.
@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: ``` 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. File name: 'System.Runtime, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' 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. ```
Author
Owner

@Flaminel commented on GitHub:

I still can't reproduce it on an M4 MacBook, with neither latest nor 1.5.18 tags. I've tried it from both Docker Desktop and the terminal. Any other suggestions on how I could reproduce this?

@Flaminel commented on GitHub: I still can't reproduce it on an M4 MacBook, with neither `latest` nor `1.5.18` tags. I've tried it from both Docker Desktop and the terminal. Any other suggestions on how I could reproduce this?
Author
Owner

@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.

@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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Cleanuparr-Cleanuparr#119
No description provided.