Jump to content

DSM 6 - DS414 / ArmadaXP


horstepipe
Go to solution Solved by solabc16,

Recommended Posts

horstepipe

hey

catched my eye that in several boards people report the same problem:

Emby is unstartable on a Synology DS414 (or maybe on all armadaxp machines?) running DSM 6.

I start this thread in the hope that all affected people come together here so we might get attention by the devs.

I link this thread in all boards this error is reported.

So please report here,

thank you

 

Regards

Link to comment
Share on other sites

  • 3 weeks later...
hexagram

Hello,

 

I'm having a DS414 with DSM 5 for a while.

After the upgrade to DSM 6, i got the same issue, even if using the 5882 package

I made the modifcation for sudo with no effect

 

Kind regards,

Edited by hexagram
Link to comment
Share on other sites

I believe mono might be the problem.

 

SSH to your server, try to launch mono from the package:

/usr/local/bin/mono

 

I get a segfault.

 

install the official (synology) mono release, and give it a shot.

mono /usr/local/emby/share/emby/MediaBrowser.Server.Mono.exe
 

works for me (so far!), since I basically f***ed up my setup, I have to reindex everything but hey ... it might works.

 

btw, I used the 5881 package.

 

 

configuring properly is left as an exercise (if it works), something similar to: https://github.com/SynoCommunity/spksrc/issues/2207 (search for mono, Sonarr is also a .NET app, so same problem).

  • Like 1
Link to comment
Share on other sites

hexagram

Hello,

 

You right, i got a segfault too ! And for me that's a good newss, i will try with the other package from xamarin !

 

# ./mono
Segmentation fault (core dumped)

Link to comment
Share on other sites

hexagram

You right, after modifying the start-stop-status script to point to Xamarin mono package, it's working like a charm ! ;)

Thanks for your help ! It's a good workaround !

The "not that good" thing is that we still need to have the other mono from synocommunity installed because of the dependency.

I'm trying to upgrade to 5911 now...

  • Like 1
Link to comment
Share on other sites

horstepipe

oh that's sounds like good news, will try it later today.

Anything else to keep in mind?

 

Editing sudoers is not needed by force when I edit the files via putty, right?

Edited by horstepipe
Link to comment
Share on other sites

metarded

To avoid rescraping your content, edit the MediaBrowser.Server.Mono.exe.config in the emby/share/emby folder. Change both "ProgramData-Server" to the location of your data. In my case "/usr/local/emby/var/" or else emby will create the folder ProgramData-Server in emby/share/emby and put your data there. Or I guess you can copy your content to ProgramData-Server.

Link to comment
Share on other sites

horstepipe

is it really necessary to install both mono versions? Can't the dependencies be adjusted like it is described here by baskient?

https://github.com/SynoCommunity/spksrc/pull/1673#issuecomment-199728872

 

 

Hi there,
just wanted to let you guys know that I love emby. I was using it before my nas (Synology DiskStation DS215j) updated to DSM 6 automatically last night. Now it stopped working.There is no FFMPEG package for my nas so I ended up editing the dependencies of the info file of the emby_armada375 package to remove the FFMPEG dependencies. I have been using it in that way in kodi for quite some time. So in theory FFMPEG is not mandatory if you are playing the files in kodi through a direct network link. So would it be possible for me to run this new package that should be working under DSM 6 without the FFMPEG dependency?

Edited by horstepipe
Link to comment
Share on other sites

hexagram

mhh I installed Mono by Xamarin but can't start it via package center

Ok, you have the strange thing i got before.

 (i thought i made a mistake, but if you have the same, it's more a problem with the package).

For me, uninstall and reinstall resolve the problem .

Link to comment
Share on other sites

hexagram

is it really necessary to install both mono versions? Can't the dependencies be adjusted like it is described here by baskient?

https://github.com/SynoCommunity/spksrc/pull/1673#issuecomment-199728872

Yes, the other mono (xamarin) is not the one that will be checked.

The package can be modified but i don't have the method (i'm used to compiling) to do it from the emby sources.

  • Like 1
Link to comment
Share on other sites

horstepipe

hmmm

I edited the emby start-stop-status file as follows:

MONO_PATH="/volume1/@appstore/Mono/usr/bin"

I can start mono from synocommunity, but not from Xamarin, even after several reinstallations.

At least now I can start emby via package centre (shows "running"), but trying to access it via standard port doesn't work

Link to comment
Share on other sites

hexagram

oh that's sounds like good news, will try it later today.

Anything else to keep in mind?

 

Editing sudoers is not needed by force when I edit the files via putty, right?

Sudo has nothing to do with it in my opinion.

Your Admin account should be sufficient.

I had deleted the line but after install.

  • Like 1
