Emby preventing Synology from sleeping

[mph55 1]

Hi,

I started noticing my synology NAS stopped sleeping after installing version 3.0.5818.0.  When I stop the emby process the NAS goes to sleep as usual.  I saw the changelog mentioned that real time monitoring was enabled in Linux so I changed the setting to No in Media Library but it's still not sleeping.  In my log file I see that emby is pinging itself every 3 minutes.  This constant pinging is not happening in my older log files.   Is there a feature or setting that's controlling this that I can disable?

[Luke 36997]

Thanks, it will be reviewed.

[richie83 5]

Any update on this? Over the weekend I've been trialling Plex vs. Emby and the Emby Kodi addon is just so much more superior in every way. Less laggy and compatible with normal skins. 

 

The only thing stopping me is the sleep issue with Emby (which admittedly, is an issue with Plex too).

 

Even if we can have some guidance as to what is causing it not to sleep (I assume scanning or logs)?

[Luke 36997]

Any update on this? Over the weekend I've been trialling Plex vs. Emby and the Emby Kodi addon is just so much more superior in every way. Less laggy and compatible with normal skins. 

 

The only thing stopping me is the sleep issue with Emby (which admittedly, is an issue with Plex too).

 

Even if we can have some guidance as to what is causing it not to sleep (I assume scanning or logs)?

 

Hi, it is being looked into. Thanks.

[richie83 5]

I've done a bit of investigating on this and have narrowed it down to what is waking the Synology. I unplugged the Synology unit from the network and ran it with only the emby package installed. The log gives me this:

2016-02-27 00:00:00.1127 Info TaskManager: Start new log file Completed after 0 minute(s) and 0 seconds
2016-02-27 00:00:11.5676 Info TaskManager: ExecuteQueuedTasks
2016-02-27 01:08:44.8598 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-02-27 01:08:48.3994 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=***
2016-02-27 01:08:49.0934 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=***
2016-02-27 04:08:45.2364 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-02-27 04:08:47.8183 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=***
2016-02-27 04:08:48.3821 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=***
2016-02-27 07:08:44.6552 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-02-27 07:08:46.0593 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=***
2016-02-27 07:08:46.4101 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=***

The first one is understandable, a new log being created. The wake ups at 1:08, 4:08 and 7:08 look to be related to emby connect 'phoning home', every three hours.

 

I tried moving the logs off of the Synology and onto a USB using a symlink, but it still does it, I assume because it accesses the filesystem on the hard drives to receive the symlink

 

So is it possible to either:

 

1) allow us to change the logging path to a locally attached USB device (other packages, like SickRage, allow you to do this in the GUI) or

2) allow us to disable, or at least schedule, the connection 'ping' to emby connect

 

I understand the importance of emby connect, but for advanced users, would it be possible to disable it? I use a VPN with port forwarding on all my devices, so don't really have a need for it.

 

Thanks for listening.

Edited February 27, 2016 by richie83

[Luke 36997]

Actually I don't think that's the cause. The timers that we are using do not cause wake-ups and they do not prevent sleep. The assessment in the first post is actually the right answer, i think.

[richie83 5]

I'm just going by what I see in the log. My NAS sleeps, but every three hours it wakes up, the log coincides with the exact same times that the Synology /var/messages logs the disks spinning up.

 

I've got realtime folder monitoring switched off, if that makes any difference.

 

From my experience, anything being written to a log file on the Synology (and QNAP, IIRC) gets written to the array, as the filesystem (DSM in the Synology) is distributed across the whole array. The issues I've had in the past have all usually boiled down to some sort of data being written by the package. As mentioned in my post, SickRage had the exact same problem until the logs were shifted onto a USB drive, which (at least in the Synology) doesn't cause the RAID array to spin up.

 

Unfortunately the file system on the synology is pretty dumb IMO, in other systems (such as Freenas, NAS4Free and Unraid) you have the system files on a disk/USB, hence any changes to logs etc get written to that one disk without disturbing the RAID array (ie. Freenas runs completely off a USB drive). There is no option for that, which means it's nice to have a bit more granular control over where the logs are kept.

[mph55 1]

I think this problem is resolved with either an updated server or kodi sync plugin.  I installed server 3.0.5871.0 and the 1.0.5904.13042  kodi sync queue plugin last night and forgot to stop the emby process on the NAS.  This morning the NAS was asleep with emby running so I'm assuming something in the update fixed this.  

[Luke 36997]

Well done.

[solabc16 379]

For anybody picking up this thread, please refer to https://emby.media/community/index.php?/topic/39319-synology-nas-ds415-does-not-hibernate-after-installing-emby-server/?p=403693

 

- James