Recently, Radarr and Sonarr stopped working, and I don’t know why or where to look.

Host: Kubuntu 22.04

Kernel: 3.2.0-39-generic (64 bits)

Docker: 24.0.5, build 24.0.5-0ubuntu1~22.04.1

Image: linuxserver/sonarr 3.0.10.1567 and linuxserver/radarr 5.2.6.

Every other app, including other servarr app (readarr, lidarr, etc.) is working

Apps is giving me the following message:

[Info] Bootstrap: Starting Sonarr - /app/sonarr/bin/Sonarr.exe - Version 3.0.10.1567 
[Info] AppFolderInfo: Data directory is being overridden to [/config] 
[Info] Router: Application mode: Interactive 
[Info] MigrationLogger: *** Checking database for required migrations data source=/config/sonarr.db;cache size=-10000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 *** 
[Info] MigrationLogger: *** Checking database for required migrations data source=/config/logs.db;cache size=-10000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 *** 
[Info] OwinHostController: Listening on the following URLs: 
[Info] OwinHostController:   http://192.168.1.100:8989/ 
[Info] OwinHostController:   http://localhost:8989/ 
[Info] SonarrBootstrapper: Starting Web Server 
[Fatal] ConsoleApp: The requested address is not valid in this context. This can happen if another instance of Sonarr is already running another application is using the same port (default: 8989) or the user has insufficient permissions 
Press enter to exit...

I checked, and nothing seems to use the same port:

~$ sudo netstat -nlp | grep 8989
tcp        0      0 0.0.0.0:8989            0.0.0.0:*               LISTEN      48005/docker-proxy  
tcp6       0      0 :::8989                 :::*                    LISTEN      48011/docker-proxy  

And I don’t think permission is at fault since other docker apps works fine.

Where should I look to fix that?

Edit: the compose file

version: '3.8'
services:
    Sonarr:
        container_name: sonarr
        image: linuxserver/sonarr
        ports:
        - '8989:8989' # sonarr
        environment:
        - PUID=1000
        - PGID=1000
        - TZ=Canada/Eastern
        volumes:
        - '/etc/timezone:/etc/timezone:ro'
        - '/etc/localtime:/etc/localtime:ro'
        - '/bibliotheque1/configs/sonarr:/config'
        - '/bibliotheque1:/data'
        - '/bibliotheque2:/data2'
        restart: unless-stopped
    radarr:
        container_name: radarr
        image: linuxserver/radarr
        environment:
        - PUID=1000
        - PGID=1000
        - TZ=Canada/Eastern
        ports:
        - '7878:7878'
        volumes:
        - '/etc/timezone:/etc/timezone:ro'
        - '/etc/localtime:/etc/localtime:ro'
        - '/bibliotheque1/configs/radarr:/config'
        - '/bibliotheque1:/data'
        - '/bibliotheque2:/data2'
        restart: unless-stopped

edit2: added all the details of the logs

edit 3:

I don’t think the issue is actually the port since I’ve got the same issue when I’m switching to a different port, and if I stop the container, its ports no longer appears in the netstats commands.

Might be permission issue (but no idea what that would mean in its context) or something else.

Edit 4 and kinda solution

It IS a permission issue, although I’m not getting why it’s happening

If the config file is in another volume, the container starts no problem. But if I try to starts with the old directory, it gave the error message.

    volumes:
        - '/bibliotheque1/configs/radarr_test:/config'

But there is no difference in the owner of this repository

Why can’t the container access it?

drwxr-xr-x   7 $USER $USER 4096 mar 19  2023 heimdall
drwxr-xr-x   6 $USER $USER 4096 déc 26 11:39 radarr
drwxr-xr-x   6 $USER $USER 4096 déc 26 11:43 radarr_test
drwxr-xr-x   6 $USER $USER 4096 déc 26 11:43 sonarr
drwxr-xr-x   6 $USER $USER 4096 déc 26 11:43 sonarr_test
drwxr-xr-x   4 $USER $USER 4096 aoû 28 23:07 plex

I’ll use my backups and use a different directory, but I want to know what went wrong…

  • @BiorixOP
    link
    English
    11 year ago

    I was assuming that it was the container since it’s running. The app itself doesn’t work, but the container starts normally.

    • @bigredgiraffe
      link
      English
      1
      edit-2
      1 year ago

      hmm the last line in the log above there says:

      “[Fatal ConsoleApp: The requested address is not valid in this context. This can happen if another instance of Sonarr is already running another application is using the same port (default: 8989) or the user has insufficient permissions Press enter to exit.“

      So that sounds like that the container might be running but sonarr is not. Did you ever get it working?

      • @BiorixOP
        link
        English
        11 year ago

        Yes Sonarr is not working but I have a container It worked fine for the last month and it just stopped working maybe a week ago