Jump to content

Synology NAS (DS415+) does not hibernate after installing Emby Server


budha300
 Share

Go to solution Solved by solabc16,

Recommended Posts

Dear Community Experts, I am a newbie and I like Emby a lot. I have Synology DS415+. Since installing Emby, Synology unit is messed up with hibernation - basically, the unit wakes every 30min / 1hr when there is no need for it. When I uninstall Emby, NAS goes into hibernation very nicely. It does look like the Emby server in NAS is impacting hibernation. I tried to adjust 'scheduled tasks' even to once/week (e.g., media indexing, media scan, etc), however this does not. I would be grateful if experts in the community have solution to fix this issue. Thanks so much.

Link to comment
Share on other sites

Happy2Play

Not a nas user but could the server be communicating with other devices on your network, dlna or open apps?  Your server log should shed some light also.

Link to comment
Share on other sites

solabc16

Hello @@budha300

 

If possible, can you send me your logs: https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs

 

Also, can you give us an idea of your setup.

 

e.g.

 

     What type of content do you have loaded?

     What clients are you using for playback?

     Are you using live TV?

 

Best

- James

  • Like 1
Link to comment
Share on other sites

Dear James, I am travelling and will send you the logs soon. I have loaded media contents to Emby server - Movies, TV shows, Music. I am using Emby for Kodi on OSMC/LibreELEC/iPad for playback. I am not using Live TV at present. Apart from the logs, please let me know if there is any other information that may be of help. I will come back to you on the logs soon. Thanks again!

Link to comment
Share on other sites

Dear James,

 

Please find below the log filename

 

sendlogs_DS-REEYAN_synology_avoton_415+_20160922T050902UTC.tgz 

 

I would be grateful for your review - perhaps you will be able to detect the issue.

 

as stated previously, media contents to Emby server include - Movies, TV shows, music. I am using Emby for Kodi on OSMC/LibreELEC/iPad for playback. I am not using Live TV at present. Thanks again! B

 

Link to comment
Share on other sites

  • 5 weeks later...

I'm trying to track down the same issue. No hibernation if Emby is running. If I stop Emby, the NAS hibernates just fine. Based on the logs it looks like it's the Envy Android app on my phone which is checking periodically for items to sync.

 

Sent from my SM-P605 using Tapatalk

Link to comment
Share on other sites

So after removing my NAS as a server in the Android app, there were no more entries in the log file about the app checking for media to sync. Here is what the log file looks like over a period of 8 hours while I was at work:

2016-10-24 09:19:40.6691 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-24 09:19:42.2644 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 09:19:42.6041 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 10:19:40.6691 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-24 10:19:43.2665 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 10:19:43.6054 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 11:19:40.6694 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-24 11:19:42.2984 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 11:19:42.6384 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 12:19:40.6963 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-24 12:19:42.3214 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 12:19:42.6702 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 13:19:40.6951 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-24 13:19:42.2639 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 13:19:42.6108 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 13:37:30.5877 Info TaskManager: IntervalTrigger fired for task: Download missing subtitles
2016-10-24 13:37:30.5877 Info TaskManager: Queueing task SubtitleScheduledTask
2016-10-24 13:37:30.5877 Info TaskManager: Executing Download missing subtitles
2016-10-24 13:37:30.5878 Info TaskManager: Download missing subtitles Completed after 0 minute(s) and 0 seconds
2016-10-24 13:37:30.5889 Info TaskManager: ExecuteQueuedTasks
2016-10-24 14:19:40.6957 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-24 14:19:42.3190 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 14:19:42.6581 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 15:19:40.6957 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-24 15:19:42.4495 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 15:19:42.8115 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 16:19:40.6988 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-24 16:19:42.3570 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 16:19:42.6957 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-24 17:19:35.4651 Info HttpClient: HttpClientManager POST: https://www.mb3admin.com/admin/service/registration/validate
2016-10-24 17:19:40.7076 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com

Here is the corresponding log file from the NAS for the same period (sorted and re-formated for clarity):

2016/10/24 08:11	Internal disks woke up from hibernation.
2016/10/24 08:44	Internal disks woke up from hibernation.
2016/10/24 10:04	Internal disks woke up from hibernation.
2016/10/24 11:20	Internal disks woke up from hibernation.
2016/10/24 12:20	Internal disks woke up from hibernation.
2016/10/24 13:12	Internal disks woke up from hibernation.
2016/10/24 14:20	Internal disks woke up from hibernation.
2016/10/24 14:57	Internal disks woke up from hibernation.
2016/10/24 15:20	Internal disks woke up from hibernation.
2016/10/24 16:20	Internal disks woke up from hibernation.
2016/10/24 17:20	Internal disks woke up from hibernation.
2016/10/24 18:14	Internal disks woke up from hibernation.

Based on the above, it would seem that the checking of the IP address and then the updating of Emby connect every hour does in fact cause the NAS to wake up.

 

