emby inside chroot

[diogosena 0]

hi, im trying to use emby inside a chroot because i want to run on a linux stb.

what's the correct way to startup the server inside a chroot ? (i assume systemd doesnt work)

[Luke 42077]

Hi, welcome. I've forwarded this question to our developer who handles the packaging. Please be aware he's out this week so you may not get an answer until next week. Thanks.

[alucryd 315]

Could you be more specific? What kind of chroot on what distribution and architecture? If systemd doesn't work you can just manually run the ExecStart line from the service unit file.

[diogosena 0]

my stb is running enigma2 openatv (armhf and rc.d and init.d based),

I made a debian stretch chroot, so I can install emby there.

for now I'm running using this line, but it's crashing sometimes, thats why i want to know the correct way.

 

chroot /mnt/sda2/debian/binary/ /opt/emby-server/bin/emby-server &

[dcrdev 255]

my stb is running enigma2 openatv (armhf and rc.d and init.d based),

I made a debian stretch chroot, so I can install emby there.

for now I'm running using this line, but it's crashing sometimes, thats why i want to know the correct way.

 

chroot /mnt/sda2/debian/binary/ /opt/emby-server/bin/emby-server &

 

Have  you bound the kernels virtual filesystem(s) to the chroot's filesystem beforehand?

 

Other than that - the line from ExecStart is the correct way of running it...

 

Although you obviously aren't going to  be wanting to run it as root, you'll want to run it as a normal user - for example the one that gets created when you install the package i.e. "emby".

[diogosena 0]

Have  you bound the kernels virtual filesystem(s) to the chroot's filesystem beforehand?

 

Other than that - the line from ExecStart is the correct way of running it...

 

Although you obviously aren't going to  be wanting to run it as root, you'll want to run it as a normal user - for example the one that gets created when you install the package i.e. "emby".

 

i do these mounts before

 

mount --bind /proc /mnt/sda2/debian/binary/proc

mount --bind /tmp /mnt/sda2/debian/binary/tmp

mount --bind /sys /mnt/sda2/debian/binary/sys

mount --bind /dev /mnt/sda2/debian/binary/dev

mount --bind /dev/pts /mnt/sda2/debian/binary/dev/pts

mount --bind /dev/pts /mnt/sda2/debian/binary/dev/pts

mount --bind /media/sda2 /mnt/sda2/debian/binary/media/sda2

 

Thanks! seems the way I'm starting is ok,

I guess i just have to find out the reason for the crashes

Edited March 16, 2018 by diogosena

[Luke 42077]

Under what scenarios does it crash?

[diogosena 0]

i was messing around with every possible setting, maybe it was my fault..

It seems stable right now (2 days without crash).

Debug is already enabled, if it crashes again, I'll send you the logs, thank's!

Edited March 17, 2018 by diogosena

[Luke 42077]

Thanks for the feedback.

[diogosena 0]

Hi, restart button was not working too, 

I look around in the forum and found this flag "-restartpath /path/somescript.sh"

Just created a script to manual kill and start emby, and its all good!

 

Now I'm trying to make some kind of autoupdate.

[Luke 42077]

That command line params is no longer used in our new packages, fyi.

[diogosena 0]

i have to disagree, in latest beta it is working (please keep that way)

[Luke 42077]

Can you please provide an emby server log? it sounds like you are using our legacy installation package. thanks.

[diogosena 0]

Can you please provide an emby server log? it sounds like you are using our legacy installation package. thanks.

I reinstalled a clean version of deb package today, pretty sure i'm using the latest beta version.

 

I'm including my "personalized" emby_server file too.

server-63657077412.txt

emby-server.txt

[Luke 42077]

Ok yes this version of the server you have should be ignoring that restartpath param.

[diogosena 0]

Ok yes this version of the server you have should be ignoring that restartpath param.

Just restarted NOW, logs attached, before and after.

 

Do you really have to disable that? I think is needed in my use case (chroot manual run)

server-63657077412.txt

server-63657094685.txt

[Luke 42077]

it's not disabled, it's just obsolete at this point. We no longer have any use for it. 

[Luke 42077]

@@diogosena how is this going?

[diogosena 0]

@@diogosena how is this going?

 

Thanks for taking the interest, i have some problems:

 

That restart parameter is not working anymore, 

The DLNA server part of emby sometimes simply disappear from all my devices, restarting the process solves that. (since restart button is not working, that's very annoying)

It's not frequent, but I still have some crashes one day or the other.

 

How is the correct way do log that?

[Luke 42077]

Please attach the the emby server log from the time frame that you had a problem. Thanks.

[diogosena 0]

Please attach the the emby server log from the time frame that you had a problem. Thanks.

 

just got a freeze, one of my cpu cores is stuck at 100, and can't access anything emby related.

if you need to check anything, its still running

server-63657705601.txt

server-63657693329.txt

Edited March 27, 2018 by diogosena

[Luke 42077]

You could try removing those installed plugins and see if that has any impact.

[diogosena 0]

Hi, @@Luke Dlna crash when trying to play

The log is with debug enabled.

embyserver.txt

[Luke 42077]

Can you please define crashed? Thanks.

[diogosena 0]

Can you please define crashed? Thanks.

 

Tried to play something trough DLNA directly to my TV and didn't worked, then I can't find the dlna server (I assume the dlna server part crashed)