Jump to content

Problems with Version 4.9.1.90


Recommended Posts

Posted

Hi,

I have Emby on a Synology DS1817+ with two Synology DX517 and DSM 7.1.1. I installed emby-server-synology7_4.9.1.90_x86_64 - better I didn't.

Is it possible, that it is a new function, to put different versions of the same movie in one collection and this function is activated by default? I do not remember, that I ever activated this feature. It looks like Emby did an initial scan to realize this. Many movies could not be identified, before the scan they were OK, maybe fixed by me earlier. I have to check all and correct many movies now manually :(
Here you can't help, but please check this so that no more users have to go through this.

Second thing: Movies in folders containing a file .ignore will now be imported, this was not the case in earlier versions. Can this be fixed please?

Hope you understand my English ;)

Best regards
Ulli

 

Posted

Hi,

well... this is difficult. I attache the oldest log-file, I reported this on Sunday morning, the log file is dated just before the post, maybe it does not show the exact problem.

I just saw, that this function was activated in the movie library (sorry, German language)

image.png.b45d28f848ab6cbfd837bb67fbea0158.png

I don't remember that I did that. So I thought that it has been set in the new version by default.
I recognized long scan of the media library over 1 1/2 hour, normally about 1/2 hour.

After this I found a lot of movies, that could not be identified, they were allright before, f.e.
image.png.d56aa636fdd64a2ab31e2a8b2bbada71.png

And different versions of the same movie have been stored in one folder. 

Some movies have been identified wrong, so I have to check every movie if it is OK. This happens, when the movie title is not unique like "Carrie" oder "Bettina" and there is no IMDP path in an information file.


In addition I have a lot of Movies with a Sample-File in a subfolder Sample. There i created an empty text file called .ignore.
In earlier versions files in these folders have been ignored when scanning the media library. Now I have a lot of movies with the word sample included in the database:

image.png.b711ce84354775a2f1ff7c2b47874414.png

 

Hope that helps - I did not thougt, that examples where needed in this case.

Best regards
Ulli
 

embyserver-63900748801.txt

  • 3 weeks later...
Posted

@Ulli66why do you keep the Samples folders? What is the use case for that?

  • 3 weeks later...
Posted

Because I can. Sorry, I have no time for a discussion about it. I'm still checking my Movie-Database, finished letter K now. I think I will be ready with it in three months.

Changing a movie, the metadata or a picture of it takes more and more time until I restart emby server, that it works fast again. Yesterday I added new movies and series, the scheduled scan of the media library started at 2 am, now it is 12:40 PM and it reached 90%. I have to look how I can add a restart of emby before the scan. I will add the actual log file later, when the scan is ready.

Posted

Hi, have you updated to Emby server 4.9.3? Has that helped?

fArtbReath
Posted

4.9.3.0   Ignores .Ignore

I have sooo much `temporary` files imported now.  My Emby is a total mess.  😖😱

Neminem
Posted

That was changed 😉

@LukeIs it not about time to come with a proper release blog about 4.9 🤷‍♂️

People are confused and it generates a lot more support questions.

As people don't follow beta releases.

Posted
1 hour ago, Neminem said:

That was changed 😉

@LukeIs it not about time to come with a proper release blog about 4.9 🤷‍♂️

People are confused and it generates a lot more support questions.

As people don't follow beta releases.

HI, yes it is. Thanks.

Posted
1 hour ago, Neminem said:

People are confused and it generates a lot more support questions.

As people don't follow beta releases.

Ahh... beta releases. I searched a long time to find release notes, changes, fixes etc. I never thought about beta releases.
 

 

5 hours ago, Luke said:

Hi, have you updated to Emby server 4.9.3? Has that helped?

No. Based on this experience I wait a while before another update. I don't want to start the fixing from beginning on again.

Neminem
Posted
39 minutes ago, Ulli66 said:

No. Based on this experience I wait a while before another update. I don't want to start the fixing from beginning on again.

It was changed during last beta.

And implemented in 4.9 so its the new reality.

 

  • 4 months later...
Posted

WTF... it happened again. After Updating to 4.9.5.0 an initial scan has been done, it took 1 1/2 day. All the corrections I have done are away, I still was not ready with it. Example:

image.png.51c5050f533d2d1b60af4e9a1f6fabec.png

Is that really necessary? I have no time to fix my movies and series after every update. Better I stop using Emby.

 

Posted
11 hours ago, Ulli66 said:

WTF... it happened again. After Updating to 4.9.5.0 an initial scan has been done, it took 1 1/2 day. All the corrections I have done are away, I still was not ready with it. Example:

