Closed JahFyahh closed 1 year ago
Try running the upstream image and see if it works or if you have the same issue... (linuxserver sonarr develop tag)
I installed sonarr using de dev tag from lscr.io and that is running as it should. No errors
If that's the case, you should retry this from a fresh install. Empty config folder. Because this is essentially the same. Maybe you just got unlucky and had something go wrong at that time...
Does that mean I will lose all my configs/lists etc...? That would really set me back... is there a way to do this without losing all my settings?
Edit: For the sake of testing i renamed my sonarr config folder and recreated the container, but im still getting the same message. I also ran the linuxserver develop again on a different server (not rpi) and here i am getting the same error, with a clean config. Does this mean I need to make an issue at linuxserver?
Probably, if it happens in the source image also, it's a problem upstream. However, I'm having no issues personally. So it may something unique to your setup.
Strange. Im running it on a Proxmox VM running debian 11, VM has 6GB memory and a single CPU. All the other containers are running, im also using Radarr from your docker and sab and readarr from linuxserver.io. anything i could be looking at? The only thing i can think of is that my server crashed a couple days ago due to diskspace, but after cleaning up everything including sonarr started and worked as it should. Any ideas?
It does have something to do with my server, i ran it on another vm and no issues there. Thank you for taking the time.
Quick update: apparently the image was corrupted and somehow also gave issues for the image from linuxserver.io. After removing all unused images/volumes and rebuilding the container it worked again with my settings.
Im running this image on a proxmox vm with others like Radarr and Sab, and since this week i noticed that sonar is unreachable. When looking at the logs i keep getting the errors stated below. A restart and rebuild of the container dit not resolve this, and im not sure how to continue. All other containers are running as they should