Sonarr container stop working

Hello,

I use the latest version of Sonarr container. Everything was working extremely well for months. I was upgrading without any problem (Watchtower). Until recently, when the container seems to launch but impossible to access the container itself on TCP port 8989.

In the logs I can see this, but it doesn’t tell me anything:

2023-03-01T07:04:55.649940895Z 	Native Crash Reporting
2023-03-01T07:04:55.649952423Z =================================================================
2023-03-01T07:04:55.649986424Z Got a SIGABRT while executing native code. This usually indicates
2023-03-01T07:04:55.650000677Z a fatal error in the mono runtime or one of the native libraries 
2023-03-01T07:04:55.650013090Z used by your application.
2023-03-01T07:04:55.650024945Z =================================================================
2023-03-01T07:04:55.650038104Z 
2023-03-01T07:04:55.650075009Z =================================================================
2023-03-01T07:04:55.650088411Z 	Native stacktrace:
2023-03-01T07:04:55.650099916Z =================================================================
2023-03-01T07:04:55.650113352Z 	0x5650ddf67ffb - mono : 
2023-03-01T07:04:55.650126889Z 	0x5650ddf6838d - mono : 
2023-03-01T07:04:55.650237338Z 	0x5650ddf15087 - mono : 
2023-03-01T07:04:55.650252588Z 	0x5650ddf6757c - mono : 
2023-03-01T07:04:55.650332105Z 	0x7f23e715d520 - /lib/x86_64-linux-gnu/libc.so.6 : 
2023-03-01T07:04:55.650347002Z 	0x7f23e71b1a7c - /lib/x86_64-linux-gnu/libc.so.6 : pthread_kill
2023-03-01T07:04:55.650360468Z 	0x7f23e715d476 - /lib/x86_64-linux-gnu/libc.so.6 : raise
2023-03-01T07:04:55.650458379Z 	0x7f23e71437f3 - /lib/x86_64-linux-gnu/libc.so.6 : abort
2023-03-01T07:04:55.650470279Z 	0x5650dded73c4 - mono : 
2023-03-01T07:04:55.650598088Z 	0x5650de1bc135 - mono : 
2023-03-01T07:04:55.650617391Z 	0x5650de1d95be - mono : 
2023-03-01T07:04:55.650629887Z 	0x5650de1d9c73 - mono : monoeg_assertion_message
2023-03-01T07:04:55.650643663Z 	0x5650de156f08 - mono : 
2023-03-01T07:04:55.650657470Z 	0x5650de0449f6 - mono : 
2023-03-01T07:04:55.650669850Z 	0x5650ddeda047 - mono : 
2023-03-01T07:04:55.650681624Z 	0x5650ddee87b6 - mono : mono_main
2023-03-01T07:04:55.650693730Z 	0x5650dded74df - mono : 
2023-03-01T07:04:55.650705781Z 	0x7f23e7144d90 - /lib/x86_64-linux-gnu/libc.so.6 : 
2023-03-01T07:04:55.650719062Z 	0x7f23e7144e40 - /lib/x86_64-linux-gnu/libc.so.6 : __libc_start_main
2023-03-01T07:04:55.650732722Z 	0x5650dded7b1e - mono : _start
2023-03-01T07:04:55.650744829Z 
2023-03-01T07:04:55.650756438Z =================================================================
2023-03-01T07:04:55.650768121Z 	Telemetry Dumper:
2023-03-01T07:04:55.650781541Z =================================================================
2023-03-01T07:04:55.652553599Z Entering thread summarizer pause from 0x139792177275008x
2023-03-01T07:04:55.652616275Z Finished thread summarizer pause from 0x139792177275008x.
2023-03-01T07:04:55.652631129Z Failed to create breadcrumb file (null)/crash_hash_0x0
2023-03-01T07:04:55.673459668Z 
2023-03-01T07:04:55.673504780Z Waiting for dumping threads to resume
2023-03-01T07:04:56.675255425Z 
2023-03-01T07:04:56.675297886Z =================================================================
2023-03-01T07:04:56.675311523Z 	External Debugger Dump:
2023-03-01T07:04:56.675347723Z =================================================================
2023-03-01T07:04:56.675442733Z mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb
2023-03-01T07:04:56.679196822Z 
2023-03-01T07:04:56.679248143Z =================================================================
2023-03-01T07:04:56.679260686Z 	Basic Fault Address Reporting
2023-03-01T07:04:56.679274032Z =================================================================
2023-03-01T07:04:56.679287351Z Memory around native instruction pointer (0x7f23e71b1a7c):0x7f23e71b1a6c  05 00 44 89 e2 89 ee 89 c7 b8 ea 00 00 00 0f 05  ..D.............
2023-03-01T07:04:56.679324226Z 0x7f23e71b1a7c  41 89 c5 41 f7 dd 3d 00 f0 ff ff b8 00 00 00 00  A..A..=.........
2023-03-01T07:04:56.679336101Z 0x7f23e71b1a8c  44 0f 46 e8 e9 6d ff ff ff 0f 1f 00 48 89 ef e8  D.F..m......H...
2023-03-01T07:04:56.679347716Z 0x7f23e71b1a9c  10 a8 ff ff e9 29 ff ff ff 0f 1f 00 48 89 ef e8  .....)......H...
2023-03-01T07:04:56.679359152Z 
2023-03-01T07:04:56.679371960Z =================================================================
2023-03-01T07:04:56.679407255Z 	Managed Stacktrace:
2023-03-01T07:04:56.679420334Z =================================================================
2023-03-01T07:04:56.679505050Z =================================================================
2023-03-01T07:04:56.718845056Z * Assertion at gc.c:1005, condition `is_ok (error)' not met, function:mono_gc_init_finalizer_thread, Couldn't create thread. Error 0x0 assembly:<unknown assembly> type:<unknown type> member:(null)
2023-03-01T07:04:56.718887875Z 
2023-03-01T07:04:56.718921575Z 
2023-03-01T07:04:56.718935179Z =================================================================
2023-03-01T07:04:56.718948947Z 	Native Crash Reporting
2023-03-01T07:04:56.718962955Z =================================================================
2023-03-01T07:04:56.718975755Z Got a SIGABRT while executing native code. This usually indicates
2023-03-01T07:04:56.719010862Z a fatal error in the mono runtime or one of the native libraries 
2023-03-01T07:04:56.719024127Z used by your application.
2023-03-01T07:04:56.719037081Z =================================================================
2023-03-01T07:04:56.719062748Z 
2023-03-01T07:04:56.719098409Z =================================================================
2023-03-01T07:04:56.719111912Z 	Native stacktrace:
2023-03-01T07:04:56.719124989Z =================================================================
2023-03-01T07:04:56.719138307Z 	0x5612ceb4bffb - mono : 
2023-03-01T07:04:56.719150356Z 	0x5612ceb4c38d - mono : 
2023-03-01T07:04:56.719475631Z 	0x5612ceaf9087 - mono : 
2023-03-01T07:04:56.719491488Z 	0x5612ceb4b57c - mono : 
2023-03-01T07:04:56.719503034Z 	0x7f1277d21520 - /lib/x86_64-linux-gnu/libc.so.6 : 
2023-03-01T07:04:56.719516327Z 	0x7f1277d75a7c - /lib/x86_64-linux-gnu/libc.so.6 : pthread_kill
2023-03-01T07:04:56.719529766Z 	0x7f1277d21476 - /lib/x86_64-linux-gnu/libc.so.6 : raise
2023-03-01T07:04:56.719565115Z 	0x7f1277d077f3 - /lib/x86_64-linux-gnu/libc.so.6 : abort
2023-03-01T07:04:56.719578354Z 	0x5612ceabb3c4 - mono : 
2023-03-01T07:04:56.719590561Z 	0x5612ceda0135 - mono : 
2023-03-01T07:04:56.719603836Z 	0x5612cedbd5be - mono : 
2023-03-01T07:04:56.719618206Z 	0x5612cedbdc73 - mono : monoeg_assertion_message
2023-03-01T07:04:56.719653487Z 	0x5612ced3af08 - mono : 
2023-03-01T07:04:56.719666493Z 	0x5612cec289f6 - mono : 
2023-03-01T07:04:56.719678262Z 	0x5612ceabe047 - mono : 
2023-03-01T07:04:56.719691355Z 	0x5612ceacc7b6 - mono : mono_main
2023-03-01T07:04:56.719705284Z 	0x5612ceabb4df - mono : 
2023-03-01T07:04:56.719741379Z 	0x7f1277d08d90 - /lib/x86_64-linux-gnu/libc.so.6 : 
2023-03-01T07:04:56.719897647Z 	0x7f1277d08e40 - /lib/x86_64-linux-gnu/libc.so.6 : __libc_start_main
2023-03-01T07:04:56.719913112Z 	0x5612ceabbb1e - mono : _start
2023-03-01T07:04:56.719924857Z 
2023-03-01T07:04:56.719964722Z =================================================================
2023-03-01T07:04:56.719978810Z 	Telemetry Dumper:
2023-03-01T07:04:56.719990638Z =================================================================
2023-03-01T07:04:56.721111647Z Entering thread summarizer pause from 0x139717296119936x
2023-03-01T07:04:56.721150012Z Finished thread summarizer pause from 0x139717296119936x.
2023-03-01T07:04:56.721161860Z Failed to create breadcrumb file (null)/crash_hash_0x0
2023-03-01T07:04:56.741395251Z 
2023-03-01T07:04:56.741469710Z Waiting for dumping threads to resume

Any idea?

For your information, I pilot my containers with Portainer.

Thanks

Using portainer compose, I pulled this image. Unfortunately I am not getting anything on the webUI.
I am not sure if these 2 things are linked. Based on my logs I would expect it to be working. Not sure where to go from here. I don’t mean to hijack your post.

[migrations] started
[migrations] no migrations found
-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/
Brought to you by linuxserver.io
-------------------------------------
To support the app dev(s) visit:
Sonarr: https://sonarr.tv/donate
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid:    1000
User gid:    1000
-------------------------------------
[custom-init] No custom files found, skipping...
[Info] Bootstrap: Starting Sonarr - /app/sonarr/bin/Sonarr.exe - Version 3.0.9.1549 
[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://*:7878/ 
[Info] SonarrBootstrapper: Starting Web Server 
[Info] RssSyncService: Starting RSS Sync 
[Warn] FetchAndParseRssService: No available indexers. check your configuration. 
[Info] DownloadDecisionMaker: No results found 
[Info] RssSyncService: RSS Sync Completed. Reports found: 0, Reports grabbed: 0 
[Info] RssSyncService: Starting RSS Sync 
[Warn] FetchAndParseRssService: No available indexers. check your configuration. 
[Info] DownloadDecisionMaker: No results found 
[Info] RssSyncService: RSS Sync Completed. Reports found: 0, Reports grabbed: 0 type or paste code here

I have navigated inside my container and see many .dll files and a sonar.exe file. I specified to pull the arm64 version. Is there a change this could be related to the new image?

Hi @dirtyfnd

Your installation looks very recent and the container seems to start correctly. What does the command look like:

telnet IP_LAN_SONARR TCP_PORT_WEBUI
telnet IP_LAN_SONARR 7878

On my side, my container should answer on TCP port 8989, but even in Telnet I have no answer.

telnet IP_LAN_SONARR 8989 (for me)
telnet 192.168.1.X 8989 (for me)

I’ll be honest, I have never used telnet before. I do everything through SSH or portainer.

t[custom-init] No custom files found, skipping...
[Info] Bootstrap: Starting Sonarr - /app/sonarr/bin/Sonarr.exe - Version 3.0.9.1549 
[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://*:7878/ 
[Info] SonarrBootstrapper: Starting Web Server 
[Info] RssSyncService: Starting RSS Sync 
[Warn] FetchAndParseRssService: No available indexers. check your configuration. 
[Info] DownloadDecisionMaker: No results found 
[Info] RssSyncService: RSS Sync Completed. Reports found: 0, Reports grabbed: 0 
[Info] SceneMappingService: Updating Scene mappings 
ype or paste code here

[Info] Bootstrap: Starting Sonarr - /app/sonarr/bin/Sonarr.exe - Version 3.0.9.1549

I don’t understand why its starting an exe file in a linux environment. Especially when I’ve already forced the use of image: lscr.io/linuxserver/sonarr:arm64v8-latest

When I compare the file system of Sonarr to Radarr (which I have working), I notice there are tons of .json files which there are not with the Sonarr directory.

[migrations] started
[migrations] no migrations found
-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/
Brought to you by linuxserver.io
-------------------------------------
To support the app dev(s) visit:
Radarr: https://opencollective.com/radarr
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid:    1000
User gid:    1000
-------------------------------------
[custom-init] No custom files found, skipping...
[Info] Bootstrap: Starting Radarr - /app/radarr/bin/Radarr - Version 4.3.2.6857 
[Info] AppFolderInfo: Data directory is being overridden to [/config] 
[Debug] Bootstrap: Console selected 
[Info] AppFolderInfo: Data directory is being overridden to [/config] 
[Info] AppFolderInfo: Data directory is being overridden to [/config] 
[Info] MigrationController: *** Migrating data source=/config/radarr.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 *** 
[Info] MigrationController: *** Migrating data source=/config/logs.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 *** 
[Info] UpdaterConfigProvider: External updater uses branch master instead of the currently selected main, changing to master. 
[ls.io-init] done.
[Info] CommandExecutor: Starting 2 threads for tasks. 

Thats the logs of Radarr. There are definitely subtle differences between the two

On my side Radarr works very well as well as Lidarr. I have only a problem with Sonarr.

Personally I am on an x64 architecture. Intel processor.

My Sonarr runs on a LXC Alpine Linux container virtualized with the Proxmox VE hypervisor.

I have not yet had the time to test going back to images of previous versions instead of the “latest” version/tag.

  1. we do not support or recommend deploying containers with portainer due to the number of problems it introduces. Instead, we suggest using docker run or docker compose.
  2. we do not test or support LXC, proxmox, or anything outside of a debian derived linux distribution
  3. sonarr and radarr/lidarr/readarr are completely separate projects, you can’t compare them to each other.
  4. how are you trying to access the web ui? show your stack or some screenshots

Hello @driz ,

I am quite surprised by your first point. For me (without knowledge developed like yours), Portainer was just a Web UI interface allowing to manage more easily its Docker containers without particular incidence on the container itself (without being intrusive).

Here are some screenshots to help understanding :

C:\Users\CanardBannana>ping seedbox

Sending a 'ping' request to seedbox.my.lan [192.168.10.247] with 32 bytes of data:
Response from 192.168.10.247 : bytes=32 time=3 ms TTL=64
Response from 192.168.10.247 : bytes=32 time=3 ms TTL=64
Response from 192.168.10.247 : bytes=32 time=3 ms TTL=64
Reply from 192.168.10.247 : bytes=32 time=4 ms TTL=64

Ping statistics for 192.168.10.247:
    Packets: sent = 4, received = 4, lost = 0 (0% loss),
Approximate loop duration in milliseconds :
    Minimum = 3ms, Maximum = 4ms, Average = 3ms
C:\Users\CanardBannana>telnet seedbox 8989
Connection to seedbox...Unable to open a connection to the host, on port 8989: Failed to connect

In addition, I tried to deploy a new clean Sonarr container and I get the same logs and behavior!

I’ll try to upgrade my Alpine Linux that hosts this container.

Portainer breaks a lot of things unless you’re an expert. It is not for beginners who don’t know the issues or how to work around them. SOMETIMES it works, but we do not support it because of those issues. Copy pasting from a template and changing a couple things is not a challenging thing to do.

You need to read the readme, first of all, and input required settings. The only things you can skip are labeled as optional in our readme.
We do not support using a PUID/PGID of root

Please also review the application setup portion. I suggest you try http://192.168.10.247:8989 to eliminate any local dns issues from the picture, but without your full container logs, i have nothing else to suggest aside from fixing the other issues and recreating the issue using docker run or docker compose.

you are the only one to not provide full container logs which begin with our ascii logo yet. Two others provided them, look to see what a proper example is.

How are you trying to access the web ui?

Hey driz, I appreciate your support. I am attempting to access the webUI through my local ip address. http://192.168.1.10:8989. I apologize for my ignorance in comparing sonarr and radarr, I assumed they had the same framework with minor variations. I did deploy the container with a portainer stack, so I will remove that and complete the process with SSH.

@driz I deployed it as you suggested and it works. Thanks again for your assistance, you rock!

Great to hear, glad you got it sorted. FYI, lidarr/radarr/readarr/prowlarr/whisparr are all the same team, sonarr, while in the family, is a different team and the base is vastly different.

Getting the same issue. Suddenly started a few days ago. Not using portainer, deploying with a docker-compose. Startup logs below:

Docker-compose:

  sonarr:
    image: ghcr.io/linuxserver/sonarr
    container_name: sonarr
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
    volumes:
      - ${CONFIG_DIR}/sonarr:/config
      - ${MEDIA_DIR}/tvshows:/tv
      - ${DOWNLOAD_DIR}:/downloads
    ports:
      - 5003:8989
    restart: always
[/share/config/docker-compose] # docker logs sonarr
[migrations] started
[migrations] no migrations found

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
-------------------------------------

To support the app dev(s) visit:
Sonarr: https://sonarr.tv/donate

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1001
User gid:    100
-------------------------------------

[custom-init] No custom files found, skipping...
* Assertion at gc.c:1005, condition `is_ok (error)' not met, function:mono_gc_init_finalizer_thread, Couldn't create thread. Error 0x0 assembly:<unknown assembly> type:<unknown type> member:(null)


