Jump to content

HDD Hibernation every hour wake up connect.emby.media


marcoxyz123

Recommended Posts

marcoxyz123

HI All

 

There is still an issue with the HDD hibernation. 

 

The advice from this topic is not working in emby 3.2.30.0.

2017-09-11 00:55:55.761 Info HttpServer: HTTP Response 200 to 192.168.86.100. Time: 2ms. http://192.168.86.200:8096/emby/Emby.Kodi.SyncQueue/GetServerDateTime?format=json 
2017-09-11 01:26:24.433 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 01:26:24.707 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 01:27:12.570 Info HttpServer: HTTP GET http://192.168.86.200:8096/emby/Users/25a44c7a6a9546adac08708a0ab758c1/Items/b9d3e9ce1db24b7514846fb4551fed24?format=json. UserAgent: 
2017-09-11 01:27:12.581 Info HttpServer: HTTP Response 200 to 192.168.86.100. Time: 11ms. http://192.168.86.200:8096/emby/Users/25a44c7a6a9546adac08708a0ab758c1/Items/b9d3e9ce1db24b7514846fb4551fed24?format=json 
2017-09-11 02:08:15.682 Error HttpServer: Error in SharpWebSocket: An exception has occurred while receiving a message.. Exception.Message: The header part of a frame cannot be read from the data source.
2017-09-11 02:26:24.449 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 02:26:24.711 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 03:26:24.430 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 03:26:24.690 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 04:26:24.428 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 04:26:24.696 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 05:26:24.433 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 05:26:24.703 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 05:26:28.416 Info HttpClient: HttpClientManager POST: https://mb3admin.com/admin/service/registration/validate
2017-09-11 06:26:24.434 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 06:26:24.696 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 07:26:24.418 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 07:26:24.679 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 08:26:24.422 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 08:26:24.700 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 09:26:24.462 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=b3884cd56706d82ab6c83dbaaf08c30b
2017-09-11 09:26:24.748 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=b3884cd56706d82ab6c83dbaaf08c30b

And this wakes up the NAS every hour. What other or what is the new way to prevent the logging or to disable emby connect at all.

 

Best regards,

 

Marco Berger

Link to comment
Share on other sites

  • 2 weeks later...
Amargedon

I can confirm the log entries are gone with the latest version (3.2.32). Thanks!

 

One sidenote; I tried to add the log lines to the NLog as described in an earlier topic (linked in the startpost), but that didn't work.

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...