Jump to content

"Error LibraryMonitor" -- heaps and heaps of error reports in the server log

pryoclastic

By pryoclastic
in FreeBSD

 Share

Recommended Posts

pryoclastic

pryoclastic   6

Posted
Posted (edited)

The server log file is full of these types of errors for the various content folders:

2018-11-04 21:46:29.529 Error LibraryMonitor: Error in Directory watcher for: /home/--/emby_content/Music_Videos	*** Error Report ***	Version: 3.5.2.0	Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -os freebsd -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server	Operating system: Unix 11.2.4.0	64-Bit OS: True	64-Bit Process: True	User Interactive: False	Mono: 5.10.1.57 (5.10.1.57 Thu Sep 13 08:28:08 UTC 2018)	Processor count: 4	Program data path: /var/db/emby-server	Application directory: /usr/local/lib/emby-server	System.IO.IOException: persistent kevent() error, error code = '13'	  at System.IO.KqueueMonitor.Monitor () [0x00121] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0 	  at System.IO.KqueueMonitor.DoMonitor () [0x0003f] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0 	System.IO.IOException	  at System.IO.KqueueMonitor.Monitor () [0x00121] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0 	  at System.IO.KqueueMonitor.DoMonitor () [0x0003f] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0

l did several forum keyword searches but did not really find anything.  They all have "error code 13" in common.

 

Thoughts?

Edited by pryoclastic
Link to comment
Share on other sites
Luke Emby Team

Luke   37058

Posted
Posted

This is going to happen on FreeBSD. Try turning off the realtime monitor if you don't like seeing errors in your server log.

 

This feature is not officially supported on BSD by the mono runtime. Some FreeBSD developers have patched the mono runtime themselves to try and get it to work. That's really as much as I know about the situation right now.

Link to comment
Share on other sites
pryoclastic

pryoclastic   6

Posted
  • Author
Posted

Try turning off the realtime monitor ..

hrmm .. I don't recall turning it on. :D Hold my hand, where do I go to disable it?

 

Thanks!

Link to comment
Share on other sites
pryoclastic

pryoclastic   6

Posted
  • Author
Posted

It's a setting on each individual library in Emby library setup.

 

Got it.  Might mention that I had to enable "show advanced settings" to see the option once inside of the media folder.

 

Thanks!

  • Like 1
Link to comment
Share on other sites
tdiaz

tdiaz   3

Posted
Posted

Would this be why I have had bouts of crashes at starting up, where it seems it needs to get through something before becoming ready?

 

Is it possible to have a "Refresh/Scan" option less buried than in Scheduled Tasks?

 

Like say, if the user has delete privs, then there could be a button to update the library visible on the front end, too?

 

It's not 100% clear to me if browsing by folder / directory will just show what is actually there like Plex and pretty much Everything Else, without having to wait for a library update.

Link to comment
Share on other sites
Luke Emby Team

Luke   37058

Posted
Posted

Would this be why I have had bouts of crashes at starting up, where it seems it needs to get through something before becoming ready?

 

Is it possible to have a "Refresh/Scan" option less buried than in Scheduled Tasks?

 

Like say, if the user has delete privs, then there could be a button to update the library visible on the front end, too?

 

It's not 100% clear to me if browsing by folder / directory will just show what is actually there like Plex and pretty much Everything Else, without having to wait for a library update.

 

We'd have to look at the log file of an example.

 

Regarding folder views, our folder views are not perfect, however they will be vastly improved in the upcoming 3.6 release and will more closely align with your folder contents.

Link to comment
Share on other sites
tdiaz

tdiaz   3

Posted
Posted 
2018-11-04 00:50:16.508 LibraryMonitor: Error in Directory watcher for: /mnt/Cattlecar/DVR/Cinema/Crime & Gangster
	*** Error Report ***
	Version: 3.6.0.59
	Command line: /usr/local/opt/emby-server/system/EmbyServer.exe -os freebsd -ffmpeg /usr/local/opt/emby-server/bin/ffmpeg -ffprobe /usr/local/opt/emby-server/bin/ffprobe -programdata /var/db/emby-server -updatepackage emby-server-freebsd_{version}_amd64.txz
	Operating system: Unix 11.2.4.0
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: False
	Mono: 5.10.1.57 (5.10.1.57 Thu Oct 25 02:19:20 UTC 2018)
	Processor count: 16
	Program data path: /var/db/emby-server
	Application directory: /usr/local/opt/emby-server/system
	System.IO.IOException: System.IO.IOException: persistent kevent() error, error code = '0'
	  at System.IO.KqueueMonitor.Monitor () [0x00121] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0 
	  at System.IO.KqueueMonitor.DoMonitor () [0x0003f] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0 
	Source: System
	TargetSite: Void Monitor()
	  at System.IO.KqueueMonitor.Monitor () [0x00121] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0 
	  at System.IO.KqueueMonitor.DoMonitor () [0x0003f] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0 
	
