Jump to content

Emby-server don't start after upgrade


Przemek

Recommended Posts

Hello, some time ago I move my Emby installation from broken sd-card to new one (copy `/var/lib/emby` and `/opt/emby-server` folders). I add permissions and everything was fine.
Today when I see notice that there's new release for upgrade so I enter ssh to my Dietpi and run as always `dietpi-software reinstall 41`. That install new version of Emby server but it won't start. 

 

root@DietPi:/home/dietpi# dietpi-services status
[ SUB1 ] DietPi-Services > status
[ OK ] DietPi-Services | avahi-daemon active (running) since Thu 2020-12-17 17:00:37 CET; 1h 37min ago
[ OK ] DietPi-Services | proftpd active (running) since Thu 2020-12-17 17:00:37 CET; 1h 37min ago
[ OK ] DietPi-Services | nfs-kernel-server active (exited) since Thu 2020-12-17 17:00:39 CET; 1h 37min ago
[ OK ] DietPi-Services | redis-server active (running) since Thu 2020-12-17 17:00:39 CET; 1h 37min ago
[ OK ] DietPi-Services | mariadb active (running) since Thu 2020-12-17 17:00:41 CET; 1h 37min ago
[ OK ] DietPi-Services | php7.3-fpm active (running) since Thu 2020-12-17 17:00:42 CET; 1h 37min ago
[ OK ] DietPi-Services | lighttpd active (running) since Thu 2020-12-17 17:00:42 CET; 1h 37min ago
[FAILED] DietPi-Services | ● 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; disabled; vendor preset: enabled)
Active: failed (Result: signal) since Thu 2020-12-17 17:00:43 CET; 1h 37min ago
Process: 821 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=SEGV)
Main PID: 821 (code=killed, signal=SEGV)

Dec 17 17:00:42 DietPi systemd[1]: Started Emby Server is a personal media server with apps on just about every device..
Dec 17 17:00:43 DietPi systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Dec 17 17:00:43 DietPi systemd[1]: emby-server.service: Failed with result 'signal'.
[ OK ] DietPi-Services | medusa active (running) since Thu 2020-12-17 17:00:43 CET; 1h 37min ago
[ OK ] DietPi-Services | jackett active (running) since Thu 2020-12-17 17:00:43 CET; 1h 37min ago
[ OK ] DietPi-Services | noip2 active (running) since Thu 2020-12-17 17:00:43 CET; 1h 37min ago
[ OK ] DietPi-Services | cron active (running) since Thu 2020-12-17 17:00:43 CET; 1h 37min ago
[ OK ] DietPi-Services | ssh active (running) since Thu 2020-12-17 17:00:37 CET; 1h 37min ago
[ OK ] DietPi-Services | fail2ban active (running) since Thu 2020-12-17 17:00:13 CET; 1h 38min ago
[ OK ] DietPi-Services | dietpi-ramlog active (exited) since Thu 2020-12-17 17:00:12 CET; 1h 38min ago
[ OK ] DietPi-Services | dietpi-preboot active (exited) since Thu 2020-12-17 17:00:13 CET; 1h 38min ago
[ OK ] DietPi-Services | dietpi-boot active (exited) since Thu 2020-12-17 17:00:37 CET; 1h 37min ago
[ OK ] DietPi-Services | dietpi-postboot active (exited) since Thu 2020-12-17 17:00:37 CET; 1h 37min ago
[ INFO ] DietPi-Services | dietpi-wifi-monitor inactive (dead)
root@DietPi:/home/dietpi#


 

I change one more time permissions to `/var/lib/emby` as `drwxr-xr-x 12 emby   emby   4096 Dec  8 07:56 emby` and nothing change for `/opt/emby-server` `drwxr-xr-x 8 emby    dietpi   4096 Dec  8 07:39 emby-server`.

Can I fix that or better to make dietpi-restore last backup?

Regards,
Przemek

 

 

 

Edited by Przemek
Link to post
Share on other sites

@ Luke

I see in emby log that was nr 4.5.2.0. 

I see also in jurnalctl but nothing more:

root@DietPi:/# journalctl -u emby-server.service
-- Logs begin at Thu 2019-02-14 11:11:58 CET, end at Fri 2020-12-18 07:10:54 CET. --
Dec 17 20:03:43 DietPi systemd[1]: Started Emby Server is a personal media server with apps on just about every device..
Dec 17 20:03:43 DietPi systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Dec 17 20:03:43 DietPi systemd[1]: emby-server.service: Failed with result 'signal'.
Dec 17 20:35:13 DietPi systemd[1]: Started Emby Server is a personal media server with apps on just about every device..
Dec 17 20:35:13 DietPi systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Dec 17 20:35:13 DietPi systemd[1]: emby-server.service: Failed with result 'signal'.
Dec 17 23:21:48 DietPi systemd[1]: Started Emby Server is a personal media server with apps on just about every device..
Dec 17 23:21:48 DietPi systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Dec 17 23:21:48 DietPi systemd[1]: emby-server.service: Failed with result 'signal'.

Regards,
Przemek
 

Edited by Przemek
add jurnalctl entry
Link to post
Share on other sites

Hmm status 11 is a segfault 😕 What pi model is that? Can you please post the output of the following commands?

uname -a
ls -la /lib/ld*
sudo -u emby /opt/emby-server/bin/emby-server

Those are weird ownership you have on /opt/emby-server, probably harmless but the whole tree should belong to root:root after installation, not emby:dietpi.

