Error: ENOSPC: System limit for number of file watchers reached, watch '/home/foldername/abcrypto/static'

Question

Error: ENOSPC: System limit for number of file watchers reached, watch '/home/foldername/abcrypto/static'

omrllm opened this issue 5 years ago · 107 comments

Description

The web app compiles but when I reload the website, the compilation end with an error.

Steps to reproduce

Just type gatsby develop and if you click an article for example or you reload (ctrl + r) the website compilation will end.

Repo: There you go.

Expected result

gatsby develop should work.

Actual result

success open and validate gatsby-configs — 0.015 s
success load plugins — 0.382 s
success onPreInit — 0.606 s
success delete html and css files from previous builds — 0.133 s
success initialize cache — 0.013 s
success copy gatsby files — 0.052 s
success onPreBootstrap — 0.006 s
success source and transform nodes — 0.164 s
success building schema — 0.393 s
success createPages — 0.086 s
success createPagesStatefully — 0.072 s
success onPreExtractQueries — 0.006 s
success update schema — 0.224 s
success extract queries from components — 0.216 s
success run graphql queries — 0.164 s — 14/14 88.14 queries/second
success write out page data — 0.004 s
success write out redirect data — 0.001 s
⢀ onPostBootstrapdone generating icons for manifest
success onPostBootstrap — 0.274 s

info bootstrap finished - 4.655 s

 DONE  Compiled successfully in 1926ms                                                                                                               1:43:58 AM


You can now view abcrypto in the browser.

  http://localhost:8000/

View GraphiQL, an in-browser IDE, to explore your site's data and schema

  http://localhost:8000/___graphql

Note that the development build is not optimized.
To create a production build, use gatsby build

ℹ ｢wdm｣:
ℹ ｢wdm｣: Compiled successfully.
error UNHANDLED EXCEPTION


  Error: ENOSPC: System limit for number of file watchers reached, watch '/home/foldername/abcrypto/static'

  - watchers.js:165 FSWatcher.start
    internal/fs/watchers.js:165:26

  - nodefs-handler.js:37 createFsWatchInstance
    [abcrypto]/[chokidar]/lib/nodefs-handler.js:37:15

  - nodefs-handler.js:80 setFsWatchListener
    [abcrypto]/[chokidar]/lib/nodefs-handler.js:80:15

  - nodefs-handler.js:232 FSWatcher.NodeFsHandler._watchWithNodeFs
    [abcrypto]/[chokidar]/lib/nodefs-handler.js:232:14

  - nodefs-handler.js:414 FSWatcher.NodeFsHandler._handleDir
    [abcrypto]/[chokidar]/lib/nodefs-handler.js:414:19

  - nodefs-handler.js:462 FSWatcher.<anonymous>
    [abcrypto]/[chokidar]/lib/nodefs-handler.js:462:19

  - nodefs-handler.js:467 FSWatcher.<anonymous>
    [abcrypto]/[chokidar]/lib/nodefs-handler.js:467:16

Environment

System:
    OS: Linux 4.20 Fedora 29 (Workstation Edition) 29 (Workstation Edition)
    CPU: (4) x64 Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
    Shell: 4.4.23 - /bin/bash
  Binaries:
    Node: 11.3.0 - ~/.nvm/versions/node/v11.3.0/bin/node
    Yarn: 1.12.3 - /var/lib/snapd/snap/bin/yarn
    npm: 6.7.0 - ~/.nvm/versions/node/v11.3.0/bin/npm
  Languages:
    Python: 2.7.15 - /usr/bin/python
  Browsers:
    Firefox: 64.0.2
  npmPackages:
    gatsby: ^2.0.104 => 2.0.104
    gatsby-cli: ^2.4.8 => 2.4.8
    gatsby-image: ^2.0.29 => 2.0.29
    gatsby-plugin-catch-links: ^2.0.9 => 2.0.9
    gatsby-plugin-feed: ^2.0.12 => 2.0.12
    gatsby-plugin-google-analytics: ^2.0.12 => 2.0.12
    gatsby-plugin-manifest: ^2.0.14 => 2.0.14
    gatsby-plugin-offline: ^2.0.22 => 2.0.22
    gatsby-plugin-react-helmet: ^3.0.0 => 3.0.5
    gatsby-plugin-sharp: ^2.0.18 => 2.0.18
    gatsby-plugin-typography: ^2.2.6 => 2.2.6
    gatsby-remark-copy-linked-files: ^2.0.5 => 2.0.8
    gatsby-remark-images: ^2.0.4 => 2.0.6
    gatsby-remark-prismjs: ^3.2.3 => 3.2.3
    gatsby-remark-responsive-iframe: ^2.0.5 => 2.0.8
    gatsby-remark-smartypants: ^2.0.5 => 2.0.7
    gatsby-source-filesystem: ^2.0.18 => 2.0.18
    gatsby-transformer-remark: ^2.2.2 => 2.2.2
    gatsby-transformer-sharp: ^2.1.12 => 2.1.12
  npmGlobalPackages:
    gatsby-cli: 2.4.8
    gatsby: 2.0.98

