code=killed, status=11/SEGV

[jjhayn 1]

Starting on 2/19/2019 Emby Server started crashing when loading landing/main media page. The admin page does not cause a crash.

 

Running: Ubuntu 18.04.2 LTS

 

Error: EmbyServer[3461]: segfault at 0 ip 00007f9656f7b7b0 sp 00007f95867f7678 error 4 in libc-2.27.so[7f9656ef4000+1e7000]

 

 

I suspect recent security updates are the cause.

 

Start-Date: 2019-02-19  06:16:38

Commandline: /usr/bin/unattended-upgrade

Upgrade: systemd-sysv:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13)

End-Date: 2019-02-19  06:16:44

 

Start-Date: 2019-02-19  06:16:48

Commandline: /usr/bin/unattended-upgrade

Upgrade: udev:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), libudev1:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13)

End-Date: 2019-02-19  06:17:25

 

Start-Date: 2019-02-19  06:17:29

Commandline: /usr/bin/unattended-upgrade

Upgrade: libsystemd0:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), libpam-systemd:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), systemd:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), libnss-systemd:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13)

End-Date: 2019-02-19  06:17:39

 

I attached syslog and emby logs.

 

 

 

 

syslog.txt

emby_log.txt

[Luke 37096]

Hi there, how have you setup your libraries? Are any using smb or unc paths?

[jjhayn 1]

It's just a local directory on the system running emby

[Luke 37096]

Where is the media?

[jjhayn 1]

All media is stored locally on the Emby server.

[Luke 37096]

Hmmm unfortunately there is nothing obvious here.

 

Can you enable debug logging under logs, restart the server, then try again and produce a new server log? Thanks.

[jjhayn 1]

This pointed me down the right path. Emby crashes if it doesn't have read access to poster.jpg or xxx.nfo within the folder. I gave the emby account full ready write access to these files and it appears to have resolved the crashing. 

[Luke 37096]

Interesting, thanks for the info.

[justmejustme 3]

This pointed me down the right path. Emby crashes if it doesn't have read access to poster.jpg or xxx.nfo within the folder. I gave the emby account full ready write access to these files and it appears to have resolved the crashing. 

 

Thanks for posting - I had the exact same issue. A few folders and files had wrong permissions, and rather than a simple error message, emby-server decided to do a full crash and burn SEGV.

 

Fixing permissions fixed it for me as well, though the server should have handled it far more gracefully (@Luke)@Luke

Feb 27 08:47:18 server kernel: [2765474.380583] EmbyServer[31161]: segfault at 0 ip 00007f5920d91ad0 sp 00007f5887ffb278 error 4 in libc-2.23.so[7f5920d1c000+1c0000]
Feb 27 08:47:18 server systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Feb 27 08:47:18 server systemd[1]: emby-server.service: Unit entered failed state.
Feb 27 08:47:18 server systemd[1]: emby-server.service: Failed with result 'signal'.

[Luke 37096]

Yes agreed, thanks.

[Tygre 1]

Hi!
Sorry for reviving this thread but I have exactly the same error but without any log produced by EmbyServer as far as I can tell...

I installed EmbyServer on my RPI following the instructions at https://www.electromaker.io/tutorial/blog/emby-server-raspberry-pi

I rebooted my RPI (several times).

>systemctl status emby-server

● 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: enabled)
   Active: failed (Result: signal) since Wed 2022-08-17 17:35:59 EDT; 14min ago
  Process: 773 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=SEGV)
 Main PID: 773 (code=killed, signal=SEGV)

Aug 17 17:35:59 chamsae systemd[1]: Started Emby Server is a personal media server with apps on just about every device..
Aug 17 17:35:59 chamsae systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Aug 17 17:35:59 chamsae systemd[1]: emby-server.service: Failed with result 'signal'.

There is nothing in /var/lib/emby (it's just an empty directory) so I don't know where to start debugging...

Could you please help?

[Luke 37096]

22 hours ago, Tygre said:

Hi!
Sorry for reviving this thread but I have exactly the same error but without any log produced by EmbyServer as far as I can tell...

I installed EmbyServer on my RPI following the instructions at https://www.electromaker.io/tutorial/blog/emby-server-raspberry-pi

I rebooted my RPI (several times).

>systemctl status emby-server

● 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: enabled)
   Active: failed (Result: signal) since Wed 2022-08-17 17:35:59 EDT; 14min ago
  Process: 773 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=SEGV)
 Main PID: 773 (code=killed, signal=SEGV)

Aug 17 17:35:59 chamsae systemd[1]: Started Emby Server is a personal media server with apps on just about every device..
Aug 17 17:35:59 chamsae systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Aug 17 17:35:59 chamsae systemd[1]: emby-server.service: Failed with result 'signal'.

There is nothing in /var/lib/emby (it's just an empty directory) so I don't know where to start debugging...

Could you please help?

Hi @Tygre what RPI do you have? What package file did you install?

[Tygre 1]

Hi @Luke!
Thanks for your answer: I have RPI2 and installed https://github.com/MediaBrowser/Emby.Releases/releases/download/4.3.1.0/emby-server-deb_4.3.1.0_armhf.deb
Now, I installed Emby on a Synology NAS, and it worked out-of-the-box, so I'll be using that one
Best!