emby-server segfaulting on 16.04 LTS

[popey 0]

I can only imagine that I'm using a feature others aren't. Maybe some of my videos or music are coded with uncommon codecs which leads to another code-path or library that others aren't using? But I'm not doing anything especially odd. Pointing emby at my NAS which has folders full of video files and music files. No different that pointing plex at it, or my smart TV.

[Luke 37128]

You're probably right, I was just curious for your thoughts. Thanks.

[unixsurfer 0]

I have similar problem with Debian Stable (9.5 version) and Emby server Version 3.5.2.0.

Here is the log of the last crash, which happens few seconds after starting the server.

sudo journalctl -f -u  emby-server.service 
-- Logs begin at Fri 2018-08-31 19:15:35 CEST. --


Sep 02 16:46:32 naxos emby-server[26639]: Info App: Starting entry point Emby.Server.MediaEncoding.Api.ApiEntryPoint
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Entry point completed: Emby.Server.MediaEncoding.Api.ApiEntryPoint. Duration: 0.0008201 seconds
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Starting entry point Emby.Notifications.Notifications
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Entry point completed: Emby.Notifications.Notifications. Duration: 0.0006414 seconds
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Starting entry point MediaBrowser.XbmcMetadata.EntryPoint
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Entry point completed: MediaBrowser.XbmcMetadata.EntryPoint. Duration: 0.0002219 seconds
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Starting entry point Emby.Security.PluginSecurityManager
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 3.76E-05 seconds
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Starting entry point Emby.Server.Sync.SyncManagerEntryPoint
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Sqlite version: 3.24.0
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Sqlite compiler options: COMPILER=gcc-6.3.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS5,ENABLE_JSON1,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MAX_SCHEMA_RETRY=25,MAX_VARIABLE_NUMBER=250000,OMIT_LOOKASIDE,SECURE_DELETE,THREADSAFE=1
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal
Sep 02 16:46:32 naxos emby-server[26639]: Info App: PRAGMA synchronous=1
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.008542 seconds
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Sep 02 16:46:32 naxos emby-server[26639]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0019517 seconds
Sep 02 16:46:32 naxos emby-server[26639]: Info App: All entry points have started
Sep 02 16:47:11 naxos systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Sep 02 16:47:11 naxos systemd[1]: emby-server.service: Unit entered failed state.
Sep 02 16:47:11 naxos systemd[1]: emby-server.service: Failed with result 'signal'.

and the crash occured while I was trying to browse the photos from a libary using the  Android appand the following lines are last in the log

2018-09-02 16:47:05.558 Info ImageProcessor: Getting image size for item Photo /data/photos/Summer2018/IMG_4807.JPG
2018-09-02 16:47:05.558 Info ImageProcessor: Getting image size for item Photo /data/photos/Summer2018/IMG_4808.JPG
2018-09-02 16:47:05.559 Info ImageProcessor: Getting image size for item Photo /data/photos/Summer2018/IMG_4809.JPG

and there is nothing else before 16:47:11

 

any ideas how to debug this?

[Luke 37128]

These are always difficult. It might be resolved in the beta but I'm not sure.

[unixsurfer 0]

Will it help if I run the server under gdb?

[popey 0]

Re-visiting this topic, I may have made a breakthrough.

 

I just installed emby-server on my laptop, and copied media locally to my laptop and had emby scan that. It all worked fine, didn't crash at all.

I then deleted all the files and deleted the media locations set in emby. I then pointed emby to my NetGear ReadyNAS which has a "Music" samba share, containing the exact same files as I had locally.

After adding the location, now emby crashes, repeatedly.

 

So it seems perhaps network or samba related.

 

In emby I added the remote location in the wizard as \\192.168.1.3\Music - being the ip and share name on the ReadyNAS.

I hope that's useful information. I'm happy to have made a breakthrough. In all my previous tests some weeks ago, I was *always* loading media from the SAMBA share on my NAS, where emby was crashing all the time.

[Luke 37128]

Thanks ! What version did you test that with?

[popey 0]

I used 3.5.2.0 on Ubuntu 16.04.

[troyscorer 3]

this has been happening to me more and more frequently as well. It used to be that remote clients would stop being able to access the server, it would partially load but local clients worked fine. Now the server starts but any attempt to access the dashboard would cause an insta crash and navigating through the web inteface will crash the server at random places, usually within 30 seconds

 

i, to seem to be affected by this