=================================================================
        Native Crash Reporting
=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

=================================================================
        Native stacktrace:
=================================================================
        0x55e5c9e1bffb - mono :
        0x55e5c9e1c38d - mono :
        0x55e5c9dc9087 - mono :
        0x55e5c9e1b57c - mono :
        0x7fb23f913520 - /lib/x86_64-linux-gnu/libc.so.6 :
        0x7fb23f967a7c - /lib/x86_64-linux-gnu/libc.so.6 : pthread_kill
        0x7fb23f913476 - /lib/x86_64-linux-gnu/libc.so.6 : raise
        0x7fb23f8f97f3 - /lib/x86_64-linux-gnu/libc.so.6 : abort
        0x55e5c9d8b3c4 - mono :
        0x55e5ca070135 - mono :
        0x55e5ca08d5be - mono :
        0x55e5ca08dc73 - mono : monoeg_assertion_message
        0x55e5ca00af08 - mono :
        0x55e5c9ef89f6 - mono :
        0x55e5c9d8e047 - mono :
        0x55e5c9d9c7b6 - mono : mono_main
        0x55e5c9d8b4df - mono :
        0x7fb23f8fad90 - /lib/x86_64-linux-gnu/libc.so.6 :
        0x7fb23f8fae40 - /lib/x86_64-linux-gnu/libc.so.6 : __libc_start_main
        0x55e5c9d8bb1e - mono : _start

