mueslo 17 Posted June 1, 2024 Posted June 1, 2024 (edited) Just tried upgrading from 4.8.0.x to 4.9.0.22 on FreeBSD 13.2 Jail (on TrueNAS, FreeBSD 13.1 Kernel) However, emby doesn't even launch and there are also no logs generated. If I try to manually launch emby as follows, it immediately exits with exit code 137 $ sudo -u emby /usr/local/lib/emby-server/system/EmbyServer -os freebsd Failed to create CoreCLR, HRESULT: 0x8007054F $ echo $? 137 Upgrading to 4.8.7.x and 4.8.8.x instead and it still works fine. So something else is causing it. Interestingly, I see the same error when running $ dotnet --info Failed to create CoreCLR, HRESULT: 0x8007054F Host: Version: 8.0.0 Architecture: x64 Commit: 5535e31a71 RID: freebsd-x64 .NET SDKs installed: 8.0.100 [/usr/local/dotnet/sdk] .NET runtimes installed: Microsoft.AspNetCore.App 8.0.0 [/usr/local/dotnet/shared/Microsoft.AspNetCore.App] Microsoft.NETCore.App 8.0.0 [/usr/local/dotnet/shared/Microsoft.NETCore.App] Other architectures found: None Environment variables: Not set global.json file: Not found Learn more: https://aka.ms/dotnet/info Download .NET: https://aka.ms/dotnet/download Did 4.9 shift to using system dotnet, which appears to have some issue on FreeBSD 13 with the latest version? https://github.com/dotnet/runtime/issues/99857 Edited June 1, 2024 by mueslo
alucryd 315 Posted June 6, 2024 Posted June 6, 2024 You will need to upgrade to a 13.3 jail, dotnet 8 doesn't work on 13.2 and older.
bolok 18 Posted June 8, 2024 Posted June 8, 2024 Ran into this personally. 4.9.18? and previous ran fine on a 13.1 jail/truenas 13.1. But i got stymied updating beyond that. I'm fairly certain you need to update to the 13.3 beta+ of Truenas for the 13.3 jails to fully work correctly with the new dotnet reqs. I did install the TN beta, and a 13.3 jail with the latest emby started with no issue. Was too lazy to try upgrading my old jail, so just copied over the library files and remapped all the library mounts. Working fine.
Luke 42077 Posted June 8, 2024 Posted June 8, 2024 Yea it’s not that we want to raise the requirements, it’s just that it seems it is necessary for dotnet 8.
mueslo 17 Posted June 8, 2024 Author Posted June 8, 2024 Yep, I can confirm that it works with jail updated to 13.3 (still on 13.1 host) 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now