curro88 0 Posted October 12, 2018 Posted October 12, 2018 Hi there! I've been using Emby since a few years without any problems on my DS213, but in the last weeks, I noticed that Emby stops running every day and I have to restart it manually from Package Center. With the last update it seems to be working correctly again, but it doesn't solve the "Check for plugin updates failed" which gives me the next message: The operation has timed out. at Emby.Server.Implementations.HttpClientManager.HttpClientManager+d__18.MoveNext () [0x006b6] in <8252e50122f84f82af882c36d707f6ce>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in :0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in :0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in :0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in :0 at Emby.Server.Implementations.HttpClientManager.HttpClientManager+d__15.MoveNext () [0x001f4] in <8252e50122f84f82af882c36d707f6ce>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in :0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in :0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in :0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in :0 at Emby.Server.Implementations.Updates.InstallationManager+d__48.MoveNext () [0x000c0] in <8252e50122f84f82af882c36d707f6ce>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in :0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in :0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in :0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in :0 at Emby.Server.Implementations.Updates.InstallationManager+d__57.MoveNext () [0x000a5] in <8252e50122f84f82af882c36d707f6ce>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in :0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in :0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in :0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in :0 at Emby.Server.Implementations.ScheduledTasks.PluginUpdateTask+d__7.MoveNext () [0x000a1] in <8252e50122f84f82af882c36d707f6ce>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in :0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in :0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in :0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in :0 at Emby.Server.Implementations.ScheduledTasks.ScheduledTaskWorker+d__68.MoveNext () [0x00156] in <8252e50122f84f82af882c36d707f6ce>:0 I've also noticed that when I add a new show to my library, it doesn't add all the metadata, just the title but not the episodes info and that before all this problems, I never had on my library .NFO files with the metadata and now I saw them in some folders. Anyone can help me? Thanks in advance and great day to all, curro88
solabc16 379 Posted October 12, 2018 Posted October 12, 2018 Hello @@curro88 Thanks for getting in touch, have you installed the 3.5.3.0-7 update? Best - James
curro88 0 Posted October 12, 2018 Author Posted October 12, 2018 Hi James, Synology's Package Center says that I have v3.5.3.0-7 installed but Emby Dashboard says v3.5.3.0 Thanks for answering, curro88
Luke 40079 Posted October 12, 2018 Posted October 12, 2018 Hi there, can you please attach the complete emby server log? Thanks.
solabc16 379 Posted October 12, 2018 Posted October 12, 2018 Hello @@curro88 That's fine, you're up to date then - so this must be something else; we can look more when you've posted the logs. The '-7' means it's revision 7 of the Synology Package for release 3.5.3.0. Best - James
curro88 0 Posted October 13, 2018 Author Posted October 13, 2018 Hi there, can you please attach the complete emby server log? Thanks. Hi Luke, Thanks in advance for the help. Here you have the last log from the server. Thanks again, curro88 embyserver-63674985600.txt
solabc16 379 Posted October 13, 2018 Posted October 13, 2018 Hello @@curro88 This appears to be an Internet connectivity issue, if possible can you run the diagnostic and send logs utilities:- https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Run-Diagnostics https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs Best - James
Darkjeje 11 Posted October 14, 2018 Posted October 14, 2018 Hello James, I have also the "Check for plugin updates failed" so you can find my log below sendlogs_DiskstationJR_synology_evansport_214play_20181014T142129UTC.tgz Have a nice day !
curro88 0 Posted October 15, 2018 Author Posted October 15, 2018 Hello @@curro88 This appears to be an Internet connectivity issue, if possible can you run the diagnostic and send logs utilities:- https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Run-Diagnostics https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs Best - James Hello James, I've done already the diagnostics and here they are the logs: sendlogs_DS213_synology_88f6282_213_20181015T071832UTC.tgz Thanks again, curro88
solabc16 379 Posted October 17, 2018 Posted October 17, 2018 Hello @@Darkjeje Do you have a working IPv6 network in your environment? I see this message reported frequently in the logs, coupled with attempts to use IPv6. 2018-10-14 16:20:06.640 Debug NetworkManager: NetworkAvailabilityChanged 2018-10-14 16:20:56.084 Debug NetworkManager: NetworkAvailabilityChanged 2018-10-14 16:21:10.103 Debug NetworkManager: NetworkAvailabilityChanged Best - James
Darkjeje 11 Posted October 18, 2018 Posted October 18, 2018 Hello @@Darkjeje Do you have a working IPv6 network in your environment? I see this message reported frequently in the logs, coupled with attempts to use IPv6. 2018-10-14 16:20:06.640 Debug NetworkManager: NetworkAvailabilityChanged 2018-10-14 16:20:56.084 Debug NetworkManager: NetworkAvailabilityChanged 2018-10-14 16:21:10.103 Debug NetworkManager: NetworkAvailabilityChanged Best - James Yes I have IPv6 in my network. It is a problem for Emby ?
solabc16 379 Posted October 26, 2018 Posted October 26, 2018 Hello @@Darkjeje There is an update now available for your platform (3.5.3.0-16), please let us know how you get on. Best - James
solabc16 379 Posted October 26, 2018 Posted October 26, 2018 Hello @@curro88 How are you getting on? I did take a look at the logs and for the most part they look 'normal'. The DS213 is limited in terms of CPU and memory and it's halting due to resource limits. I notice a lot of DLNA requests, so if you're not using DLNA it would be worth switching this off in the Emby Server's configuration. If you've added more DLNA capable devices to your network, this would have increased the workload on your system. Best - James
Darkjeje 11 Posted October 27, 2018 Posted October 27, 2018 Hello @@Darkjeje There is an update now available for your platform (3.5.3.0-16), please let us know how you get on. Best - James Install OK, and no problem for this moment ! To help you, my log was sending : sendlogs_DiskstationJR_synology_evansport_214play_20181027T143919UTC.tgz Thank you James !
solabc16 379 Posted October 27, 2018 Posted October 27, 2018 Thanks for the update and the logs @@Darkjeje, appreciated. Everythingn looks good and is running as expected. Let us know how you get on, once you've had a few days using it. Best - James
curro88 0 Posted January 15, 2019 Author Posted January 15, 2019 Hello @@curro88 How are you getting on? I did take a look at the logs and for the most part they look 'normal'. The DS213 is limited in terms of CPU and memory and it's halting due to resource limits. I notice a lot of DLNA requests, so if you're not using DLNA it would be worth switching this off in the Emby Server's configuration. If you've added more DLNA capable devices to your network, this would have increased the workload on your system. Best - James Hi @@solabc16! I'm so sorry for the delay answering here but I was working a lot and I forget this thread After disabling the IPv6 in my network as you suggested to @@Darkjeje! everything started to working fine so thanks! Regards, curro88
solabc16 379 Posted January 15, 2019 Posted January 15, 2019 Hello @@curro88 No worries, thanks for the update - appreciated. Best - James
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