88fingerslukee 2 Posted August 4, 2015 Share Posted August 4, 2015 We are actively working in new packages for CentOS and Fedora. I hope we will be able to deliver something soon. Awesome, thanks! Link to comment Share on other sites More sharing options...
Luke 36999 Posted August 8, 2015 Author Share Posted August 8, 2015 Ok guys, heads up. There are new CentOS and Fedora download instructions on the website, thanks to the help of @@fc7! This is a brand new package so you'll need to decide between upgrading and installing fresh. If you would like to upgrade, fc7 has prepared a procedure for that, and it is as follows: If upgrading from older Emby packages (as root):systemctl stop MediaBrowserServer systemctl stop emby ORservice MediaBrowserServer stop service emby stop yum remove ImageMagick ImageMagick-libs MediaBrowserServer mono-opt mono-opt-devel libgdiplus libwebp5 MediaBrowserServer-repositories emby-server-corewget http://download.open...ies/home:/emby//home:emby.repo -O /etc/yum.repos.d/emby.repo yum clean allyum update sqliteyum install emby-serversystemctl start emby-server ORservice emby-server start *Replace with: CentOS_6, CentOS_7, Fedora_20 or Fedora_21. Depending on your distribution release.** Your old library, users, settings, metadata will be kept in the original data location (/var/opt), untouched, but they will also be duplicated and migrated to new data location (/var/lib). After upgrading and verifying that all the information was migrated correctly you can safely remove the old library path to same some space. Link to comment Share on other sites More sharing options...
fc7 123 Posted August 9, 2015 Share Posted August 9, 2015 Any feedback you can provide after installing or upgrading (working smoothly or giving you problems) will be highly appreciated to enhance the packages quality. Thanks. Sent from my iPad using Tapatalk Link to comment Share on other sites More sharing options...
jvandy7 0 Posted August 9, 2015 Share Posted August 9, 2015 I ran into the wrong permissions on the /etc/init.d/emby-server file: -rw-r--r-- 1 root root 2753 Aug 9 11:44 emby-server I'm also missing a server.conf file: [root@bobafett ~]# service emby-server start/etc/init.d/emby-server: line 19: /root/.emby-server/server.conf: No such file or directory Link to comment Share on other sites More sharing options...
fc7 123 Posted August 9, 2015 Share Posted August 9, 2015 Thanks a lot for the feedback @@jvandy7 we will check this and fix it. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
88fingerslukee 2 Posted August 9, 2015 Share Posted August 9, 2015 Thanks a lot for the feedback @@jvandy7 we will check this and fix it. Sent from my iPhone using Tapatalk I can confirm the init script permission issue on the Fedora 21 packages but I didn't see the other error. Everything is running smoothly it seems. Link to comment Share on other sites More sharing options...
fc7 123 Posted August 9, 2015 Share Posted August 9, 2015 Excellent. Fedora 21 is not using that script since it uses systemd. Thanks for the feedback! Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
fc7 123 Posted August 9, 2015 Share Posted August 9, 2015 I ran into the wrong permissions on the /etc/init.d/emby-server file: -rw-r--r-- 1 root root 2753 Aug 9 11:44 emby-server I'm also missing a server.conf file: [root@bobafett ~]# service emby-server start /etc/init.d/emby-server: line 19: /root/.emby-server/server.conf: No such file or directory Can you confirm if creating an empty server.conf file in /root/.emby-server will start Emby and it works fine? Also, I guess you are running CentOS 6.x, but can you confirm this? Thanks Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
jvandy7 0 Posted August 9, 2015 Share Posted August 9, 2015 I'm using CentOS 6.7 lsb_release -aLSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarchDistributor ID: CentOSDescription: CentOS release 6.7 (Final)Release: 6.7Codename: Final I created the file, but it still doesn't start: # service emby-server start /etc/init.d/emby-server: line 30: [: {:=/opt/emby-server}/emby-server.sh: binary operator expected Link to comment Share on other sites More sharing options...
jvandy7 0 Posted August 9, 2015 Share Posted August 9, 2015 The binary is thrown because of the EXEC defined in the init script. Once I changed that to the execute check and added the flag to the command, I could get a bit farther. The /opt/emby-server/emy-server.sh script looks to reference mono in /bin, and I have mono in /usr/bin. I take it $mono_path gets set in one of the configuration files that gets sourced from the init script /opt/emby-server/emby-server.sh: line 31: /bin/mono: No such file or directory/opt/emby-server/emby-server.sh: line 31: exec: /bin/mono: cannot execute: No such file or directory On another note, /etc/emby-server.conf is also blank. Link to comment Share on other sites More sharing options...
fc7 123 Posted August 9, 2015 Share Posted August 9, 2015 Thanks for the information. One more question. You installed mono from Emby repo correct? Anyway, I will fix it in the coming days Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
jvandy7 0 Posted August 9, 2015 Share Posted August 9, 2015 Thanks for the information. One more question. You installed mono from Emby repo correct? Anyway, I will fix it in the coming days Sent from my iPhone using Tapatalk Correct, I installed mono from the Emby repo. I had removed all the previous versions that were included with mediabrowswer. per the directions posted earlier. Link to comment Share on other sites More sharing options...
fc7 123 Posted August 9, 2015 Share Posted August 9, 2015 Excellent. Thanks for the detailed information. I will work on this in the coming days. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
jvandy7 0 Posted August 9, 2015 Share Posted August 9, 2015 The binary is thrown because of the EXEC defined in the init script. Once I changed that to the execute check and added the flag to the command, I could get a bit farther. The /opt/emby-server/emy-server.sh script looks to reference mono in /bin, and I have mono in /usr/bin. I take it $mono_path gets set in one of the configuration files that gets sourced from the init script /opt/emby-server/emby-server.sh: line 31: /bin/mono: No such file or directory /opt/emby-server/emby-server.sh: line 31: exec: /bin/mono: cannot execute: No such file or directory On another note, /etc/emby-server.conf is also blank. Adding mono_path="/usr" to /etc/emby-server.conf did get it running My changes to /etc/init.d/emby-server 22: #EXEC="{$LauncherDir:=/opt/emby-server}/emby-server.sh -s" 23: #USER="{$EmbyUser:=emby}" 24: EXEC="/opt/emby-server/emby-server.sh" 25: USER="emby" 39: daemon --user $USER $EXEC -s > $LOGFILE 2>&1 & Link to comment Share on other sites More sharing options...
manf0001 4 Posted August 10, 2015 Share Posted August 10, 2015 (edited) Hi I'm using CentOS 7 Version 3.10.0-229.7.2el7.x86_64 I upgraded to the new version of emby. However I can't get it to start. When I run the command service emby-server start I am getting this output: env: /etc/init.d/emby-server:Permission denied I am running the command as root when I run ls -l for emby-server this is the permission output for that file. -rw-r--r-- 1 root root 2753 Aug 10 04:19 emby-server I changed the permission of the file to rwx across the board, and after I ran the service emby-server start command again it said emby-server started. However I am still unable to access the web interface for it. I've tried rebooting the machine and restarting the command but still no access via web interface TIA Edited August 10, 2015 by manf0001 Link to comment Share on other sites More sharing options...
fc7 123 Posted August 10, 2015 Share Posted August 10, 2015 Since you are running CentOS 7 you shouldn't be using SysV scripts but systemd. Please try: systemctl start emby-server. You can double check the instructions and use the systemd commands. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
manf0001 4 Posted August 10, 2015 Share Posted August 10, 2015 (edited) So when I run the command systemctl start emby-server it takes does the below output [root@@nas ~]# systemctl start emby-server [root@@nas ~]# I assume it started so I try to access emby and it still won't load. I came across the status command so I ran that and here is the output [root@@nas ~]# systemctl status emby-server emby-server.service - Emby Media Server Loaded: loaded (/etc/systemd/system/emby-server.service; disabled) Active: failed (Result: start-limit) since Mon 2015-08-10 05:27:01 EDT; 1s ago Process: 4406 ExecStopPost=/opt/emby-server/emby-server.sh -c (code=exited, status=0/SUCCESS) Process: 4393 ExecStart=/opt/emby-server/emby-server.sh -s (code=dumped, signal=ABRT) Main PID: 4393 (code=dumped, signal=ABRT) Aug 10 05:27:01 nas systemd[1]: Unit emby-server.service entered failed state. Aug 10 05:27:01 nas systemd[1]: emby-server.service holdoff time over, scheduling restart. Aug 10 05:27:01 nas systemd[1]: Stopping Emby Media Server... Aug 10 05:27:01 nas systemd[1]: Starting Emby Media Server... Aug 10 05:27:01 nas systemd[1]: emby-server.service start request repeated too quickly, refusing to start. Aug 10 05:27:01 nas systemd[1]: Failed to start Emby Media Server. Aug 10 05:27:01 nas systemd[1]: Unit emby-server.service entered failed state. [root@@nas ~]# And I have also restarted my server completly and re ran the start command and I still get the same results in the status. When installing it there were no issues that arose Edited August 10, 2015 by manf0001 Link to comment Share on other sites More sharing options...
fc7 123 Posted August 10, 2015 Share Posted August 10, 2015 (edited) Can you share some system logs and emby logs aswell? Are you upgrading or is it a fresh install? Sent from my iPhone using Tapatalk Edited August 10, 2015 by fc7 Link to comment Share on other sites More sharing options...
manf0001 4 Posted August 10, 2015 Share Posted August 10, 2015 (edited) Can you share some system logs and emby logs aswell? Are you upgrading or is it a fresh install? Sent from my iPhone using Tapatalk Please forgive me, but where do I find the logs? I'm still learning Linux. I did an upgrade.. it wasn't an upgrade from MediaBrowser, but from an Emby install that I did from this page http://emby.media/community/index.php?/topic/13398-fedoracentos-rpm/?p=221256 Edited August 10, 2015 by manf0001 Link to comment Share on other sites More sharing options...
jvandy7 0 Posted August 10, 2015 Share Posted August 10, 2015 So when I run the command systemctl start emby-server it takes does the below output [root@@nas ~]# systemctl start emby-server [root@@nas ~]# I assume it started so I try to access emby and it still won't load. I came across the status command so I ran that and here is the output [root@@nas ~]# systemctl status emby-server emby-server.service - Emby Media Server Loaded: loaded (/etc/systemd/system/emby-server.service; disabled) Active: failed (Result: start-limit) since Mon 2015-08-10 05:27:01 EDT; 1s ago Process: 4406 ExecStopPost=/opt/emby-server/emby-server.sh -c (code=exited, status=0/SUCCESS) Process: 4393 ExecStart=/opt/emby-server/emby-server.sh -s (code=dumped, signal=ABRT) Main PID: 4393 (code=dumped, signal=ABRT) Aug 10 05:27:01 nas systemd[1]: Unit emby-server.service entered failed state. Aug 10 05:27:01 nas systemd[1]: emby-server.service holdoff time over, scheduling restart. Aug 10 05:27:01 nas systemd[1]: Stopping Emby Media Server... Aug 10 05:27:01 nas systemd[1]: Starting Emby Media Server... Aug 10 05:27:01 nas systemd[1]: emby-server.service start request repeated too quickly, refusing to start. Aug 10 05:27:01 nas systemd[1]: Failed to start Emby Media Server. Aug 10 05:27:01 nas systemd[1]: Unit emby-server.service entered failed state. [root@@nas ~]# And I have also restarted my server completly and re ran the start command and I still get the same results in the status. When installing it there were no issues that arose This is similar to what happened to me with the mono path. Run: which mono If it shows up as /usr/bin/mono then edit the /etc/emby-server.conf by adding: mono_path="/usr" Link to comment Share on other sites More sharing options...
jdepth 0 Posted August 10, 2015 Share Posted August 10, 2015 (edited) So when I run the command systemctl start emby-server it takes does the below output [root@@nas ~]# systemctl start emby-server [root@@nas ~]# I assume it started so I try to access emby and it still won't load. I came across the status command so I ran that and here is the output [root@@nas ~]# systemctl status emby-server emby-server.service - Emby Media Server Loaded: loaded (/etc/systemd/system/emby-server.service; disabled) Active: failed (Result: start-limit) since Mon 2015-08-10 05:27:01 EDT; 1s ago Process: 4406 ExecStopPost=/opt/emby-server/emby-server.sh -c (code=exited, status=0/SUCCESS) Process: 4393 ExecStart=/opt/emby-server/emby-server.sh -s (code=dumped, signal=ABRT) Main PID: 4393 (code=dumped, signal=ABRT) Aug 10 05:27:01 nas systemd[1]: Unit emby-server.service entered failed state. Aug 10 05:27:01 nas systemd[1]: emby-server.service holdoff time over, scheduling restart. Aug 10 05:27:01 nas systemd[1]: Stopping Emby Media Server... Aug 10 05:27:01 nas systemd[1]: Starting Emby Media Server... Aug 10 05:27:01 nas systemd[1]: emby-server.service start request repeated too quickly, refusing to start. Aug 10 05:27:01 nas systemd[1]: Failed to start Emby Media Server. Aug 10 05:27:01 nas systemd[1]: Unit emby-server.service entered failed state. [root@@nas ~]# And I have also restarted my server completly and re ran the start command and I still get the same results in the status. When installing it there were no issues that arose I'm having this same issue and it doesn't have anything to do with the mono config path. My mono binary is at /bin/mono as the startup script expects. Here is the error in the system log which may shed some light on the issue: Aug 10 14:45:49 <localhost> systemd: Starting Emby Media Server... Aug 10 14:45:49 <localhost> systemd: Started Emby Media Server. Aug 10 14:45:49 <localhost> emby-server.sh: Reading system-wide config.... Aug 10 14:45:49 <localhost> emby-server.sh: Can't find custom attr constructor image: /opt/emby-server/bin/NLog.dll mtoken: 0x0a000359 Aug 10 14:45:49 <localhost> emby-server.sh: Can't find custom attr constructor image: /opt/emby-server/bin/NLog.dll mtoken: 0x0a000359 Aug 10 14:45:49 <localhost> emby-server.sh: Can't find custom attr constructor image: /opt/emby-server/bin/NLog.dll mtoken: 0x0a000359 Aug 10 14:45:49 <localhost> emby-server.sh: Can't find custom attr constructor image: /opt/emby-server/bin/NLog.dll mtoken: 0x0a000359 Aug 10 14:45:49 <localhost> emby-server.sh: Can't find custom attr constructor image: /opt/emby-server/bin/NLog.dll mtoken: 0x0a000359 Aug 10 14:45:49 <localhost> emby-server.sh: Can't find custom attr constructor image: /opt/emby-server/bin/NLog.dll mtoken: 0x0a000359 Aug 10 14:45:49 <localhost> emby-server.sh: Can't find custom attr constructor image: /opt/emby-server/bin/NLog.dll mtoken: 0x0a000359 Aug 10 14:45:49 <localhost> emby-server.sh: Can't find custom attr constructor image: /opt/emby-server/bin/NLog.dll mtoken: 0x0a000359 Aug 10 14:45:49 <localhost> emby-server.sh: Can't find custom attr constructor image: /opt/emby-server/bin/NLog.dll mtoken: 0x0a000359 Aug 10 14:45:49 <localhost> emby-server.sh: * Assertion at loader.c:1153, condition `!mono_loader_get_last_error ()' not met Aug 10 14:45:49 <localhost> emby-server.sh: Stacktrace: Aug 10 14:45:49 <localhost> emby-server.sh: at <unknown> <0xffffffff> Aug 10 14:45:49 <localhost> emby-server.sh: at (wrapper managed-to-native) System.MonoCustomAttrs.IsDefinedInternal (System.Reflection.ICustomAttributeProvider,System.Type) <0xffffffff> Aug 10 14:45:49 <localhost> emby-server.sh: at System.MonoCustomAttrs.IsDefined (System.Reflection.ICustomAttributeProvider,System.Type,bool) <0x00081> Aug 10 14:45:49 <localhost> emby-server.sh: at System.MonoType.IsDefined (System.Type,bool) <0x00023> Aug 10 14:45:49 <localhost> emby-server.sh: at NLog.Config.MethodFactory`2.RegisterType (System.Type,string) <0x00051> Aug 10 14:45:49 <localhost> emby-server.sh: at NLog.Config.MethodFactory`2.ScanTypes (System.Type[],string) <0x00088> Aug 10 14:45:49 <localhost> emby-server.sh: at NLog.Config.ConfigurationItemFactory.RegisterItemsFromAssembly (System.Reflection.Assembly,string) <0x001a4> Aug 10 14:45:49 <localhost> emby-server.sh: at NLog.Config.ConfigurationItemFactory.RegisterItemsFromAssembly (System.Reflection.Assembly) <0x0002a> Aug 10 14:45:49 <localhost> emby-server.sh: at NLog.Config.ConfigurationItemFactory..ctor (System.Reflection.Assembly[]) <0x0055f> Aug 10 14:45:49 <localhost> emby-server.sh: at NLog.Config.ConfigurationItemFactory.BuildDefaultFactory () <0x00095> Aug 10 14:45:49 <localhost> emby-server.sh: at NLog.Config.ConfigurationItemFactory..cctor () <0x00010> Aug 10 14:45:49 <localhost> emby-server.sh: at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff> Aug 10 14:45:49 <localhost> emby-server.sh: at <unknown> <0xffffffff> Aug 10 14:45:49 <localhost> emby-server.sh: at NLog.Layouts.Layout.FromString (string) <0x00014> Aug 10 14:45:49 <localhost> emby-server.sh: at NLog.Layouts.Layout.op_Implicit (string) <0x00014> Aug 10 14:45:49 <localhost> emby-server.sh: at NLog.Targets.TargetWithLayout..ctor () <0x00075> Aug 10 14:45:49 <localhost> emby-server.sh: at NLog.Targets.TargetWithLayoutHeaderAndFooter..ctor () <0x00014> Aug 10 14:45:49 <localhost> emby-server.sh: at NLog.Targets.FileTarget..ctor () <0x00085> Aug 10 14:45:49 <localhost> emby-server.sh: at MediaBrowser.Common.Implementations.Logging.NlogManager.AddFileTarget (string,MediaBrowser.Model.Logging.LogSeverity) <0x000d4> Aug 10 14:45:49 <localhost> emby-server.sh: at MediaBrowser.Common.Implementations.Logging.NlogManager.ReloadLogger (MediaBrowser.Model.Logging.LogSeverity) <0x0022d> Aug 10 14:45:49 <localhost> emby-server.sh: at MediaBrowser.Server.Mono.MainClass.Main (string[]) <0x0010e> Aug 10 14:45:49 <localhost> emby-server.sh: at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) <0xffffffff> Aug 10 14:45:49 <localhost> emby-server.sh: Native stacktrace: Aug 10 14:45:49 <localhost> emby-server.sh: /bin/mono() [0x4b8fa2] Aug 10 14:45:49 <localhost> emby-server.sh: /lib64/libpthread.so.0(+0xf130) [0x7f9a36187130] Aug 10 14:45:49 <localhost> emby-server.sh: /lib64/libc.so.6(gsignal+0x37) [0x7f9a35bd65d7] Aug 10 14:45:49 <localhost> emby-server.sh: /lib64/libc.so.6(abort+0x148) [0x7f9a35bd7cc8] Aug 10 14:45:49 <localhost> emby-server.sh: /bin/mono() [0x6350b9] Aug 10 14:45:49 <localhost> emby-server.sh: /bin/mono() [0x63532c] Aug 10 14:45:49 <localhost> emby-server.sh: /bin/mono() [0x6354c3] Aug 10 14:45:49 <localhost> emby-server.sh: /bin/mono() [0x54f672] Aug 10 14:45:49 <localhost> emby-server.sh: /bin/mono() [0x54f714] Aug 10 14:45:49 <localhost> emby-server.sh: /bin/mono() [0x54fdc0] Aug 10 14:45:49 <localhost> emby-server.sh: /bin/mono(mono_get_method_full+0x23) [0x54ff13] Aug 10 14:45:49 <localhost> emby-server.sh: /bin/mono(mono_custom_attrs_from_index+0x128) [0x5bfb18] Aug 10 14:45:49 <localhost> emby-server.sh: /bin/mono() [0x543f25] Aug 10 14:45:49 <localhost> emby-server.sh: [0x41fa6943] Aug 10 14:45:49 <localhost> emby-server.sh: Debug info from gdb: Aug 10 14:45:49 <localhost> emby-server.sh: ================================================================= Aug 10 14:45:49 <localhost> emby-server.sh: Got a SIGABRT while executing native code. This usually indicates Aug 10 14:45:49 <localhost> emby-server.sh: a fatal error in the mono runtime or one of the native libraries Aug 10 14:45:49 <localhost> emby-server.sh: used by your application. Aug 10 14:45:49 <localhost> emby-server.sh: ================================================================= Aug 10 14:45:49 <localhost> systemd: emby-server.service: main process exited, code=killed, status=6/ABRT Aug 10 14:45:49 <localhost> emby-server.sh: Reading system-wide config.... Aug 10 14:45:49 <localhost> emby-server.sh: Removing PID FILE Aug 10 14:45:49 <localhost> systemd: Unit emby-server.service entered failed state. Aug 10 14:45:49 <localhost> systemd: emby-server.service holdoff time over, scheduling restart. Aug 10 14:45:49 <localhost> systemd: Stopping Emby Media Server... Edited August 10, 2015 by jdepth Link to comment Share on other sites More sharing options...
fc7 123 Posted August 10, 2015 Share Posted August 10, 2015 (edited) Are you also upgrading? Also can any of you confirm if you follow the upgrade procedures including the removal of the old packages and stopping Emby before doing it? Sent from my iPhone using Tapatalk Edited August 10, 2015 by fc7 Link to comment Share on other sites More sharing options...
jdepth 0 Posted August 10, 2015 Share Posted August 10, 2015 Are you also upgrading? Also can any of you confirm if you follow the upgrade procedures including the removal of the old packages and stopping Emby before doing it? Sent from my iPhone using Tapatalk I'm not upgrading per se. I had been trying to get the latest emby version running with a self-built version of ImageMagick and mono from their repo. I did remove those versions and installed the versions from the emby repo. Link to comment Share on other sites More sharing options...
fc7 123 Posted August 10, 2015 Share Posted August 10, 2015 I faced a similar issue during testing of the packages. A couldn't find a root cause but after several tests I found that if I remove all the old packages before installing the new ones (previously making sure Emby wasn't running) the issue didn't reproduce. Having said that to be honest I can't tell why sometimes mono gives this error. Maybe some developer will read this and throw some light. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
fc7 123 Posted August 10, 2015 Share Posted August 10, 2015 @@manf0001 and @jdepth: can you guys confirm if mono binaries are present under /bin but also under /usr/bin? Example: ll /bin/mono and compare with ll /usr/bin/mono. Thanks Sent from my iPhone using Tapatalk 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