inotify watch failure

If none of the more specific forums is the right place to ask

inotify watch failure

Postby w4kh » 2019-11-20 15:51

When up dating/upgrading chrome and teamviewer, I twice got the message:
Code: Select all
Failed to add /run/systemd/ask-password to directory watch: inotify watch limit reached

In the past, I have ignored that warning, but today I wanted to track it down and find out what is actually causing it, what package is "offended", and what potential danger there is to ignoring such a failure warning.
Searching the forums, I found "Best value for max_user_watches" with these two links:
Code: Select all
https://wiki.archlinux.org/index.php/ReadyMedia#Automatic_Media_DB_Update

and
Code: Select all
https://wiki.archlinux.org/index.php/ReadyMedia#Automatic_Media_DB_Update

Apparently I have never added "inotify-tools" to my system, so the related man pages from the bottom of the inotify man page yield no results.
After some study, it appeared that the "solution" offered in the first of the two links might work, so I tried:
Code: Select all
/etc/sysctl.d# sysctl fs.inotify.max_user_watches=65535
fs.inotify.max_user_watches = 65535

and
Code: Select all
cat fs.inotify.max_user_watches=65535 >> /etc/sysctl.d/90-inotify.conf

So, my question holds:
What is actually causing this failure? system? package?
Exactly what package is "offended"?
And, MOST important, what potential danger there is to ignoring such a failure warning?
4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11)
MB: Gigabyte 970A-D3P
CPU: AMD FX-8350 @4000.000 MHz cache: 2048 KB
RAM: 32GB (4x8GB) Unbuffered/Unregistered
LTO-5 SAS Tape on LSI SAS9211 controller
Video: GeForce 8400 GS to VIZIO E320VA
User avatar
w4kh
 
Posts: 83
Joined: 2006-09-09 19:10
Location: Tennessee, USA

Return to General Questions

Who is online

Users browsing this forum: No registered users and 8 guests

fashionable