Link to comment
Share on other sites

hexagram

hmmm

I edited the emby start-stop-status file as follows:

MONO_PATH="/volume1/@appstore/Mono/usr/bin"

I can start mono from synocommunity, but not from Xamarin, even after several reinstallations.

At least now I can start emby via package centre (shows "running"), but trying to access it via standard port doesn't work

56fd172c92503_mono.png

 

As you can see, i have both running.

So let's try like this :

1/ uninstall xamarin mono

2/ uninstall synocommunity mono

3/ install xamarin mono

4/ install synocommunity mono

 

With those steps, it's still not functional ?

  • Like 1
Link to comment
Share on other sites

horstepipe

restarted Emby package and now it's accessible, although only one Mono is running according to package centre.

I'll try to setup Emby now, let's see if I run into more trouble :D

 

thank you for support

Link to comment
Share on other sites

hexagram

hmmm

I edited the emby start-stop-status file as follows:

MONO_PATH="/volume1/@appstore/Mono/usr/bin"

I can start mono from synocommunity, but not from Xamarin, even after several reinstallations.

At least now I can start emby via package centre (shows "running"), but trying to access it via standard port doesn't work

waitwaitwait... mine is different and maybe it's due to this

The mono binary from xamarin is not in the same place

MONO_PATH="/var/packages/Mono/target/usr/bin"

I verified on my NAS and it does not make any difference, those two paths are ok

Edited by hexagram
Link to comment
Share on other sites

hexagram

restarted Emby package and now it's accessible, although only one Mono is running according to package centre.

I'll try to setup Emby now, let's see if I run into more trouble :D

 

thank you for support

you welcome.

emby is based on his start-stop-status only, it does not care if the two are running or not

Link to comment
Share on other sites

horstepipe

Yes, the other mono (xamarin) is not the one that will be checked.

The package can be modified but i don't have the method (i'm used to compiling) to do it from the emby sources.

shouldn't it be enough to edit the "INFO" file in

/var/packages/Mono/

(the one with the capital letter is the xamarin package)

here are the dependencies stored.

  • Like 1
Link to comment
Share on other sites

horstepipe

ops sorry, for sure I mean editing this INFO file

/var/packages/emby/INFO

editing the line

install_dep_packages="mono>3.6:imagemagick>=6.9.0-1:mediainfo>=0.7.72-1:ffmpeg>=2.6-3"

to

install_dep_packages="Mono>3.6:imagemagick>=6.9.0-1:mediainfo>=0.7.72-1:ffmpeg>=2.6-3"
Edited by horstepipe
Link to comment
Share on other sites

hexagram

shouldn't it be enough to edit the "INFO" file in

/var/packages/Mono/

(the one with the capital letter is the xamarin package)

here are the dependencies stored.

Good tip ! i edited emby INFO file :

root@Syn:/var/packages/emby# vi INFO

Modified the dep_packages line to match the xamarin mono (which package name is "Mono" and not "mono"):

package="emby"
version="3.0.5882.0-6"
description="Emby streams everything Your personal videos, music, photos, and live television in the palm of your hand."

arch="armadaxp"
distributor="SynoCommunity"
distributor_url="http://synocommunity.com"
maintainer="SynoCommunity"
maintainer_url="http://synocommunity.com"
firmware="DSM 6.0-7307"
report_url="https://github.com/SynoCommunity/spksrc/issues"
reloadui="yes"
displayname="Emby"
dsmuidir="app"
adminport="8096"
changelog="Update emby to 3.0.5882.0"
install_dep_packages="Mono>3.6:imagemagick>=6.9.0-1:mediainfo>=0.7.72-1:ffmpeg>=2.6-3"

And Mono synocommunity can be uninstalled :)

Edited by hexagram
Link to comment
Share on other sites

hexagram

 

ops sorry, for sure I mean editing this INFO file

/var/packages/emby/INFO

editing the line

install_dep_packages="mono>3.6:imagemagick>=6.9.0-1:mediainfo>=0.7.72-1:ffmpeg>=2.6-3"

to

install_dep_packages="Mono>3.6:imagemagick>=6.9.0-1:mediainfo>=0.7.72-1:ffmpeg>=2.6-3"

lol we made the same change ;)

  • Like 1
Link to comment
Share on other sites

horstepipe

ahh damn I can't remove the second mono because the other one is not marked as started, so Emby won't start :-/

Removing it completely from the dependency list unfortunately doesn't work, either

Edited by horstepipe
Link to comment
Share on other sites

hexagram

ahh damn I can't remove the second mono because the other one is not marked as started, so Emby won't start :-/

Removing it completely from the dependency list unfortunately doesn't work, either

Did you tried my method mentionned before to resolve that problem ?

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...