gatsbyjs / gatsby

The best React-based framework with performance, scalability and security built in.
https://www.gatsbyjs.com
MIT License
55.21k stars 10.33k forks source link

events.js:182 throw er; // Unhandled 'error' event #1767

Closed OleksandrSachuk closed 4 years ago

OleksandrSachuk commented 7 years ago

After command, gatsby develop (npm run develop) I have got an error. Please, help.

Your site is running at http://localhost:8000 I Your graphql debugger is running at http://localhost:8000/___graphql events.js:182 throw er; // Unhandled 'error' event ^

Error: watch /data/home/user/Sasha/Gatsbyjs/node_modules/babel-polyfill/node_modules/core-js/library/fn/array ENOSPC at exports._errnoException (util.js:1024:11) at FSWatcher.start (fs.js:1382:19) at Object.fs.watch (fs.js:1408:11) at createFsWatchInstance (/data/home/user/Sasha/Gatsbyjs/node_modules/chokidar/lib/nodefs-handler.js:37:15) at setFsWatchListener (/data/home/user/Sasha/Gatsbyjs/node_modules/chokidar/lib/nodefs-handler.js:80:15) at FSWatcher.NodeFsHandler._watchWithNodeFs (/data/home/user/Sasha/Gatsbyjs/node_modules/chokidar/lib/nodefs-handler.js:228:14) at FSWatcher.NodeFsHandler._handleDir (/data/home/user/Sasha/Gatsbyjs/node_modules/chokidar/lib/nodefs-handler.js:407:19) at FSWatcher. (/data/home/user/Sasha/Gatsbyjs/node_modules/chokidar/lib/nodefs-handler.js:455:19) at FSWatcher. (/data/home/user/Sasha/Gatsbyjs/node_modules/chokidar/lib/nodefs-handler.js:460:16) at FSReqWrap.oncomplete (fs.js:153:5) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! gatsby-starter-default@1.0.0 develop: gatsby develop npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the gatsby-starter-default@1.0.0 develop script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /data/home/user/.npm/_logs/2017-08-11T06_20_35_175Z-debug.log

eliassotodo commented 7 years ago

I am am having what seems to be the same issue. Any ideas about of what's going on here?

 DONE  Compiled successfully in 317ms                                11:09:48 PM

 I  Your site is running at http://localhost:8000
 I  Your graphql debugger is running at http://localhost:8000/___graphql
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: watch /home/username/_Code/project-dir/node_modules/find-node-modules/test/b/c/d/e/f ENOSPC
    at exports._errnoException (util.js:1020:11)
    at FSWatcher.start (fs.js:1443:19)
    at Object.fs.watch (fs.js:1470:11)
    at createFsWatchInstance (/home/username/_Code/project-dir/node_modules/chokidar/lib/nodefs-handler.js:37:15)
    at setFsWatchListener (/home/username/_Code/project-dir/node_modules/chokidar/lib/nodefs-handler.js:80:15)
    at FSWatcher.NodeFsHandler._watchWithNodeFs (/home/username/_Code/project-dir/node_modules/chokidar/lib/nodefs-handler.js:228:14)
    at FSWatcher.NodeFsHandler._handleDir (/home/username/_Code/project-dir/node_modules/chokidar/lib/nodefs-handler.js:407:19)
    at FSWatcher.<anonymous> (/home/username/_Code/project-dir/node_modules/chokidar/lib/nodefs-handler.js:455:19)
    at FSWatcher.<anonymous> (/home/username/_Code/project-dir/node_modules/chokidar/lib/nodefs-handler.js:460:16)

NOTE:

eliassotodo commented 7 years ago

the old "reboot the system" fixed it...

EDIT: I am having this issue again :/

theangryangel commented 7 years ago

Might want to check out https://github.com/facebook/jest/issues/3254 @sotocodes

kalinchernev commented 6 years ago

I also got error with chokidar and this error code migrating from a hugo site with nested folders in static after forestry handles assets like this. The linux-specific command for fs worked.

shivamlekhi commented 6 years ago

For what it's worth, I ran npm install npm update and it works again.

OmarJaber commented 6 years ago

I have The same error !!

KyleAMathews commented 6 years ago

Closing older issues, please open new issues if you need more help!

hemnathmouli commented 6 years ago

Your site is running at http://localhost:8000 Try changing your port. Like 3000 or 8080.

app.listen(3000)

My 8080 post was taken, so I got this same error

anitahkimanthi commented 6 years ago

i also have the issue with the

events.js:137 throw er; // Unhandled 'error' event

This happens when I try to create-react-app and also I am not able to run react app

rahulbit commented 6 years ago

events.js:167 throw er; // Unhandled 'error' event ^

