ZoleeBB 0 Posted January 10, 2025 Posted January 10, 2025 Hi! I am using the program on a Synology DS420+ NAS. OS version: DSM 7.2.2-72806 Update 2 Emby version: 4.8.10.0-724081000 My issue is that the new media search task stops at 74% and halts after the set timeout. It reaches this point relatively quickly (around 20 minutes) but doesn't progress further for 6 hours. At this stage, the server either freezes or becomes unusably slow. What could be the cause of this? The server contains about 3TB of media content.
ZoleeBB 0 Posted January 10, 2025 Author Posted January 10, 2025 (edited) LOG: ... 2025-01-10 12:10:55.840 Info MediaProbeManager: ProcessRun 'ffprobe' Process exited with code 0 - Succeeded 2025-01-10 12:10:55.842 Info HttpClient: GET https://api4.thetvdb.com/v4/episodes/9662645/extended?meta=translations 2025-01-10 12:10:56.040 Info MediaProbeManager: ProcessRun 'ffprobe' Execute: /var/packages/EmbyServer/target/bin/ffprobe -i file:"/volume1/video/! SOROZATOK/NCIS/S20/NCIS.S20E01.WEBRip.x264.Hun.Eng-HHD.mkv" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data 2025-01-10 12:10:56.151 Info MediaProbeManager: ProcessRun 'ffprobe' Process exited with code 0 - Succeeded 2025-01-10 12:10:56.152 Info HttpClient: GET https://api4.thetvdb.com/v4/episodes/9229801/extended?meta=translations 2025-01-10 13:34:29.641 Info HttpClient: GET https://www.mb3admin.com/admin/service/EmbyPackages.json 2025-01-10 13:34:36.622 Info Server: http/1.1 Response 500 to host1. Time: 1713ms. GET http://192.168.2.3:8096/emby/ScheduledTasks/6330ee8fb4a957f33981f89aa78b030f?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=05794356-af37-48ee-ac4c-84aefca28dfd&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret1_x&X-Emby-Language=hu 2025-01-10 13:34:37.208 Info Server: http/1.1 Response 500 to host1. Time: 2303ms. GET http://192.168.2.3:8096/emby/Users/b4d044ed061b4c4cb9bb14e13d0ac61e?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=05794356-af37-48ee-ac4c-84aefca28dfd&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret1_x&X-Emby-Language=hu 2025-01-10 13:34:37.208 Info Server: http/1.1 Response 500 to host1. Time: 2303ms. GET http://192.168.2.3:8096/emby/ScheduledTasks?isHidden=false&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=05794356-af37-48ee-ac4c-84aefca28dfd&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret1_x&X-Emby-Language=hu 2025-01-10 13:34:37.228 Info Server: http/1.1 Response 500 to host1. Time: 2323ms. GET http://192.168.2.3:8096/emby/Users/b4d044ed061b4c4cb9bb14e13d0ac61e?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=05794356-af37-48ee-ac4c-84aefca28dfd&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret1_x&X-Emby-Language=hu 2025-01-10 13:34:37.251 Info Server: http/1.1 Response 500 to host1. Time: 2343ms. GET http://192.168.2.3:8096/emby/Users/b4d044ed061b4c4cb9bb14e13d0ac61e?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=05794356-af37-48ee-ac4c-84aefca28dfd&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret1_x&X-Emby-Language=hu 2025-01-10 13:36:21.664 Error HttpClient: Connection to https://www.mb3admin.com/admin/service/EmbyPackages.json timed out 2025-01-10 13:36:26.891 Error App: Error getting available plugin updates *** Error Report *** Version: 4.8.10.0 Command line: /volume1/@appstore/EmbyServer/system/EmbyServer.dll -programdata /var/packages/EmbyServer/var -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -nolocalportconfig -ignore_vaapi_enabled_flag -pidfile /var/packages/EmbyServer/var/EmbyServer.pid -defaultdirectory /volume1/Public -updatepackage emby-server-synology72_{version}_x86_64.spk Operating system: Linux version 4.4.302+ (root@build5) (gcc version 12.2.0 (GCC) ) #72806 SMP Thu Sep 5 13:44:44 CST 2024 Framework: .NET 6.0.31 OS/Process: x64/x64 Runtime: volume1/@appstore/EmbyServer/system/System.Private.CoreLib.dll Processor count: 2 Data path: /var/packages/EmbyServer/var Application path: /volume1/@appstore/EmbyServer/system MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Connection to https://www.mb3admin.com/admin/service/EmbyPackages.json timed out ---> System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 20 seconds elapsing. ---> System.TimeoutException: A task was canceled. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled. at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken) at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) --- End of inner exception stack trace --- --- End of inner exception stack trace --- at System.Net.Http.HttpClient.HandleFailure(Exception e, Boolean telemetryStarted, HttpResponseMessage response, CancellationTokenSource cts, CancellationToken cancellationToken, CancellationTokenSource pendingRequestsCts) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) --- End of inner exception stack trace --- at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod) at Emby.Server.Implementations.Updates.InstallationManager.GetAvailablePackagesWithoutRegistrationInfo(Boolean enableCache, CancellationToken cancellationToken) at Emby.Server.Implementations.Updates.InstallationManager.GetAvailablePluginUpdates(Version applicationVersion, CancellationToken cancellationToken) at Emby.Server.Implementations.ScheduledTasks.PluginUpdateTask.Execute(CancellationToken cancellationToken, IProgress`1 progress) Source: Emby.Server.Implementations TargetSite: Void MoveNext() InnerException: System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 20 seconds elapsing. Source: System.Net.Http TargetSite: Void HandleFailure(System.Exception, Boolean, System.Net.Http.HttpResponseMessage, System.Threading.CancellationTokenSource, System.Threading.CancellationToken, System.Threading.CancellationTokenSource) at System.Net.Http.HttpClient.HandleFailure(Exception e, Boolean telemetryStarted, HttpResponseMessage response, CancellationTokenSource cts, CancellationToken cancellationToken, CancellationTokenSource pendingRequestsCts) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) InnerException: System.TimeoutException: A task was canceled. Source: TargetSite: InnerException: System.Threading.Tasks.TaskCanceledException: A task was canceled. Source: System.Private.CoreLib TargetSite: Void ThrowForNonSuccess(System.Threading.Tasks.Task) at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken) at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) 2025-01-10 13:44:26.725 Info Server: http/1.1 POST http://192.168.2.3:8096/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=05794356-af37-48ee-ac4c-84aefca28dfd&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret1_x&X-Emby-Language=hu&reqformat=json. Source Ip: host1, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 2025-01-10 13:44:34.328 Info Server: http/1.1 Response 204 to host1. Time: 7612ms. POST http://192.168.2.3:8096/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=05794356-af37-48ee-ac4c-84aefca28dfd&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret1_x&X-Emby-Language=hu&reqformat=json 2025-01-10 14:15:04.989 Info Server: http/1.1 POST http://192.168.2.3:8096/emby/ScheduledTasks/Running/6330ee8fb4a957f33981f89aa78b030f/Delete?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=05794356-af37-48ee-ac4c-84aefca28dfd&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret1_x&X-Emby-Language=hu. Source Ip: host1, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 2025-01-10 14:15:14.875 Info TaskManager: Attempting to cancel Scheduled Task Scan media library 2025-01-10 14:15:15.136 Info Server: http/1.1 Response 204 to host1. Time: 10434ms. POST http://192.168.2.3:8096/emby/ScheduledTasks/Running/6330ee8fb4a957f33981f89aa78b030f/Delete?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=05794356-af37-48ee-ac4c-84aefca28dfd&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret1_x&X-Emby-Language=hu 2025-01-10 14:15:56.442 Info Server: http/1.1 POST http://192.168.2.3:8096/emby/ScheduledTasks/Running/6330ee8fb4a957f33981f89aa78b030f/Delete?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=05794356-af37-48ee-ac4c-84aefca28dfd&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret1_x&X-Emby-Language=hu. Source Ip: host1, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 2025-01-10 14:15:58.056 Error Server: Error processing request *** Error Report *** Version: 4.8.10.0 Command line: /volume1/@appstore/EmbyServer/system/EmbyServer.dll -programdata /var/packages/EmbyServer/var -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -nolocalportconfig -ignore_vaapi_enabled_flag -pidfile /var/packages/EmbyServer/var/EmbyServer.pid -defaultdirectory /volume1/Public -updatepackage emby-server-synology72_{version}_x86_64.spk Operating system: Linux version 4.4.302+ (root@build5) (gcc version 12.2.0 (GCC) ) #72806 SMP Thu Sep 5 13:44:44 CST 2024 Framework: .NET 6.0.31 OS/Process: x64/x64 Runtime: volume1/@appstore/EmbyServer/system/System.Private.CoreLib.dll Processor count: 2 Data path: /var/packages/EmbyServer/var Application path: /volume1/@appstore/EmbyServer/system System.InvalidOperationException: System.InvalidOperationException: Cannot cancel a Task unless it is in the Running state. at Emby.Server.Implementations.ScheduledTasks.ScheduledTaskWorker.Cancel() at Emby.Server.Implementations.ScheduledTasks.TaskManager.Cancel(IScheduledTaskWorker task) at Emby.Api.ScheduledTasks.ScheduledTaskService.Any(StopScheduledTask request) at Emby.Server.Implementations.Services.ServiceController.<>c__DisplayClass8_0.<VoidActionDelegate>b__0(Object service, Object request) at Emby.Server.Implementations.Services.ServiceController.Execute(HttpListenerHost appHost, Object requestDto, IRequest req, Type serviceType) at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost httpHost, IServerApplicationHost appHost, IRequest httpReq, IResponse httpRes, IStreamHelper streamHelper, RestPath restPath, String responseContentType, CancellationToken cancellationToken) at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IRequest httpReq, ReadOnlyMemory`1 urlString, ReadOnlyMemory`1 localPath, CancellationToken cancellationToken) Source: Emby.Server.Implementations TargetSite: Void Cancel() 2025-01-10 14:15:58.098 Info Server: http/1.1 Response 500 to host1. Time: 1657ms. POST http://192.168.2.3:8096/emby/ScheduledTasks/Running/6330ee8fb4a957f33981f89aa78b030f/Delete?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=05794356-af37-48ee-ac4c-84aefca28dfd&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret1_x&X-Emby-Language=hu Edited January 10, 2025 by ZoleeBB
Luke 42077 Posted January 14, 2025 Posted January 14, 2025 hi @ZoleeBBplease attach the complete emby server log file. Thanks !
Carlo 4560 Posted January 20, 2025 Posted January 20, 2025 @ZoleeBB Hi, are you still having an issue?
ZoleeBB 0 Posted January 21, 2025 Author Posted January 21, 2025 On 2025. 01. 14. at 15:28, Luke said: Szia@ZoleeBBkérjük, csatolja a teljes emby szerver naplófájlt. Köszönöm ! embyserver.txt
ZoleeBB 0 Posted January 21, 2025 Author Posted January 21, 2025 13 hours ago, Carlo said: @ZoleeBB Szia, még mindig problémád van? yes, unfortunately.
Carlo 4560 Posted January 26, 2025 Posted January 26, 2025 You have another error that will affect RTM 0 Real Time Monitoring "The configured user limit (8192) on the number of inotify watches has been reached, or the operating system failed to allocate a required resource." The log shows the same problem as above. "Connection to https://www.mb3admin.com/admin/service/EmbyPackages.json timed out" Step 1: Test Connectivity for Both IPv4 and IPv6 Enable SSH Access: Go to Control Panel -> Terminal & SNMP -> Terminal. Enable the SSH service and click Apply. Connect to Your NAS via SSH: Use an SSH client (like PuTTY on Windows or Terminal on macOS/Linux). Connect to your NAS using its IP address and your admin credentials. Test IPv4 Connectivity: Run the following command to ping the specific URL: ping -4 www.mb3admin.com What to look for: If the ping test is successful, you should see replies indicating the IP address and response times. If the ping test fails, you may see error messages such as "Request timed out" or "Destination host unreachable". Test IPv6 Connectivity: Run the following command to ping the specific URL: ping -6 www.mb3admin.com What to look for: If the ping test is successful, you should see replies indicating the IP address and response times. If the ping test fails, you may see error messages such as "Request timed out" or "Destination host unreachable". Step 2: Test Connection to Specific URL Use the curl Command: To test the connection to the specific URL, use the following command: curl -v https://www.mb3admin.com/admin/service/EmbyPackages.json This command will provide detailed information about the connection attempt and help identify any issues. Step 3: Check Network Configuration (If Step 1 Tests Did Not Work) Check IPv4/IPv6 Configuration on Synology NAS: If the ping tests in Step 1 did not show successful replies, ensure that both IPv4 and IPv6 are correctly configured on your Synology NAS and Emby Server. Go to Control Panel -> Network -> Network Interface. Select the network interface you're using and click "Edit". Verify that both IPv4 and IPv6 settings are accurate. Step 4: Network Interface Priority (If Step 1 Tests Did Not Work) Set Network Interface Priority: If the ping tests in Step 1 did not show successful replies, in the Network Interface settings on your Synology NAS, ensure that the network interface you're using is set as the primary interface. Check for any IP conflicts and resolve them if necessary. These steps should help diagnose the connectivity issue on your Synology NAS. Let us know if this helped resolve the issue or not. If you still require help, post the results of the two ping commands and the curl result.
ZoleeBB 0 Posted January 26, 2025 Author Posted January 26, 2025 3 hours ago, Carlo said: You have another error that will affect RTM 0 Real Time Monitoring "The configured user limit (8192) on the number of inotify watches has been reached, or the operating system failed to allocate a required resource." The log shows the same problem as above. "Connection to https://www.mb3admin.com/admin/service/EmbyPackages.json timed out" Step 1: Test Connectivity for Both IPv4 and IPv6 Enable SSH Access: Go to Control Panel -> Terminal & SNMP -> Terminal. Enable the SSH service and click Apply. Connect to Your NAS via SSH: Use an SSH client (like PuTTY on Windows or Terminal on macOS/Linux). Connect to your NAS using its IP address and your admin credentials. Test IPv4 Connectivity: Run the following command to ping the specific URL: ping -4 www.mb3admin.com What to look for: If the ping test is successful, you should see replies indicating the IP address and response times. If the ping test fails, you may see error messages such as "Request timed out" or "Destination host unreachable". Test IPv6 Connectivity: Run the following command to ping the specific URL: ping -6 www.mb3admin.com What to look for: If the ping test is successful, you should see replies indicating the IP address and response times. If the ping test fails, you may see error messages such as "Request timed out" or "Destination host unreachable". Step 2: Test Connection to Specific URL Use the curl Command: To test the connection to the specific URL, use the following command: curl -v https://www.mb3admin.com/admin/service/EmbyPackages.json This command will provide detailed information about the connection attempt and help identify any issues. Step 3: Check Network Configuration (If Step 1 Tests Did Not Work) Check IPv4/IPv6 Configuration on Synology NAS: If the ping tests in Step 1 did not show successful replies, ensure that both IPv4 and IPv6 are correctly configured on your Synology NAS and Emby Server. Go to Control Panel -> Network -> Network Interface. Select the network interface you're using and click "Edit". Verify that both IPv4 and IPv6 settings are accurate. Step 4: Network Interface Priority (If Step 1 Tests Did Not Work) Set Network Interface Priority: If the ping tests in Step 1 did not show successful replies, in the Network Interface settings on your Synology NAS, ensure that the network interface you're using is set as the primary interface. Check for any IP conflicts and resolve them if necessary. These steps should help diagnose the connectivity issue on your Synology NAS. Let us know if this helped resolve the issue or not. If you still require help, post the results of the two ping commands and the curl result. Thank you very much for your help! I created the RTM fix task and ran it successfully. I logged in to the server using SSH through Putty and ran the pings with the sudo command. The ping (v4) responds immediately, but IPv6 is disabled on my side, so the "ping -6 www.mb3admin.com" doesn't work. I also tried the JSON query with curl, and I immediately received the JSON file content, so the server can reach it. I have now rerun the "Scan media library" task, but the result is the same. I’m not sure if this is related, but another issue I’m facing is that the Emby app on Samsung TVs is very slow. After logging in, it doesn’t load anything for 3-4 minutes, it just stays gray, and then suddenly the content appears, and from that point, it works fine. But during the first 3-4 minutes, nothing works. I have about 2-3 TB of data, and I don’t think that’s too much. I also checked the server load during tasks. During the media scan, the CPU is at ~30-40% and the RAM usage is around ~60-70%, which I think is normal. hardware_detection-63873479538.txt embyserver.txt
Luke 42077 Posted January 27, 2025 Posted January 27, 2025 Hi, we’ll take a look at it. Thanks for reporting. 1
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