Answer 1 · 2019-01-30T01:01:07.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Answer 2 · 2019-01-30T15:17:51.000Z

Alright I restarted the computer, and now everything works fine again.

Answer 3 · 2019-04-04T10:57:38.000Z

I solved this way
https://code.visualstudio.com/docs/setup/linux
"Visual Studio Code is unable to watch for file changes in this large workspace" (error ENOSPC)#

cat /proc/sys/fs/inotify/max_user_watches

fs.inotify.max_user_watches=524288

Answer 4 · 2019-04-21T15:25:23.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

thank you very much!!!

Answer 5 · 2019-04-21T20:08:13.000Z

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
worked

Answer 6 · 2019-04-26T12:31:46.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

it saved my day

Answer 7 · 2019-05-17T18:44:44.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

I ran this line of code in a react-app and everything went back to normal again, thanks!!

Answer 8 · 2019-05-30T03:32:25.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

thanks. it's really helpfull

Answer 9 · 2019-06-26T12:30:08.000Z

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Thanks man , you are a hero

Answer 10 · 2019-07-08T08:23:07.000Z

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Give me the error:
sysctl: illegal option -- p

Using on MacOS

Answer 11 · 2019-07-11T09:17:16.000Z

Serve your app as root.....It's work!

Answer 12 · 2019-07-15T07:20:21.000Z

Serve your app as root.....It's work!

Could you explain ?

Answer 13 · 2019-07-15T08:01:57.000Z

Run sudo npm run serve inside you app folder or run this commands as below:

su
enter your password
npm run serve

Answer 14 · 2019-07-17T09:49:09.000Z

Noooooooo don't run your app as root! 💀 🚨 That can cause all kinds of security problems!

Answer 15 · 2019-07-27T04:17:23.000Z

What if I deploy to netlify and encounter that error when netlify tries to build the app? On local it's fine

Answer 16 · 2019-07-30T12:38:34.000Z

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
worked

Yes It is working

Answer 17 · 2019-07-31T06:18:10.000Z

I'm getting this error on Netlify.
Anyone know how to fix it?

Answer 18 · 2019-08-02T01:14:59.000Z

I got it today too and did a "clear cache and redeploy" and it worked.

Answer 19 · 2019-08-08T09:54:22.000Z

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
worked

worked too. thanks

Answer 20 · 2019-08-11T23:41:56.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Reopening this since it looks the above is a popular answer and that this issue is prevalent enough to warrant better resources/warnings on

We should do two things for now:

Add the quoted answer in documentation
Investigate how to catch this in Gatsby and add a more helpful error that enables the user to resolve this themselves

Answer 21 · 2019-08-12T01:53:25.000Z

@sidharthachatterjee where exactly do you see this quoted in the documentation, what page? 🤔

Answer 22 · 2019-08-12T07:45:58.000Z

@sidharthachatterjee, is this taken ? If not, I can take it up, but definitely need your help. :D

Answer 23 · 2019-08-12T10:44:26.000Z

