Radarr: update is failing (version `GLIBC_2.27' not found)

[woutercoppens]

Is this a new Bug?

• I checked that the bug hasn't been reported before

Package Name

Radarr

Package Version

5.14.0.9383

Device Model

Synology DS414

Device Architecture

ARMv7

Firmware Version

7.1.1-42962 Update 5

What happened?

Launching the update from within Radarr is failing

Reproduction steps

1. Launch update from within Radarr

Install Log

2024-11-07 09:40:50.6|Info|InstallUpdateService|Downloading update 5.14.0.9383
2024-11-07 09:41:02.7|Info|InstallUpdateService|Verifying update package
2024-11-07 09:41:04.3|Info|InstallUpdateService|Update package verified successfully
2024-11-07 09:41:04.3|Info|InstallUpdateService|Extracting Update package
2024-11-07 09:41:37.5|Info|InstallUpdateService|Update package extracted successfully
2024-11-07 09:41:37.6|Info|BackupService|Starting Backup
2024-11-07 09:41:43.1|Info|InstallUpdateService|Preparing client
2024-11-07 09:41:48.4|Info|InstallUpdateService|Starting update client /volume1/@apptemp/radarr/radarr_update/Radarr.Update
2024-11-07 09:41:48.4|Info|InstallUpdateService|Radarr will restart shortly.
2024-11-07 09:41:48.9|Error|Radarr.Update|Failed to load /volume1/@apptemp/radarr/radarr_update/libcoreclr.so, error: /lib/libm.so.6: version `GLIBC_2.27' not found (required by /volume1/@apptemp/radarr/radarr_update/libcoreclr.so)

Service Log

No response

Other Logs

No response

[mreid-tt]

Hey @woutercoppens, it looks like there might be a compatibility issue with DSM 7.1.1, but I’m unable to reproduce it on my DS916+ running DSM 7.1.1-42962 Update 6.

For example, on my system, I seem to have an older library file, but it doesn’t appear to cause any issues.

$ ls -al /lib/libm.so.6
lrwxrwxrwx 1 root root 12 May 31 16:42 /lib/libm.so.6 -> libm-2.26.so

$ ls -al /lib/libm-2.26.so
-r-xr-xr-x 1 root root 1346296 Jun 22  2022 /lib/libm-2.26.so

Could you confirm if this is a fresh installation or an upgrade? If it’s an upgrade, do you remember the previous Radarr version that was working?

[mreid-tt]

As an update I've even installed Radarr from a fresh install on DSM 6.2.4-25556 Update 7. The built-in update on install runs perfectly:

[Info] InstallUpdateService: Installing post-install update from 5.1.3.8246 to 5.14.0.9383 
[Info] InstallUpdateService: Downloading update 5.14.0.9383 
[Info] InstallUpdateService: Verifying update package 
[Info] InstallUpdateService: Update package verified successfully 
[Info] InstallUpdateService: Extracting Update package 
[Info] InstallUpdateService: Update package extracted successfully 
[Info] BackupService: Starting Backup 
[Info] InstallUpdateService: Preparing client 
[Info] InstallUpdateService: Starting update client /volume1/@appstore/radarr/tmp/radarr_update/Radarr.Update 
[Info] InstallUpdateService: Radarr will restart shortly. 
radarr is not running
Starting radarr ...
tail: /var/packages/radarr/var/radarr.log: file truncated
Thu Nov  7 09:10:58 -04 2024
Starting radarr command env HOME=/volume1/@appstore/radarr/var LD_LIBRARY_PATH=/volume1/@appstore/radarr/lib /volume1/@appstore/radarr/share/Radarr/bin/Radarr -nobrowser -data=/volume1/@appstore/radarr/var/.config/Radarr
[Info] Bootstrap: Starting Radarr - /volume1/@appstore/radarr/share/Radarr/bin/Radarr - Version 5.14.0.9383 
[Info] AppFolderInfo: Data directory is being overridden to [/volume1/@appstore/radarr/var/.config/Radarr] 
[Debug] Bootstrap: Console selected 
[Info] AppFolderInfo: Data directory is being overridden to [/volume1/@appstore/radarr/var/.config/Radarr] 
[Info] AppFolderInfo: Data directory is being overridden to [/volume1/@appstore/radarr/var/.config/Radarr] 
[Info] MigrationController: *** Migrating data source=/volume1/@appstore/radarr/var/.config/Radarr/radarr.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 *** 
[Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrating 
[Info] FluentMigrator.Runner.MigrationRunner: PerformDBOperation  
[Info] NzbDrone.Core.Datastore.Migration.Framework.NzbDroneSQLiteProcessor: Performing DB Operation 
[Info] DatabaseEngineVersionCheck: SQLite 3.10.2 
[Info] FluentMigrator.Runner.MigrationRunner: => 0.2321498s 
[Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrated 
[Info] FluentMigrator.Runner.MigrationRunner: => 0.2422033s 
[Info] MigrationController: *** Migrating data source=/volume1/@appstore/radarr/var/.config/Radarr/logs.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 *** 
[Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrating 
[Info] FluentMigrator.Runner.MigrationRunner: PerformDBOperation  
[Info] NzbDrone.Core.Datastore.Migration.Framework.NzbDroneSQLiteProcessor: Performing DB Operation 
[Info] DatabaseEngineVersionCheck: SQLite 3.10.2 
[Info] FluentMigrator.Runner.MigrationRunner: => 0.0044507s 
[Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrated 
[Info] FluentMigrator.Runner.MigrationRunner: => 0.005313s 
[Info] Microsoft.Hosting.Lifetime: Now listening on: http://[::]:8310 
[Info] CommandExecutor: Starting 2 threads for tasks. 
[Info] Microsoft.Hosting.Lifetime: Application started. Press Ctrl+C to shut down. 
[Info] Microsoft.Hosting.Lifetime: Hosting environment: Production 
[Info] Microsoft.Hosting.Lifetime: Content root path: / 
[Info] ManagedHttpDispatcher: IPv4 is available: True, IPv6 will be disabled 

This is with a very old library file:

$ ls -al /lib/libm.so.6
lrwxrwxrwx 1 root root 20 Dec 31  1969 /lib/libm.so.6 -> libm-2.20-2014.11.so

I don't know if this is something specific to ARMv7.

[mreid-tt]

Hey @woutercoppens, I noticed you cross-posted this issue at Radarr/Radarr#10653. From the additional details, it looks like you were upgrading from Radarr 5.11.0.9244 (which includes .NET 6.0.32) to Radarr 5.14.0.9383. Starting with Radarr version 5.12.2.9335, .NET 6.0.35 was included, which could be a contributing factor. Interestingly, based on my testing, this issue doesn’t seem to affect x64 platforms.

[woutercoppens]

Hi Michael,
I cross-posted this issue because it was not clear to me where the updates are pulled from. Are they build by the Radarr team or the synoCommunity?

[woutercoppens]

ls -al /lib/libm.so.6
lrwxrwxrwx 1 root root 12 Sep  8  2022 /lib/libm.so.6 -> libm-2.26.so

I restarted Radarr and launched the update again:

Fri Nov  8 09:30:26 CET 2024
Starting radarr command env HOME=/volume1/@appdata/radarr /volume1/@appstore/radarr/share/Radarr/bin/Radarr -nobrowser -data=/volume1/@appdata/radarr/.config/Radarr
[Info] Bootstrap: Starting Radarr - /volume1/@appstore/radarr/share/Radarr/bin/Radarr - Version 5.11.0.9244
[Info] AppFolderInfo: Data directory is being overridden to [/volume1/@appdata/radarr/.config/Radarr]
[Debug] Bootstrap: Console selected
[Info] AppFolderInfo: Data directory is being overridden to [/volume1/@appdata/radarr/.config/Radarr]
[Info] AppFolderInfo: Data directory is being overridden to [/volume1/@appdata/radarr/.config/Radarr]
[Info] MigrationController: *** Migrating data source=/volume1/@appdata/radarr/.config/Radarr/radarr.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 ***
[Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrating
[Info] FluentMigrator.Runner.MigrationRunner: PerformDBOperation
[Info] NzbDrone.Core.Datastore.Migration.Framework.NzbDroneSQLiteProcessor: Performing DB Operation
[Info] DatabaseEngineVersionCheck: SQLite 3.34.1
[Info] FluentMigrator.Runner.MigrationRunner: => 0.5268356s
[Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrated
[Info] FluentMigrator.Runner.MigrationRunner: => 0.5526659s
[Info] MigrationController: *** Migrating data source=/volume1/@appdata/radarr/.config/Radarr/logs.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 ***
[Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrating
[Info] FluentMigrator.Runner.MigrationRunner: PerformDBOperation
[Info] NzbDrone.Core.Datastore.Migration.Framework.NzbDroneSQLiteProcessor: Performing DB Operation
[Info] DatabaseEngineVersionCheck: SQLite 3.34.1
[Info] FluentMigrator.Runner.MigrationRunner: => 0.0408477s
[Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrated
[Info] FluentMigrator.Runner.MigrationRunner: => 0.0420052s
[Info] Microsoft.Hosting.Lifetime: Now listening on: http://[::]:8310
[Info] CommandExecutor: Starting 2 threads for tasks.
[Info] Microsoft.Hosting.Lifetime: Application started. Press Ctrl+C to shut down.
[Info] Microsoft.Hosting.Lifetime: Hosting environment: Production
[Info] Microsoft.Hosting.Lifetime: Content root path: /
[Info] ManagedHttpDispatcher: IPv4 is available: True, IPv6 will be disabled
[Info] Radarr.Http.Authentication.BasicAuthenticationHandler: Basic was not authenticated. Failure message: Authorization header missing.
[Info] InstallUpdateService: Downloading update 5.14.0.9383
[Info] InstallUpdateService: Verifying update package
[Info] InstallUpdateService: Update package verified successfully
[Info] InstallUpdateService: Extracting Update package
[Info] InstallUpdateService: Update package extracted successfully
[Info] BackupService: Starting Backup
[Info] InstallUpdateService: Preparing client
[Info] InstallUpdateService: Starting update client /volume1/@apptemp/radarr/radarr_update/Radarr.Update
[Info] InstallUpdateService: Radarr will restart shortly.
[Error] Radarr.Update: Failed to load /volume1/@apptemp/radarr/radarr_update/libcoreclr.so, error: /lib/libm.so.6: version `GLIBC_2.27' not found (required by /volume1/@apptemp/radarr/radarr_update/libcoreclr.so)

[mreid-tt]

Hey @woutercoppens, I've spoken with the Radarr team, and they plan to re-open your original cross-posted ticket since this issue seems related to .NET versions newer than 6.0.32 on ARMv7 platforms. The Microsoft .NET 6.0.33 issue (see dotnet/core#9447 (comment)) describes a very similar problem, so it likely requires an upstream fix from Microsoft. I've also added a comment in the latest Microsoft issue (dotnet/core#9532 (comment)) to help bring more attention to it.

[hgy59]

@mreid-tt we could fix this by adding DEPENDS += cross/glibc when building for DSM 7.1.

and we would need to set LD_LIBRARY_PATH for DSM 7.1 too in SERVICE_COMMAND.

we alread do this for DSM 6 to include and find the newer libstdc++ library added to the package.

This seems to be an issue for models that are limitted to DSM 7.1.1 or DSM 6.2.4.
My Models with DSM 7.2 have glibc 2.36 and my ds115j with DSM 7.1.1 has glibc 2.20.

IMHO it would not be a probem to add cross/glibc and LD_LIBRARY_PATH for all packages.

BTW the version of glibc can be seen in the name of the Synology toolchain file

[mreid-tt]

@mreid-tt we could fix this by adding DEPENDS += cross/glibc when building for DSM 7.1.

and we would need to set LD_LIBRARY_PATH for DSM 7.1 too in SERVICE_COMMAND.

hey @hgy59, thanks for this solution, I'll give it a try. Would you suggest including it for any DSM 7.1 build or just restricting the inclusion to ARMv7 builds?

[hgy59]

hey @hgy59, thanks for this solution, I'll give it a try. Would you suggest including it for any DSM 7.1 build or just restricting the inclusion to ARMv7 builds?

I recommend it for all TC_VERSION (DSM 6.2.4, DSM 7+) and all archs.
(thats what I meant with "it would not be a probem to add cross/glibc and LD_LIBRARY_PATH for all packages")

[mreid-tt]

Hey @woutercoppens, unfortunately, our attempts to work around the issue by manually including an updated version of glibc were unsuccessful. As a result, the only viable solution now lies with Microsoft resolving the underlying issue. I've logged a ticket with Microsoft for this (dotnet/runtime#109739), and hopefully, it will be addressed in a future .NET release, which can then be integrated into Radarr.

In the meantime, I’ve created a new SynoCommunity Radarr release using the last version compatible with your ARMv7 CPU (v5.12.2.9335). This ensures that reinstallations can use the most recent version supported on your device, as the built-in updater will always attempt to install the latest version.