Luke 36879 Posted March 2, 2020 Author Share Posted March 2, 2020 I just recently installed Emby Server 4.3.1.0_x86_64 on CentOS 8 and ran into the following errors after install: I even tried removing both group and user for emby and reinstalled to no avail. Not sure if this is an issue with the latest systemd version and Python3. Any update would help. Hi, please see here: https://emby.media/community/index.php?/topic/82976-new-install-failed/ Thanks. Link to comment Share on other sites More sharing options...
Xnet Project 0 Posted March 2, 2020 Share Posted March 2, 2020 (edited) As a suggestion you may want to include the following in the setup instructions: If Emby does not start try the following:sudo nano /etc/emby-server.conf# Path to your emby library (default: /var/lib/emby)EMBY_DATA=/your/data/driveMake sure data drive has write permissionschmod 755 /your/data/driveRestart Emby Serversystemctl start emby-server This will eliminate confusion for RPM installs. Edited March 2, 2020 by Xnet Project Link to comment Share on other sites More sharing options...
Q-Droid 609 Posted March 2, 2020 Share Posted March 2, 2020 (edited) As a suggestion you may want to include the following in the setup instructions: This will eliminate confusion for RPM installs. Retracted... Edited March 3, 2020 by Q-Droid Link to comment Share on other sites More sharing options...
Luke 36879 Posted March 3, 2020 Author Share Posted March 3, 2020 For those looking for additional options to run Emby Server, we now have Snap packages available for testing: https://emby.media/community/index.php?/topic/83274-emby-server-snap-packages/ Thanks ! Link to comment Share on other sites More sharing options...
drynkins 0 Posted March 24, 2020 Share Posted March 24, 2020 (edited) Hey guys, have some problems setting up the Server on RHEL 8. Follow the instructions on the official download page. The same rpm file works as expected on Fedora-32 beta. But on RHEL 8 the systemd unit failes to start. systemctl status emby-server goes like this: ● emby-server.service - Emby Server is a personal media server with apps on just about every device. Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: disabled) Active: failed (Result: core-dump) since Wed 2020-03-25 07:11:02 +10; 7min ago Process: 1221 ExecStart=/opt/emby-server/bin/emby-server (code=dumped, signal=ABRT) Main PID: 1221 (code=dumped, signal=ABRT) мар 25 07:10:24 localhost.localdomain emby-server[1221]: at System.IO.FileSystem.CreateDirectory(String fullPath) мар 25 07:10:24 localhost.localdomain emby-server[1221]: at System.IO.Directory.CreateDirectory(String path) мар 25 07:10:24 localhost.localdomain emby-server[1221]: at Emby.Server.Implementations.Logging.FileLogger..ctor(String path) мар 25 07:10:24 localhost.localdomain emby-server[1221]: at Emby.Server.Implementations.Logging.SimpleLogManager.ReloadLogger(LogSeverity severity, CancellationToken cancellationToken) мар 25 07:10:24 localhost.localdomain emby-server[1221]: --- End of inner exception stack trace --- мар 25 07:10:24 localhost.localdomain emby-server[1221]: at System.Threading.Tasks.Task.WaitAllCore(Task[] tasks, Int32 millisecondsTimeout, CancellationToken cancellationToken) мар 25 07:10:24 localhost.localdomain emby-server[1221]: at System.Threading.Tasks.Task.WaitAll(Task[] tasks) мар 25 07:10:24 localhost.localdomain emby-server[1221]: at EmbyServer.Program.Main(String[] args) мар 25 07:11:02 localhost.localdomain systemd[1]: emby-server.service: Main process exited, code=dumped, status=6/ABRT мар 25 07:11:02 localhost.localdomain systemd[1]: emby-server.service: Failed with result 'core-dump'. didn't mess with systemd unit itself. it still reads like this [root@[member="Localhost"] user02]# systemctl cat emby-server # /usr/lib/systemd/system/emby-server.service [Unit] Description=Emby Server is a personal media server with apps on just about every device. After=network.target [Service] EnvironmentFile=/etc/emby-server.conf WorkingDirectory=/opt/emby-server ExecStart=/opt/emby-server/bin/emby-server RestartForceExitStatus=3 User=emby [Install] WantedBy=multi-user.target tried changing permissions with sudo chown -R emby:emby /var/lib/emby tried changing the data folder. So my emby-server.conf goes like this: # Path to your emby library (default: /var/lib/emby) EMBY_DATA=/home/user02/Downloads # Path to your vaapi drivers LIBVA_DRIVERS_DIR= after the fresh install and reboot i get no logs in /var/lib/emby starting /opt/emby-server/bin/emby-server as root does start evertyhing perfectly and the web interface gets accessible here's the terminal output of launching it as root [root@[member="Localhost"] user02]# /opt/emby-server/bin/emby-server Info Main: Application path: /opt/emby-server/system/EmbyServer.dll Info Main: Emby Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-rpm_{version}_x86_64.rpm Operating system: Unix 4.18.0.147 64-Bit OS: True 64-Bit Process: True User Interactive: True Runtime: file:///opt/emby-server/system/System.Private.CoreLib.dll System.Environment.Version: 3.1.2 Processor count: 8 Program data path: /var/lib/emby Application directory: /opt/emby-server/system Info App: Application version: 4.4.0.40 Info App: Loading assemblies Info App: Copying plugin from /opt/emby-server/system/plugins/Tvdb.dll to /var/lib/emby/plugins/Tvdb.dll Info App: Copying plugin from /opt/emby-server/system/plugins/Fanart.dll to /var/lib/emby/plugins/Fanart.dll Info App: Copying plugin from /opt/emby-server/system/plugins/NfoMetadata.dll to /var/lib/emby/plugins/NfoMetadata.dll Info App: Copying plugin from /opt/emby-server/system/plugins/OMDb.dll to /var/lib/emby/plugins/OMDb.dll Info App: Copying plugin from /opt/emby-server/system/plugins/Emby.Dlna.dll to /var/lib/emby/plugins/Emby.Dlna.dll Info App: Copying plugin from /opt/emby-server/system/plugins/StudioImages.dll to /var/lib/emby/plugins/StudioImages.dll Info App: Copying plugin from /opt/emby-server/system/plugins/MusicBrainz.dll to /var/lib/emby/plugins/MusicBrainz.dll Info App: Copying plugin from /opt/emby-server/system/plugins/AudioDb.dll to /var/lib/emby/plugins/AudioDb.dll Info App: Copying plugin from /opt/emby-server/system/plugins/BlurayMounter.dll to /var/lib/emby/plugins/BlurayMounter.dll Info App: Copying plugin from /opt/emby-server/system/plugins/Emby.PortMapper.dll to /var/lib/emby/plugins/Emby.PortMapper.dll Info App: Copying plugin from /opt/emby-server/system/plugins/DvdMounter.dll to /var/lib/emby/plugins/DvdMounter.dll Info App: Copying plugin from /opt/emby-server/system/plugins/Emby.Server.CinemaMode.dll to /var/lib/emby/plugins/Emby.Server.CinemaMode.dll Info App: Copying plugin from /opt/emby-server/system/plugins/OpenSubtitles.dll to /var/lib/emby/plugins/OpenSubtitles.dll Info App: Copying plugin from /opt/emby-server/system/plugins/Emby.Webhooks.dll to /var/lib/emby/plugins/Emby.Webhooks.dll Info App: Copying plugin from /opt/emby-server/system/plugins/MovieDb.dll to /var/lib/emby/plugins/MovieDb.dll Info App: Loading Tvdb, Version=1.0.30.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Tvdb.dll Info App: Loading Fanart, Version=1.0.7.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Fanart.dll Info App: Loading NfoMetadata, Version=1.0.27.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/NfoMetadata.dll Info App: Loading OMDb, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/OMDb.dll Info App: Loading Emby.Dlna, Version=1.0.37.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Dlna.dll Info App: Loading StudioImages, Version=1.0.3.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/StudioImages.dll Info App: Loading MusicBrainz, Version=1.0.12.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MusicBrainz.dll Info App: Loading AudioDb, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/AudioDb.dll Info App: Loading BlurayMounter, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/BlurayMounter.dll Info App: Loading Emby.PortMapper, Version=1.0.4.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.PortMapper.dll Info App: Loading DvdMounter, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/DvdMounter.dll Info App: Loading Emby.Server.CinemaMode, Version=1.0.31.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Server.CinemaMode.dll Info App: Loading OpenSubtitles, Version=1.0.24.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/OpenSubtitles.dll Info App: Loading Emby.Webhooks, Version=1.0.11.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Webhooks.dll Info App: Loading MovieDb, Version=1.3.1.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MovieDb.dll Info App: Loading Emby.Api, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading Emby.Web, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading MediaBrowser.Model, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading MediaBrowser.Common, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading MediaBrowser.Controller, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading Emby.Providers, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading Emby.Photos, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading Emby.Server.Implementations, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading Emby.LiveTV, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading Emby.ActivityLog, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null Info App: Loading Emby.Server.MediaEncoding, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading Emby.LocalMetadata, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading Emby.Notifications, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading Emby.Codecs.Dxva, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading Emby.Codecs, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading Emby.Server.Connect, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading Emby.Server.Sync, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info App: Loading EmbyServer, Version=4.4.0.40, Culture=neutral, PublicKeyToken=null Info SqliteUserRepository: Sqlite version: 3.30.1 Info SqliteUserRepository: Sqlite compiler options: COMPILER=gcc-8.3.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS4,ENABLE_FTS5,ENABLE_JSON1,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MAX_SCHEMA_RETRY=25,MAX_VARIABLE_NUMBER=250000,OMIT_LOOKASIDE,SECURE_DELETE,THREADSAFE=1 Info SqliteUserRepository: Default journal_mode for /var/lib/emby/data/users.db is delete Info AuthenticationRepository: Default journal_mode for /var/lib/emby/data/authentication.db is delete Info ActivityRepository: Default journal_mode for /var/lib/emby/data/activitylog.db is delete Info SqliteDisplayPreferencesRepository: Default journal_mode for /var/lib/emby/data/displaypreferences.db is delete Info App: Requesting administrative access to authorize http server Info ServerConfigurationManager: Saving system configuration Info App: Adding HttpListener prefix http://+:8096/ Info SqliteItemRepository: Default journal_mode for /var/lib/emby/data/library.db is delete Info ServerConfigurationManager: Saving system configuration Info ServerConfigurationManager: Saving system configuration Info Skia: SkiaSharp version: 1.68.0.0 Info TaskManager: Daily trigger for Thumbnail image extraction set to fire at 03/26/2020 02:00:00, which is 1117.888747575 minutes from now. Info TaskManager: Daily trigger for Rotate log file set to fire at 03/26/2020 00:00:00, which is 997.88865377 minutes from now. Info App: ServerId: 4d7e07dacd1d43f6a04418c1abd886a3 Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint Info Dlna: Registering publisher for urn:schemas-upnp-org:device:MediaServer:1 Info App: Init BeginReceive on 0.0.0.0 Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.1364395 seconds Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint Info App: Loading data from /var/lib/emby/data/connect.txt Info App: Loading data from /var/lib/emby/data/wan.dat Info App: Entry point completed: Emby.Server.Connect.ConnectEntryPoint. Duration: 0.0035084 seconds Info App: Core startup complete Info App: Post-init migrations complete Info App: Starting entry point NfoMetadata.EntryPoint Info App: Entry point completed: NfoMetadata.EntryPoint. Duration: 0.0001889 seconds Info App: Starting entry point Emby.PortMapper.ExternalPortForwarding Info App: Entry point completed: Emby.PortMapper.ExternalPortForwarding. Duration: 0.000835 seconds Info App: Starting entry point Emby.Security.PluginSecurityManager Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 2.3E-05 seconds Info App: Starting entry point Emby.Server.CinemaMode.IntrosEntryPoint Info App: Entry point completed: Emby.Server.CinemaMode.IntrosEntryPoint. Duration: 6.45E-05 seconds Info App: Starting entry point Emby.Webhooks.WebhooksEntryPoint Info App: Entry point completed: Emby.Webhooks.WebhooksEntryPoint. Duration: 0.0009215 seconds Info App: Starting entry point MediaBrowser.Api.ApiEntryPoint Info App: Entry point completed: MediaBrowser.Api.ApiEntryPoint. Duration: 3.08E-05 seconds Info App: Starting entry point Emby.Server.Implementations.Udp.UdpServerEntryPoint Info App: Entry point completed: Emby.Server.Implementations.Udp.UdpServerEntryPoint. Duration: 0.0010486 seconds Info App: Starting entry point Emby.Server.Implementations.Playlists.PlaylistsEntryPoint Info App: Entry point completed: Emby.Server.Implementations.Playlists.PlaylistsEntryPoint. Duration: 0.0006778 seconds Info App: Starting entry point Emby.Server.Implementations.News.NewsEntryPoint Info App: Entry point completed: Emby.Server.Implementations.News.NewsEntryPoint. Duration: 0.0001306 seconds Info App: Starting entry point Emby.Server.Implementations.Library.DeviceAccessEntryPoint Info App: Entry point completed: Emby.Server.Implementations.Library.DeviceAccessEntryPoint. Duration: 0.0001712 seconds Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.094049 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.0001663 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 0.0001047 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0006167 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0007782 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.000322 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.0001514 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 7.74E-05 seconds Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.0015216 seconds Info App: Starting entry point Emby.LiveTV.EntryPoint Info LiveTV: Loading live tv data from /var/lib/emby/data/livetv/timers Info App: Entry point completed: Emby.LiveTV.EntryPoint. Duration: 0.0113213 seconds Info App: Starting entry point Emby.LiveTV.LiveTVEntryPoint Info App: Entry point completed: Emby.LiveTV.LiveTVEntryPoint. Duration: 0.0001337 seconds Info App: Starting entry point Emby.LiveTV.RecordingNotifier Info App: Entry point completed: Emby.LiveTV.RecordingNotifier. Duration: 0.0007542 seconds Info App: Starting entry point Emby.ActivityLog.ActivityLogEntryPoint Info App: Entry point completed: Emby.ActivityLog.ActivityLogEntryPoint. Duration: 0.0010809 seconds Info App: Starting entry point Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 0.0010464 seconds Info App: Starting entry point Emby.Notifications.Notifications Info App: Entry point completed: Emby.Notifications.Notifications. Duration: 0.0001827 seconds Info App: Starting entry point Emby.Server.Sync.SyncManagerEntryPoint Info App: SyncRepository Initialize taking write lock Info App: SyncRepository Initialize write lock taken Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0033641 seconds Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0006896 seconds Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 0.0001541 seconds Info App: All entry points have started ^CInfo App: Disposing CoreAppHost Info App: Disposing LoopUtilEntryPoint Info App: Disposing SyncNotificationEntryPoint Info App: Disposing SyncManagerEntryPoint Info App: Disposing ConnectEntryPoint Info App: Disposing Notifications Info App: Disposing EncodingManagerEntryPoint Info App: Disposing ActivityLogEntryPoint Info App: Disposing RecordingNotifier Info App: Disposing LiveTVEntryPoint Info App: Disposing EntryPoint Info App: Disposing ChannelsEntryPoint Info App: Disposing UserDataChangeNotifier Info App: Disposing SystemEvents Info App: Disposing StartupWizard Info App: Disposing ServerEventNotifier Info App: Disposing LibraryChangedNotifier Info App: Disposing KeepServerAwake Info App: Disposing AutomaticRestartEntryPoint Info App: Disposing LibraryMonitorStartup Info App: Disposing DeviceAccessEntryPoint Info App: Disposing NewsEntryPoint Info App: Disposing PlaylistsEntryPoint Info App: Disposing UdpServerEntryPoint Info App: Disposing ApiEntryPoint Info App: Disposing WebhooksEntryPoint Info App: Disposing IntrosEntryPoint Info App: Disposing PluginSecurityManager Info App: Disposing ExternalPortForwarding Info App: Disposing DlnaEntryPoint Info Dlna: Disposing PlayToManager Info App: Disposing EntryPoint Info App: Disposing StrmMounter Info App: Disposing DvdMounter Info App: Disposing BlurayMounter Info App: Disposing OpenSubtitleDownloader Info App: Disposing HauppaugeTunerWindows Info App: Disposing EmbyTV Info App: Disposing ActivityLogWebSocketListener Info App: Disposing SessionWebSocketListener Info App: Disposing ScheduledTasksWebSocketListener Info App: Disposing SessionInfoWebSocketListener Info App: Disposing SessionInfosWebSocketListener Info App: Disposing SessionEventsWebSocketListener Info App: Disposing EncodingManager Info App: Disposing ActivityRepository Info App: Disposing MediaEncoder Info App: Disposing SsdpDevicePublisher Info App: Disposing SsdpCommunicationsServer Info App: SsdpCommunicationsServer disposing _BroadcastListenSocket. Info App: SsdpCommunicationsServer Disposing 1 sendSockets Info App: SsdpCommunicationsServer disposing sendSocket from 0.0.0.0:44906 Info App: Disposing LiveTvManager Info App: Disposing SessionManager Info App: Disposing ProviderManager Info App: Disposing MediaSourceManager Info App: Disposing ImageProcessor Info App: Disposing ProcessManager Info App: Disposing HttpListenerHost Info HttpServer: Stopping HttpListener... Info HttpServer: HttpListener stopped Info App: Disposing LibraryMonitor Info App: Disposing AuthenticationRepository Info App: Disposing SqliteItemRepository Info App: Disposing SqliteDisplayPreferencesRepository Info App: Disposing SqliteUserRepository Info App: Disposing InstallationManager Info App: Disposing TaskManager Info App: Disposing MediaMountManager Info Main: Shutdown complete How do i get the systemd unit to autostart? Thanks in advance!! PS added the info on systemd unit itself Edited March 24, 2020 by drynkins Link to comment Share on other sites More sharing options...
alucryd 213 Posted March 25, 2020 Share Posted March 25, 2020 The only place emby needs to write to is /var/lib/emby if you don't change it. By running as root you've probably borked all the perms in it, please give them back to emby:emby and try launching the regular unit again. The full version of the log you posted first would have been nice to understand why it failed in the first place. If you're feeling adventurous and your systemd (235 and above) is recent enough, you may create the following file: /etc/systemd/system/emby-server.service.d/dynamic-user.conf [Unit] DynamicUser=yes StateDirectory=emby Then run as root: systemctl daemon-reload && systemctl restart emby-server What this will do is assign a random pid to the emby user and automatically chown everything in /var/lib/emby when the unit starts. Note that you may need to userdel emby first, haven't actually tried DynamicUser on existing users before. Link to comment Share on other sites More sharing options...
drynkins 0 Posted March 25, 2020 Share Posted March 25, 2020 Hey, thanks so much for the reply and sorry for me being so wordy... Let me retrace the steps to clear the mess out a little. 0. I'm on rhel 8, just chrome and virtualbox repos added to the default repositories, no epel. System is up to date 1. Systemd unit didn't autostart after fresh install of stable RPM file from github 2. No logs in /var/lib/emby by deafault - no errors,no nothing 3. Tried chowning the /var/lib folder to emby:emby and restart the service - no luck, Systemd unit still fails 4. As a matter of exercise launched the binary as root - and it launched just fine 5. Tried installing the RPM file from github on fresh fedora beta 32,and it just worked - Systemd unit got enabled and stated without any manual intervention In the meantime I Will check the Systemd version I've got here Link to comment Share on other sites More sharing options...
alucryd 213 Posted March 26, 2020 Share Posted March 26, 2020 Quick question, did you by chance create an emby user yourself prior to installing the package? Link to comment Share on other sites More sharing options...
drynkins 0 Posted March 26, 2020 Share Posted March 26, 2020 Hey! No i did not Link to comment Share on other sites More sharing options...
Luke 36879 Posted March 26, 2020 Author Share Posted March 26, 2020 Please see my response in this thread here for workarounds: https://emby.media/community/index.php?/topic/82976-new-install-failed/?view=getnewpost Link to comment Share on other sites More sharing options...
aptalca 70 Posted June 3, 2021 Share Posted June 3, 2021 Hi @Luke I noticed the rpm artifacts are missing in the latest release here: https://github.com/MediaBrowser/Emby.Releases/releases/tag/4.6.2.0 Was that an oversight or an issue with the ci? Link to comment Share on other sites More sharing options...
Luke 36879 Posted June 3, 2021 Author Share Posted June 3, 2021 1 hour ago, aptalca said: Hi @Luke I noticed the rpm artifacts are missing in the latest release here: https://github.com/MediaBrowser/Emby.Releases/releases/tag/4.6.2.0 Was that an oversight or an issue with the ci? HI, yes the rpms are missing. My mistake, sorry. They're headed up now. 1 Link to comment Share on other sites More sharing options...
mrteufel 0 Posted November 17, 2021 Share Posted November 17, 2021 Hi @Luke, The rpms seem to be missing from the latest release https://github.com/MediaBrowser/Emby.Releases/releases/tag/4.6.5.0 Can they be added? Thanks! Link to comment Share on other sites More sharing options...
Luke 36879 Posted November 17, 2021 Author Share Posted November 17, 2021 3 hours ago, mrteufel said: Hi @Luke, The rpms seem to be missing from the latest release https://github.com/MediaBrowser/Emby.Releases/releases/tag/4.6.5.0 Can they be added? Thanks! Hi, they're coming, thanks. 1 Link to comment Share on other sites More sharing options...
Bun_Bun 4 Posted February 11, 2023 Share Posted February 11, 2023 On 3/2/2020 at 11:15 AM, Xnet Project said: As a suggestion you may want to include the following in the setup instructions: This will eliminate confusion for RPM installs. This should be added to the install instructions. Fresh CentOS 7 install fails to start because while the user emby owns the data directory, there are no permissions allowed on the directory. I figured it out on my own, but I bet many users would get stumped here. chmod 755 /var/lib/emby systemctl restart emby-server 1 Link to comment Share on other sites More sharing options...
Stevepruebas 0 Posted February 4 Share Posted February 4 OS: CentOS 7, up to date. Installed Emby: 4.7.14.0 (stable) Hi! I'm trying to update to 4.8.0.80 (stable), but it seems my centOS 7 is too old: [root@server ~]# yum install https://github.com/MediaBrowser/Emby.Releases/releases/download/4.8.0.80/emby-server-rpm_4.8.0.80_x86_64.rpm Loaded plugins: fastestmirror, langpacks emby-server-rpm_4.8.0.80_x86_64.rpm | 157 MB 00:00:01 Examining /var/tmp/yum-root-fZwD2T/emby-server-rpm_4.8.0.80_x86_64.rpm: emby-server-4.8.0.80-1.x86_64 Marking /var/tmp/yum-root-fZwD2T/emby-server-rpm_4.8.0.80_x86_64.rpm as an update to emby-server-4.7.14.0-1.x86_64 Resolving Dependencies --> Running transaction check ---> Package emby-server.x86_64 0:4.7.14.0-1 will be updated ---> Package emby-server.x86_64 0:4.8.0.80-1 will be an update --> Processing Dependency: libc.so.6(GLIBC_2.18)(64bit) for package: emby-server-4.8.0.80-1.x86_64 Loading mirror speeds from cached hostfile * base: mirrors * epel: mirrors * extras: mirrors * nux-dextop: mirror.li.nux.ro * updates: ftp.plusline.net --> Processing Dependency: libc.so.6(GLIBC_2.22)(64bit) for package: emby-server-4.8.0.80-1.x86_64 --> Processing Dependency: libc.so.6(GLIBC_2.25)(64bit) for package: emby-server-4.8.0.80-1.x86_64 --> Processing Dependency: libc.so.6(GLIBC_2.27)(64bit) for package: emby-server-4.8.0.80-1.x86_64 --> Processing Dependency: libm.so.6(GLIBC_2.27)(64bit) for package: emby-server-4.8.0.80-1.x86_64 --> Processing Dependency: libmvec.so.1(GLIBC_2.22)(64bit) for package: emby-server-4.8.0.80-1.x86_64 --> Processing Dependency: libpthread.so.0(GLIBC_2.18)(64bit) for package: emby-server-4.8.0.80-1.x86_64 --> Processing Dependency: libmvec.so.1()(64bit) for package: emby-server-4.8.0.80-1.x86_64 --> Finished Dependency Resolution Error: Package: emby-server-4.8.0.80-1.x86_64 (/emby-server-rpm_4.8.0.80_x86_64) Requires: libpthread.so.0(GLIBC_2.18)(64bit) Error: Package: emby-server-4.8.0.80-1.x86_64 (/emby-server-rpm_4.8.0.80_x86_64) Requires: libmvec.so.1()(64bit) Error: Package: emby-server-4.8.0.80-1.x86_64 (/emby-server-rpm_4.8.0.80_x86_64) Requires: libc.so.6(GLIBC_2.22)(64bit) Error: Package: emby-server-4.8.0.80-1.x86_64 (/emby-server-rpm_4.8.0.80_x86_64) Requires: libc.so.6(GLIBC_2.25)(64bit) Error: Package: emby-server-4.8.0.80-1.x86_64 (/emby-server-rpm_4.8.0.80_x86_64) Requires: libmvec.so.1(GLIBC_2.22)(64bit) Error: Package: emby-server-4.8.0.80-1.x86_64 (/emby-server-rpm_4.8.0.80_x86_64) Requires: libc.so.6(GLIBC_2.27)(64bit) Error: Package: emby-server-4.8.0.80-1.x86_64 (/emby-server-rpm_4.8.0.80_x86_64) Requires: libm.so.6(GLIBC_2.27)(64bit) Error: Package: emby-server-4.8.0.80-1.x86_64 (/emby-server-rpm_4.8.0.80_x86_64) Requires: libc.so.6(GLIBC_2.18)(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest my GLIBC version is the latest: [root@server ~]# yum install glibc Package glibc-2.17-326.el7_9.x86_64 already installed and latest version Nothing to do Is there any workaround for this, or just abandon centOS ? Thanks! Link to comment Share on other sites More sharing options...
alucryd 213 Posted February 4 Share Posted February 4 I would recommended uprading to something like Rocky Linux or Alma Linux, as CentOS 7 is getting EOLed later this year. You could also switch to the docker image, or the Flatpak/Snap packages if upgrading is not an option. Making our RPM package compatible would require bypassing the system glibc and providing our own, in which case using docker would be the better option. 1 Link to comment Share on other sites More sharing options...
Stevepruebas 0 Posted February 4 Share Posted February 4 6 hours ago, alucryd said: I would recommended uprading to something like Rocky Linux or Alma Linux, as CentOS 7 is getting EOLed later this year. You could also switch to the docker image, or the Flatpak/Snap packages if upgrading is not an option. Making our RPM package compatible would require bypassing the system glibc and providing our own, in which case using docker would be the better option. Ok! I´ll try to use Flatpak/Snap, I need to move a lot of data before taking the "risk" of upgrading to another OS. I always thought docker images used more server resources than installing it straight on the OS (comparing other docker images, not tried with emby) Thanks for your help! Link to comment Share on other sites More sharing options...
alucryd 213 Posted February 5 Share Posted February 5 Docker uses slightly more resources, but it's not very much, it just introduces some potential network headaches that are mostly figured out nowadays. I'd still recommend Docker over Flatpak if you can, our Docker image is extremely lightweight, Flatpak will also be slightly more resource intensive as it runs in a sandbox with its own runtime, overall its footprint will be larger than our Docker image. 1 Link to comment Share on other sites More sharing options...
Stevepruebas 0 Posted February 9 Share Posted February 9 On 2/5/2024 at 10:21 AM, alucryd said: Docker uses slightly more resources, but it's not very much, it just introduces some potential network headaches that are mostly figured out nowadays. I'd still recommend Docker over Flatpak if you can, our Docker image is extremely lightweight, Flatpak will also be slightly more resource intensive as it runs in a sandbox with its own runtime, overall its footprint will be larger than our Docker image. Hello again! I made a fresh centos 7 install (for testing porpuses and then apply to another server) and installed emby-server using snap, but can't get it running: >> snap install emby-server >> snap list Name Version Rev Tracking Publisher Notes emby-server 4.8.1.0 18 latest/stable apps-z - >> snap start emby-server Failed Logs: 2024-02-09T19:16:10+01:00 systemd[1]: Started Service for snap application emby-server.emby-server. 2024-02-09T19:16:10+01:00 emby-server.emby-server[14059]: Failed to create CoreCLR, HRESULT: 0x80070008 2024-02-09T19:16:10+01:00 systemd[1]: snap.emby-server.emby-server.service: main process exited, code=exited, status=137/n/a 2024-02-09T19:16:10+01:00 systemd[1]: Unit snap.emby-server.emby-server.service entered failed state. 2024-02-09T19:16:10+01:00 systemd[1]: snap.emby-server.emby-server.service failed. It would be a pain in the ass to make a fresh AlmaLinux install... move all data... I didn't try anything, as I told, is a Centos 7 minimal install. It was working before with emby, no problem at all. Any clue? Thanks! Link to comment Share on other sites More sharing options...
Luke 36879 Posted February 9 Author Share Posted February 9 7 minutes ago, Stevepruebas said: Hello again! I made a fresh centos 7 install (for testing porpuses and then apply to another server) and installed emby-server using snap, but can't get it running: >> snap install emby-server >> snap list Name Version Rev Tracking Publisher Notes emby-server 4.8.1.0 18 latest/stable apps-z - >> snap start emby-server Failed Logs: 2024-02-09T19:16:10+01:00 systemd[1]: Started Service for snap application emby-server.emby-server. 2024-02-09T19:16:10+01:00 emby-server.emby-server[14059]: Failed to create CoreCLR, HRESULT: 0x80070008 2024-02-09T19:16:10+01:00 systemd[1]: snap.emby-server.emby-server.service: main process exited, code=exited, status=137/n/a 2024-02-09T19:16:10+01:00 systemd[1]: Unit snap.emby-server.emby-server.service entered failed state. 2024-02-09T19:16:10+01:00 systemd[1]: snap.emby-server.emby-server.service failed. It would be a pain in the ass to make a fresh AlmaLinux install... move all data... I didn't try anything, as I told, is a Centos 7 minimal install. It was working before with emby, no problem at all. Any clue? Thanks! Is that the complete log? Link to comment Share on other sites More sharing options...
Stevepruebas 0 Posted February 9 Share Posted February 9 2 minutes ago, Luke said: Is that the complete log? Yep. It seems to be a seccomp limitation, like in docker, related to memory limitations related to confinement. Link to comment Share on other sites More sharing options...
Stevepruebas 0 Posted February 19 Share Posted February 19 Hi! Tried again with other pc, snap is not working. I give up, will install AlmaLinux. Link to comment Share on other sites More sharing options...
Luke 36879 Posted February 20 Author Share Posted February 20 9 hours ago, Stevepruebas said: Hi! Tried again with other pc, snap is not working. I give up, will install AlmaLinux. Hi, what issue did you have with the snap package? Link to comment Share on other sites More sharing options...
Stevepruebas 0 Posted February 20 Share Posted February 20 (edited) 6 hours ago, Luke said: Hi, what issue did you have with the snap package? The one explained before, a few posts earlier. It seems to be a seccomp limitation, like in docker, related to memory limitations due to confinement. Maybe your team has to fix the snap package, or maybe is only my problem (or just happens to me). Edited February 20 by Stevepruebas Link to comment Share on other sites More sharing options...
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