@eduarmreyes That's a very good question! Perhaps a new page linked to in https://www.gatsbyjs.org/docs/debugging/

@KirankumarAmbati If @eduarmreyes is taking up the documentation you could try out the second point in the list! Happy to help 🙂

Answer 24 · 2019-08-12T13:26:18.000Z

I'm currently working on this. @sidharthachatterjee I'm unable to assign or add labels. Thanks for your help!

Answer 25 · 2019-08-17T01:09:50.000Z

I still get this occasionally on Netlify with gatsby build, even through my project is fairly small. It's difficult to debug, because it doesn't occur every time. Clearing the cache & redeploying will fix it, but also, just a normal re-deploy will often work.

There's no sudo access during netlify builds, so changing the system limit isn't an option. Also, manually re-deploying isn't a real "solution" - I have client websites that rebuild after CMS changes, and I don't want to be 'on call' to click the 'redeploy + clear cache' button whenever this happens.

Is there a way to see and/or limit what files are being watched? I don't know much about how Gatsby works under the hood, but, assuming that gatsby watches files in order to re-build while developing, does gatsby build really need to be watching anything in the first place?

Answer 26 · 2019-08-18T03:58:33.000Z

It's work fine for me !
Thanks very much !

Answer 27 · 2019-08-22T08:17:57.000Z

I still get this issue with Gatsby 2.13.73, and as @good-idea wrote, manually re-deploying is not a viable long term solution especially when making websites for clients with CMS.
Why do files even need to be "watched" when building for production?

8:10:54 AM: error watch /opt/build/repo/gatsby-config.js ENOSPC
8:10:54 AM: UNHANDLED EXCEPTION watch /opt/build/repo/gatsby-config.js ENOSPC
8:10:54 AM: See our docs page for more info on this error: https://gatsby.dev/issue-how-to
8:10:54 AM: 
8:10:54 AM:   Error: watch /opt/build/repo/gatsby-config.js ENOSPC
8:10:54 AM:   
8:10:54 AM:   - nodefs-handler.js:38 createFsWatchInstance
8:10:54 AM:     [repo]/[chokidar]/lib/nodefs-handler.js:38:15
8:10:54 AM:   
8:10:54 AM:   - nodefs-handler.js:81 setFsWatchListener
8:10:54 AM:     [repo]/[chokidar]/lib/nodefs-handler.js:81:15
8:10:54 AM:   
8:10:54 AM:   - nodefs-handler.js:233 FSWatcher.NodeFsHandler._watchWithNodeFs
8:10:54 AM:     [repo]/[chokidar]/lib/nodefs-handler.js:233:14
8:10:54 AM:   
8:10:54 AM:   - nodefs-handler.js:262 FSWatcher.NodeFsHandler._handleFile
8:10:54 AM:     [repo]/[chokidar]/lib/nodefs-handler.js:262:21
8:10:54 AM:   
8:10:54 AM:   - nodefs-handler.js:495 FSWatcher.<anonymous>
8:10:54 AM:     [repo]/[chokidar]/lib/nodefs-handler.js:495:21
8:10:54 AM:

Answer 28 · 2019-08-29T11:35:33.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Thanks man! it saved my time 🙌

Answer 29 · 2019-09-06T23:07:30.000Z

it still happens ... with the quick start guide 👀

Answer 30 · 2019-09-09T09:57:23.000Z

Note that @pieh answered the question of "why do files need to be watched while building for production?" over in #15843:

Because used package for globbing + watching (chokidar) doesn't have way to disable watching. We were looking for alternatives, but there were none that actually allow to disable watching. We could use different packages for builds (so only globbing, without watching) and develop (globbing + watching) - but this introduce potential to cause differences between builds and develop

Looks like this issue should be taken up with chokidar first to add a watch option, then a followup issue created for Gatsby to implement the watch option.

Answer 31 · 2019-09-09T12:29:30.000Z

thank you so much!! It worked for me :D

Answer 32 · 2019-09-09T15:13:20.000Z

Also, chokidar isn't going to add an option to disable watching, since it's literally a file watcher. The only possible solution I can think of would be for Gatsby to switch to a different library for traversing directories that allows both watch and non-watch options.

