popey 0 Posted June 22, 2018 Share Posted June 22, 2018 (edited) Hello, I've installed emby-server 3.4.1.0 on my Ubuntu server, and added two media locations, movies and music. Now whenever I start emby, it dies shortly after. Any ideas what's going on? [Fri Jun 22 16:19:55 2018] EmbyServer[19852]: segfault at 0 ip 00007fec74d0ead0 sp 00007fec57ad1578 error 4 in libc-2.23.so[7fec74c99000+1c0000] alan@robby:~⟫ 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 Fri 2018-06-22 16:17:42 BST; 6s ago Process: 19647 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=SEGV) Main PID: 19647 (code=killed, signal=SEGV) Jun 22 16:17:28 robby emby-server[19647]: 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_FTSJun 22 16:17:28 robby emby-server[19647]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal Jun 22 16:17:28 robby emby-server[19647]: Info App: PRAGMA synchronous=1 Jun 22 16:17:28 robby emby-server[19647]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0356121 seconds Jun 22 16:17:28 robby emby-server[19647]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint Jun 22 16:17:28 robby emby-server[19647]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0021302 seconds Jun 22 16:17:28 robby emby-server[19647]: Info App: All entry points have started Jun 22 16:17:42 robby systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV Jun 22 16:17:42 robby systemd[1]: emby-server.service: Unit entered failed state. Jun 22 16:17:42 robby systemd[1]: emby-server.service: Failed with result 'signal'. 3 alan@robby:~⟫ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial Here's the server log. http://paste.ubuntu.com/p/cNcnq3czHM/ Edited June 22, 2018 by popey Link to comment Share on other sites More sharing options...
Luke 37253 Posted June 22, 2018 Share Posted June 22, 2018 Hi, unfortunately these are always difficult to hunt down, as they're usually happening in a native dependency that we're bundling. Can you try updating to the beta release? It has updated to .net core 2.1 so there's a chance that will make a difference. thanks. Link to comment Share on other sites More sharing options...
popey 0 Posted June 22, 2018 Author Share Posted June 22, 2018 Thanks. Unfortunately it also fails. alan@robby:~⟫ 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 Fri 2018-06-22 20:09:33 BST; 1min 21s ago Process: 18565 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=SEGV) Main PID: 18565 (code=killed, signal=SEGV) Jun 22 20:07:50 robby emby-server[18565]: Info App: Sqlite compiler options: COMPILER=gcc-6.3.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOK Jun 22 20:07:50 robby emby-server[18565]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal Jun 22 20:07:50 robby emby-server[18565]: Info App: PRAGMA synchronous=1 Jun 22 20:07:50 robby emby-server[18565]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0258664 seconds Jun 22 20:07:50 robby emby-server[18565]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint Jun 22 20:07:50 robby emby-server[18565]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0022482 seconds Jun 22 20:07:50 robby emby-server[18565]: Info App: All entry points have started Jun 22 20:09:33 robby systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV Jun 22 20:09:33 robby systemd[1]: emby-server.service: Unit entered failed state. Jun 22 20:09:33 robby systemd[1]: emby-server.service: Failed with result 'signal'. [1887989.233627] EmbyServer[18706]: segfault at 0 ip 00007f6caf25dad0 sp 00007f6c0cb04bb8 error 4 in libc-2.23.so[7f6caf1e8000+1c0000] In what environment does emby (and the libraries) get built? Is it possible you're pulling in libraries from a variety of mis-matched places? Link to comment Share on other sites More sharing options...
Luke 37253 Posted June 24, 2018 Share Posted June 24, 2018 We do use a single environment to build for all platforms. I've passed this onto our build developer to respond to this. Thanks. Link to comment Share on other sites More sharing options...
alucryd 217 Posted June 24, 2018 Share Posted June 24, 2018 Everything is built from source and is the latest upstream (or close) version available using the same toolchain, the environment doesn't matter. The segfault happens in your system's glibc, we don't ship our own on linux platforms. Is there any way you can upgrade to the latest LTS, 18.04? It has a much more up-to-date glibc. Link to comment Share on other sites More sharing options...
icsy7867 8 Posted June 24, 2018 Share Posted June 24, 2018 Sounds similar to the issue I had after using the Deb to update. https://emby.media/community/index.php?/topic/60120-emby-server-failing-after-loading-web-interface/&do=findComment&comment=590237 Link to comment Share on other sites More sharing options...
popey 0 Posted June 25, 2018 Author Share Posted June 25, 2018 I certainly could upgrade to 18.04, but that's quite a brutal fix. Instead I'll install emby in a fresh 18.04 system and test there. Worth noting the vast majority of Ubuntu server users are on 16.04 (and even 14.04) and below. Only a small proportion of people will have upgraded to 18.04 by now. Canonical doesn't enable the upgrade flag for 16.04 (to 18.04) until next month. Link to comment Share on other sites More sharing options...
popey 0 Posted June 25, 2018 Author Share Posted June 25, 2018 Ok, span up an 18.04 machine and it crashes on libc there too. [ 611.274357] EmbyServer[2409]: segfault at 0 ip 00007f09c8d337b0 sp 00007f09250c6558 error 4 in libc-2.27.so[7f09c8cac000+1e7000] Link to comment Share on other sites More sharing options...
alucryd 217 Posted June 25, 2018 Share Posted June 25, 2018 Could you please post the whole log? See at which point it breaks. Thx. Link to comment Share on other sites More sharing options...
alucryd 217 Posted June 25, 2018 Share Posted June 25, 2018 Also, could you try this deb out? https://www.dropbox.com/s/5gt8ha1zg5x5apr/emby-server-netgear_3.4.1.20_amd64.deb?dl=0 It works fine on a 18.04 docker I just fired on my server. Added a library without issue. It's also compatible with 16.04 if you'd prefer. Link to comment Share on other sites More sharing options...
popey 0 Posted June 26, 2018 Author Share Posted June 26, 2018 That deb won't work. dpkg: dependency problems prevent configuration of emby-server: emby-server depends on readynasos (>= 6.8.0); however: Package readynasos is not installed. Link to comment Share on other sites More sharing options...
popey 0 Posted June 26, 2018 Author Share Posted June 26, 2018 Could you please post the whole log? See at which point it breaks. Thx. That's the only line that appears in the syslog, which log file do you need? Link to comment Share on other sites More sharing options...
Luke 37253 Posted June 26, 2018 Share Posted June 26, 2018 Was there any emby server log generated? Link to comment Share on other sites More sharing options...
popey 0 Posted June 26, 2018 Author Share Posted June 26, 2018 My first post had one. http://paste.ubuntu.com/p/cNcnq3czHM/ Link to comment Share on other sites More sharing options...
Luke 37253 Posted June 26, 2018 Share Posted June 26, 2018 Can you provide an emby server log based on the beta release? thanks. Link to comment Share on other sites More sharing options...
popey 0 Posted June 28, 2018 Author Share Posted June 28, 2018 Apologies for the delay. Here's the log from the beta build. http://paste.ubuntu.com/p/Jz4Xf9BxCS/ Link to comment Share on other sites More sharing options...
Luke 37253 Posted June 28, 2018 Share Posted June 28, 2018 Hmm, last log line is about images, which would suggest something related to the skia graphics library. Can you try the latest beta and see if that makes any difference? Thanks. Link to comment Share on other sites More sharing options...
Mekong 0 Posted June 28, 2018 Share Posted June 28, 2018 I'm having the exact same issue as popey; also on 16.04 LTS. This started with Emby 3.4.1.0. The behavior is inconsistent; sometimes it crashes when clicking on a library from the Home page, other times it does not. I have not installed any beta releases; waiting to see popey's response to Luke's latest suggestion. Link to comment Share on other sites More sharing options...
Luke 37253 Posted June 28, 2018 Share Posted June 28, 2018 @@Mekong can you please attach the emby server log? Thanks. Link to comment Share on other sites More sharing options...
popey 0 Posted June 29, 2018 Author Share Posted June 29, 2018 Tried 3.4.1.22 and got much the same experience. I managed to stream part of a movie for a bit, but if I tried to stop it and do something else, emby dies. http://paste.ubuntu.com/p/yTFvJY6HqK/ Link to comment Share on other sites More sharing options...
Luke 37253 Posted June 29, 2018 Share Posted June 29, 2018 What do you mean by do something else? Link to comment Share on other sites More sharing options...
popey 0 Posted June 29, 2018 Author Share Posted June 29, 2018 Just refreshing / visiting the home page. Link to comment Share on other sites More sharing options...
Mekong 0 Posted June 29, 2018 Share Posted June 29, 2018 (edited) Here's the systemctl status and the related emby server log. jmfont@LINUX0 ~ $ sudo 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 Thu 2018-06-28 16:10:12 CDT; 24s ago Process: 21241 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=SEGV) Main PID: 21241 (code=killed, signal=SEGV) Jun 28 16:07:56 LINUX0 emby-server[21241]: 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 Jun 28 16:07:56 LINUX0 emby-server[21241]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal Jun 28 16:07:56 LINUX0 emby-server[21241]: Info App: PRAGMA synchronous=1 Jun 28 16:07:56 LINUX0 emby-server[21241]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0109884 seconds Jun 28 16:07:56 LINUX0 emby-server[21241]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint Jun 28 16:07:56 LINUX0 emby-server[21241]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0007756 seconds Jun 28 16:07:56 LINUX0 emby-server[21241]: Info App: All entry points have started Jun 28 16:10:12 LINUX0 systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV Jun 28 16:10:12 LINUX0 systemd[1]: emby-server.service: Unit entered failed state. Jun 28 16:10:12 LINUX0 systemd[1]: emby-server.service: Failed with result 'signal'. embyserver-63665799042.txt Edited June 30, 2018 by Mekong Link to comment Share on other sites More sharing options...
popey 0 Posted July 10, 2018 Author Share Posted July 10, 2018 I have further tested the latest beta emby-server-deb_3.4.1.30_amd64.deb on both Ubuntu 16.04 and 18.04. They both still segfault. I'm still keen to understand how the libraries that make up the emby-server package are built. Are they somehow building on bleeding edge of something, which means they're built against a libc which is far too new and thus not going to work on 'older' distros like Ubuntu 18.04 and 16.04? I'd love to help get this fixed, but without knowing how it's being built, that's really hard. Link to comment Share on other sites More sharing options...
Luke 37253 Posted July 10, 2018 Share Posted July 10, 2018 That's a good question, and something we can look into, whether or not some of the dependencies we're using might be a little too new. One curiosity i have though is do you have any thoughts on why others are able to run it? This is definitely affecting a few people, so I realize you're not alone, but it's not something I'd call widespread at the moment. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now