Metadata is no longer imported

[kimare 0]

For some reason the server no longer import metadata. No longer covers and proper episode name are displayed.

The Emby setting have been unchanged. I don't know if this has happened after an update or if there is any other reason.

I've tried to refresh several times, but no luck. No message, it's just nothing happening.
Last time also the cover images of several shows disappeared. The show is linked with the correct shows at the different db's.

Edited December 27, 2020 by kimare

[Abobader 3470]

Hello kimare,

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[Luke 42083]

Hi there, what metadata providers are enabled on the library, and in what order? How are the files named and organized?

[kimare 0]

39 minutes ago, Luke said:

Hi there, what metadata providers are enabled on the library, and in what order? How are the files named and organized?

Files are organized like this:
F:\\Shows\Category\Show\Show S01\Show S01E01.mkv

 

After I encountered the problems I've tried several setting for metadata providers. Currently I have these. 

Edited December 27, 2020 by kimare

[Luke 42083]

Ok, please try refreshing the metadata for a series, then attach the emby server log so that we can see what's going on. thanks.

[Happy2Play 9783]

Looking at the first post it would appear the Series is partially identified but the episodes are not identified as the episode titles are not right.

What externalid appear for this example?

[ebr 16187]

13 hours ago, kimare said:

F:\\Shows\Category\Show\Show S01\Show S01E01.mkv

Is that a supported Season folder name?

[kimare 0]

I've looked over when was the last time Emby collected the correct metadata. It looks like it this was at the end of may 2020.

The first time where I'm certain correct metadata isn't loaded is probably at the end of june or beginning of july.

 

22 hours ago, Luke said:

Ok, please try refreshing the metadata for a series, then attach the emby server log so that we can see what's going on. thanks.

Refreshed the same show as in the first post. Also added another season of an existing show and a totally new show.

Latest server log attached.

 

22 hours ago, Happy2Play said:

Looking at the first post it would appear the Series is partially identified but the episodes are not identified as the episode titles are not right.

What externalid appear for this example?

That's because season 1 was added before Emby refused to add metadata  The external-ids are correct.

11 hours ago, ebr said:

Is that a supported Season folder name?

I don't know. But for sure it wasn't a problem before june 2020. The filestructure have been unchanged.

 

Edited December 28, 2020 by kimare

[Happy2Play 9783]

Is there a reason you are still on 4.4.3.0 and not the current version 4.5.4.0? 

Synology requires manual updates for time being via download page.   Emby Server for Synology NAS - Emby

But if I remember correctly this is a know issue with the older version. @Luke

But you have a trust issue on this install.  (all providers)

2020-12-28 00:43:48.316 Error HttpClient: Error TrustFailure getting response from 
	*** Error Report ***
	Version: 4.4.3.0
	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 2.6.32.12
	64-Bit OS: False
	64-Bit Process: False
	User Interactive: False
	Mono: 6.8.0.105 (tarball Wed Apr  8 20:33:25 UTC 2020)
	Runtime: file:///volume1/@appstore/EmbyServer/3rdparty/mono/6.8.0.105/lib/mono/4.5/mscorlib.dll
	System.Environment.Version: 4.0.30319.42000
	Processor count: 1
	Program data path: /var/packages/EmbyServer/target/var
	Application directory: /volume1/@appstore/EmbyServer/releases/4.4.3.0
	System.Net.WebException: System.Net.WebException: Error: TrustFailure (Authentication failed, see inner exception.) ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. ---> Mono.Btls.MonoBtlsException: Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED
	  at /source/mono/external/boringssl/ssl/handshake_client.c:1132
	  at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x00048] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncOperationStatus status, System.Boolean renegotiate) [0x000da] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake(Mono.Net.Security.AsyncOperationStatus,bool)
	  at Mono.Net.Security.AsyncHandshakeRequest.Run (Mono.Net.Security.AsyncOperationStatus status) [0x00006] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (System.Threading.CancellationToken cancellationToken) [0x000fc] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	   --- End of inner exception stack trace ---
	  at Mono.Net.Security.MobileAuthenticatedStream.ProcessAuthentication (System.Boolean runSynchronously, Mono.Net.Security.MonoSslAuthenticationOptions options, System.Threading.CancellationToken cancellationToken) [0x00262] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at Mono.Net.Security.MonoTlsStream.CreateStream (System.Net.WebConnectionTunnel tunnel, System.Threading.CancellationToken cancellationToken) [0x0016a] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x001ba] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	   --- End of inner exception stack trace ---
	  at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x0021a] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at System.Net.WebConnection.InitConnection (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x00141] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at System.Net.WebOperation.Run () [0x0009a] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at System.Net.WebCompletionSource`1[T].WaitForCompletion () [0x00094] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00020] in <b373cc92cfb94ef6a19b4f1140645494>: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 <9d3f0d4bd0fb4c1e8b6c2ac1ba1303ac>:0 
	Source: System
	TargetSite: System.Net.WebResponse EndGetResponse(System.IAsyncResult)
	InnerException: System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception.
	Source: mscorlib
	TargetSite: Void Throw()
	  at Mono.Net.Security.MobileAuthenticatedStream.ProcessAuthentication (System.Boolean runSynchronously, Mono.Net.Security.MonoSslAuthenticationOptions options, System.Threading.CancellationToken cancellationToken) [0x00262] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at Mono.Net.Security.MonoTlsStream.CreateStream (System.Net.WebConnectionTunnel tunnel, System.Threading.CancellationToken cancellationToken) [0x0016a] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x001ba] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	InnerException: Mono.Btls.MonoBtlsException: Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED
	  at /source/mono/external/boringssl/ssl/handshake_client.c:1132
	Source: System
	TargetSite: Boolean ProcessHandshake()
	  at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x00048] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncOperationStatus status, System.Boolean renegotiate) [0x000da] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake(Mono.Net.Security.AsyncOperationStatus,bool)
	  at Mono.Net.Security.AsyncHandshakeRequest.Run (Mono.Net.Security.AsyncOperationStatus status) [0x00006] in <b373cc92cfb94ef6a19b4f1140645494>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (System.Threading.CancellationToken cancellationToken) [0x000fc] in <b373cc92cfb94ef6a19b4f1140645494>:0 

 

[kimare 0]

5 minutes ago, Happy2Play said:

Is there a reason you are still on 4.4.3.0 and not the current version 4.5.4.0? 

Synology requires manual updates for time being via download page.   Emby Server for Synology NAS - Emby

But if I remember correctly this is a know issue with the older version. @Luke

But you have a trust issue on this install.  (all providers)

I didn't know there was a version I had to install manually. I've trusted the auto-update from Synology would take care of things. I'll look into this.

[Luke 42083]

Let us know how you get on. Thanks.

[Happy2Play 9783]

Yes are lots of topics in the Synology section but currently the old repo is no longer being used.  It will eventually make it back to the package center.

[kimare 0]

17 minutes ago, Luke said:

Let us know how you get on. Thanks.

It looks like it's working. The server is working, but some new covers are loaded in. I'll report back if I have any issues. Thanks.

[Luke 42083]

Thanks for the feedback.