Error: spawn C:\Program Files\nodejs ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:217:19) at onErrorNT (internal/child_process.js:394:16) at process._tickCallback (internal/process/next_tick.js:174:19) Emitted 'error' event at: at Process.ChildProcess._handle.onexit (internal/child_process.js:223:12) at onErrorNT (internal/child_process.js:394:16) at process._tickCallback (internal/process/next_tick.js:174:19) help me resolve the issue getting this error after running ng new command

mazux commented 6 years ago

Changing the port number worked for me

ghost commented 6 years ago

image

What is this error?!

juliancorrea commented 6 years ago

In my MAC, I ran "killall node" and "yarn start" (or npm start) and everything is fine now.

AliZeynalov commented 6 years ago

@juliancorrea thanks man. executing killall node solved my problem, as well

tallcoder commented 6 years ago

npm install fixed it for me

pzb568 commented 6 years ago

events.js:167 throw er; // Unhandled 'error' event ^

Error: EACCES: permission denied, open '/data/data/com.termux/files/home/hexoproject/source/_posts/科学上网软件ss系列.md' Emitted 'error' event at: at /data/data/com.termux/files/home/hexoproject/node_modules/graceful-fs/graceful-fs.js:190:14 at /data/data/com.termux/files/home/hexoproject/node_modules/graceful-fs/graceful-fs.js:241:16 at FSReqWrap.oncomplete (fs.js:141:20) %

obiha commented 5 years ago

All you have to do is close all other open terminals.

Also in my case I had working through Intellij, and when ever I closed the terminal, i had to make my way back to the folder with the js file.

henriqueslaporta commented 5 years ago

This fix for me:

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

Source: Node.JS Error: ENOSPC

kw3ku commented 5 years ago

if you are on node project, kindly change the port number. if it was port Listen="3004", make it port listing ="3005"

kapomaho commented 5 years ago

After closed the Intellij idea my problem solved.

rmsparajuli commented 5 years ago

image

i got this error , Please help me.

ArunEdathadan commented 5 years ago

Check this ,solved mine https://stackoverflow.com/questions/43931986/how-to-upgrade-angular-cli-to-the-latest-version

jpbbrito commented 5 years ago

@kw3ku be right, in my case used port 80 i changed to 3000 it running normally now.

Jiunsr commented 5 years ago

@kw3ku be right, in my case used port 80 i changed to 3000 it running normally now.

Right!My project port number changed to 3200 just fine. Previously number 9080.

AkankS19 commented 5 years ago

image

i got this error , Please help me.

I am getting the same issue. Did you get any fix for this ?

satyendrakannaujiya commented 5 years ago

This fix for me:

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

Source: Node.JS Error: ENOSPC it works for me also

mdmasumbillah commented 5 years ago

Run killall node and start your app

MarcusWiilo commented 5 years ago

Just change the door, in my case change to 8080 and function

garrettbear commented 5 years ago

I've run into this issue a handful of times and it always leads to something is running on that port. So just make sure to kill the PID running on that port

Find the PID: lsof -i :3000

Kill: kill -9 <PID>

sengbh commented 5 years ago

In my MAC, I ran "killall node" and "yarn start" (or npm start) and everything is fine now.

Yep, it works for me. Thanks, man.

nehakuragayala commented 5 years ago

I have an error while running my react code on visual studio. How do you handle the below error???

events.js:174 throw er; // Unhandled 'error' event ^

Error: listen EACCES: permission denied 127.0.0.1:8080 at Server.setupListenHandle [as _listen2] (net.js:1253:19) at listenInCluster (net.js:1318:12) at GetAddrInfoReqWrap.doListen [as callback] (net.js:1451:7) at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:61:10) Emitted 'error' event at: at emitErrorNT (net.js:1297:8) at process._tickCallback (internal/process/next_tick.js:63:19) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! my-app@1.0.0 start: webpack-dev-server --hot npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the my-app@1.0.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

garrettbear commented 5 years ago

@nehakuragayala could be an error with the npm global config. Take a look at Error: EACCES: permission denied

Primo1991 commented 5 years ago

at linux - sudo npm install then change port, or closing existing server at this port. that how i fixed it

deepkesh26 commented 5 years ago

For what it's worth, I ran npm install npm update and it works again.

I had the same error

ng build --prod && electron .

Date: 2019-04-11T09:37:41.804Z
Hash: 339909bc988fb9628a0e Time: 16126ms chunk {scripts} scripts.5994b0d4263eaf6f8498.bundle.js (scripts) 207 kB [initial] [rendered] chunk {0} main.1eca2b65ad0743f06cc3.bundle.js (main) 867 kB [initial] [rendered] chunk {1} polyfills.1457c99db4b6dba06e8d.bundle.js (polyfills) 59.4 kB [initial] [rendered] chunk {2} styles.67e6dcccd1a619e76bae.bundle.css (styles) 175 kB [initial] [rendered] chunk {3} inline.318b50c57b4eba3d437b.bundle.js (inline) 796 bytes [entry] [rendered] events.js:183 throw er; // Unhandled 'error' event ^