Answer 33 · 2019-09-26T14:20:01.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Dang Sid beat me to the punch i was ganna say this yea it has to do with (Im assuming your on linux) how linux has there default setup of file watchers its an easy fix just by running that command in terminal or you can go here https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc on VS Code website they have a whole section on it teaching you how to solve this issue

Answer 34 · 2019-10-17T17:27:34.000Z

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

Answer 35 · 2019-10-24T21:49:54.000Z

Hello! Any updates on this issue? I encounter this occasionally when building my gatsby site in Jenkins. I don't have permissions to the modify the inotify max_user_watches in my Jenkins build environment.

Answer 36 · 2019-11-02T06:23:16.000Z

#11406 (comment)

Answer 37 · 2019-11-13T17:27:35.000Z

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community!

Answer 38 · 2019-11-15T09:57:11.000Z

cc #15843 (comment)

Answer 39 · 2019-12-14T20:01:57.000Z

@ethannkschneider I was running into this problem when building in a restrictive Jenkins environment as well. Using CHOKIDAR_USEPOLLING=1 avoids hitting the watched limit for me.

Answer 40 · 2019-12-17T13:11:57.000Z

Following is the best solution.
Hit the command - echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Answer 41 · 2020-01-29T23:58:35.000Z

delete react node_modules

rm -r node_modules

yarn or npm install

yarn start or npm start

if error occurs use this method again

Answer 42 · 2020-02-14T13:49:16.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Tks!!!

Answer 43 · 2020-02-26T11:01:53.000Z

@cedricdelpoux did you solve this error?

Give me the error:
sysctl: illegal option -- p

Using on MacOS

Answer 44 · 2020-03-01T08:56:05.000Z

got the same issue:
solved with: increasing users.
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Answer 45 · 2020-03-21T02:56:24.000Z

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Is work!!

Answer 46 · 2020-04-01T17:11:16.000Z

@irokhes sysctl -p is used to reload the changed config from /etc/sysctl.conf on Linux. You will have to find out how to change sysctl.conf (probably located somewhere else) on Mac. Then you can change the fs.inotify.max_user_watches-property (if it is called the same on Mac).

Answer 47 · 2020-04-05T07:05:29.000Z

I just had to close Visual Studio Code and that solved the problem.

Answer 48 · 2020-04-09T00:23:22.000Z

If you are not interested in the technical details and only want to get Listen to work:

If you are running Debian, RedHat, or another similar Linux distribution, run the following in a terminal:

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

If you are running ArchLinux, run the following command instead (see here for why):

echo fs.inotify.max_user_watches=524288 | sudo tee /etc/sysctl.d/40-max-user-watches.conf && sudo sysctl --system

Then paste it in your terminal and press on enter to run it.

More info: https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers

Answer 49 · 2020-04-23T11:32:04.000Z

Alright I restarted the computer, and now everything works fine again.

Thanks! It the computer's way of saying "restart me"

Answer 50 · 2020-04-24T12:01:32.000Z

This is happening here in Travis too, I think the crux of the issue is it's watching /static. Even if it has to run chokidar in build mode, if we could pass a watch ignore pattern, we could ignore folders like static. Unless doing so would prevent it from copying to build? 🤔 Using CHOKIDAR_USEPOLLING=1 seems to help.

Answer 51 · 2020-04-27T14:51:24.000Z

I followed the 'fix' to set max watchers to 524288, rebooting, none of it fixed the issue. I'm sure it helped, but I was still experiencing this issue.

I added the environment variable using:

export CHOKIDAR_USEPOLLING=1

And that helped. I was able to run gatsby develop on my site.

Answer 52 · 2020-04-28T14:30:50.000Z

That's what I meant in my last post. I tried that exact command and it did not work. I'm running Ubuntu 18.04. However, running that command, rebooting, then changing the CHOKIDAR_USEPOLLING environment variable worked.

Answer 53 · 2020-04-29T06:42:20.000Z