I have just removed the Emby Connect mapping for the one local user account which had this, which will hopefully remove the need for Emby to do the IP address check and Emby Connect update. Hopefully this resolves the issue.

 

Edit: My NAS is set to hibernate after 20 minutes, by the way.

Edited by newb
  • Like 1
Link to comment
Share on other sites

budha300

Thank you very much Newb. I will give this a go and see what happens.

I really appreciate your efforts to resolve this.

best,

Link to comment
Share on other sites

Hi @@budha300,

 

No problem, I am trying to resolve the issue for myself as well.

 

After looking through the Emby code, however, I do not think that this issue can be resolved easily without a code change.

Emby automatically tries to get the public IP address of the server every hour. After a valid IP address is obtained, Emby connect is updated, causing disk activity and logging - this either wakes up the NAS or causes the NAS to not hibernate.

 

So, @@Luke, would it be possible to allow us the option to turn off the automatic public IP address detection which ultimately prevents the NAS from hibernating? I actually do not need public IP address detection because my NAS is already doing DDNS for me and have already configured an external domain in Emby. I am not sure whether all users running Emby on their NAS devices would be willing to give up the hourly public IP address detection for the sake of allowing their NAS to hibernate, but if they have already configured an external domain, then I do not see why public IP address detection would be necessary.

 

Your thoughts?

Edited by newb
Link to comment
Share on other sites

solabc16

Thanks for the information @@newb, this is the same position we got to when researching this earlier in the month with @@budha300.

 

Copied below, so we can keep the conversation together in one thread.

 

It's not unusual for server type applications to generate frequent or periodic disk I/O when running, it's par for the course.

 

The Synology platform, except for the DS213+ and D413 which support system hibernation, only support HDD hibernation; so it's expected that this causes the HDDs to wake up (or not sleep).

 

It's something we will need to think about some more, if hibernation is a key requirement.

 

The interim solution, if you're not scheduling Live TV recording, is to only start the package when you intend to use it or use the scheduler to start/stop the package based on your typical viewing habits.

 

Best

- James

 

 


Hello @@budha300
 
Thanks for the update. As I mentioned, it will take a few iterations to understand what activity in particular is causing the HDDs to come out of hibernation.
 
Please can you post a screenshot of your hibernation configuration.
 
From looking at the log and specifically the timing, this would appear to be the most likely cause, now we have quitened everything else down.

2016-09-30 16:02:34.2629 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-09-30 16:02:35.1243 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=77934b4d3016ef323b73faca18637562
2016-09-30 16:02:35.3062 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=77934b4d3016ef323b73faca18637562

2016-09-30 17:02:34.2628 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-09-30 17:02:35.0997 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=77934b4d3016ef323b73faca18637562
2016-09-30 17:02:35.2808 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=77934b4d3016ef323b73faca18637562

2016-09-30 18:02:34.2630 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-09-30 18:02:35.1131 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=77934b4d3016ef323b73faca18637562
2016-09-30 18:02:35.2917 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=77934b4d3016ef323b73faca18637562

 
- James


Edited by solabc16
Link to comment
Share on other sites

That is not preventing it, it is just what you currently happen to think is preventing it.

 

Indeed, it is what I think is preventing it. You are in the best position to confirm whether this is so or not. Please do not take me jumping to conclusions the wrong way - in the end, all I am trying to do is to have a hibernating NAS while at work :) I apologize if it came out the wrong way.

Link to comment
Share on other sites

It's something we will need to think about some more, if hibernation is a key requirement.

 

The interim solution, if you're not scheduling Live TV recording, is to only start the package when you intend to use it or use the scheduler to start/stop the package based on your typical viewing habits.

 

Thanks @@solabc16!

 

I would not say that hibernation is a key requirement, it is a nice to have at this stage. My argument for it would be, if the hard disks are only really being used for a few hours a day, why should they be on 24/7? Could their lifespan be extended if the NAS were to hibernate? Maybe. Is it worth it, given that hard disks are pretty easily replaceable should they fail? I am not sure. That is why I cannot justify hibernation as a key requirement if it means a big code change.

 

Your alternate solution of using the DSM scheduler would work, thanks!

Link to comment
Share on other sites

solabc16

Hello @@newb

 

If there are notable constraints on heat generation and/or power consumption, then it may make sense to hibernate the disks.

 

I would not do it solely for the purpose of attempting to increase the lifespan of the drives.

 

In terms of behaviour, what you would want to avoid is overly frequent sleep/wake cycles.

 

So, to that end, the task scheduler is probably a better solution and you have the granularity to do different things on weekdays to weekends, etc.

 

If you have remote access to your DSM desktop configured, then logging in and starting up Emby Server manually isn't a massive overhead either, if you've prioritised the above concerns over seamless 24/7 availability.

 

Best

- James

Edited by solabc16
  • Like 1
Link to comment
Share on other sites

