sea3pea0 5 Posted August 17, 2016 Share Posted August 17, 2016 (edited) If I shutdown emby from the web app, I can't start it from the synology package manager. I recently started experiencing this problem after updating from beta 3.1.105.0 to 3.1.106.0. However, if I shut down emby from the synology package manager, it will start back up from the package manager just fine Here are the server logs from the point the shutdown command was issued in the web app. This is what I am seeing in the start-stop-status log when I try and start emby: [2016-08-17 23:06:45 UTC] Script called with action [status]... [2016-08-17 23:06:45 UTC] >> PID file [/var/packages/EmbyServer/target/var/embysvr.pid] does not exist. [2016-08-17 23:06:45 UTC] >> Emby Server is not running. [2016-08-17 23:06:45 UTC] >> Exit status is [3]. I am running emby version 3.1.106.0 on a synology Ds412+ running DSM 6.0.1-7393 Update 2 Edited August 17, 2016 by sea3pea0 Link to comment Share on other sites More sharing options...
Luke 36887 Posted August 18, 2016 Share Posted August 18, 2016 Try removing the kodi sync plugin and let us know if the issue persists with just the core server. Thanks. Link to comment Share on other sites More sharing options...
solabc16 379 Posted August 18, 2016 Share Posted August 18, 2016 (edited) Hi @@sea3pea0 Thanks for the report, I'll take a look at this - can you send me your logs using this procedure: https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs Best - James Edited August 18, 2016 by solabc16 Link to comment Share on other sites More sharing options...
Abobader 2934 Posted August 19, 2016 Share Posted August 19, 2016 Good day, Good idea to send log to James, but I faced that before and simple re booting your nas will fix the issue. My best Link to comment Share on other sites More sharing options...
solabc16 379 Posted August 19, 2016 Share Posted August 19, 2016 Morning Rebooting is a 'fix', but I would like to find out the root cause and resolve this properly. A reboot is disruptive, especially if the NAS is being used for multiple other purposes. - James Link to comment Share on other sites More sharing options...
Solution solabc16 379 Posted August 19, 2016 Solution Share Posted August 19, 2016 Hello @sea3pea0 This issue is resolved in releases 3.0.6060.0-15 (stable) and 3.1.113.0-2 (beta), which are available on the beta channel. Best - James Link to comment Share on other sites More sharing options...
Abobader 2934 Posted August 19, 2016 Share Posted August 19, 2016 Morning Rebooting is a 'fix', but I would like to find out the root cause and resolve this properly. A reboot is disruptive, especially if the NAS is being used for multiple other purposes. - James True buddy, but no user if the program not running, unless it mainly share folders matters, then yes Well my suggestion that he make his emby running while waiting for help after providing the log. Link to comment Share on other sites More sharing options...
sea3pea0 5 Posted August 20, 2016 Author Share Posted August 20, 2016 Thanks it is fixed now. @@solabc16 I would've sent the logs but I have since updated and no longer have this problem. If I run into it again I will send logs. @@Abobader Thanks, yea I figured out by restarting the NAS, I was able to get emby running again when I was having the problem. Link to comment Share on other sites More sharing options...
solabc16 379 Posted August 20, 2016 Share Posted August 20, 2016 Thanks for the feedback @sea3pea0. 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