Same for me.
Combination of fs.inotify.max_user_watches=524288 in /etc/sysctl.conf and command

CHOKIDAR_USEPOLLING=1 node --max_old_space_size=4096 ./node_modules/.bin/gatsby develop -S

works but not at all the time, sometimes computer restart is need.
So this issue has not been solved yet.

OS: macOS Catalina 10.15.4
CPU: Intel i7-4750HQ (8) @ 2.00GHz
Memory: 8192MiB

Gatsby CLI version: 2.11.5
Gatsby version: 2.20.12
Node: v13.12.0

Answer 54 · 2020-04-30T04:15:08.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

save my day, thanks!!

Answer 55 · 2020-05-17T01:07:02.000Z

instead of increase max_user_watches, webpack watcher should not watch 1 million file inside node_modules!

Answer 56 · 2020-05-18T14:18:03.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Thanks,

Answer 57 · 2020-05-22T15:07:18.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

This worked for me

Answer 58 · 2020-05-26T14:26:34.000Z

Está atingindo o limite de observadores de arquivos do seu sistema
Tentar echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
Leia mais sobre o que está acontecendo em https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Muito obrigado!!!

Answer 59 · 2020-05-26T14:27:36.000Z

Thanks, solved

Answer 60 · 2020-05-28T16:06:09.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Thanks 😄

Answer 61 · 2020-05-30T15:17:42.000Z

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
worked

Thanks this works on Ubuntu 18.04 LTS

Answer 62 · 2020-06-12T20:00:38.000Z

export CHOKIDAR_USEPOLLING=1
worked.

Answer 63 · 2020-06-14T21:35:46.000Z

Please just add a reaction to the solution that worked for you, rather than making a new comment that just says "worked for me".

Answer 64 · 2020-06-15T10:08:09.000Z

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p``

Thank You so much!!!

Answer 65 · 2020-06-15T12:15:49.000Z

If anyone was curious about the numbers and overhead, I ended up looking into it a bit rather than just copying what appears like random numbers online and hoping for the best :P

The 524288 mentioned here and some other places from the guard/listen wiki (seems to be original source?), is 2^19 (exponent, as in 2x2x2x2..19 times), where each watch(only when actually used) requires 1,080 bytes of memory, meaning you would use 540MiB of RAM if you managed to use all those, just for the file watchers.

There's also this handy script, which can tell you where all the watchers are allocated to presently. In my case I had been using a max_user_watches of 2^16 (65536) and two electron processes(VS Code) had 24-28k watches each active, a few others had a few thousand each, and minor watches for everything else.

@x0xl0ma in future just add a 👍 to the comment that helped you, if your comment doesn't provide any value for others due to being a thankyou (🎉) or repeating confirmation, it just adds noise that others have to wade through (notice that Github hides 30+ comments on this thread as an optimization, that can hide good/useful information that might be missed in a sea of "thanks" and "works".

Answer 66 · 2020-06-18T01:35:39.000Z

@omrllm

Alright I restarted the computer, and now everything works fine again.

in reality when you

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

you didn't had to restart your computer since sudo sysctl -p reload and apply system parameters to the current system

Answer 67 · 2020-06-28T11:47:49.000Z

Error: ENOSPC: System limit for number of file watchers reached,

I am having this issue

Tried
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
but didn't work for me.

Answer 68 · 2020-08-04T14:19:47.000Z

Error: ENOSPC: System limit for number of file watchers reached

I am facing this issue when i started my React app for next time

Please try with this below code:- (in your terminal)

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Answer 69 · 2020-08-11T19:46:56.000Z

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
worked

thank you sir, it worked. So precise.

Answer 70 · 2020-08-20T19:14:45.000Z

Alternative solution for vscode:

Instead of increasing limits you could also add public and .cache folders to files.watcherExclude

"files.watcherExclude": {
    "**/public/**": true,
    "**/.cache/**": true
}

or

via https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc

Answer 71 · 2020-08-25T17:42:27.000Z

It’s hitting your system's file watchers limit
Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

thank you very much!!!

Thank you for providing the right issue where we should looked for in!!!

