-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Jellyfin does not run on DS414 #28
Comments
Did you have plugins installed? |
You mean in Jellyfin? No, I did a new installation of Jellyfin and I had no chance to open it and install plugins by now. What might be special is my parallel Emby installation. In the beginning I was not able to install Jellyfin because it uses the same port like Emby. So I did the manual edit of the spk that was mentioned here: #18 (comment). Additionally I stopped the Emby package to avoid any interference with Jellyfin. |
Thanks for the additional info. The fact that Jellyfin is logging the environment is good, but a What is the output of: I don't suppose the newer version 10.7.6 changes anything? |
The output of
I can confirm that my Emby installation works without problems. Sometimes it is slow because the NAS is an older model but it is sufficient for my use cases. I updated Jellyfin to 10.7.6-3 but the issue still persists. |
@rfrmarco can you find the dump file or create one? If you need the dotnet cli. I can provide you with a .NET SDK package that just uses the official |
I have installed the .NET SDK and it is in status "Running". If I understand this correctly, then I need to install the dotnet-dump tool afterwards. But if I execute
Did I get something wrong? I am not used to .NET programming and the tools needed to do it so I hope that is not a too basic question... |
No nothing wrong just the environment is not setup properly and missing the updated libstdc++. I've made a new version which fixes this: https://github.com/publicarray/spksrc/releases/tag/dotnet-fix
env DOTNET_ROOT=/var/packages/dotnet-sdk/target/ LD_LIBRARY_PATH=/var/packages/dotnet-sdk/target/lib dotnet I tried using root@dsm6 /# ps aux | grep radarr
sc-rada+ 31490 9.0 3.1 3635352 128836 ? SLl 10:43 0:03 /volume1/@appstore/radarr/share/Radarr/bin/Radarr
root 32150 0.0 0.0 23144 2320 pts/18 S+ 10:44 0:00 grep --color=auto radarr
root@dsm6 /# dotnet-env /var/packages/dotnet-sdk/target/shared/Microsoft.NETCore.App/5.0.8/createdump -u 31490
Gathering state for process 31490 Radarr
Writing full dump to file /tmp/coredump.31490
Written 311914496 bytes (76151 pages) to core file
Dump successfully written |
I have installed the new package dotnet-sdk_armv7-6.1_5.0.302-1.spk and executed
Any ideas what's wrong? |
Thanks for your patience. Actually this confirms this is a problem with .net and the environment. Any dotnet commad needs to have @mangod9 how do I know the libstdc from debian is working? On x64 we successfully use this trick to get around the error above. ( |
Setup
Package Name: jellyfin
Package Version: 10.7.2-1 for arm7-6.1
NAS Model: DS414
NAS Architecture: ARMADA XP
DSM version: 6.2.4-25556
Expected behavior
After installation of the Jellyfin package the status of the service should be "running". It should be possible to open the Jellyfin dashboard.
Actual behavior
The Jellyfin service starts and is shown as "running" in the package center. But after some seconds the status changes to "stopped". It is not possible to call the dashboard and to start the setup of Jellyfin.
If I start the Jellyfin service manually in the package center, it has the same effect. The service starts and goes to status "running" but after a short time the status changes to "stopped".
A reboot of the NAS has no effect.
Steps to reproduce
1. Install package
2. The service remains in status "stopped". Restart the service manually in the package center.
Package log
/usr/local/jellyfin/var/jellyfin.log
Other logs
/var/log/synopkg.log
/var/log/messages
/var/log/packages/jellyfin.log
/var/packages/jellyfin/target/var/jellyfin.log
Other notes
The only message that sounds like an error to me is in /var/log/messages. I am quite new to the Synology packages. If there are other logs which might help, please let me know.
The text was updated successfully, but these errors were encountered: