Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

inotify watch failure

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
User avatar
w4kh
Posts: 98
Joined: 2006-09-09 19:10
Location: Alabama, USA

inotify watch failure

#1 Post by w4kh »

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-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1
CPU: AMD FX(tm)-8350 Eight-Core Processor
RAM: 32GB (8x8GB) DDR3 DRAM
Video: GeForce 8400 GS to VIZIO E320VA Monitor

Post Reply