imennoharm 1 Posted August 28, 2022 Share Posted August 28, 2022 Hello all... Last night we had a storm roll through which killed my server last night... I power cycled the system and everything came up the way that it should except for Emby... and when checking the logs, it seems that www.mb3admin.com is not responding... from the server I am able to ping the site... via the IP 173.230.139.54... besides the power outage I have not changed anything on the firewall or network side of things... Ideas? Error HttpClient: Error getting response from https://www.mb3admin.com/admin/service/EmbyPackages.json *** Error Report *** Version: 4.7.6.0 Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 5.15.46-Unraid (root@Develop) (gcc (GCC) 11.2.0, GNU ld version 2.37-slack15) #1 SMP Fri Jun 10 11:08:41 PDT 2022 Framework: .NET 6.0.2 OS/Process: x64/x64 Runtime: system/System.Private.CoreLib.dll Processor count: 24 Data path: /config Application path: /system System.Net.Http.HttpRequestException: System.Net.Http.HttpRequestException: Name or service not known (www.mb3admin.com:443) ---> System.Net.Sockets.SocketException (0xFFFDFFFF): Name or service not known at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) --- End of inner exception stack trace --- at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request) 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) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) Source: System.Net.Http TargetSite: Void MoveNext() InnerException: System.Net.Sockets.SocketException: Name or service not known Source: System.Net.Sockets TargetSite: Void ThrowException(System.Net.Sockets.SocketError, System.Threading.CancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) Error App: Error getting available plugin updates *** Error Report *** Version: 4.7.6.0 Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 5.15.46-Unraid (root@Develop) (gcc (GCC) 11.2.0, GNU ld version 2.37-slack15) #1 SMP Fri Jun 10 11:08:41 PDT 2022 Framework: .NET 6.0.2 OS/Process: x64/x64 Runtime: system/System.Private.CoreLib.dll Processor count: 24 Data path: /config Application path: /system System.Net.Http.HttpRequestException: System.Net.Http.HttpRequestException: Name or service not known (www.mb3admin.com:443) ---> System.Net.Sockets.SocketException (0xFFFDFFFF): Name or service not known at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) --- 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: System.Net.Http TargetSite: Void MoveNext() InnerException: System.Net.Sockets.SocketException: Name or service not known Source: System.Net.Sockets TargetSite: Void ThrowException(System.Net.Sockets.SocketError, System.Threading.CancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 27.142511 seconds Info App: Starting entry point Emby.Notifications.Notifications Info App: Entry point completed: Emby.Notifications.Notifications. Duration: 0.0008271 seconds Info App: Starting entry point Emby.Server.Sync.SyncManagerEntryPoint Info App: SyncRepository Initialize taking write lock Info App: SyncRepository Initialize write lock taken Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0079248 seconds Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0022363 seconds Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 0.0001366 seconds Info App: All entry points have started Link to comment Share on other sites More sharing options...
imennoharm 1 Posted August 28, 2022 Author Share Posted August 28, 2022 offhand... I tried to make some changes in the Docker settings and I got a new error complaining about an invalid setting... nvidia... After removing the --runtime=nvidia flag I was able to get the machine up and running again... but without hardware acceleration... huh? Link to comment Share on other sites More sharing options...
imennoharm 1 Posted August 28, 2022 Author Share Posted August 28, 2022 Please Ignore this... After posting this I proceeded to validate the OS loaded the drivers for the video card, which went missing for some reason... I reinstalled the drivers for the video card and added in --runtime=nvidia setting and everything is back to normal... At the start it's a strange error to get when missing drivers for the video card... Link to comment Share on other sites More sharing options...
Q-Droid 670 Posted August 28, 2022 Share Posted August 28, 2022 50 minutes ago, imennoharm said: Name or service not known (www.mb3admin.com:443) Do you happen to also have a local DNS resolver like pi-hole? Maybe that also went down because this looks more like a name resolution error. If not that then something else network related. Link to comment Share on other sites More sharing options...
imennoharm 1 Posted August 28, 2022 Author Share Posted August 28, 2022 2 hours ago, Q-Droid said: Do you happen to also have a local DNS resolver like pi-hole? Maybe that also went down because this looks more like a name resolution error. If not that then something else network related. I do... But I wouldnt think that was the issue due to resolving the DNS name from the server... The issue was only fixed by reinstalling the video card drivers of all things... just strange that this log pointed to something completely different vs the real issue Link to comment Share on other sites More sharing options...
Luke 37250 Posted August 28, 2022 Share Posted August 28, 2022 That's very odd, but glad to hear you're back up and running. 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