Can someone do a test and set your sleep time to something less than 10 minutes and see if it is able to hibernate? thanks.

Link to comment
Share on other sites

@@Luke

 

I think @@solabc16 was absolutely correct in distinguishing between NAS hibernation and HDD hibernation being controlled by the NAS where disks are spun down while the NAS continues to operate in a low power state. It is definitely the latter which the bulk of the Synology devices support. To wake up the drives, one does not need WOL or Wake on WAN, the Synology OS automatically wakes up the drives when there is disk activity and similarly it does not allow the drives to hibernate if they have not been idle for a sufficient period of time.

 

The minimum HDD hibernation time is 10 minutes in the DSM interface (at least on my NAS):

580f96c787fa5_Powersettings.png

 

 

I changed it to 10 minutes this morning. Here is the Emby log from this morning until I got back:

2016-10-25 09:19:40.7135 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-25 09:19:42.3879 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 09:19:42.7261 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 10:19:40.7144 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-25 10:19:42.3820 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 10:19:42.7752 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 11:19:40.7152 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-25 11:19:42.3467 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 11:19:42.6871 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 12:19:40.7153 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-25 12:19:44.9581 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 12:19:45.5687 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 13:19:40.7158 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-25 13:19:42.2725 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 13:19:42.6134 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 13:37:30.5875 Info TaskManager: IntervalTrigger fired for task: Download missing subtitles
2016-10-25 13:37:30.5875 Info TaskManager: Queueing task SubtitleScheduledTask
2016-10-25 13:37:30.5875 Info TaskManager: Executing Download missing subtitles
2016-10-25 13:37:30.5879 Info TaskManager: Download missing subtitles Completed after 0 minute(s) and 0 seconds
2016-10-25 13:37:30.5916 Info TaskManager: ExecuteQueuedTasks
2016-10-25 14:19:40.7164 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-25 14:19:42.3556 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 14:19:42.6934 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 15:19:40.7172 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-25 15:19:42.3361 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 15:19:42.6717 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 16:19:40.7173 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-25 16:19:42.3729 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 16:19:42.7137 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 17:19:35.3501 Info HttpClient: HttpClientManager POST: https://www.mb3admin.com/admin/service/registration/validate
2016-10-25 17:19:40.7173 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-10-25 17:19:42.3490 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=30f83995585ed8ef3c38338bdaca06ee
2016-10-25 17:19:42.6876 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=30f83995585ed8ef3c38338bdaca06ee

Here is the log from the NAS showing all the times the drives came out of hibernation:

2016/10/25 08:35    HDD hibernation time is set to [10 minutes].
2016/10/25 08:52    Internal disks woke up from hibernation.
2016/10/25 09:20    Internal disks woke up from hibernation.
2016/10/25 09:46    Internal disks woke up from hibernation.
2016/10/25 10:20    Internal disks woke up from hibernation.
2016/10/25 10:47    Internal disks woke up from hibernation.
2016/10/25 11:20    Internal disks woke up from hibernation.
2016/10/25 12:20    Internal disks woke up from hibernation.
2016/10/25 13:19    Internal disks woke up from hibernation.
2016/10/25 13:38    Internal disks woke up from hibernation.
2016/10/25 14:20    Internal disks woke up from hibernation.
2016/10/25 15:20    Internal disks woke up from hibernation.
2016/10/25 15:44    Internal disks woke up from hibernation.
2016/10/25 15:57    Internal disks woke up from hibernation.
2016/10/25 16:20    Internal disks woke up from hibernation.
2016/10/25 16:45    Internal disks woke up from hibernation.
2016/10/25 17:20    Internal disks woke up from hibernation.

As you can see, most of the times that the drives came out of hibernation correspond to an entry in the Emby log. There are a few other wake ups that might have been caused by something else, but there is definitely a correlation between Emby auto detecting the WAN IP address every hour and the disks coming out of hibernation just after that.

Link to comment
Share on other sites

Ok, so you can't test lower than 10 minutes. In order to test a theory of mine then, i will add a change to the next beta. thanks.

Link to comment
Share on other sites

solabc16

Thanks for the feedback @@newb, that now gives us a good, clear and consistent picture of what we suspected was happening.

 

Did you use 'syno_hibernate_debug_tool --enable 1' and pull the data from /var/log/messages?

 

- James

Link to comment
Share on other sites

Hi @@solabc16,

 

There was no command line involved.

 

I had the "Enable hibernation logs" option enabled on the same tab where you enable HDD hibernation (Control Panel -> Hardware & Power -> HDD Hibernation). These extra log entries are then accessible via Log Center. I just exported the logs to CSV from Log Center, sorted ascending by date and removed all but the Date & Time + Event columns.

Link to comment
Share on other sites

solabc16

Ah, ok - thanks, wanted to make sure we were pulling data from the same place.

 

- James

Edited by solabc16
Link to comment
Share on other sites

  • 4 weeks later...
Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...