japi 0 Posted December 14, 2017 Share Posted December 14, 2017 Hi I've been using emby server with my odroid-xu4 ubuntu 16.04 for half year and it has been worked fine until month or so after upgrading packets it started to die after couple minutes of streaming. Now service dies ● emby-server.service - Emby Media Server Loaded: loaded (/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2017-12-14 17:21:15 EET; 1min 17s ago Process: 18575 ExecStopPost=/usr/bin/emby-server clear (code=exited, status=0/SUCCESS) Process: 18331 ExecStart=/usr/bin/emby-server start (code=exited, status=134) Main PID: 18331 (code=exited, status=134) Dec 14 17:19:58 odroid systemd[1]: Started Emby Media Server. Dec 14 17:19:58 odroid su[18331]: Successful su for emby by root Dec 14 17:19:58 odroid su[18331]: + ??? root:emby Dec 14 17:19:58 odroid su[18331]: pam_unix(su:session): session opened for user emby by (uid=0) Dec 14 17:21:15 odroid systemd[1]: emby-server.service: Main process exited, code=exited, status=134/n/a Dec 14 17:21:15 odroid systemd[1]: emby-server.service: Unit entered failed state. Dec 14 17:21:15 odroid systemd[1]: emby-server.service: Failed with result 'exit-code'. what might be wrong? I'm totally stuck... Thanks Japi Link to comment Share on other sites More sharing options...
mastrmind11 717 Posted December 14, 2017 Share Posted December 14, 2017 Hi I've been using emby server with my odroid-xu4 ubuntu 16.04 for half year and it has been worked fine until month or so after upgrading packets it started to die after couple minutes of streaming. Now service dies ● emby-server.service - Emby Media Server Loaded: loaded (/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2017-12-14 17:21:15 EET; 1min 17s ago Process: 18575 ExecStopPost=/usr/bin/emby-server clear (code=exited, status=0/SUCCESS) Process: 18331 ExecStart=/usr/bin/emby-server start (code=exited, status=134) Main PID: 18331 (code=exited, status=134) Dec 14 17:19:58 odroid systemd[1]: Started Emby Media Server. Dec 14 17:19:58 odroid su[18331]: Successful su for emby by root Dec 14 17:19:58 odroid su[18331]: + ??? root:emby Dec 14 17:19:58 odroid su[18331]: pam_unix(su:session): session opened for user emby by (uid=0) Dec 14 17:21:15 odroid systemd[1]: emby-server.service: Main process exited, code=exited, status=134/n/a Dec 14 17:21:15 odroid systemd[1]: emby-server.service: Unit entered failed state. Dec 14 17:21:15 odroid systemd[1]: emby-server.service: Failed with result 'exit-code'. what might be wrong? I'm totally stuck... Thanks Japi What is the output of : sudo journalctl -xe | grep -emby Link to comment Share on other sites More sharing options...
japi 0 Posted December 14, 2017 Author Share Posted December 14, 2017 What is the output of : sudo journalctl -xe | grep -emby It shows nothing Link to comment Share on other sites More sharing options...
dcrdev 251 Posted December 14, 2017 Share Posted December 14, 2017 Typo: sudo journalctl -xe | grep emby Link to comment Share on other sites More sharing options...
mastrmind11 717 Posted December 14, 2017 Share Posted December 14, 2017 It shows nothing what about sudo journalctl -xe | grep emby if nothing, what about sudo journalctl -xe Link to comment Share on other sites More sharing options...
japi 0 Posted December 14, 2017 Author Share Posted December 14, 2017 (edited) heres log attached. log.txt Edited December 14, 2017 by japi Link to comment Share on other sites More sharing options...
Solution Luke 37186 Posted December 14, 2017 Solution Share Posted December 14, 2017 I notice you're running mono 5.4. Our highest supported version is 4.8.1. We've seen crashes with anything beyond that. Please consider rolling that back. Thanks. 1 Link to comment Share on other sites More sharing options...
mastrmind11 717 Posted December 14, 2017 Share Posted December 14, 2017 Was just about to say your mono version is no good but @@Luke beat me. Anyway, that should fix it. Link to comment Share on other sites More sharing options...
japi 0 Posted December 14, 2017 Author Share Posted December 14, 2017 Thanks downgraded mono to 4.8.1 and now it works Link to comment Share on other sites More sharing options...
Luke 37186 Posted December 14, 2017 Share Posted December 14, 2017 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