linuxserver / docker-jellyfin

GNU General Public License v3.0
647 stars 97 forks source link

20200524-ls67 fails to launch the jellyfin server #44

Closed KristupasSavickas closed 4 years ago

KristupasSavickas commented 4 years ago

The 20200524-ls67 tag fails to start the Jellyfin server with the following error:

jellyfin         | [10:32:26] [INF] [1] Main: Jellyfin version: 10.6.0
jellyfin         | [10:32:26] [INF] [1] Main: Environment Variables: ["[JELLYFIN_CACHE_DIR, /config/cache]", "[JELLYFIN_DATA_DIR, /config/data]", "[JELLYFIN_CONFIG_DIR, /config]", "[JELLYFIN_LOG_DIR, /config/log]"]
jellyfin         | [10:32:26] [INF] [1] Main: Arguments: ["/usr/lib/jellyfin/bin/jellyfin.dll", "--ffmpeg=/usr/lib/jellyfin-ffmpeg/ffmpeg"]
jellyfin         | [10:32:26] [INF] [1] Main: Operating system: Linux
jellyfin         | [10:32:26] [INF] [1] Main: Architecture: X64
jellyfin         | [10:32:26] [INF] [1] Main: 64-Bit Process: True
jellyfin         | [10:32:26] [INF] [1] Main: User Interactive: True
jellyfin         | [10:32:26] [INF] [1] Main: Processor count: 4
jellyfin         | [10:32:26] [INF] [1] Main: Program data path: /config/data
jellyfin         | [10:32:26] [INF] [1] Main: Web resources path: /usr/lib/jellyfin/bin/jellyfin-web
jellyfin         | [10:32:26] [INF] [1] Main: Application directory: /usr/lib/jellyfin/bin/
jellyfin         | [10:32:26] [INF] [1] ServerConfigurationManager: Setting cache path: /config/cache
jellyfin         | [10:32:26] [FTL] [1] Main: Error while starting server.
jellyfin         | System.InvalidOperationException: The server is expected to host the web client, but the provided content directory is either invalid or empty: /usr/lib/jellyfin/bin/jellyfin-web. If you do not want to host the web client with the server, you may set the '--nowebclient' command line flag, or set'hostwebclient=false' in your config settings.
jellyfin         |    at Jellyfin.Server.Program.StartApp(StartupOptions options)
jellyfin         | [10:32:26] [INF] [1] Emby.Server.Implementations.ApplicationHost: Disposing CoreAppHost
jellyfin         | [10:32:26] [INF] [2] Main: Received a SIGTERM signal, shutting down

According to the log Jellyfin looks for the directory with web files at /usr/lib/jellyfin/bin/jellyfin-web which does not exist.

LaggAt commented 4 years ago

seems a watchtower update broke this in my case. I fixed the version to

linuxserver/jellyfin:v10.5.5-ls54

which is working fine. On latest or nightly it fails.

KristupasSavickas commented 4 years ago

@LaggAt ~what's a nigthly in this case? AFAIK CI is broken on Jellyfin and nightlies were not built for the last 3 months. So would that be constant updates of the Linux Server base or is Jellyfin built as well?~ <- EDIT: That's only applicable to jellyfin docker builds.

KristupasSavickas commented 4 years ago

Found the cause: jellyfin was split into jellyfin-servert and jellyfin-web in the latest master, changes not yet present in any release. The web files are installed to /usr/share/jellyfin/web on Ubuntu.

To fix this,/etc/services.d/jellyfin/run needs to be updated to run jellyfin with a --webdir=/usr/share/jellyfin/web command line argument. Not sure how to do this for nigthlies only as I'm not familiar with the Linux Server build process.

aptalca commented 4 years ago

@KristupasSavickas great find and thanks for letting us know. We'll do a PR

Just so you know, different tags build from different github branches. This is the branch the nightlies build from: https://github.com/linuxserver/docker-jellyfin/tree/nightly