this post was submitted on 24 Dec 2023
25 points (90.3% liked)

Selfhosted

39964 readers
408 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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

all 20 comments
sorted by: hot top controversial new old
[–] [email protected] 11 points 10 months ago (1 children)

Have you tried turning the server off and then on again?

[–] [email protected] 4 points 10 months ago (1 children)

Yes I did

Restarted the container, docker, and the whole server.

Same issue

[–] [email protected] 1 points 10 months ago

I noticed it tries to start listening on 192.168.1.100, don't see a "network: host" in the compose file, don't think it should have access to that IP address.

Not sure how to explore that further but might put you on the right path

[–] [email protected] 8 points 10 months ago (1 children)

Your netstat command shows a process named docker-proxy using that port, which confirms what the log says. If your container isn’t running you can try to find the process using it with netstat or lsof, it might be a stale container process or something but a reboot is often faster than figuring out what it is to see if that clears up whatever is using the port.

[–] [email protected] 1 points 10 months ago (1 children)

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

[–] [email protected] 1 points 10 months ago* (last edited 10 months ago) (1 children)

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?

[–] [email protected] 1 points 10 months 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

[–] [email protected] 3 points 10 months ago* (last edited 10 months ago) (1 children)

Run docker ps and kill all running sonarr/radarr containers.

[–] [email protected] 2 points 10 months ago (1 children)

Good idea, but there is just one container of each

[–] [email protected] 4 points 10 months ago

I wouldn't expect anything else. Kill it and start again. If it still misbehaving, kill it again and check what's listening on problematic ports.

[–] [email protected] 2 points 10 months ago

Check and make sure that Snaps didn’t get installed somehow. Upgraded Ubuntu and it installed snaps, which broke it.

[–] [email protected] 2 points 10 months ago (1 children)

Have you tried mapping it to a different port?

[–] [email protected] 1 points 10 months ago

Good point, I'll try

[–] [email protected] 2 points 10 months ago* (last edited 10 months ago) (1 children)

When you issued the netstat command, were the containers up or down? Issue it again after docker-compose stop If you moved or renamed the compose file, the old conrainers would still run in the old context.

[–] [email protected] 1 points 10 months ago (1 children)

When the container is down, the port is not listed in the netstats

[–] [email protected] 2 points 10 months ago (1 children)

Okay, then it simply has an issue with the addresses you are providing, as someone pointed out already, the issue likely is the 192.168.100 network. Find out where exactly you define localhost and 192.168.100.1 as addresses to listen to and change them to e.g. 0.0.0.0 and 127.0.0.1 instead (or ideally just 0.0.0.0 as this includes localhost as well). Restart the container afterwards, see if it works. Of course make a backup of your config first so you can go back.

[–] [email protected] 1 points 10 months ago

Thank you

The issue was actually that the container somehow didn't have access to its directory anymore. No idea why or how to correct it.

I just created another config directory and use the backup to set everything

So it's working again, but I have no idea how it got stuck

[–] [email protected] 2 points 10 months ago (1 children)

Post your launch command, or compose file

[–] [email protected] 2 points 10 months ago* (last edited 10 months ago)

Ha yes you're right, thanks

I edited the post

fyi nothing changed before it broke