Edited by alucryd
Link to post
Share on other sites

Looked at the dietpi images, their 32 bit flavor seems to be armv6, probably to accomodate even the older raspberry pi 1. Our packages are for armv7 and were previously shipping with a hack to use our own glibc instead of the system one, and that most likely explains why it worked on dietpi despite it being armv6 at its core. I'm not too keen of reintroducing this hack as the whole point of my latest endeavors was to get rid of it, and I would highly recommend you switch to an armv7 os, but if there are more examples of distros resorting to armv6 we will have no choice but to reintroduce the hack.

Link to post
Share on other sites

I just gave DietPi a try, looks like it switches to armv7 on later pi models after the fact, so I installed emby and it works fine here on a raspberry pi 3. Please share the output of the above commands whenever you can.

Edited by alucryd
Link to post
Share on other sites

Hi, @alucryd I use Emby before and there was no problem on my Rpi4B.
 

DietPi v6.33.3 : 16:26 - Fri 12/18/20
 - Device model : RPi 4 Model B (armv7l)



 

root@DietPi:/home/dietpi# /opt/emby-server/bin/emby-server
Segmentation fault
root@DietPi:/home/dietpi# exit
exit
dietpi@DietPi:~$ ls -la /lib/ld*
lrwxrwxrwx 1 root root 30 May 14  2019 /lib/ld-linux-armhf.so.3 -> arm-linux-gnueabihf/ld-2.28.so
lrwxrwxrwx 1 root root 24 Aug 20 12:31 /lib/ld-linux.so.3 -> /lib/ld-linux-armhf.so.3
dietpi@DietPi:~$ uname -a
Linux DietPi 5.4.79-v7l+ #1373 SMP Mon Nov 23 13:27:40 GMT 2020 armv7l GNU/Linux
dietpi@DietPi:~$ 

Regards.

Link to post
Share on other sites

I don't doubt it worked before, it seemed weird that the dietpi download says armv6, but now I know how it works, it's all cleared out. Could you try to uninstall emby and start fresh? You can just mv /var/lib/emby somewhere else if you want to keep your data, and mv it back afterwards.

You'll need to something along those lines:

apt-get uninstall emby-server
mv /var/lib/emby /var/lib/emby.bkp
userdel emby
dpkg -i emby-server-*.deb

I'm not sure it'll help since an immediate segfault usually indicates the dotnet runtime doesn't like something about the system, in most cases it's the installed glibc.

Do you have a premiere subscription? I'm asking to know whether you'd miss out if you had to switch to the armv8 version. I see DietPi offers armv8 downloads for the rpi4, and the armv8 dotnet runtime is a lot less picky than its little armv7 brother. The armv8 has the advantage of being faster overall and can use the whole 8Gb of RAM if you have that model, but it can't make use of openmax and mmal like the armv7 model does, at least not until the raspberry foundation releases an armv8 firmware. Right now the armv8 build can only do V4L2-M2M.

Link to post
Share on other sites

I think it's only mine issue because I copy from old sd card to new on my Ubuntu latop as root folders /opt/emby-server and /var/lib/emby to new installation. I think it's OK to copy also /opt/emby-server to keep my config. Now I will restore backup on Dietpi and only backup /var/lib/emby folder. Then I install Emby again.
I'm not premiere subscribent. I have only 2GB RAM Rpi4. It works OK with Emby until today but nextcloud is not too fast. I think I will change that Rpi to something better like Odroid or RockPro64 in next year.

Link to post
Share on other sites
2 hours ago, Luke said:

Hi, so are you all set now?

Hi, @Luke and @alucryd I install fresh last version of Emby and it works but when I move old /var/lib/emby to new /var/lib/emby Emby failed to start. Maybe I will copy only some config files? Can You tell me what files are needet to have my old config?  

Link to post
Share on other sites

Did you make sure /var/lib/emby recursively belongs to emby:emby? Is it still a segfault (status 11)?

@Luke Could a plugin be interfering and causing a segfault?

Link to post
Share on other sites
7 minutes ago, alucryd said:

Did you make sure /var/lib/emby recursively belongs to emby:emby? Is it still a segfault (status 11)?

@Luke Could a plugin be interfering and causing a segfault?

He says it's not even generating any log file, so assuming he's correct about that, it's very unlikely to be plugin related because there would have at least been some log file created before the server tried to load plugins.

Link to post
Share on other sites

@alucryd/var/lib/emby belongs to emby:dietpi. The same segfault.
 

root@DietPi:/var/lib/emby# ls -l
total 32
drwxr-xr-x 16 emby dietpi 4096 Dec  8 07:47 cache
drwxr-xr-x  5 emby dietpi 4096 Dec  8 07:47 config
drwxr-xr-x  6 emby dietpi 4096 Dec  9 21:27 data
drwxr-xr-x  2 emby dietpi 4096 Dec 19 20:54 logs
drwxr-xr-x  4 emby dietpi 4096 Dec  8 07:45 metadata
drwxr-xr-x  3 emby dietpi 4096 Dec  8 07:44 plugins
drwxr-xr-x  3 emby dietpi 4096 Dec  7 21:32 root
drwxr-xr-x  2 emby dietpi 4096 Dec 19 20:52 transcoding-temp


 

Link to post
Share on other sites

OK, it works now. I uninstall Emby, remove /opt/emby-server, then copy backup of old /var/lib/emby to /var/lib/ but without 3 folders: .cache, .dotnet and /cache.
Thanks for help.
Regards,
Przemek  

Link to post
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...