Server crashes when accessing any series through Roku

[MrChimp 0]

Hi,

I am having an odd issue where if I access a series via Roku it instantly crashes the server, accessing through a web browser is fine. When I say crash the emby-server application crashes, I can instantly start it up again and all is fine once again. The server is running CentOS 7 inside a VM (the host is also CentOS 7) and I am using Emby version 3.3.1.14 beta, this wasn't happening at least a week ago when I believe I was on the previous beta release.

 

Here is the log file from the crash: embyserver-63658903979.txt

Also if it is useful here is the log after I restarted Emby: embyserver.txt

 

Here is what systemctl -l status emby-server reports after it has crashed if that is at all helpful:

● 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: disabled)
   Active: failed (Result: signal) since Mon 2018-04-09 20:51:24 BST; 25s ago
  Process: 27958 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=SEGV)
 Main PID: 27958 (code=killed, signal=SEGV)

Apr 09 20:37:39 embyserver emby-server[27958]: 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
Apr 09 20:37:39 embyserver emby-server[27958]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal
Apr 09 20:37:39 embyserver emby-server[27958]: Info App: PRAGMA synchronous=1
Apr 09 20:37:39 embyserver emby-server[27958]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0078252 seconds
Apr 09 20:37:39 embyserver emby-server[27958]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Apr 09 20:37:39 embyserver emby-server[27958]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.000362 seconds
Apr 09 20:37:39 embyserver emby-server[27958]: Info App: All entry points have started
Apr 09 20:51:24 embyserver systemd[1]: emby-server.service: main process exited, code=killed, status=11/SEGV
Apr 09 20:51:24 embyserver systemd[1]: Unit emby-server.service entered failed state.
Apr 09 20:51:24 embyserver systemd[1]: emby-server.service failed.

I can't see anything in the log files that indicates what is wrong, other than it seems to be loading an image for the series when it fails, I have replicated this a few times now and this line is always the last thing in the log:

2018-04-09 20:51:24.200 Info HttpServer: HTTP GET http://192.168.1.150:8096/emby/Items/e72f293e63896fb73c376f46aa85fc33/Images/Primary/0?EnableImageEnhancers=false&tag=5276cf9d8dd4471e5ecb19ce57d1ed47&maxheight=245&quality=80. UserAgent: Roku/DVP-8.1 (518.01E04090A)

Could it be something to do with that image that is causing it?

Thanks in advance

[Luke 42078]

When you start it up again, does it crash again on the same series, or does that one work after that?

[MrChimp 0]

The same series keeps on crashing the Roku. I did notice at least one other series worked when I last tested it.

[MrChimp 0]

I just made a discovery, the one series that worked previously I just added a logo to it and locked the metadata. It now crashes Emby when I try to view it on the server. I am going to unlock it and then try removing the logo and see which makes it work again.

[MrChimp 0]

So after repeatedly trying different things (removing images and locking metadata) both of the series now crash Emby so I think my previous theory doesn't hold any weight.

 

I did find some other useful log info in /var/log/messages:

Apr 9 22:48:28 embyserver kernel: EmbyServer[31210]: segfault at 0 ip 00007f3b2058c570 sp 00007f3a6d735f48 error 4 in libc-2.17.so[7f3b20519000+1b6000]
Apr 9 22:48:28 embyserver systemd: emby-server.service: main process exited, code=killed, status=11/SEGV
Apr 9 22:48:28 embyserver systemd: Unit emby-server.service entered failed state.
Apr 9 22:48:28 embyserver systemd: emby-server.service failed.

Not sure if that helps pint point what the issue is or could be related to?

[Luke 42078]

Are you still seeing this?