2018-11-04 00:50:16.508 Info LibraryMonitor: Stopping directory watching for path /mnt/Cattlecar/DVR/Cinema/Crime & Gangster
2018-11-04 00:50:16.511 Error LibraryMonitor: Error in Directory watcher for: /mnt/Cattlecar/DVR/Cinema/Epics & Historical
	*** Error Report ***
	Version: 3.6.0.59
	Command line: /usr/local/opt/emby-server/system/EmbyServer.exe -os freebsd -ffmpeg /usr/local/opt/emby-server/bin/ffmpeg -ffprobe /usr/local/opt/emby-server/bin/ffprobe -programdata /var/db/emby-server -updatepackage emby-server-freebsd_{version}_amd64.txz
	Operating system: Unix 11.2.4.0
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: False
	Mono: 5.10.1.57 (5.10.1.57 Thu Oct 25 02:19:20 UTC 2018)
	Processor count: 16
	Program data path: /var/db/emby-server
	Application directory: /usr/local/opt/emby-server/system
	System.IO.IOException: System.IO.IOException: persistent kevent() error, error code = '0'
	  at System.IO.KqueueMonitor.Monitor () [0x00121] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0 
	  at System.IO.KqueueMonitor.DoMonitor () [0x0003f] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0 
	Source: System
	TargetSite: Void Monitor()
	  at System.IO.KqueueMonitor.Monitor () [0x00121] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0 
	  at System.IO.KqueueMonitor.DoMonitor () [0x0003f] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0 
	
2018-11-04 00:50:16.511 Info LibraryMonitor: Stopping directory watching for path /mnt/Cattlecar/DVR/Cinema/Epics & Historical

The options are enabled as I had originally been using Windows, but switched to FreeBSD a while back. The entries are similar to the first post, but error code is 0.

Link to comment
Share on other sites
Luke Emby Team

Luke   37058

Posted
Posted

Personally I think it is best that we disable this altogether on FreeBSD and then re-evaluate when Microsoft releases their .NET Core runtime for FreeBSD.

 

Unfortunately I don't have an answer for those errors in the log file based on my previous response.

Link to comment
Share on other sites
  • 3 weeks later...
djhifi

djhifi   55

Posted
Posted (edited)

I seem to be having a somewhat same behavior on a Synology in several of my library paths.

In Windows I'm aware that there's a limit on the number of changes allowed within a given amount of time. But does the same apply here?

 

Example from the logs:

 

2018-11-22 06:06:13.119 Error LibraryMonitor: Error in Directory watcher for: /volume11/Array-6.5/Filmes (HD13.5)/TV Shows
*** Error Report ***
Version: 3.6.0.64
Command line: /volume6/@appstore/EmbyServerNET/releases/3.6.0.64-beta/EmbyServer.dll -package synology -nocustomffmpeg -programdata /var/packages/EmbyServerNET/target/var -ffmpeg /var/packages/EmbyServerNET/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServerNET/target/ffmpeg/bin/ffprobe -restartexitcode 121
Operating system: Unix 3.10.105.0
64-Bit OS: True
64-Bit Process: True
User Interactive: True
Processor count: 4
Program data path: /var/packages/EmbyServerNET/target/var
Application directory: /volume6/@appstore/EmbyServerNET/releases/3.6.0.64-beta
System.IO.IOException: System.IO.IOException: The configured user limit (8192) on the number of inotify watches has been reached.
Source:
TargetSite:
No Stack Trace Available

2018-11-22 06:06:13.119 Info LibraryMonitor: Stopping directory watching for path /volume11/Array-6.5/Filmes (HD13.5)/TV Shows
 

2018-11-22 06:06:13.126 Error LibraryMonitor: Error in Directory watcher for: /volume7/Array-6.1/Filmes (HD13.1)/Movies
*** Error Report ***
Version: 3.6.0.64
Command line: /volume6/@appstore/EmbyServerNET/releases/3.6.0.64-beta/EmbyServer.dll -package synology -nocustomffmpeg -programdata /var/packages/EmbyServerNET/target/var -ffmpeg /var/packages/EmbyServerNET/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServerNET/target/ffmpeg/bin/ffprobe -restartexitcode 121
Operating system: Unix 3.10.105.0
64-Bit OS: True
64-Bit Process: True
User Interactive: True
Processor count: 4
Program data path: /var/packages/EmbyServerNET/target/var
Application directory: /volume6/@appstore/EmbyServerNET/releases/3.6.0.64-beta
System.IO.IOException: System.IO.IOException: The configured user limit (8192) on the number of inotify watches has been reached.
Source:
TargetSite:
No Stack Trace Available
 

2018-11-22 06:06:13.126 Info LibraryMonitor: Stopping directory watching for path /volume7/Array-6.1/Filmes (HD13.1)/Movies

****

 

 

This is a minor concern since the folder monitoring is working. But still, doesn't hurt to know a little bit more.

Edited by djhifi
Link to comment
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
 Share
Go to topic listing
×
×
  • Create New...