Sep 03 18:23:54 UbuntuServer emby-server[1836]: Info App: Sqlite compiler options: COMPILER=gcc-6.3.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS5,ENABLE_JSON1,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MAX_SCHEMA_RETRY=25,MAX_VARIABLE_NUMBER=250000,OMIT_LOOKASIDE,SECURE_DELETE,THREADSAFE=1
Sep 03 18:23:54 UbuntuServer emby-server[1836]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal
Sep 03 18:23:54 UbuntuServer emby-server[1836]: Info App: PRAGMA synchronous=1
Sep 03 18:23:54 UbuntuServer emby-server[1836]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0126911 seconds
Sep 03 18:23:54 UbuntuServer emby-server[1836]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Sep 03 18:23:54 UbuntuServer emby-server[1836]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0028035 seconds
Sep 03 18:23:54 UbuntuServer emby-server[1836]: Info App: All entry points have started
Sep 03 18:24:25 UbuntuServer systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Sep 03 18:24:25 UbuntuServer systemd[1]: emby-server.service: Unit entered failed state.
Sep 03 18:24:25 UbuntuServer systemd[1]: emby-server.service: Failed with result 'signal'.

I am on ubuntu 16.04.5 and Server 3.5.2.0

 

EDIT: Clean purge and reinstall of latest beta 3.6.0.33 beta and does the same thing as soon as Emby Theatre Connects to it. (3.0.2)

 

Looking at the embyserver.txt each time it, the last line is related to an image file... like this

 

2018-09-03 21:31:59.304 Info HttpServer: HTTP GET http://192.168.1.200:8096/emby/Items/1204/Images/Primary?maxHeight=319&maxWidth=213&tag=e2d8328da5bfeca781ca0aaf60696ff8&quality=90. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0

2018-09-03 21:31:59.310 Debug HttpResultFactory: Transmit file /media/raid/embycache/cache/images/resized-images/3/324c6bd7-64cb-0476-6954-5785b86ea7e2.jpg

embyserver.txt

Edited September 4, 2018 by troyscorer

[unixsurfer 0]

In my case, the libraries are on the local file-system, different partiton.

[Luke 37128]

Please make sure to attach complete log files, thanks.

[troyscorer 3]

Please make sure to attach complete log files, thanks.

Ive updated my original post but here is the logfile

embyserver.txt

[troyscorer 3]

Update:

 

Updated to the new Beta 3.6.0.34, no plugins, 1 user, when any client connects, instant server crash as the home page has images on it.

2018-09-05 19:49:30.914 Info HttpServer: HTTP GET http://192.168.1.200:8096/emby/Items/1200/Images/Primary?maxHeight=334&maxWidth=223&tag=8002e993aad10ce5aacc9b3e3f6b9fd0&quality=90. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
2018-09-05 19:49:30.936 Debug App: ConvertImageToLocal item 1204 - image url: https://image.tmdb.org/t/p/original/to0spRl1CMDvyUbOnbb4fTk3VAd.jpg
2018-09-05 19:49:30.938 Info HttpClient: GET https://image.tmdb.org/t/p/original/to0spRl1CMDvyUbOnbb4fTk3VAd.jpg

last 3 lines. also attached the whole log file. Still throwing a segfault in the journal

 

 

Sep 05 19:49:03 UbuntuServer emby-server[70148]: Info App: Starting entry point MediaBrowser.XbmcMetadata.EntryPoint
Sep 05 19:49:03 UbuntuServer emby-server[70148]: Info App: Entry point completed: MediaBrowser.XbmcMetadata.EntryPoint. Duration: 0.0001241 seconds
Sep 05 19:49:03 UbuntuServer emby-server[70148]: Info App: Starting entry point Emby.Security.PluginSecurityManager
Sep 05 19:49:03 UbuntuServer emby-server[70148]: Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 4.88E-05 seconds
Sep 05 19:49:03 UbuntuServer emby-server[70148]: Info App: Starting entry point Emby.Server.Sync.SyncManagerEntryPoint
Sep 05 19:49:03 UbuntuServer emby-server[70148]: Info App: PRAGMA synchronous=1
Sep 05 19:49:03 UbuntuServer emby-server[70148]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0052542 seconds
Sep 05 19:49:03 UbuntuServer emby-server[70148]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Sep 05 19:49:03 UbuntuServer emby-server[70148]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0013141 seconds
Sep 05 19:49:03 UbuntuServer emby-server[70148]: Info App: All entry points have started
Sep 05 19:49:31 UbuntuServer systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Sep 05 19:49:31 UbuntuServer systemd[1]: emby-server.service: Unit entered failed state.
Sep 05 19:49:31 UbuntuServer systemd[1]: emby-server.service: Failed with result 'signal'.
 

 