image.png.51c5050f533d2d1b60af4e9a1f6fabec.png

Is that really necessary? I have no time to fix my movies and series after every update. Better I stop using Emby.

 

Hi there, please attach the Emby server log from when the problem occurred:

Thanks!

 

Posted

I did this last time, did not help, hopefully something will be done this time.

I think the problem is here:

 

2026-05-23 19:45:36.778 Error LibraryMonitor: Error in Directory watcher for: /volume1/video/2D_Filme
	*** Error Report ***
	Version: 4.9.5.0
	Command line: /volume1/@appstore/EmbyServer/system/EmbyServer.dll -programdata /var/packages/EmbyServer/var -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -nolocalportconfig -ignore_vaapi_enabled_flag -pidfile /var/packages/EmbyServer/var/EmbyServer.pid -defaultdirectory /volume1/Public -updatepackage emby-server-synology7_{version}_x86_64.spk
	Operating system: Linux version 3.10.108 (root@build3) (gcc version 8.5.0 (GCC) ) #42962 SMP Tue Jul 29 14:28:52 CST 2025
	OS/Process: x64/x64
	Framework: .NET 8.0.25
	Runtime: volume1/@appstore/EmbyServer/system/System.Private.CoreLib.dll
	Processor count: 4
	Data path: /var/packages/EmbyServer/var
	Application path: /volume1/@appstore/EmbyServer/system
	System.IO.IOException: System.IO.IOException: The configured user limit (8192) on the number of inotify watches has been reached, or the operating system failed to allocate a required resource.
	Source: 
	TargetSite: 
	No Stack Trace Available
	
2026-05-23 19:45:36.779 Info LibraryMonitor: Stopping directory watching for path /volume1/video/2D_Filme
2026-05-23 19:45:48.806 Info LibraryMonitor: Watching directory with new FileSystemWatcher for /volume1/video/2D_Filme for item 13755
2026-05-23 19:45:57.902 Info ScheduledTaskService-0HNLOUC9N80AC:0000002D: http/1.1 POST http://192.168.2.105:8096/emby/ScheduledTasks/Running/6330ee8fb4a957f33981f89aa78b030f?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=d46cf24f-2b26-49a1-99f3-79f83f01aa74&X-Emby-Client-Version=4.9.5.0&X-Emby-Token=x_secret5_x&X-Emby-Language=de. Source Ip: host3, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36
2026-05-23 19:45:57.945 Info TaskManager: Executing Scan media library
2026-05-23 19:45:57.945 Info ScheduledTaskService-0HNLOUC9N80AC:0000002D: http/1.1 Response 204 to host3. Time: 43ms. POST http://192.168.2.105:8096/emby/ScheduledTasks/Running/6330ee8fb4a957f33981f89aa78b030f?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=d46cf24f-2b26-49a1-99f3-79f83f01aa74&X-Emby-Client-Version=4.9.5.0&X-Emby-Token=x_secret5_x&X-Emby-Language=de. 
2026-05-23 19:45:58.444 Info App: ValidatePhysicalRoots start validating 13755 2D_Filme /volume1/video/2D_Filme
2026-05-23 19:47:43.289 Info App: Removing item from database, Type: Folder, Name: 13.Uhr.mittags, Path: /volume1/video/2D_Filme/13.Uhr.mittags, Id: 386934
2026-05-23 19:47:43.556 Info App: Deleting path /var/packages/EmbyServer/var/metadata/library/f8/f87e4caa89a0eea85e1f94f4d0d3858d
2026-05-23 19:47:43.580 Info App: Deleting path /var/packages/EmbyServer/var/metadata/library/f8/f87e4caa89a0eea85e1f94f4d0d3858d
2026-05-23 19:47:43.580 Info App: Deleting path /var/packages/EmbyServer/var/metadata/library/37/3704906a855270080c1fbff0b83c6e36

Then everything will be removed from the database :(

I installed emby-server-synology7_4.9.5.0_x86_64.spk
DSM Version is DSM 7.1.1-42962 Update 9

20260523_embyserver_after_update_cut.txt

Posted

@Ulli66This should help you with your error.

"The configured user limit (8192) on the number of inotify watches has been reached, or the operating system failed to allocate a required resource."

 

  • Like 1
FrostByte
Posted (edited)
16 hours ago, Ulli66 said:

I did this last time, did not help, hopefully something will be done this time.

I think the problem is here:

The fix Neminem posted will definitely fix that error, but that error isn't what is causing your long scans.  Inotify is used by RTM for tracking changes to trigger automatic scans.

Edited by FrostByte

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