=================================================================
        Telemetry Dumper:
=================================================================
Entering thread summarizer pause from 0x140403547111552x
Finished thread summarizer pause from 0x140403547111552x.
Failed to create breadcrumb file (null)/crash_hash_0x0

Waiting for dumping threads to resume

=================================================================
        External Debugger Dump:
=================================================================
mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb

=================================================================
        Basic Fault Address Reporting
=================================================================
Memory around native instruction pointer (0x7fb23f967a7c):0x7fb23f967a6c  05 00 44 89 e2 89 ee 89 c7 b8 ea 00 00 00 0f 05  ..D.............
0x7fb23f967a7c  41 89 c5 41 f7 dd 3d 00 f0 ff ff b8 00 00 00 00  A..A..=.........
0x7fb23f967a8c  44 0f 46 e8 e9 6d ff ff ff 0f 1f 00 48 89 ef e8  D.F..m......H...
0x7fb23f967a9c  10 a8 ff ff e9 29 ff ff ff 0f 1f 00 48 89 ef e8  .....)......H...

=================================================================
        Managed Stacktrace:
=================================================================
=================================================================
* Assertion at gc.c:1005, condition `is_ok (error)' not met, function:mono_gc_init_finalizer_thread, Couldn't create thread. Error 0x0 assembly:<unknown assembly> type:<unknown type> member:(null)

Thanks @driz for the information, I was not aware of this subtlety. Thank you very much.

All right, I’ve noted the impact of Portainer @driz .

I appreciate Portainer because it allows me to obtain the desired result and configuration very quickly.

I can understand your lack of support due to elements outside the test and qualification environment of your containers.

Copying and pasting templates and adapting them may not be difficult for some but for others it is not so obvious.

I had already read (a while ago, I confess) the readme details of the Sonarr container (for its initialization). But from the logs visible on my first post, I could not see any direct link with my personal variables.

During my tests, I tried to connect to the Sonarr Web UI in HTTP and HTTPS because I know that browsers are now programmed to work in HTTPS by default. But I should have made this point clear.
You could anyway see that TCP port 8989 was quite unavailable although the container responds well to ICMP requests.

But the most important thing is that I finally had the time to test my (very stupid) but strongest hypothesis: simply upgrade my Alpine Linux hosting my containers, including Sonarr.

After a simple

apk upgrade

and a reboot for fun, my Sonarr container is back to life with its data as before.

Thank you all for your support and your investment in my problem :heart_eyes_cat:

Hi @fstanley,

I just solved my problem by updating the operating system that carries my Docker. Have you tested this simple manipulation on your side?