I should mention that my backup server running 3.5.2.0 on my synology nas runs fine, but horribly slow. The media is stored on that NAS

embyserver.txt

[olbj 0]

Hello! I have the same problem. I have tried to upgrade to 3.5.2 on an Ubuntu 16.04 virtual instance but I have also tried a fresh install on an Ubuntu 18.04 virtual instance. Both the upgraded and the fresh server crashes like troyscorer's and popey's systems. Is this an open issue.

 

Best regards Olle

[Luke 37128]

Hi there @@olbj, can you please attach the emby server log? thanks.

[olbj 0]

Hi @@Luke. Thank you for a quick reply. I have just reproduced the error and attach the file below.  My syslog say's:

 

Oct 10 20:17:22 bjembynew kernel: [   82.810636] EmbyServer[639]: segfault at 0 ip 00007f3d804927b0 sp 00007f3ca4ff74d8 error 4 in libc-2.27.so[7f3d8040b000+1e7000]

Oct 10 20:17:22 bjembynew systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV

Oct 10 20:17:22 bjembynew systemd[1]: emby-server.service: Failed with result 'signal'.

 

Best regards. Olle

embyserver.txt

[Luke 37128]

If this is a fresh install do you mind trying the beta server? thanks.

[olbj 0]

Thank you for the answer. I will try that at the weekend. Olle

Skickat från min SM-G930F via Tapatalk

Edited October 11, 2018 by olbj

[olbj 0]

Hi again. I had some spare minutes and installed the beta version. Unfortunately it still crashes:

 

Oct 11 10:19:28 bjembynew kernel: [ 3961.170902] EmbyServer[31354]: segfault at 0 ip 00007f4cf3e887b0 sp 00007f4c227f6528 error 4 in libc-2.27.so[7f4cf3e01000+1e7000]

Oct 11 10:19:29 bjembynew systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV

Oct 11 10:19:29 bjembynew systemd[1]: emby-server.service: Failed with result 'signal'.

 

I attach the logfile that was created directly after the fresh install and a debug log file that I generated when I reproduced the crash.

 

Regards Olle 

embyserver.txt

embyserver_debug.txt

[Mekong 0]

I'm running Emby 3.5.3 on an Ubuntu 16.04 LTS machine, and I still have this SEGV error periodically. When I do I have found that the issue is related to one or both of the following problems:

 

1) Emby does not have the permission to read, or read/write as necessary, one or more of the files within the library. This is typically related to an image file; poster or fanart in my case.

 

2) One of the files defined within a collection no longer exists within the library. This can happen when a delete or rename occurs outside of the Emby context. This can be resolved by directly editing the collection xml file(s) to remove the invalid entries.

 

I typically perform a full library scan after correcting one of these issues.

 

Hope this helps someone that is also experiencing these crashes.

Edited October 11, 2018 by Mekong

[olbj 0]

Hi Mekong. Thanks for your advise. I had that kind of problem in the past but today I run a frequent cron job that handles the permission. However I do think that my problem can have somthing to do with my collection that is rather large. Olle

[Luke 37128]

Have either of you setup libraries using smb or unc paths?

[olbj 0]

I have a my libraries in a mapped filesystem as I run my emby-server as a KVM/QEMU instance. (I tried a smb share in the past but that was a terrible experience; very long library update times).

 

The mount line in fstab looks like this:

media   /mnt/media      9p      noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=0,trans=virtio,version=9p2000.L,rw        0       0

 

The corresponding lines in my instance definition are:

<filesystem type='mount' accessmode='mapped'>

   <source dir='/mnt/data/media'/>

   <target dir='media'/>

   <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>

</filesystem>

 

It has been working well until the new version.

 

Do you need any more information about my configuration?

Edited October 13, 2018 by olbj

[Mekong 0]

Yes, I have Samba paths defined as the "optional shared network folder" for each of my libraries. But, the libraries themselves are local to the Ubuntu machine that is running Emby.

[olbj 0]

Mekong showed me into the right direction. I found some files with wrong file permission and owner in my library. I corrected the permissons and version 3.5.3.0 of Emby runs perfectlly after that (and the beta version as well). Thank you for your help Mekong and Luke!