Jump to content

System.IO.FileNotFoundException exits library scan


antivist
Go to solution Solved by antivist,

Recommended Posts

antivist

Hi all,

 

so here's my problem:

Im running Emby Server 4.1.1.0-1 on DSM 6.2.2-24922.

 

In german we have characters like: ä, ü, ö, ß and so on. After a library scan / metadata update Emby renames these characters to for example: ¿½ for ü. 

A while ago (before 4.x update), I've been browsing my Library Folder and was renaming these paths back to ¿½ -> ü for a better reading.

A few days ago I was wondering why my movie library was not displaying recently added movies, while other libraries like series do.

So I've been investigating the issue. 

 

- Was manually triggering some library scans.

- Deleted library.db in data folder.

- Reinstalled Emby Server and restored previous backup.

With no success. Movie library remained unchanged.

 

So I took a look into logs and I've found the following:

2019-05-22 20:53:50.366 Error LibraryMonitor: Error in Directory watcher for: /volume1/video/Filme
	*** Error Report ***
	Version: 4.1.1.0
	Command line: /volume1/@appstore/EmbyServer/releases/4.1.1.0/EmbyServer.dll -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 4.4.59.0
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: True
	Runtime: file:///volume1/@appstore/EmbyServer/3rdparty/netcore/2.2.1/runtime/System.Private.CoreLib.dll
	Processor count: 2
	Program data path: /var/packages/EmbyServer/target/var
	Application directory: /volume1/@appstore/EmbyServer/releases/4.1.1.0
	System.IO.FileNotFoundException: System.IO.FileNotFoundException: Could not find file '/volume1/video/Filme/Welteng�nger (2018)'.
	File name: '/volume1/video/Filme/Welteng�nger (2018)'
	Source: 
	TargetSite: 
	No Stack Trace Available
	
2019-05-22 20:53:50.366 Info LibraryMonitor: Stopping directory watching for path /volume1/video/Filme

So what happens is that somewhere this path was saved (I assume library.db) and after renaming the folder to: Weltengänger (2018), this file could no longer be found, of course.

 

Unfortunately this stops the entire library scan, which then results in no new titles for this library.

 

But what I would have expected is that if there is a System.IO.FileNotFoundException raised, this path would have been either ignored or removed from library.db or where it is saved and the scan just skips this particular path instead of exiting the entire process.

 

After renaming the paths back to where Emby is expecting to find files in, library scan is running without problems and movies been added again.

 

Hope this helps someone with similiar problems and maybe leads to some improvements.

Link to comment
Share on other sites

  • 2 weeks later...
antivist

Hi Luke,

 

the old logs were overwritten or deleted so I recreated the issue, please see the log attached.

 

It happens at / around 2019-06-02 23:42:10.556.

 

I'd guess this is an issue with encoding.

 

Greetings,

 

Sebastian

Link to comment
Share on other sites

  • 1 month later...
antivist

@@Luke,

 

the exception is still fired but it seems that the scan is continuing.

Unfortunately it creates a new folder with the original filename when the exception is raised.

 

This is what I did:

 

I renamed the original folder "Das Komplott - Verrat auf höchster Ebene (2017)" to "Das Komplott - Verrat auf höchster Ebene (2017)"  notice the Ã¶ is now ö.


In my library folder theres now only "Das Komplott - Verrat auf höchster Ebene (2017)".

Now I did a scan from the webinterface.

The exception is fired and the folder  "Das Komplott - Verrat auf höchster Ebene (2017)" was created by emby with only a .nfo file as content.

 

I do now have two folders: Das Komplott - Verrat auf höchster Ebene (2017) and Das Komplott - Verrat auf höchster Ebene (2017).

I'll attach a log so you can have a look. Scroll to timestamp: 2019-07-28 18:00:19.294

Regards,

 

Sebastian

 

 

 

 

embyserver.txt

Link to comment
Share on other sites

  • 4 months later...

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...