Loke 4 Posted July 8, 2018 Share Posted July 8, 2018 Hello, I installed recently emby and it run fine for the first 1-2 days. After that every several hours I get a crash. It happened so far while I am not actively using emby: no streaming, no android app open, only the webpage open on a non active firefox tab. Nothing on emby logs. service status gives the following. Keep in mind I had finished watching an episode, exited the android app and re-opened it to check the app version to be greeted by the connect to server message, as I see the error mentions a subtitle stream. OS: Debian stretch 9.4 (armbian) on an arm orangepi (ARMv7) Files are direct streamed to a chromecast 2 with no transcoding, using the android app. ● emby-server.service - Emby Server is a personal media server with apps on just about every device. Loaded: loaded (/etc/systemd/system/emby-server.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Sun 2018-07-08 23:20:04 EEST; 5min ago Process: 836 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=ABRT) Main PID: 836 (code=killed, signal=ABRT) Jul 08 22:37:53 orangepipc emby-server[836]: _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Jul 08 22:37:53 orangepipc emby-server[836]: Stream mapping: Jul 08 22:37:53 orangepipc emby-server[836]: Stream #0:2 -> #0:0 (copy) Jul 08 22:37:53 orangepipc emby-server[836]: Press [q] to stop, [?] for help Jul 08 22:38:05 orangepipc emby-server[836]: [1.5K blob data] Jul 08 22:38:05 orangepipc emby-server[836]: video:0kB audio:0kB subtitle:24kB other streams:0kB global headers:4kB muxing overhead: 64.108261% Jul 08 23:20:04 orangepipc emby-server[836]: *** Error in `/opt/emby-server/system/EmbyServer': double free or corruption (fasttop): 0xb5155e20 *** Jul 08 23:20:04 orangepipc systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT Jul 08 23:20:04 orangepipc systemd[1]: emby-server.service: Unit entered failed state. Jul 08 23:20:04 orangepipc systemd[1]: emby-server.service: Failed with result 'signal'. Link to comment Share on other sites More sharing options...
Luke 37113 Posted July 8, 2018 Share Posted July 8, 2018 Hi there, can you please attach the emby server log? you can learn how to do that here: https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/ Thanks. Link to comment Share on other sites More sharing options...
Loke 4 Posted July 8, 2018 Author Share Posted July 8, 2018 There you go, I have attached the log before emby crashed and after I started it. I copied the whole logs without editing or removing an information - I hope there is nothing sensitive in there. emby_before.log emby_After.log Link to comment Share on other sites More sharing options...
Luke 37113 Posted July 9, 2018 Share Posted July 9, 2018 Ok, we're looking into your crash, thanks. Link to comment Share on other sites More sharing options...
Loke 4 Posted July 10, 2018 Author Share Posted July 10, 2018 Another crash slightly different error. Also there is a question related to the service below! ● emby-server.service - Emby Server is a personal media server with apps on just about every device. Loaded: loaded (/etc/systemd/system/emby-server.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Tue 2018-07-10 17:24:51 EEST; 4h 35min ago Main PID: 8625 (code=killed, signal=ILL) Jul 10 16:31:36 orangepipc emby-server[8625]: _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Jul 10 16:31:36 orangepipc emby-server[8625]: _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Jul 10 16:31:36 orangepipc emby-server[8625]: Stream mapping: Jul 10 16:31:36 orangepipc emby-server[8625]: Stream #0:2 -> #0:0 (copy) Jul 10 16:31:36 orangepipc emby-server[8625]: Press [q] to stop, [?] for help Jul 10 16:31:52 orangepipc emby-server[8625]: [1.8K blob data] Jul 10 16:31:52 orangepipc emby-server[8625]: video:0kB audio:0kB subtitle:25kB other streams:0kB global headers:3kB muxing overhead: 56.147903% Jul 10 17:24:51 orangepipc systemd[1]: emby-server.service: Main process exited, code=killed, status=4/ILL Jul 10 17:24:51 orangepipc systemd[1]: emby-server.service: Unit entered failed state. Jul 10 17:24:51 orangepipc systemd[1]: emby-server.service: Failed with result 'signal'. Question semi-related to this. If I try service emby-server X I am told there is no emby-server.service. If I : cp /usr/lib/systemd/system/emby-server.service /etc/systemd/system/emby-server.service && systemctl daemon-reload it then works. It seems emby was updated sometime these days? so that stopped working and had to re-do it (can't think of another reason why it would stop working). I could softlink it instead I guess but in general I don't find this as normal behavior, I would expect emby to have out of the box a working service. Link to comment Share on other sites More sharing options...
Luke 37113 Posted July 10, 2018 Share Posted July 10, 2018 I'm a little confused by this, that pretty much looks like the same segfault. We have not pushed any updates to our stable channel in recent days. Link to comment Share on other sites More sharing options...
Loke 4 Posted July 10, 2018 Author Share Posted July 10, 2018 That's weird indeed then. For the service I don't get it unless it's screen that's doing tricks but doubtful. Still why it doesn't work out of the box is a valid question. Link to comment Share on other sites More sharing options...
Luke 37113 Posted July 10, 2018 Share Posted July 10, 2018 But you're saying it's fine now? Link to comment Share on other sites More sharing options...
Loke 4 Posted July 10, 2018 Author Share Posted July 10, 2018 the service? Yes after I re-copied it and reloaded the daemon "service emby-server status" works fine, that's how I got the output I pasted above. Link to comment Share on other sites More sharing options...
Luke 37113 Posted July 10, 2018 Share Posted July 10, 2018 That's strange. Thanks for the info. Link to comment Share on other sites More sharing options...
Loke 4 Posted July 16, 2018 Author Share Posted July 16, 2018 (edited) bumping for update: Since last time it crashed again ( Wed 2018-07-11 01:54:24) and since Thu 2018-07-12 19:53:29 it's been stable. In that time the app got updated (twice I reckon). I don't quite remember but I think between the two dates I restarted the server due to a plugin or something. Edited July 16, 2018 by Loke Link to comment Share on other sites More sharing options...
Loke 4 Posted July 25, 2018 Author Share Posted July 25, 2018 (edited) And here we go, now with more error types. Also I think I upgraded to the latest version the day it came out. Active: active (running) since Sun 2018-07-22 20:48:41 EEST; 17s ago Active: failed (Result: signal) since Mon 2018-07-23 02:30:14 EEST; 12h ago Process: 21749 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=SEGV) Main PID: 21749 (code=killed, signal=SEGV) Jul 23 00:36:54 orangepipc emby-server[21749]: _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Jul 23 00:36:54 orangepipc emby-server[21749]: _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Jul 23 00:36:54 orangepipc emby-server[21749]: Stream mapping: Jul 23 00:36:54 orangepipc emby-server[21749]: Stream #0:2 -> #0:0 (copy) Jul 23 00:36:54 orangepipc emby-server[21749]: Press [q] to stop, [?] for help Jul 23 00:37:06 orangepipc emby-server[21749]: [1.5K blob data] Jul 23 00:37:06 orangepipc emby-server[21749]: video:0kB audio:0kB subtitle:24kB other streams:0kB global headers:1kB muxing overhead: 47.978825% Jul 23 02:30:14 orangepipc systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV Active: failed (Result: signal) since Mon 2018-07-23 15:49:04 EEST; 20h ago Active: failed (Result: signal) since Tue 2018-07-24 15:21:25 EEST; 20min ago Process: 31153 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=ABRT) Main PID: 31153 (code=killed, signal=ABRT) Jul 24 12:36:22 orangepipc emby-server[31153]: Info App: Sqlite compiler options: COMPILER=gcc-6.4.1 20170707,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT Jul 24 12:36:22 orangepipc emby-server[31153]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal Jul 24 12:36:22 orangepipc emby-server[31153]: Info App: PRAGMA synchronous=1 Jul 24 12:36:22 orangepipc emby-server[31153]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.1123745 second Jul 24 12:36:22 orangepipc emby-server[31153]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint Jul 24 12:36:22 orangepipc emby-server[31153]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0286424 s Jul 24 12:36:22 orangepipc emby-server[31153]: Info App: All entry points have started Jul 24 15:21:25 orangepipc systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT Jul 24 15:21:25 orangepipc systemd[1]: emby-server.service: Unit entered failed state. Jul 24 15:21:25 orangepipc systemd[1]: emby-server.service: Failed with result 'signal'. Active: active (running) since Tue 2018-07-24 15:43:24 EEST; 2s ago Active: failed (Result: signal) since Tue 2018-07-24 18:01:52 EEST; 6h ago Process: 11831 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=ABRT) Main PID: 11831 (code=killed, signal=ABRT) Jul 24 15:43:49 orangepipc emby-server[11831]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal Jul 24 15:43:49 orangepipc emby-server[11831]: Info App: PRAGMA synchronous=1 Jul 24 15:43:49 orangepipc emby-server[11831]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.1026374 second Jul 24 15:43:49 orangepipc emby-server[11831]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint Jul 24 15:43:49 orangepipc emby-server[11831]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0236159 s Jul 24 15:43:49 orangepipc emby-server[11831]: Info App: All entry points have started Jul 24 18:01:52 orangepipc emby-server[11831]: *** Error in `/opt/emby-server/system/EmbyServer': double free or corruption (fasttop): 0xaec061f8 Jul 24 18:01:52 orangepipc systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT Jul 24 18:01:52 orangepipc systemd[1]: emby-server.service: Unit entered failed state. Jul 24 18:01:52 orangepipc systemd[1]: emby-server.service: Failed with result 'signal'. Active: active (running) since Wed 2018-07-25 00:18:28 EEST; 2s ago Active: failed (Result: signal) since Wed 2018-07-25 00:59:57 EEST; 7h ago Process: 5142 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=ABRT) Main PID: 5142 (code=killed, signal=ABRT) Jul 25 00:38:07 orangepipc emby-server[5142]: _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Jul 25 00:38:07 orangepipc emby-server[5142]: Stream #0:3: Attachment: ttf Jul 25 00:38:07 orangepipc emby-server[5142]: Metadata: Jul 25 00:38:07 orangepipc emby-server[5142]: filename : OpenSans-Semibold.ttf Jul 25 00:38:07 orangepipc emby-server[5142]: mimetype : application/x-truetype-font Jul 25 00:38:07 orangepipc emby-server[5142]: Unsupported codec with id 98304 for input stream 3 Jul 25 00:59:57 orangepipc emby-server[5142]: *** Error in `/opt/emby-server/system/EmbyServer': double free or corruption (fasttop): 0xac82c040 * Jul 25 00:59:57 orangepipc systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT Jul 25 00:59:57 orangepipc systemd[1]: emby-server.service: Unit entered failed state. Jul 25 00:59:57 orangepipc systemd[1]: emby-server.service: Failed with result 'signal'. Active: active (running) since Wed 2018-07-25 08:45:58 EEST; 5s ago Main PID: 4866 (EmbyServer) Tasks: 7 (limit: 4915) CGroup: /system.slice/emby-server.service └─4866 /opt/emby-server/system/EmbyServer -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ Jul 25 08:46:02 orangepipc emby-server[4866]: Info App: Loading Emby.Notifications, Version=3.5.0.0, Culture=neutral, PublicKeyToken=null Jul 25 08:46:02 orangepipc emby-server[4866]: Info App: Loading MediaBrowser.XbmcMetadata, Version=3.5.0.0, Culture=neutral, PublicKeyToken=null Jul 25 08:46:02 orangepipc emby-server[4866]: Info App: Loading Emby.Server.Connect, Version=3.5.0.0, Culture=neutral, PublicKeyToken=null Jul 25 08:46:02 orangepipc emby-server[4866]: Info App: Loading Emby.Server.Sync, Version=3.5.0.0, Culture=neutral, PublicKeyToken=null Jul 25 08:46:03 orangepipc emby-server[4866]: Info SqliteUserRepository: Sqlite version: 3.24.0 Jul 25 08:46:03 orangepipc emby-server[4866]: Info SqliteUserRepository: Sqlite compiler options: COMPILER=gcc-6.4.1 20170707,ENABLE_COLUMN_METADA Jul 25 08:46:04 orangepipc emby-server[4866]: Info SqliteUserRepository: Default journal_mode for /var/lib/emby/data/users.db is wal Jul 25 08:46:04 orangepipc emby-server[4866]: Info SqliteUserRepository: PRAGMA synchronous=1 Jul 25 08:46:04 orangepipc emby-server[4866]: Info AuthenticationRepository: Default journal_mode for /var/lib/emby/data/authentication.db is wal Jul 25 08:46:04 orangepipc emby-server[4866]: Info AuthenticationRepository: PRAGMA synchronous=1 Edited July 25, 2018 by Loke Link to comment Share on other sites More sharing options...
Luke 37113 Posted July 25, 2018 Share Posted July 25, 2018 Can you try upgrading to 3.5.1? thanks. Link to comment Share on other sites More sharing options...
Loke 4 Posted July 25, 2018 Author Share Posted July 25, 2018 Can you try upgrading to 3.5.1? thanks. Sure thing. Link to comment Share on other sites More sharing options...
Luke 37113 Posted July 26, 2018 Share Posted July 26, 2018 Let us know how you get on. If you still have an issue, go into dlna settings and set the blast interval from 30 seconds to 1800. That is the new default for new installs. Than restart the server. Thanks. Link to comment Share on other sites More sharing options...
Loke 4 Posted July 26, 2018 Author Share Posted July 26, 2018 (edited) didn't last more than ~3 hours. Will try the DLNA settings now. With blast you meant Alive message interval (seconds) ? Cause Client discovery interval (seconds) refuses a value above 300 Active: failed (Result: signal) since Thu 2018-07-26 01:15:52 EEST; 10h ago Process: 10501 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=ABRT) Main PID: 10501 (code=killed, signal=ABRT) Jul 26 00:02:03 orangepipc emby-server[10501]: _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Jul 26 00:02:03 orangepipc emby-server[10501]: _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Jul 26 00:02:03 orangepipc emby-server[10501]: Stream mapping: Jul 26 00:02:03 orangepipc emby-server[10501]: Stream #0:2 -> #0:0 (copy) Jul 26 00:02:03 orangepipc emby-server[10501]: Press [q] to stop, [?] for help Jul 26 00:02:15 orangepipc emby-server[10501]: [1.5K blob data] Jul 26 00:02:15 orangepipc emby-server[10501]: video:0kB audio:0kB subtitle:23kB other streams:0kB global headers:1kB muxing overhead: 49.098526% Jul 26 01:15:52 orangepipc systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT Jul 26 01:15:52 orangepipc systemd[1]: emby-server.service: Unit entered failed state. Jul 26 01:15:52 orangepipc systemd[1]: emby-server.service: Failed with result 'signal'. Edited July 26, 2018 by Loke Link to comment Share on other sites More sharing options...
Luke 37113 Posted July 26, 2018 Share Posted July 26, 2018 Yes i meant Alive message interval (seconds). Thanks. Link to comment Share on other sites More sharing options...
Loke 4 Posted July 29, 2018 Author Share Posted July 29, 2018 (edited) Crash on 28/07 23:11:40, last couple of days though! And it crashed after the restart couple of hours later: Active: failed (Result: signal) since Sun 2018-07-29 17:54:01 EEST; 2h 39min ago Process: 6955 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=ABRT) Main PID: 6955 (code=killed, signal=ABRT) Jul 29 15:39:17 orangepipc emby-server[6955]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal Jul 29 15:39:17 orangepipc emby-server[6955]: Info App: PRAGMA synchronous=1 Jul 29 15:39:17 orangepipc emby-server[6955]: Info TaskManager: Check for application updates Completed after 0 minute(s) and 5 seconds Jul 29 15:39:17 orangepipc emby-server[6955]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.1191469 seconds Jul 29 15:39:17 orangepipc emby-server[6955]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint Jul 29 15:39:18 orangepipc emby-server[6955]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0304007 seconds Jul 29 15:39:18 orangepipc emby-server[6955]: Info App: All entry points have started Jul 29 17:54:01 orangepipc systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT Jul 29 17:54:01 orangepipc systemd[1]: emby-server.service: Unit entered failed state. Jul 29 17:54:01 orangepipc systemd[1]: emby-server.service: Failed with result 'signal'. There is one thing I will try the following days. Edited July 29, 2018 by Loke Link to comment Share on other sites More sharing options...
Luke 37113 Posted July 29, 2018 Share Posted July 29, 2018 What will you try? Link to comment Share on other sites More sharing options...
Loke 4 Posted July 30, 2018 Author Share Posted July 30, 2018 (edited) Well I thought I had random episodes on the Library top dir, but that's not the case. The only thing that is not following Emby standards is one folder that has episodes from random series inside. Could that be somehow the problem? Also upgraded to 3.5.2 Just for sanity's sake: moved around when I setup Emby, often written to paths to the attached sata disk. Edited July 30, 2018 by Loke Link to comment Share on other sites More sharing options...
Luke 37113 Posted July 30, 2018 Share Posted July 30, 2018 Well it shouldn't cause a crash, no. Can you try disabling the server's dlna features? Thanks. Link to comment Share on other sites More sharing options...
Loke 4 Posted July 30, 2018 Author Share Posted July 30, 2018 (edited) Well it shouldn't cause a crash, no. Can you try disabling the server's dlna features? Thanks. Went ahead and disabled everything. (Blast alive I might turn back on depending if emby doesn't perform as I expect) Edited July 30, 2018 by Loke Link to comment Share on other sites More sharing options...
Luke 37113 Posted July 30, 2018 Share Posted July 30, 2018 Thanks. Link to comment Share on other sites More sharing options...
Loke 4 Posted September 13, 2018 Author Share Posted September 13, 2018 So there are still some crashes for no, apparent, reason but they are less frequent. Sometimes it stays alive for days at a time The biggest change was with DLNA I reckon. Link to comment Share on other sites More sharing options...
Luke 37113 Posted September 13, 2018 Share Posted September 13, 2018 Thanks for the feedback. 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