trmentry 0 Posted January 17, 2019 Share Posted January 17, 2019 So I'm running Emby on a Synology 918+. Upgraded to 4.0.0.2. Found that the scan media library task was nevering seeming to finish. Got to 88.9% and sat there for around 24 hours. Restarted Emby... still didn't seem to help. Found this thread. https://emby.media/community/index.php?/topic/68050-longer-library-scans-than-normal-on-upgrade-to-v4/ about turning off the extract chapter images during scan. So i went to each library and un-ticked the box. restarted emby... and it's scanning again. but now seems stuck at 88.5%. I've not touched it and just letting it do it's thing... but this seems a bit odd to me. It seems that it's timing out to or having issues with Open Movie DB. Or Open Movie DB is just crushed with all the updated Emby's hitting it. Remoted in from work and pulled this from the embyserver.txt log file. hoth = synology. 172.31.100.10 = Windows VM I remote into. 2019-01-17 05:03:39.592 Info App: [LinuxMount] Checking we can attempt to mount [/volume1/Media/MOVIES_HD/MOVIE/MOVIE.m2ts], Extension = [.m2ts], Operating System = [Linux], Executables Available = [True]. 2019-01-17 05:03:39.592 Debug MediaEncoder: Ffprobe -i file:"/volume1/Media/MOVIES_HD/MOVIE/MOVIE.m2ts" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data 2019-01-17 05:03:39.592 Info MediaEncoder: ProcessRun 'ffprobe' Execute: /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -i file:"/volume1/Media/MOVIES_HD/MOVIE/MOVIE.m2ts" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data 2019-01-17 05:03:39.599 Info MediaEncoder: ProcessRun 'ffprobe' Started. 2019-01-17 05:03:39.779 Info MediaEncoder: ProcessRun 'ffprobe' Process exited with code 0 2019-01-17 05:03:39.813 Info HttpClient: HttpClientManager GET: https://private.omdbapi.com?apikey=fe53f97e&i=tt0083943&plot=short&tomatoes=true&r=json 2019-01-17 05:03:43.772 Info HttpServer: HTTP GET http://hoth:8096/web/strings/en-US.json?v=1547726623238. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:43.774 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 2ms. http://hoth:8096/web/strings/en-US.json?v=1547726623238 2019-01-17 05:03:43.778 Info HttpServer: HTTP GET http://hoth:8096/web/bower_components/emby-webcomponents/strings/en-US.json?v=1547726623238. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:43.779 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 2ms. http://hoth:8096/web/bower_components/emby-webcomponents/strings/en-US.json?v=1547726623238 2019-01-17 05:03:44.668 Info HttpServer: HTTP GET http://hoth:8096/emby/system/info/public. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:44.670 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 1ms. http://hoth:8096/emby/system/info/public 2019-01-17 05:03:44.696 Info HttpServer: HTTP GET http://hoth:8096/emby/System/Info. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:44.700 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 4ms. http://hoth:8096/emby/System/Info 2019-01-17 05:03:44.725 Info HttpServer: WS http://hoth:8096/embywebsocket?api_key=d9bf7d9c08874a429640a2d60378c612&deviceId=TW96aWxsYS81LjAgKFdpbmRvd3MgTlQgMTAuMDsgV2luNjQ7IHg2NCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzY4LjAuMzQ0MC4xMDYgU2FmYXJpLzUzNy4zNnwxNTM2MTc3Njk0NzI5. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:44.731 Info HttpServer: HTTP GET http://hoth:8096/emby/DisplayPreferences/usersettings?userId=f8063fbe6d8943ef8abb164e35547938&client=emby. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:44.734 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 2ms. http://hoth:8096/emby/DisplayPreferences/usersettings?userId=f8063fbe6d8943ef8abb164e35547938&client=emby 2019-01-17 05:03:44.754 Info HttpServer: HTTP GET http://hoth:8096/emby/Users/f8063fbe6d8943ef8abb164e35547938. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:44.756 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 2ms. http://hoth:8096/emby/Users/f8063fbe6d8943ef8abb164e35547938 2019-01-17 05:03:44.825 Info HttpServer: HTTP GET http://hoth:8096/emby/Users/f8063fbe6d8943ef8abb164e35547938. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:44.828 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 2ms. http://hoth:8096/emby/Users/f8063fbe6d8943ef8abb164e35547938 2019-01-17 05:03:44.883 Info HttpServer: HTTP POST http://hoth:8096/emby/Sessions/Capabilities/Full. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:44.889 Info HttpServer: HTTP Response 204 to 172.31.100.10. Time: 6ms. http://hoth:8096/emby/Sessions/Capabilities/Full 2019-01-17 05:03:45.162 Info HttpServer: HTTP GET http://hoth:8096/emby/Sessions?ActiveWithinSeconds=960. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:45.164 Info HttpServer: HTTP GET http://hoth:8096/emby/ScheduledTasks. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:45.165 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 3ms. http://hoth:8096/emby/Sessions?ActiveWithinSeconds=960 2019-01-17 05:03:45.167 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 3ms. http://hoth:8096/emby/ScheduledTasks 2019-01-17 05:03:45.177 Info HttpServer: HTTP GET http://hoth:8096/emby/System/Info. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:45.179 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 2ms. http://hoth:8096/emby/System/Info 2019-01-17 05:03:45.184 Info HttpServer: HTTP GET http://hoth:8096/emby/News/Product?StartIndex=0&Limit=4. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:45.188 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 4ms. http://hoth:8096/emby/News/Product?StartIndex=0&Limit=4 2019-01-17 05:03:45.191 Info HttpServer: HTTP GET http://hoth:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2019-01-16T12%3A03%3A44.658Z&hasUserId=true. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:45.198 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 8ms. http://hoth:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2019-01-16T12%3A03%3A44.658Z&hasUserId=true 2019-01-17 05:03:45.199 Info HttpServer: HTTP GET http://hoth:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-01-10T12%3A03%3A44.664Z&hasUserId=false. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:45.205 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 7ms. http://hoth:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-01-10T12%3A03%3A44.664Z&hasUserId=false 2019-01-17 05:03:45.208 Info HttpServer: HTTP GET http://hoth:8096/emby/LiveTv/Recordings?UserId=f8063fbe6d8943ef8abb164e35547938&IsInProgress=true&Fields=CanDelete%2CPrimaryImageAspectRatio&EnableTotalRecordCount=false&EnableImageTypes=Primary%2CThumb%2CBackdrop. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:45.210 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 2ms. http://hoth:8096/emby/LiveTv/Recordings?UserId=f8063fbe6d8943ef8abb164e35547938&IsInProgress=true&Fields=CanDelete%2CPrimaryImageAspectRatio&EnableTotalRecordCount=false&EnableImageTypes=Primary%2CThumb%2CBackdrop 2019-01-17 05:03:45.217 Info HttpServer: HTTP GET http://hoth:8096/emby/web/configurationpages?pageType=PluginConfiguration&EnableInMainMenu=true. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:45.218 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 1ms. http://hoth:8096/emby/web/configurationpages?pageType=PluginConfiguration&EnableInMainMenu=true 2019-01-17 05:03:45.227 Info HttpServer: HTTP GET http://hoth:8096/web/css/images/supporter/supporterbadge.png. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:45.228 Info HttpServer: HTTP Response 304 to 172.31.100.10. Time: 1ms. http://hoth:8096/web/css/images/supporter/supporterbadge.png 2019-01-17 05:03:45.446 Info HttpServer: HTTP GET http://hoth:8096/web/css/images/logoblack.png. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:45.447 Info HttpServer: HTTP Response 304 to 172.31.100.10. Time: 1ms. http://hoth:8096/web/css/images/logoblack.png 2019-01-17 05:03:45.525 Info HttpServer: HTTP GET http://hoth:8096/web/bower_components/emby-webcomponents/themes/light/theme.json?v=4.0.0.2&r=0. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:45.526 Info HttpServer: HTTP Response 304 to 172.31.100.10. Time: 1ms. http://hoth:8096/web/bower_components/emby-webcomponents/themes/light/theme.json?v=4.0.0.2&r=0 2019-01-17 05:03:50.734 Info HttpServer: HTTP GET http://hoth:8096/emby/System/Endpoint. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:50.736 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 2ms. http://hoth:8096/emby/System/Endpoint 2019-01-17 05:03:51.556 Info HttpServer: HTTP GET http://hoth:8096/emby/Users/f8063fbe6d8943ef8abb164e35547938. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:51.558 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 2ms. http://hoth:8096/emby/Users/f8063fbe6d8943ef8abb164e35547938 2019-01-17 05:03:51.640 Info HttpServer: HTTP GET http://hoth:8096/emby/System/Logs. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:51.647 Info HttpServer: HTTP GET http://hoth:8096/emby/System/Configuration. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 2019-01-17 05:03:51.680 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 40ms. http://hoth:8096/emby/System/Logs 2019-01-17 05:03:51.716 Info HttpServer: HTTP Response 200 to 172.31.100.10. Time: 68ms. http://hoth:8096/emby/System/Configuration 2019-01-17 05:03:59.814 Error HttpClient: Error Timeout getting response from *** Error Report *** Version: 4.0.0.2 Command line: /var/packages/EmbyServer/target/server/EmbyServer.exe -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -ffdetect /var/packages/EmbyServer/target/ffmpeg/bin/ffdetect -restartexitcode 121 Operating system: Unix 4.4.59.0 64-Bit OS: True 64-Bit Process: True User Interactive: False Mono: 5.14.0.177 (tarball Sun Nov 4 20:48:29 UTC 2018) Processor count: 4 Program data path: /var/packages/EmbyServer/target/var Application directory: /volume1/@appstore/EmbyServer/releases/4.0.0.2 System.Net.WebException: System.Net.WebException: The operation has timed out. at System.Net.HttpWebRequest+<RunWithTimeoutWorker>d__244`1[T].MoveNext () [0x000c5] in <2e58ecde50444b6baf2e884bbf90860c>:0 --- End of stack trace from previous location where exception was thrown --- at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00020] in <2e58ecde50444b6baf2e884bbf90860c>:0 at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <eb1cd6c456494990813d92477245f615>:0 Source: System TargetSite: System.Net.WebResponse EndGetResponse(System.IAsyncResult) at System.Net.HttpWebRequest+<RunWithTimeoutWorker>d__244`1[T].MoveNext () [0x000c5] in <2e58ecde50444b6baf2e884bbf90860c>:0 --- End of stack trace from previous location where exception was thrown --- at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00020] in <2e58ecde50444b6baf2e884bbf90860c>:0 at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <eb1cd6c456494990813d92477245f615>:0 2019-01-17 05:03:59.817 Error App: Error in The Open Movie Database *** Error Report *** Version: 4.0.0.2 Command line: /var/packages/EmbyServer/target/server/EmbyServer.exe -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -ffdetect /var/packages/EmbyServer/target/ffmpeg/bin/ffdetect -restartexitcode 121 Operating system: Unix 4.4.59.0 64-Bit OS: True 64-Bit Process: True User Interactive: False Mono: 5.14.0.177 (tarball Sun Nov 4 20:48:29 UTC 2018) Processor count: 4 Program data path: /var/packages/EmbyServer/target/var Application directory: /volume1/@appstore/EmbyServer/releases/4.0.0.2 MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: The operation has timed out. ---> System.Net.WebException: The operation has timed out. at System.Net.HttpWebRequest+<RunWithTimeoutWorker>d__244`1[T].MoveNext () [0x000c5] in <2e58ecde50444b6baf2e884bbf90860c>:0 --- End of stack trace from previous location where exception was thrown --- at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00020] in <2e58ecde50444b6baf2e884bbf90860c>:0 at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <eb1cd6c456494990813d92477245f615>:0 --- End of inner exception stack trace --- at Emby.Server.Implementations.HttpClientManager.HttpClientManager+<SendAsyncInternal>d__18.MoveNext () [0x00693] in <914c1b9e831748ffb264e56b3c5776c3>:0 --- End of stack trace from previous location where exception was thrown --- at Emby.Server.Implementations.HttpClientManager.HttpClientManager+<SendAsync>d__15.MoveNext () [0x0009e] in <914c1b9e831748ffb264e56b3c5776c3>:0 --- End of stack trace from previous location where exception was thrown --- at OMDb.Common.OmdbProvider+<EnsureItemInfo>d__13.MoveNext () [0x0014b] in <5a392efcd368460688f8f8509972b906>:0 --- End of stack trace from previous location where exception was thrown --- at OMDb.Common.OmdbProvider+<GetRootObject>d__9.MoveNext () [0x0007e] in <5a392efcd368460688f8f8509972b906>:0 --- End of stack trace from previous location where exception was thrown --- at OMDb.Common.OmdbProvider+<Fetch>d__7`1[T].MoveNext () [0x000a7] in <5a392efcd368460688f8f8509972b906>:0 --- End of stack trace from previous location where exception was thrown --- at OMDb.Common.OmdbItemProvider+<GetMovieResult>d__20`1[T].MoveNext () [0x001a2] in <5a392efcd368460688f8f8509972b906>:0 --- End of stack trace from previous location where exception was thrown --- at MediaBrowser.Providers.Manager.MetadataService`2+<ExecuteRemoteProviders>d__38[TItemType,TIdType].MoveNext () [0x00138] in <22b2d762b5084d8ebcd403852abbfb22>:0 Source: mscorlib TargetSite: Void Throw() at Emby.Server.Implementations.HttpClientManager.HttpClientManager+<SendAsyncInternal>d__18.MoveNext () [0x00693] in <914c1b9e831748ffb264e56b3c5776c3>:0 --- End of stack trace from previous location where exception was thrown --- at Emby.Server.Implementations.HttpClientManager.HttpClientManager+<SendAsync>d__15.MoveNext () [0x0009e] in <914c1b9e831748ffb264e56b3c5776c3>:0 --- End of stack trace from previous location where exception was thrown --- at OMDb.Common.OmdbProvider+<EnsureItemInfo>d__13.MoveNext () [0x0014b] in <5a392efcd368460688f8f8509972b906>:0 --- End of stack trace from previous location where exception was thrown --- at OMDb.Common.OmdbProvider+<GetRootObject>d__9.MoveNext () [0x0007e] in <5a392efcd368460688f8f8509972b906>:0 --- End of stack trace from previous location where exception was thrown --- at OMDb.Common.OmdbProvider+<Fetch>d__7`1[T].MoveNext () [0x000a7] in <5a392efcd368460688f8f8509972b906>:0 --- End of stack trace from previous location where exception was thrown --- at OMDb.Common.OmdbItemProvider+<GetMovieResult>d__20`1[T].MoveNext () [0x001a2] in <5a392efcd368460688f8f8509972b906>:0 --- End of stack trace from previous location where exception was thrown --- at MediaBrowser.Providers.Manager.MetadataService`2+<ExecuteRemoteProviders>d__38[TItemType,TIdType].MoveNext () [0x00138] in <22b2d762b5084d8ebcd403852abbfb22>:0 InnerException: System.Net.WebException: The operation has timed out. Source: System TargetSite: System.Net.WebResponse EndGetResponse(System.IAsyncResult) at System.Net.HttpWebRequest+<RunWithTimeoutWorker>d__244`1[T].MoveNext () [0x000c5] in <2e58ecde50444b6baf2e884bbf90860c>:0 --- End of stack trace from previous location where exception was thrown --- at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00020] in <2e58ecde50444b6baf2e884bbf90860c>:0 at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <eb1cd6c456494990813d92477245f615>:0 Link to comment Share on other sites More sharing options...
trmentry 0 Posted January 17, 2019 Author Share Posted January 17, 2019 Forgot to ask... should I just try and disable Open Movie DB for now? Or just wait this out if it is just getting crushed from all the requests? Link to comment Share on other sites More sharing options...
Luke 37065 Posted January 17, 2019 Share Posted January 17, 2019 Hi, the scan is not stuck but just taking a bit of time. I would just allow it to finish and then scans after that will be faster. And yes, disabling features will also make it scan faster. Link to comment Share on other sites More sharing options...
trmentry 0 Posted January 18, 2019 Author Share Posted January 18, 2019 So this is still running... watching it... it will get to around 95%... then it will magically drop back to 87%.... and repeat. It seems to be doing the same things over and over and over again. Here is a snip from the embyserver.txt log file showing the same movie touched 3 times today. Something doesn't seem quite right... but not sure if I should let it keep going or not. It's been running over 24 hours now. 2019-01-18 03:19:19.822 Info App: [LinuxMount] Checking we can attempt to mount [/volume1/Media/MOVIES_HD/MOVIE/Movie.mkv], Extension = [.mkv], Operating System = [Linux], Executables Available = [True]. 2019-01-18 03:19:19.822 Debug MediaEncoder: Ffprobe -i file:"/volume1/Media/MOVIES_HD/MOVIE/Movie.mkv" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data 2019-01-18 03:19:19.822 Info MediaEncoder: ProcessRun 'ffprobe' Execute: /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -i file:"/volume1/Media/MOVIES_HD/MOVIE/Movie.mkv" -threads 0 -v info - 2019-01-18 08:32:40.526 Info App: [LinuxMount] Checking we can attempt to mount [/volume1/Media/MOVIES_HD/MOVIE/Movie.mkv], Extension = [.mkv], Operating System = [Linux], Executables Available = [True]. 2019-01-18 08:32:40.526 Debug MediaEncoder: Ffprobe -i file:"/volume1/Media/MOVIES_HD/MOVIE/Movie.mkv" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data 2019-01-18 08:32:40.526 Info MediaEncoder: ProcessRun 'ffprobe' Execute: /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -i file:"/volume1/Media/MOVIES_HD/MOVIE/Movie.mkv" -threads 0 -v info - 2019-01-18 13:47:46.587 Info App: [LinuxMount] Checking we can attempt to mount [/volume1/Media/MOVIES_HD/MOVIE/Movie.mkv], Extension = [.mkv], Operating System = [Linux], Executables Available = [True]. 2019-01-18 13:47:46.587 Debug MediaEncoder: Ffprobe -i file:"/volume1/Media/MOVIES_HD/MOVIE/Movie.mkv" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data 2019-01-18 13:47:46.587 Info MediaEncoder: ProcessRun 'ffprobe' Execute: /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -i file:"/volume1/Media/MOVIES_HD/MOVIE/Movie.mkv" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data Link to comment Share on other sites More sharing options...
Luke 37065 Posted January 18, 2019 Share Posted January 18, 2019 Hi there, please attach the complete emby server log. thanks. Link to comment Share on other sites More sharing options...
trmentry 0 Posted January 19, 2019 Author Share Posted January 19, 2019 (edited) The file is just under 30m. Gzip'ed it and attached. There seems to be files from log rotations. I didn't include them. Edit: forgot the attachment... now with more attachments -rw-r--r-- 1 embysvr users 35075434 Jan 15 23:59 embyserver-63683193600.txt -rw-r--r-- 1 embysvr users 9097544 Jan 16 07:09 embyserver-63683219429.txt -rw-r--r-- 1 embysvr users 12612161 Jan 16 11:56 embyserver-63683236579.txt -rw-r--r-- 1 embysvr users 25755133 Jan 17 00:00 embyserver-63683280000.txt -rw-r--r-- 1 embysvr users 6354844 Jan 17 03:59 embyserver-63683294396.txt -rw-r--r-- 1 embysvr users 32422844 Jan 18 00:00 embyserver-63683366400.txt -rw-r--r-- 1 embysvr users 29651525 Jan 18 17:29 embyserver.txt embyserver.txt.gz Edited January 19, 2019 by trmentry Link to comment Share on other sites More sharing options...
Luke 37065 Posted January 19, 2019 Share Posted January 19, 2019 Well the scan in this log took quite a long time, 5 hours, but it did eventually finish. There's a lot of outgoing http request failures so that is probably contributing to it. Do you have anything in your setup blocking access to the internet? Link to comment Share on other sites More sharing options...
trmentry 0 Posted January 19, 2019 Author Share Posted January 19, 2019 Well the scan in this log took quite a long time, 5 hours, but it did eventually finish. There's a lot of outgoing http request failures so that is probably contributing to it. Do you have anything in your setup blocking access to the internet? Nope... the Synology has access to the internet. It backs up parts of /homes to Backblaze each night.... hasn't been having any issues. So is the unit going to take 5 hours to complete each time? I have it set to scan every 15 or 20 min in task setup. I went to bed and it was scanning and was at 88.4%. Currently it's at 89.6%... so guessing it completed... and then started over as the next time for the task came into play. Link to comment Share on other sites More sharing options...
Luke 37065 Posted January 19, 2019 Share Posted January 19, 2019 No that's not normal. I think we need to get to the bottom of why it can't access the internet @@solabc16 Link to comment Share on other sites More sharing options...
solabc16 379 Posted January 19, 2019 Share Posted January 19, 2019 Hello @@trmentry As a quick test, if you're not actively using IPv6 on you Synology system, can you disabled it on the interface your using to connect to the Internet. DSM -> Control Panel -> Network -> Network Interface -> <your connection> -> IPv6 -> IPv6 setup -> Off Let me know how you get on... Best - James Link to comment Share on other sites More sharing options...
trmentry 0 Posted January 20, 2019 Author Share Posted January 20, 2019 (edited) Hello @@trmentry As a quick test, if you're not actively using IPv6 on you Synology system, can you disabled it on the interface your using to connect to the Internet. DSM -> Control Panel -> Network -> Network Interface -> <your connection> -> IPv6 -> IPv6 setup -> Off Let me know how you get on... Best - James @solabc16 Completed. Thanks trmentry@hoth:~$ ifconfig bond0 Link encap:Ethernet HWaddr 00:11:32:82:73:B5 inet addr:172.31.100.7 Bcast:172.31.100.255 Mask:255.255.255.0 UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:253734059 errors:0 dropped:0 overruns:0 frame:0 TX packets:415497007 errors:0 dropped:6 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:239280475892 (222.8 GiB) TX bytes:590968426783 (550.3 GiB) eth0 Link encap:Ethernet HWaddr 00:11:32:82:73:B5 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:179769962 errors:0 dropped:0 overruns:0 frame:0 TX packets:384837427 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:195662554597 (182.2 GiB) TX bytes:560741057770 (522.2 GiB) eth1 Link encap:Ethernet HWaddr 00:11:32:82:73:B5 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:73964097 errors:0 dropped:0 overruns:0 frame:0 TX packets:30659580 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:43617921295 (40.6 GiB) TX bytes:30227369013 (28.1 GiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:9359269 errors:0 dropped:0 overruns:0 frame:0 TX packets:9359269 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:2378134025 (2.2 GiB) TX bytes:2378134025 (2.2 GiB) trmentry@hoth:~$ Edited January 20, 2019 by trmentry Link to comment Share on other sites More sharing options...
trmentry 0 Posted January 20, 2019 Author Share Posted January 20, 2019 Sorry.... for got to attach a new Emby log. I happened to catch it finish and immediately start back up... it's back to 88%... embyserver.txt.gz Link to comment Share on other sites More sharing options...
trmentry 0 Posted January 20, 2019 Author Share Posted January 20, 2019 i think disabling v6 did the trick. it's stopped scanning and is idle now. attached is the log again.. .this time after it stopped and finished. is this a known issue with v6? i do use v6... but not really from the Synology so not a big deal disabled there. embyserver.txt.gz Link to comment Share on other sites More sharing options...
kc6108 1 Posted January 20, 2019 Share Posted January 20, 2019 (edited) My scans never seem to finish either. I will disable IPv6 and report back. Also, the DLNA icon disappeared after the latest update (from 4.0.0.2 to 4.0.0.2-2). When using Synology Media Server (DLNA) to my Oppo BDP-93. Lastly, I have 544 movies, but the Latest list inside Movies keeps loading and loading and loading my movies. My Oppo loads 60 at a time and the list of movies grew past 10k after 5 minutes or so. The seem to load in a loop... the list always contains movies that really are in my library... just dupes Synology DS1812+ Edited January 20, 2019 by kc6108 Link to comment Share on other sites More sharing options...
solabc16 379 Posted January 20, 2019 Share Posted January 20, 2019 Hello @@trmentry is this a known issue with v6? i do use v6... but not really from the Synology so not a big deal disabled there. Glad to hear that's got you moving in the right direction again. Is your ISP providing you with an IPv6 service, or are you just using it on your internal network? We have seen this happen when DNS resolution returns an IPv6 address, but end-to-end IPv6 connectivity isn't available. Best - James Link to comment Share on other sites More sharing options...
solabc16 379 Posted January 20, 2019 Share Posted January 20, 2019 Hello @@kc6108 Also, the DLNA icon disappeared after the latest update (from 4.0.0.2 to 4.0.0.2-2). When using Synology Media Server (DLNA) to my Oppo BDP-93. Can you clarify what you mean here a little further? The 4.0.0.2-2 is a platform update available on the beta channel for Emby Server. Lastly, I have 544 movies, but the Latest list inside Movies keeps loading and loading and loading my movies. My Oppo loads 60 at a time and the list of movies grew past 10k after 5 minutes or so. The seem to load in a loop... the list always contains movies that really are in my library... just dupes Has the initial full library scan completed successfully since upgrading to 4.0? Have you also checked the dashboard to make sure all plugins are up to date? Best - James Link to comment Share on other sites More sharing options...
trmentry 0 Posted January 20, 2019 Author Share Posted January 20, 2019 Hello @@trmentry Glad to hear that's got you moving in the right direction again. Is your ISP providing you with an IPv6 service, or are you just using it on your internal network? We have seen this happen when DNS resolution returns an IPv6 address, but end-to-end IPv6 connectivity isn't available. Best - James My cable provider has native v6. I use DHCPv6-PD to get a /64 from them that is for my lan. My router (Synology RT2600AC) then will issue out IPs from the /64 to the lan devices. I can get to v6 sites without issue. I'm using OpenDNS for name resolutions. I have 1 of their v4s configured and 1 of their v6s configured. Is there a v6 address you want me to try and test to from my lan? Link to comment Share on other sites More sharing options...
Luke 37065 Posted February 1, 2019 Share Posted February 1, 2019 Hi there, this is resolved for the next release. If you need immediate relief the fix is up on the beta channel. thanks ! Link to comment Share on other sites More sharing options...
trmentry 0 Posted February 1, 2019 Author Share Posted February 1, 2019 Hi there, this is resolved for the next release. If you need immediate relief the fix is up on the beta channel. thanks ! Thank you for the info. Link to comment Share on other sites More sharing options...
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