foryst 0 Posted December 3, 2017 Posted December 3, 2017 Just setup a 918+ yesterday, and thought I'd try emby. After install hibernation stopped from what appears to be a constant slow drip of HD writes from the emby logs, notably the "start-stop-status_########.log" files under /var/packages/EmbyServer/target/var/log/ E.g., here's the the last few dozen rows from my current log file, just for the last two minutes: 2017-12-03 08:04:29 UTC] Script called with action [status]... [2017-12-03 08:04:29 UTC] >> Process [24789] exists. [2017-12-03 08:04:29 UTC] >> Emby Server is running. [2017-12-03 08:04:29 UTC] >> Exit status is [0]. [2017-12-03 08:04:29 UTC] Script called with action [log]... [2017-12-03 08:04:29 UTC] >> Returning log file location [/var/packages/EmbyServer/target/var/logs/start-stop-status_20171203.log]. [2017-12-03 08:04:29 UTC] >> Exit status is [0]. [2017-12-03 08:04:55 UTC] Script called with action [status]... [2017-12-03 08:04:55 UTC] >> Process [24789] exists. [2017-12-03 08:04:55 UTC] >> Emby Server is running. [2017-12-03 08:04:55 UTC] >> Exit status is [0]. [2017-12-03 08:04:55 UTC] Script called with action [log]... [2017-12-03 08:04:55 UTC] >> Returning log file location [/var/packages/EmbyServer/target/var/logs/start-stop-status_20171203.log]. [2017-12-03 08:04:55 UTC] >> Exit status is [0]. [2017-12-03 08:05:24 UTC] Script called with action [status]... [2017-12-03 08:05:24 UTC] >> Process [24789] exists. [2017-12-03 08:05:24 UTC] >> Emby Server is running. [2017-12-03 08:05:24 UTC] >> Exit status is [0]. [2017-12-03 08:05:24 UTC] Script called with action [log]... [2017-12-03 08:05:24 UTC] >> Returning log file location [/var/packages/EmbyServer/target/var/logs/start-stop-status_20171203.log]. [2017-12-03 08:05:24 UTC] >> Exit status is [0]. [2017-12-03 08:05:50 UTC] Script called with action [status]... [2017-12-03 08:05:50 UTC] >> Process [24789] exists. [2017-12-03 08:05:50 UTC] >> Emby Server is running. [2017-12-03 08:05:50 UTC] >> Exit status is [0]. [2017-12-03 08:05:50 UTC] Script called with action [log]... [2017-12-03 08:05:50 UTC] >> Returning log file location [/var/packages/EmbyServer/target/var/logs/start-stop-status_20171203.log]. [2017-12-03 08:05:50 UTC] >> Exit status is [0]. [2017-12-03 08:06:34 UTC] Script called with action [status]... [2017-12-03 08:06:34 UTC] >> Process [24789] exists. [2017-12-03 08:06:34 UTC] >> Emby Server is running. [2017-12-03 08:06:34 UTC] >> Exit status is [0]. [2017-12-03 08:06:35 UTC] Script called with action [log]... [2017-12-03 08:06:35 UTC] >> Returning log file location [/var/packages/EmbyServer/target/var/logs/start-stop-status_20171203.log]. [2017-12-03 08:06:35 UTC] >> Exit status is [0]. It appears to be doing [status] / [log] call every 16 seconds. Further more, even after the Emby Server is stopped, whatever process is filling this log continues running: [2017-12-03 08:10:15 UTC] Script called with action [status]... [2017-12-03 08:10:15 UTC] >> PID file [/var/packages/EmbyServer/target/var/embysvr.pid] does not exist. [2017-12-03 08:10:15 UTC] >> Emby Server is not running. [2017-12-03 08:10:15 UTC] >> Exit status is [3]. [2017-12-03 08:10:15 UTC] Script called with action [log]... [2017-12-03 08:10:15 UTC] >> Returning log file location [/var/packages/EmbyServer/target/var/logs/start-stop-status_20171203.log]. [2017-12-03 08:10:15 UTC] >> Exit status is [0]. [2017-12-03 08:10:30 UTC] Script called with action [status]... [2017-12-03 08:10:30 UTC] >> PID file [/var/packages/EmbyServer/target/var/embysvr.pid] does not exist. [2017-12-03 08:10:31 UTC] >> Emby Server is not running. [2017-12-03 08:10:31 UTC] >> Exit status is [3]. [2017-12-03 08:10:31 UTC] Script called with action [log]... [2017-12-03 08:10:31 UTC] >> Returning log file location [/var/packages/EmbyServer/target/var/logs/start-stop-status_20171203.log]. [2017-12-03 08:10:31 UTC] >> Exit status is [0]. [2017-12-03 08:10:47 UTC] Script called with action [status]... [2017-12-03 08:10:47 UTC] >> PID file [/var/packages/EmbyServer/target/var/embysvr.pid] does not exist. [2017-12-03 08:10:47 UTC] >> Emby Server is not running. [2017-12-03 08:10:47 UTC] >> Exit status is [3]. [2017-12-03 08:10:47 UTC] Script called with action [log]... [2017-12-03 08:10:47 UTC] >> Returning log file location [/var/packages/EmbyServer/target/var/logs/start-stop-status_20171203.log]. [2017-12-03 08:10:47 UTC] >> Exit status is [0].
solabc16 379 Posted December 7, 2017 Posted December 7, 2017 Hello @@foryst These entries are generated by DSM’s Package Center when it’s open and the package in question has the focus. Can you confirm if you had an active DSM session at the time? Best - James
foryst 0 Posted December 8, 2017 Author Posted December 8, 2017 Blast! When you're right, you're right. I'm still having hibernation issues but will have to keep digging.
foryst 0 Posted December 9, 2017 Author Posted December 9, 2017 Well, I still don't know where in emby it's preventing hibernation, but I can verify that it's either emby or something emby tangential. I just ran 3 idle tests from a fresh system reboot with minimal network activity, nothing with an emby client turned on, and bare bones packages and ran a timer starting at a manual logout from the DSM session and window close to the time that the HDDs hibernated based on the 5 status lights on the front of the chassis. In each case, the NAS successfully entered drive hibernation within 10-14 minutes. Next, I went back into DSM started the emby package and repeated logout procedures. After 30 minutes of no hibernation, I went back in, stopped emby, and repeated logout procedures yet again, and this time the NAS again successfully hibernated in the expected window. NAS: DS918+ DSM: DSM 6.1.4-15217 Update 2 Running Packages: Filestation 1.1.1-0110, Universal Search 1.0.7-0152 Emby: 3.2.50.0-1
solabc16 379 Posted December 11, 2017 Posted December 11, 2017 Hi @@foryst Thanks for the update, if possible can you run the send logs utility as documented on the wiki here:- https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs I can then take a closer look to see what's happening. If possible can you given me the approximate times you performed the above tests? Best - James
foryst 0 Posted December 12, 2017 Author Posted December 12, 2017 Logs sent: sendlogs_Aurora_synology_apollolake_918+_20171212T045216UTC.tgz Tests were run Saturday, 20171209 around 8AM - 10 AM PST.
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