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

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

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

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

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

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

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

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

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

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

Thanks man , you are a hero

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

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

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

Could you explain ?

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

• su
• enter your password
• npm run serve

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

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

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

Yes It is working

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

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

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

worked too. thanks

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

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

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

@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 🙂

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

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?

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

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:   

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 :raised_hands:

it still happens ... with the quick start guide :eyes:

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.

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

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.

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

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! 💪💜

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.

https://github.com/gatsbyjs/gatsby/issues/11406#issuecomment-458769756

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!

cc https://github.com/gatsbyjs/gatsby/issues/15843#issuecomment-554281918

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

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

delete react node_modules

rm -r node_modules

yarn or npm install

yarn start or npm start

if error occurs use this method again

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

@cedricdelpoux did you solve this error?

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

Using on MacOS

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

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

Is work!!

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

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

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_

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

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

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.

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.

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.

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

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

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

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

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

Thanks, solved

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 :smile:

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

export CHOKIDAR_USEPOLLING=1
worked.

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

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

Thank You so much!!!

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 :+1: to the comment that helped you, if your comment doesn't provide any value for others due to being a thankyou (:tada:) 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".

@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

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.

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

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

thank you sir, it worked. So precise.

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

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

ENOSPC = Erro NO Seu PC
@Victorcorcos

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

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

Works for me! Thankss! :D

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

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

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

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

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

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!

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

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!

thats :-)

John D Allen.

T +1 417 849 0705 * CST | john.[email protected]
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 notifications@github.com 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
https://github.com/gatsbyjs/gatsby/issues/11406#issuecomment-743930745,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADGDUXOKITKKDGQWZ4SNFQ3SUQI7HANCNFSM4GTE6GVA
.