Error: spawn /Users/xx/xx/xx/xx/node_modules/electron/dist/Electron.app/Contents/MacOS/Electron ENOENT at _errnoException (util.js:1024:11) at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19) at onErrorNT (internal/child_process.js:372:16) at _combinedTickCallback (internal/process/next_tick.js:138:11) at process._tickCallback (internal/process/next_tick.js:180:9) at Function.Module.runMain (module.js:678:11) at startup (bootstrap_node.js:187:16) at bootstrap_node.js:608:3

But using npm update and npm install solved my problem Thanks

kanyo33 commented 5 years ago

I have an error while running my react code on visual studio. How do you handle the below error???

events.js:174 throw er; // Unhandled 'error' event ^

Error: listen EACCES: permission denied 127.0.0.1:8080 at Server.setupListenHandle [as _listen2] (net.js:1253:19) at listenInCluster (net.js:1318:12) at GetAddrInfoReqWrap.doListen [as callback] (net.js:1451:7) at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:61:10) Emitted 'error' event at: at emitErrorNT (net.js:1297:8) at process._tickCallback (internal/process/next_tick.js:63:19) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! my-app@1.0.0 start: webpack-dev-server --hot npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the my-app@1.0.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

This might be because your project port number and live-server port number are different

An easier way around this (if you are using vs code) is to install the live server extension After that right click the file you want to open and select 'Open with live server' In my opinion, that's much easier than changing the default port number of every project Hope that helps

gabmen1711 commented 5 years ago

For what it's worth, I ran npm install npm update and it works again.

This one worked for me

chriswang- commented 5 years ago

I run into this issue, It is simply to clean the app/build dir. That will resolve the problem.

sheecegardezi commented 5 years ago

I had another node development server running in another terminal, once I closed that this error was fixed.

taslimy commented 4 years ago

This is happening to me as well any help tried the above solutions I am on windows.

      throw er; // Unhandled 'error' event
      ^

Error: spawn cmd ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
    at onErrorNT (internal/child_process.js:456:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
    at onErrorNT (internal/child_process.js:456:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: 'ENOENT',
  code: 'ENOENT',
  syscall: 'spawn cmd',
  path: 'cmd',
  spawnargs: [ '/c', 'start', '""', '/b', 'http://localhost:3000/' ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-app@0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-app@0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Taslim\AppData\Roaming\npm-cache\_logs\2019-10-24T21_26_11_139Z-debug.log

I fixed my issue on windows by adding C:\Program Files\nodejs && C:\Windows\System32 to my Systems Variables and restarted my VS Code and its working again. Hope this helps anyone.

9717 commented 4 years ago

why this error is happening while running my react code on visual studio

D:\reactapp>npm start npm ERR! code ENOENT npm ERR! syscall open npm ERR! path D:\reactapp\package.json npm ERR! errno -4058 npm ERR! enoent ENOENT: no such file or directory, open 'D:\reactapp\package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\Nandan\AppData\Roaming\npm-cache_logs\2019-10-25T11_01_18_519Z-debug.log

D:\reactapp>

ZoharLiran commented 4 years ago

CHROMEDRIVER_FORCE_DOWNLOAD=true npm install chromedriver fixed it for me. source: https://www.npmjs.com/package/chromedriver

figencetin commented 4 years ago

Because I've run it twice. Make sure you run once

akilljain commented 4 years ago

I am getting the same issue and i could not find any accurate answer plz help me. image

developerdesigner18 commented 4 years ago

Delete node_modules Then run npm install

Worked for me

qxchen6 commented 4 years ago

clear node_modules folder , run yarn again works for me .

khushwantkodecha commented 4 years ago

Your site is running at http://localhost:8000 Try changing your port. Like 3000 or 8080.

app.listen(3000)

My 8080 post was taken, so I got this same error

ehsanasgari commented 4 years ago

Had the same issue! Just run sudo npm start instead of npm start and it worked! ;-)

rahulxyz commented 4 years ago

Due to some reason in my system variables my path was not set. Set this to System variables: %SystemRoot%\system32

In case it doesn't work, try killing your port already under use. (Source) netstat -ano | findstr :yourPortNumber taskkill /PID typeyourPIDhere /F

muqadas12 commented 4 years ago

i am trying to install reactjs but always i got this error .one step before npm start error

muqadas12 commented 4 years ago

error