Answer 72 · 2020-08-26T18:38:07.000Z

ENOSPC = Erro NO Seu PC
@Victorcorcos

Answer 73 · 2020-08-31T18:34:36.000Z

Instead of allowing Webpack to watch half a million files in node_modules (which you are never going to change), you can tell it ignore certain directories, like node_modules: https://webpack.js.org/configuration/watch/#watchoptionsignored

Answer 74 · 2020-09-17T14:20:00.000Z

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Works for me! Thankss! :D

Answer 75 · 2020-09-28T13:59:06.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

tanks!!!

Answer 76 · 2020-09-29T12:55:13.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Thank you very match :), why does this setting have that low number of file watchers by default? mmm

Answer 77 · 2020-10-28T14:12:11.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

thankss!!

Answer 78 · 2020-11-02T20:40:22.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Work fiine, thank's !!!

Answer 79 · 2020-11-14T20:00:14.000Z

yes something to do with atom also.. when atom open in my gatsby directory.. hangs onto the file
close atom.. all coolio

Answer 80 · 2020-11-16T00:43:20.000Z

Está atingindo o limite de observadores de arquivos do seu sistema

Tentar echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Leia mais sobre o que está acontecendo em https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Resolveu muito mais do que esperava!

Answer 81 · 2020-12-07T05:57:29.000Z

In ubuntu you can do the following steps
###sudo vim /etc/sysctl.conf
add the line
###fs.inotify.max_user_watches=524288
save the file .
###npm start

this should work
Thanks

Answer 82 · 2020-12-13T01:18:29.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Gracias crack, leyenda, titán!

Answer 83 · 2020-12-13T18:58:18.000Z

thats :-) *John D Allen.* *T +1 417 849 0705 ** CST | john.allen@leveridgesystems.com <john.allen@leveridgesystems.com> | https://www.leveridgesystems.com <https://www.leveridgesystems.com> | linkedin.com/in/johndallen1 <http://linkedin.com/in/johndallen1> | skype john.allen_67 * Leveridge Systems INC. Reg Missouri Charter #01082460. The information contained in this email and any attached files is confidential and intended solely for the addressee(s). The email may be legally privileged or prohibited from disclosure and unauthorized use. If you are not the named addressee you may not use, copy, or disclose this information to any other person. If you received this message in error please notify the sender immediately and permanently delete it from your system.

…

On Sat, Dec 12, 2020 at 7:18 PM xlegolaz ***@***.***> wrote: It’s hitting your system's file watchers limit Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details Gracias crack, leyenda, titán! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#11406 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGDUXOKITKKDGQWZ4SNFQ3SUQI7HANCNFSM4GTE6GVA> .

Answer 84 · 2021-03-20T09:28:52.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Works for me. Thank you :D

Answer 85 · 2021-03-20T12:23:45.000Z

yes .. thanks indeed Aleks for the kind attention to this. I'll close it out.. very best ! cheers. *John D Allen.* *T +1 417 849 0705 ** CST | ***@***.*** ***@***.***> | https://www.leveridgesystems.com <https://www.leveridgesystems.com> | linkedin.com/in/johndallen1 <http://linkedin.com/in/johndallen1> | skype john.allen_67 * Leveridge Systems INC. Reg Missouri Charter #01082460. The information contained in this email and any attached files is confidential and intended solely for the addressee(s). The email may be legally privileged or prohibited from disclosure and unauthorized use. If you are not the named addressee you may not use, copy, or disclose this information to any other person. If you received this message in error please notify the sender immediately and permanently delete it from your system.

…

On Sat, Mar 20, 2021 at 4:29 AM Aleksandar Gocanin ***@***.***> wrote: It’s hitting your system's file watchers limit Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details Works for me. Thank you :D — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#11406 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGDUXO3C6XAMVBYPBTPNILTERTGLANCNFSM4GTE6GVA> .

Answer 86 · 2021-04-25T10:10:15.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Thanks mate, it saved my day!

Answer 87 · 2021-04-26T11:40:06.000Z

It’s hitting your system's file watchers limit
Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

