dubs 1 Posted March 28, 2016 Posted March 28, 2016 (edited) Having decided to dig into the logs under /var/lib/emby-server/logs, I've found this error which I can't fix: *** Error Report *** Version: 3.0.5911.0 Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 4.2.0.34 Processor count: 4 64-Bit OS: True 64-Bit Process: True Program data path: /var/lib/emby-server Mono: 4.2.1 (Stable 4.2.1.102/6dd2d0d Thu Dec 3 04:04:55 UTC 2015) Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe There are multiple root elements. Line 191, position 2. System.Xml.XmlException at System.Xml.XmlTextReaderImpl.Throw (System.Exception e) <0x41249480 + 0x000a7> in <filename unknown>:0 at System.Xml.XmlTextReaderImpl.Throw (System.String res, System.String arg) <0x41248f60 + 0x000a7> in <filename unknown>:0 at System.Xml.XmlTextReaderImpl.Throw (Int32 pos, System.String res) <0x41248f00 + 0x0003f> in <filename unknown>:0 at System.Xml.XmlTextReaderImpl.ParseDocumentContent () <0x41b11990 + 0x003d3> in <filename unknown>:0 at System.Xml.XmlTextReaderImpl.Read () <0x41b0de20 + 0x00067> in <filename unknown>:0 at MediaBrowser.XbmcMetadata.Parsers.BaseNfoParser`1[T].Fetch (MediaBrowser.Controller.Providers.MetadataResult`1 item, System.String metadataFile, System.Xml.XmlReaderSettings settings, CancellationToken cancellationToken) <0x41145ae0 + 0x00137> in <filename unknown>:0 at MediaBrowser.XbmcMetadata.Parsers.BaseNfoParser`1[T].Fetch (MediaBrowser.Controller.Providers.MetadataResult`1 item, System.String metadataFile, CancellationToken cancellationToken) <0x411455c0 + 0x000d7> in <filename unknown>:0 at MediaBrowser.XbmcMetadata.Parsers.EpisodeNfoParser.Fetch (MediaBrowser.Controller.Providers.MetadataResult`1 item, System.Collections.Generic.List`1 images, System.String metadataFile, CancellationToken cancellationToken) <0x4123c340 + 0x00023> in <filename unknown>:0 at MediaBrowser.XbmcMetadata.Providers.EpisodeNfoProvider.Fetch (MediaBrowser.Controller.Providers.MetadataResult`1 result, System.String path, CancellationToken cancellationToken) <0x4123c140 + 0x000ef> in <filename unknown>:0 at MediaBrowser.XbmcMetadata.Providers.BaseNfoProvider`1+<GetMetadata>c__async0[T].MoveNext () <0x41144ec0 + 0x00154> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x7f2715f556d0 + 0x00029> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x7f2715f536b0 + 0x000a7> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x7f2715f53630 + 0x0006b> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x7f2715f535e0 + 0x0003a> in <filename unknown>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () <0x7f2715f53d10 + 0x00017> in <filename unknown>:0 at MediaBrowser.Providers.Manager.MetadataService`2+<RefreshWithProviders>c__async5[TItemType,TIdType].MoveNext () <0x4111b8f0 + 0x016ee> in <filename unknown>:0 It happens every time I scan the library. However, with the the filename being unknown, I don't know what I can do. It seems to be related to the Collections, but I don't have much more than that. I wonder if it is possibly related to this bug - https://github.com/MediaBrowser/Emby/issues/1255 - but if I'm honest that's a total guess. Any suggestions will be greatly appreciated! Edited March 28, 2016 by dubs
Luke 42077 Posted March 28, 2016 Posted March 28, 2016 that's coming from an episode file. i can add more logging to the next release. in the meantime you can try to reproduce by refreshing individual episodes from the web client detail screen. then if you see the error, provide a sample nfo file.
dubs 1 Posted March 28, 2016 Author Posted March 28, 2016 I guessed it was something like that, unfortunately while it appears in 31 times when I refresh, I have in the region of 8000 episodes I believe so a manual refresh of individual episodes could quite likely take a long while . Its not the end of the world, but additional logging in a future version would be great, I'll be more than happy to provide the relevant .nfo files to help with future debugging. I'll keep doing some digging now though, maybe I'll get lucky! As a, slightly unrelated, aside, this has been thrown up due to me trying to speed up my media library refresh. Previously it was taking 8m 30s. After: - Tidying up my file/folder structure (putting all movies into separate folders, peviously a mashup). - Clearing and regenerating all the metadata for everything - Removing all collections data (/var/lib/emby-server/data/collections) and regenerating it afresh - A few other steps i've forgotten Its now dropped to about 2 minutes, not sure if there is anything planned for making errors a bit more visible, it definitely helps to spend some time tidying up!
Luke 42077 Posted March 28, 2016 Posted March 28, 2016 Actually my mistake. I think I know what this is. and I'm guessing that the issue is l limited to multi-episode files. Can you confirm? thanks.
dubs 1 Posted March 29, 2016 Author Posted March 29, 2016 I think it might be (I linked to a similar bug report in the the first post). I've found a few such episodes but I don't really know how to confirm. I could try removing the episode from the library, rescanning, and comparing the count on the errors, but while its always close it doesn't seem totally consistent. I'll PM you a link to one such nfo, that could be causing the issue, in case that helps. Many thanks for the response as always Luke .
Luke 42077 Posted March 29, 2016 Posted March 29, 2016 Thanks, I got your PM. This is actually already a known issue as we just haven't yet added support for this way of storing multiple episode metadatas in a single nfo. it's planned for the future.
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