Two Servarr (Radar and Sonar) stopped working for unknown reasons
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:
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.
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.
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.