thank you very much!!!

Answer 88 · 2021-06-10T22:46:21.000Z

There is a shortcut to setting this parameter. This accomplishes the same thing as the top voted answer:

sudo sysctl fs.inotify.max_user_watches=524288

Answer 89 · 2021-06-11T13:28:23.000Z

Thanks smac.. u guys rock

Answer 90 · 2021-07-20T15:50:09.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Worked for me, thank so much!

Answer 91 · 2021-11-04T03:32:41.000Z

Error: ENOSPC: System limit for number of file watchers reached,

I am having this issue

Tried echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p but didn't work for me.

Using the sysctl -p approach after setting fs.inotify.max_user_watches did not work for me , either. (by the way this setting was already set to a high value, likely from me trying to fix this issue a while back ago).

The best solution to the problem I found here:

Use this script to identify which processes are requiring the most file watchers in your session.
You can then query the current max_user_watches value with sysctl fs.inotify.{max_queued_events,max_user_instances,max_user_watches} and then set it to a different value (a lower value may do it)
sudo sysctl -w fs.inotify.max_user_watches=16384
Or you can simply kill the process you found in (1) that consumes the most file watchers (in my case, baloo_file)
The above, however, will likely need to be done again when restarting the system - the process we identified as responsible for taking much of the file watchers will (in my case - baloo_file) - will again so the same in the next boot. So to permanently fix the issue - either disable or remove this service/package. I disabled it: balooctl disable.

Now run sudo code --user-data-dir and it should open vscode with admin privileges this time. (by the way when it does not run sudo code --user-data-dir --verbose to see what the problem is - that's how I figured out it had to do with file watchers limit).

Answer 92 · 2021-12-17T06:43:12.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Its working

Answer 93 · 2022-01-04T09:11:03.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Worked for me, Linux OS

Answer 94 · 2022-01-06T09:22:37.000Z

Alternative solution for vscode:

Instead of increasing limits you could also add public and .cache folders to files.watcherExclude
"files.watcherExclude": {
    "**/public/**": true,
    "**/.cache/**": true
}
or

via https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc

This is the actual solution in my case. It turned out that my watcher exclude pattern had an error. It excluded **/node_modules/*/** instead of **/node_modules/**.

Increasing the system's fs.inotify.max_user_watches only helped counter the symptoms of this error, and didn't help any more when even more folders were added to node_modules.

Answer 95 · 2022-01-06T11:43:18.000Z

via https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc
Link does not look right.

Answer 96 · 2022-01-06T12:05:29.000Z

via https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc
Link does not look right.

I just quote-replied and referenced an answer higher up in the conversation.

Answer 97 · 2022-07-11T23:36:54.000Z

I'm running into this issue on Google Kubernetes Engine (GKE) because you don't appear to have the ability to increase the default fs.inotify.max_user_watches.

Answer 98 · 2022-10-07T09:28:37.000Z

Please stop telling people to increase the user watches to such a ridiculously high number. The default value is 8192 for a reason. Each watch consumes 1080 bytes of kernel memory on a 64-bit system. Setting the limit to such a high number would allow EACH USER on the system to potentially allocate number of watches * 1080 bytes of memory.

Tell them to increase the value in small steps until things start to work.

Answer 99 · 2022-10-22T12:34:20.000Z

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

thanks mate, you are a hero

Answer 100 · 2023-01-10T09:44:11.000Z

If you are getting this error because you are working on a REACT/STRAPI or NODE or something related to javascript and react vis Ubuntu then below will help you.

run this on your terminal

sudo gedit /etc/sysctl.conf

Add a line at the bottom

fs.inotify.max_user_watches=524288

Then save and exit!

sudo sysctl -p

to check it

Then it is solved!

Description

Steps to reproduce

Expected result

Actual result

Environment

If you are getting this error because you are working on a REACT/STRAPI or NODE or something related to javascript and react vis Ubuntu then below will help you.

run this on your terminal

Add a line at the bottom

Then save and exit!

to check it

go back to your VS-CODE or any IDE you are using and run your code again