Jump to content

Synology keeps waking up


oxhey

Recommended Posts

So my Synology NAS is set to go into hibernation after 15 mins of inactivity.

 

It mostly does, however it keeps waking up.

 

The only packages on the NAS are Emby Server, Universal Search and File Station (which cant be disabled)

 

I have compared the times of it waking up in the Synology Log to the Emby log.

 

It appears as though the Emby app on my Samsung TV is causing this (even when its off!)

 

It also seems as though the NAS will wake up even if the TV is just on and not in the Emby app.

 

Example - I would be watching YouTube on the TV and then heard the faint rumble of HDD's starting up. 

 

See log below.

 

This log is from today, when I was at work and Emby wasn't being used.

2019-02-27 00:32:06.703 Info App: Udp message sent to 192.168.0.103:59259
2019-02-27 00:32:07.729 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/system/info/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 00:32:07.732 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 3ms. http://192.168.0.126:8096/emby/system/info/public
2019-02-27 00:32:07.767 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/users/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 00:32:07.771 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 4ms. http://192.168.0.126:8096/emby/users/public
2019-02-27 00:32:08.022 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/users/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 00:32:08.026 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 4ms. http://192.168.0.126:8096/emby/users/public
2019-02-27 02:34:40.848 Info App: Udp message sent to 192.168.0.103:41156
2019-02-27 02:34:41.875 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/system/info/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 02:34:41.878 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 3ms. http://192.168.0.126:8096/emby/system/info/public
2019-02-27 02:34:41.913 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/users/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 02:34:41.917 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 4ms. http://192.168.0.126:8096/emby/users/public
2019-02-27 02:34:42.170 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/users/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 02:34:42.174 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 4ms. http://192.168.0.126:8096/emby/users/public
2019-02-27 08:32:05.760 Info App: Udp message sent to 192.168.0.103:35545
2019-02-27 08:32:06.787 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/system/info/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 08:32:06.790 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 3ms. http://192.168.0.126:8096/emby/system/info/public
2019-02-27 08:32:06.827 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/users/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 08:32:06.831 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 4ms. http://192.168.0.126:8096/emby/users/public
2019-02-27 08:32:07.091 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/users/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 08:32:07.095 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 4ms. http://192.168.0.126:8096/emby/users/public
2019-02-27 09:03:48.793 Info App: Udp message sent to 192.168.0.103:32955
2019-02-27 09:03:49.820 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/system/info/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 09:03:49.823 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 3ms. http://192.168.0.126:8096/emby/system/info/public
2019-02-27 09:03:49.860 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/users/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 09:04:13.710 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 23850ms. http://192.168.0.126:8096/emby/users/public
2019-02-27 09:04:13.981 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/users/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 09:04:13.985 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 4ms. http://192.168.0.126:8096/emby/users/public
2019-02-27 11:05:47.611 Info App: Udp message sent to 192.168.0.103:50548
2019-02-27 11:05:48.636 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/system/info/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 11:05:48.639 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 3ms. http://192.168.0.126:8096/emby/system/info/public
2019-02-27 11:05:48.675 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/users/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 11:05:48.679 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 4ms. http://192.168.0.126:8096/emby/users/public
2019-02-27 11:05:48.944 Info HttpServer: HTTP GET http://192.168.0.126:8096/emby/users/public. UserAgent: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
2019-02-27 11:05:48.947 Info HttpServer: HTTP Response 200 to 192.168.0.103. Time: 4ms. http://192.168.0.126:8096/emby/users/public
Link to comment
Share on other sites

That is the community app for older Samsung devices.

 

I'm not really familiar with how it works, but yes those requests do appear to be coming from it.

Link to comment
Share on other sites

We'll see what @@SamES thinks but the app supports displaying content on the Samsung home screen. Periodically it will be called to refresh this and that might be what's happening.

Link to comment
Share on other sites

Possibly, it is a background service so it could be anytime. For example if we were a news app, you wouldn't want to turn on the TV and see yesterday's news.

Link to comment
Share on other sites

True...

 

If it is that, do you think it's possible to add a setting to enable/disable this?

 

On my TV there isn't any content displaying on the home screen for the emby app.

Edited by oxhey
Link to comment
Share on other sites

There shouldn't be any automatic refresh enabled in the app, so it unlikely to be the cause, but something is definitely occurring.  Can you you please confirm the app store version number and PM a full server log to me?  Thanks

