Jump to content
CaptainSandwich

ANSWERED Migrated to docker (unraid) - Many Services failing - Name or service not known

Recommended Posts

CaptainSandwich
Posted (edited)

Hi All,

 

I've recently migrated my installation over to the official Emby docker container on an Unraid server from a previous Windows setup. Settings were migrated across using the backup and restore plugin. Only user data was restored as obviously paths had changed in the migration process.

 

Since the migration, I've found that many services are failing with a "Name or service not known" exception, similar to the below. Failing to retrieve metadata and plugin updates are the most obvious problems. 

2020-04-23 19:52:21.760 Error App: Error in TheTVDB
	*** Error Report ***
	Version: 4.4.2.0
	Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3
	Operating system: Unix 4.19.107.0
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: True
	Runtime: file:///system/System.Private.CoreLib.dll
	System.Environment.Version: 3.1.2
	Processor count: 14
	Program data path: /config
	Application directory: /system
	System.Net.Http.HttpRequestException: System.Net.Http.HttpRequestException: Name or service not known
	 ---> System.Net.Sockets.SocketException (0xFFFDFFFF): Name or service not known
	   at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, 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 Tvdb.TvdbSeriesProvider.DownloadSeriesZip(String seriesId, String idType, String seriesName, Nullable`1 seriesYear, String seriesDataPath, Nullable`1 lastTvDbUpdateTime, String preferredMetadataLanguage, String saveAsMetadataLanguage, CancellationToken cancellationToken)
	   at Tvdb.TvdbSeriesProvider.DownloadSeriesZip(String seriesId, String idType, String seriesName, Nullable`1 seriesYear, String seriesDataPath, Nullable`1 lastTvDbUpdateTime, String preferredMetadataLanguage, CancellationToken cancellationToken)
	   at Tvdb.TvdbSeriesProvider.EnsureSeriesInfo(Dictionary`2 seriesProviderIds, String seriesName, Nullable`1 seriesYear, String preferredMetadataLanguage, CancellationToken cancellationToken)
	   at Tvdb.TvdbEpisodeProvider.GetMetadata(EpisodeInfo searchInfo, CancellationToken cancellationToken)
	   at MediaBrowser.Providers.Manager.MetadataService`2.ExecuteRemoteProviders(MetadataResult`1 temp, String logName, TIdType id, IEnumerable`1 providers, CancellationToken cancellationToken)
	Source: System.Net.Http
	TargetSite: Void MoveNext()
	InnerException: System.Net.Sockets.SocketException: Name or service not known
	Source: System.Private.CoreLib
	TargetSite: Void Throw()
	   at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)

IP address of the server has not changed from the Windows installation, and the firewall setup has not changed either. Docker is also new to me, so I couldn't say for certain, but I don't think this is a firewall problem? 

 

The server is behind a reverse proxy, which is successfully providing SSL certificates and allows for remote browsing/playback so not sure if this may be a factor. In any case, port 8096 is also forwarded to the server.

 

Also not sure if it may be related or an application-specific issue; Sonarr does not display cover images for shows from the "Add new series" page, however it does successfully retrieve images when the series has been added. Radarr works fine. 

 

Full log has been attached, can anyone provide any wisdom or next steps for troubleshooting?

 

Thanks. 

 

EDIT: Added docker port mappings, since it's probably relevant. 

embyserver.txt

post-132919-0-99757500-1587638999_thumb.png

Edited by CaptainSandwich

Share this post


Link to post
Share on other sites
BAlGaInTl

I'm not an expert on the subject, but I do use Unraid.

 

Did you set this up manually, or did you use the container from the Unraid apps?

 

Is there a reason you are using the "host" network instead of "bridge"?

 

I'm using bridge, and everything is working great with a very similar setup.

Share this post


Link to post
Share on other sites
CaptainSandwich

Did you set this up manually, or did you use the container from the Unraid apps?

 

Is there a reason you are using the "host" network instead of "bridge"?

 

 

It was setup from the official Emby docker container using the Community Apps plugin. To be honest, I can't even remember changing the network mode so can't really give an explanation as to why it's configured to host.

 

Overnight, I performed a force update on the container and since then things seem to be working pretty well. Metadata retrieval is working and the log has cleared up. Not sure whether there's still some underlying issue that may return, or why this might have (temporarily?) resolved it, but I'll report back if there are any further issues.

 

Thanks for the reply, BAIGaInTI. 

Share this post


Link to post
Share on other sites
BAlGaInTl

It was setup from the official Emby docker container using the Community Apps plugin. To be honest, I can't even remember changing the network mode so can't really give an explanation as to why it's configured to host.

 

Overnight, I performed a force update on the container and since then things seem to be working pretty well. Metadata retrieval is working and the log has cleared up. Not sure whether there's still some underlying issue that may return, or why this might have (temporarily?) resolved it, but I'll report back if there are any further issues.

 

Thanks for the reply, BAIGaInTI. 

 

You're welcome.

 

Hopefully everything continues to go smoothly and this was just a hiccup.  I love running Emby in Docker.  

Share this post


Link to post
Share on other sites
CaptainSandwich

So, I found that this problem came back. It was just after I had rebooted the unraid server and the Emby container auto started. I found that restarting the container resolved the issue again and it hasn't returned since (has been roughly 6 days).

 

The server is yet to be rebooted again, but if the issue returns on next reboot, I suspect it may be related to the auto-start/timing relative to a server boot. Will continue to monitor. 

Share this post


Link to post
Share on other sites
Luke

Thanks, let us know !

Share this post


Link to post
Share on other sites
CaptainSandwich

Alright, so first server reboot in about 12 days and the "Name or Service not known" exception is back immediately after the EmbyServer container autostarted. Restarted the container and there were no such errors in the new log, and Emby immediately downloaded a new TVDB plugin update. I think it's definitely somehow related to autostart of the container on server startup, so working around it is pretty straightforward at the moment. 

 

EmbyServer log files have been attached. Also a copy/paste of the EmbyServer container log from Unraid's WebUI after container restart. No timestamps in this one, and I assume it resets with the container? Unfortunately I didn't get a copy of this log whilst Emby was reporting the 'name or service' error. Does anyone know where docker log files are stored in unraid? 

embyserver_after_server_restart.txt

docker_log_after_container_restart.txt

embyserver_after_container_restart.txt

Share this post


Link to post
Share on other sites
Luke

Is it possible the server started up before the network fully initialized?

Share this post


Link to post
Share on other sites
alturismo
Posted (edited)

may just add a delay on startup, docker tab, upper right switch from basic to advanced view

 

on the right u can add a delay in seconds ...

 

sample see attachement, wait 20 = wait 20 seconds on startup

post-112497-0-94670600-1589027986_thumb.png

Edited by alturismo
  • Like 1

Share this post


Link to post
Share on other sites
CaptainSandwich

Is it possible the server started up before the network fully initialized?

 

I suppose it's possible. I'm not sure any of the logs I've been looking at in Unraid have sufficient detail to help in troubleshooting this though.

 

may just add a delay on startup, docker tab, upper right switch from basic to advanced view

 

on the right u can add a delay in seconds ...

 

sample see attachement, wait 20 = wait 20 seconds on startup

 

Added a 30 second delay after you posted this. Just rebooted the server again tonight for the first time in a few weeks and it looks like Emby has started and is running without any of the name or service not known errors. There were a couple of container updates recently, so either one of those has resolved the original issue or the delay works around it. In any case, it seems to be working for now.

 

Thanks for your help guys, I'll post back if I see the error return. 

Share this post


Link to post
Share on other sites
Luke

Thanks for the feedback.

Share this post


Link to post
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...