Unable to access Sonarr, Radarr, and Lidarr Web UI

Having issues with your DietPi installation or found a bug? Post it here.
wiggley
Posts: 6
Joined: Sat Dec 05, 2020 5:19 pm

Re: Unable to access Sonarr, Radarr, and Lidarr Web UI

Post by wiggley »

Code: Select all

DietPi v7.5.2 : 14:39 - Thu 08/26/2021
 ─────────────────────────────────────────────────────
 - Device model : RPi 4 Model B (aarch64)
 - CPU temp : 55'C : 131'F (Running warm, but safe)
 - LAN IP : 10.0.1.12 (eth0)
 - MOTD : DietPi v7.5 brings further fixes for Debian Bullseye
 ─────────────────────────────────────────────────────

[Info] Bootstrap: Starting Sonarr - /usr/lib/sonarr/bin/Sonarr.exe - Version 3.0.6.1196 
[Info] AppFolderInfo: Data directory is being overridden to [/mnt/dietpi_userdata/sonarr] 
[Info] Router: Application mode: Interactive 
[Info] MigrationLogger: *** Checking database for required migrations data source=/mnt/dietpi_userdata/sonarr/sonarr.db;cache size=-10000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 *** 

=================================================================
	Native Crash Reporting
=================================================================
Got a SIGSEGV 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:
=================================================================
	0x555a184208 - /usr/bin/mono : 
	0x555a184524 - /usr/bin/mono : 
	0x555a159130 - /usr/bin/mono : 
	0x555a11f650 - /usr/bin/mono : 
	0x7fa66d67c0 - linux-vdso.so.1 : __kernel_rt_sigreturn
	0x7fa0bdc5fc - /usr/lib/aarch64-linux-gnu/libsqlite3.so.0 : sqlite3_stmt_readonly
	0x7fa0c16aec - /usr/lib/aarch64-linux-gnu/libsqlite3.so.0 : 
	0x7fa0be5158 - /usr/lib/aarch64-linux-gnu/libsqlite3.so.0 : 
	0x7fa0be51fc - /usr/lib/aarch64-linux-gnu/libsqlite3.so.0 : 
	0x7fa0bf5be4 - /usr/lib/aarch64-linux-gnu/libsqlite3.so.0 : 
	0x7fa0bff234 - /usr/lib/aarch64-linux-gnu/libsqlite3.so.0 : sqlite3_initialize
	0x7fa0ca568c - /usr/lib/aarch64-linux-gnu/libsqlite3.so.0 : 
	0x7fa0897930 - Unknown

=================================================================
	Telemetry Dumper:
=================================================================
Pkilling 0x548176150912x from 0x548252999696x
Pkilling 0x548180353408x from 0x548252999696x
Pkilling 0x548200419712x from 0x548252999696x
Pkilling 0x548178252160x from 0x548252999696x
Entering thread summarizer pause from 0x548252999696x
Finished thread summarizer pause from 0x548252999696x.
Failed to create breadcrumb file (null)/crash_hash_0xc72444bb4
Could not exec mono-hang-watchdog, expected on path '/etc/../bin/mono-hang-watchdog' (errno 2)

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 (0x7fa0bdc5fc):0x7fa0bdc5ec  00 00 80 d2 c0 03 5f d6 1f 20 03 d5 80 00 00 b4  ......_.. ......
0x7fa0bdc5fc  00 18 43 39 00 00 00 12 c0 03 5f d6 20 00 80 52  ..C9......_. ..R
0x7fa0bdc60c  c0 03 5f d6 e1 03 00 aa 00 00 80 52 e1 00 00 b4  .._........R....
0x7fa0bdc61c  23 24 40 b9 62 b4 81 52 42 be a5 72 00 00 80 52  #$@.b..RB..r...R

=================================================================
	Managed Stacktrace:
=================================================================
	  at <unknown> <0xffffffff>
	  at System.Data.SQLite.UnsafeNativeMethods:sqlite3_open_v2 <0x00007>
	  at System.Data.SQLite.SQLite3:Open <0x00187>
	  at System.Data.SQLite.SQLiteConnection:Open <0x0103b>
	  at FluentMigrator.Runner.Processors.GenericProcessorBase:EnsureConnectionIsOpen <0x0006f>
	  at FluentMigrator.Runner.Processors.SQLite.SQLiteProcessor:Exists <0x0002b>
	  at FluentMigrator.Runner.Processors.SQLite.SQLiteProcessor:TableExists <0x0006f>
	  at FluentMigrator.Runner.VersionLoader:get_AlreadyCreatedVersionTable <0x0009b>
	  at FluentMigrator.Runner.VersionLoader:LoadVersionInfo <0x0006f>
	  at FluentMigrator.Runner.VersionLoader:.ctor <0x0057f>
	  at FluentMigrator.Runner.MigrationRunner:.ctor <0x0082b>
	  at FluentMigrator.Runner.MigrationRunner:.ctor <0x0004b>
	  at NzbDrone.Core.Datastore.Migration.Framework.MigrationController:Migrate <0x001db>
	  at NzbDrone.Core.Datastore.DbFactory:CreateMain <0x0007b>
	  at NzbDrone.Core.Datastore.DbFactory:Create <0x000c7>
	  at NzbDrone.Core.Datastore.DbFactory:Create <0x0004f>
	  at NzbDrone.Core.Datastore.DbFactory:RegisterDatabase <0x0005f>
	  at NzbDrone.Host.NzbDroneServiceFactory:Start <0x0015f>
	  at NzbDrone.Host.Router:Route <0x0017b>
	  at NzbDrone.Host.Bootstrap:Start <0x0011b>
	  at NzbDrone.Host.Bootstrap:Start <0x00237>
	  at NzbDrone.Console.ConsoleApp:Main <0x000d3>
	  at <Module>:runtime_invoke_void_object <0x000eb>
=================================================================
Aborted
User avatar
Joulinar
Posts: 5618
Joined: Sat Nov 16, 2019 12:49 am

Re: Unable to access Sonarr, Radarr, and Lidarr Web UI

Post by Joulinar »

@MichaIng
I'm not 100% sure what the issue with mono is
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
User avatar
MichaIng
Site Admin
Posts: 3214
Joined: Sat Nov 18, 2017 6:21 pm

Re: Unable to access Sonarr, Radarr, and Lidarr Web UI

Post by MichaIng »

Which Debian version is it?

Code: Select all

echo $G_DISTRO_NAME $G_RASPBIAN
Radarr and Lidarr work now, right?

I just tested it on a Bullseye VM where it works fine. Will run another test on aarch64.
EDIT: Works well on aarch64 here, too.

In the meantime, what is the issue with Nginx?

Code: Select all

journalctl -u nginx
cat /var/log/nginx/error.log
Post Reply