Link to comment
Share on other sites

There shouldn't be any automatic refresh enabled in the app, so it unlikely to be the cause, but something is definitely occurring.  Can you you please confirm the app store version number and PM a full server log to me?  Thanks

 

PM'd

Link to comment
Share on other sites

SamES

I'm pretty sure now that these are responses to server discovery requests.

2019-02-28 22:45:31.634 Info App: Udp message sent to 192.168.0.103:58404
2019-03-01 00:22:29.071 Info App: Udp message sent to 192.168.0.103:37158
2019-03-01 02:24:52.115 Info App: Udp message sent to 192.168.0.103:49720
2019-03-01 09:09:00.062 Info App: Udp message sent to 192.168.0.103:45729
2019-03-01 11:11:02.809 Info App: Udp message sent to 192.168.0.103:54842

Is your TV connected via a wired or wireless network?

 

The Samsung TV will continue to perform background activities while it is in standby.  Is it possible that your network is disconnecting and reconnecting through the night (are there any logs on your router)?  This would probably cause the app to try and reconnect to the server which I expect trigger a 'server discovery' to ensure the server is still available.  That would explain these messages.

 

The only thing that puzzles me is that the server would need to be on for this to occur.  If it was asleep I'm pretty sure a wake on lan packet would be required to wake the server, otherwise these requests would be ignored.  I don't think wake on lan packets are sent automatically.  Are you sure the server is asleep through the night or are the drives just in a spun down state with the server still awake?

Link to comment
Share on other sites

I'm pretty sure now that these are responses to server discovery requests.

2019-02-28 22:45:31.634 Info App: Udp message sent to 192.168.0.103:58404
2019-03-01 00:22:29.071 Info App: Udp message sent to 192.168.0.103:37158
2019-03-01 02:24:52.115 Info App: Udp message sent to 192.168.0.103:49720
2019-03-01 09:09:00.062 Info App: Udp message sent to 192.168.0.103:45729
2019-03-01 11:11:02.809 Info App: Udp message sent to 192.168.0.103:54842

Is your TV connected via a wired or wireless network?

 

The Samsung TV will continue to perform background activities while it is in standby.  Is it possible that your network is disconnecting and reconnecting through the night (are there any logs on your router)?  This would probably cause the app to try and reconnect to the server which I expect trigger a 'server discovery' to ensure the server is still available.  That would explain these messages.

 

The only thing that puzzles me is that the server would need to be on for this to occur.  If it was asleep I'm pretty sure a wake on lan packet would be required to wake the server, otherwise these requests would be ignored.  I don't think wake on lan packets are sent automatically.  Are you sure the server is asleep through the night or are the drives just in a spun down state with the server still awake?

 

 

TV is connected via Wifi.

 

Router logs show Send ACK requests from the TV.

 

The NAS goes into Hibernation Mode after 15 mins of inactivity.

Link to comment
Share on other sites

SamES

TV is connected via Wifi.

 

Router logs show Send ACK requests from the TV.

 

The NAS goes into Hibernation Mode after 15 mins of inactivity.

 

 

Can you connect to a wired connection and see if the problem continues?

 

Is that HDD Hibernation or System Hibernation?  I suspect it might only be HDD Hibernation

 

Which model is your Synology NAS?

Link to comment
Share on other sites

Can you connect to a wired connection and see if the problem continues?

 

Is that HDD Hibernation or System Hibernation?  I suspect it might only be HDD Hibernation

 

Which model is your Synology NAS?

 

Ill have to get an ethernet cable, but I will try it.

 

it is HDD Hibernation

 

DS418play

Link to comment
Share on other sites

SamES

Thanks.  That makes sense that it is just HDD Hibernation, so the whole server is not hibernating, just the drives.

 

Let's see whether using a cable changes things.  For now I'm more interested in the log content as the drives will continue to stay wake for this test (while debug log is on).

Link to comment
Share on other sites

Okay so the ethernet cable will have to wait untill tomorrow.

 

Just to confirm, I should leave both debug options on in emby when I plug in the cable?

Link to comment
Share on other sites

Screenshot of my DLNA settings attached.

 

What am I disabling here?

 

 

post-382294-0-43660900-1552250370_thumb.png

Edited by oxhey
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...