search

remy / nodemon

Monitor for any changes in your node.js application and automatically restart the server - perfect for development
http://nodemon.io/
MIT License
26.24k stars 1.72k forks source link

Not able to start nodemon server: Exception in nodemon killing node #504

Closed rohit13 closed 6 years ago

rohit13 commented 9 years ago

Error:

13 Feb 12:15:50 - [nodemon] v1.3.7 13 Feb 12:15:50 - [nodemon] to restart at any time, enter rs 13 Feb 12:15:50 - [nodemon] watching: . 13 Feb 12:15:50 - [nodemon] starting node C:\mykad\server.js exception in nodemon killing node Error: spawn cmd ENOENT at exports._errnoException (util.js:746:11) at Process.ChildProcess._handle.onexit (child_process.js:1046:32) at child_process.js:1137:20 at process._tickCallback (node.js:355:11)

Output from nodemon --dump:

13 Feb 12:26:44 - [nodemon] v1.3.7 13 Feb 12:26:44 - [nodemon] to restart at any time, enter rs 13 Feb 12:26:44 - [nodemon] watching: .

node: v0.12.0 nodemon: v1.3.7 command: node C:\Users\rohitsha\AppData\Roaming\npm\node_modules\nodemon\bin\nodemon.js --dump cwd: C:\Program Files\nodejs OS: win32 x64

{ run: false, system: { cwd: 'C:\Program Files\nodejs', useFind: false, useWatch: false, useWatchFile: true }, required: false, dirs: [ 'C:\Program Files\nodejs' ], timeout: 1000, options: { dump: true, ignore: [ '.git', 'node_modules', 'bower_components', '.sass-cache', re: /.git|node_modules|bowercomponents|.sass-cache/ ], watch: [ '.', re: /.../ ], restartable: 'rs', execMap: { py: 'python', rb: 'ruby' }, stdin: true, verbose: false, stdout: true, execOptions: { script: null, exec: 'node', args: [], scriptPosition: null, nodeArgs: undefined, ext: 'js', env: {}, execArgs: [] }, monitor: [ '._', '!.git', '!C:\Program Files\nodejs\nodemodules/*/_', '!bower_components', '!.sass-cache' ] }, load: [Function], reset: [Function: reset], lastStarted: 0, loaded: [], command: { raw: { executable: 'node', args: [] }, string: 'node' }, offset: 0 }

rohit13 commented 9 years ago

Why nobody is commenting anything on this issue? Have I missed out on any procedure?

remy commented 9 years ago

Can you share the code or a way to replicate what you're seeing on windows?

gcmicah commented 9 years ago

hello, I'm having the same problem I'm running Win 7 Prof. Any help is appreciated.

C:\nodejs\myRESTAPI>nodemon server.js 25 Mar 13:56:34 - [nodemon] v1.3.7 25 Mar 13:56:34 - [nodemon] to restart at any time, enter rs 25 Mar 13:56:34 - [nodemon] watching: . 25 Mar 13:56:34 - [nodemon] starting node server.js exception in nodemon killing node Error: spawn ENOENT at errnoException (child_process.js:1001:11) at Process.ChildProcess._handle.onexit (child_process.js:792:34)

If appropriate, please file an error with the output from: $ node C:\Users\IBM_ADMIN\AppData\Roaming\npm\node_modules\nodemon\bin\nodemon.j s server.js --dump

At http://github.com/remy/nodemon/issues/new

Here is the dump:

node: v0.10.33 nodemon: v1.3.7 command: node C:\Users\IBM_ADMIN\AppData\Roaming\npm\node_modules\nodemon\bin\no demon.js server.js --dump cwd: C:\nodejs\myRESTAPI

OS: win32 ia32

{ run: false, system: { cwd: 'C:\nodejs\myRESTAPI', useFind: false, useWatch: false, useWatchFile: true }, required: false, dirs: [ 'C:\nodejs\myRESTAPI' ], timeout: 1000, options: { dump: true, ignore: [ '.git', 'node_modules', 'bower_components', '.sass-cache', re: /.git|node_modules|bowercomponents|.sass-cache/ ], watch: [ '.', re: /.../ ], restartable: 'rs', execMap: { py: 'python', rb: 'ruby' }, stdin: true, verbose: false, stdout: true, execOptions: { script: 'server.js', exec: 'node', args: [], scriptPosition: 0, nodeArgs: undefined, ext: 'js', env: {}, execArgs: [] }, monitor: [ '._', '!.git', '!C:\nodejs\myRESTAPI\nodemodules/*/_', '!bower_components', '!.sass-cache' ] }, load: [Function], reset: [Function: reset], lastStarted: 0, loaded: [], command: { raw: { executable: 'node', args: [ 'server.js' ] }, string: 'node server.js' },

offset: 0 }

keberox commented 9 years ago

Hi, I am having the same issue. I am using OS: win32 x64

pretty much the same dumb data as added on previous comments.

I am running an Express app straight out of the WebStorm templates. I can run it well by simply running: node bin/www

the app runs well, but if I run: nodemon bin/www

28 Apr 13:24:18 - [nodemon] starting node bin/www exception in nodemon killing node Error: spawn cmd ENOENT at exports._errnoException (util.js:746:11) at Process.ChildProcess._handle.onexit (child_process.js:1053:32) at child_process.js:1144:20 at process._tickCallback (node.js:355:11)

nodemon is a nice tool, I hope I will get it to work. BTW, same app runs fine on Mac OSx.

Thanks!

keberox commented 9 years ago

So the Code is the Express App template from WebStorm and this is the dump data

node: v0.12.2 nodemon: v1.3.7 command: node C:\node_packages\npm\node_modules\nodemon\bin\nodemon.js bin\www --dump cwd: C:\path-to-code\webServer

OS: win32 x64

{ run: false, system: { cwd: 'C:\path-to-code\webServer', useFind: false, useWatch: false, useWatchFile: true }, required: false, dirs: [ 'C:\path-to-code\webServer' ], timeout: 1000, options: { dump: true, ignore: [ '.git', 'node_modules', 'bower_components', '.sass-cache', re: /.git|node_modules|bowercomponents|.sass-cache/ ], watch: [ '.', re: /.../ ], restartable: 'rs', execMap: { py: 'python', rb: 'ruby' }, stdin: true, verbose: false, stdout: true, execOptions: { script: 'bin\www', exec: 'node', args: [], scriptPosition: 0, nodeArgs: undefined, ext: 'js', env: {}, execArgs: [] }, monitor: [ '._', '!.git', '!C:\path-to-code\webServer\nodemodules/*/_', '!bower_components', '!.sass-cache' ] }, load: [Function], reset: [Function: reset], lastStarted: 0, loaded: [], command: { raw: { executable: 'node', args: [ 'bin\www' ] }, string: 'node bin\www' },

offset: 0 }

rodrigo-barraza commented 9 years ago

Have also been getting these errors no matter what solutions I try to apply online.

C:\dev\monochro.me>nodemon server.coffee --dump 22 May 02:28:41 - [nodemon] v1.3.7 22 May 02:28:41 - [nodemon] to restart at any time, enter rs

22 May 02:28:41 - [nodemon] watching: .

node: v0.10.32 nodemon: v1.3.7 command: node C:\Users\Rodrigo\AppData\Roaming\npm\node_modules\nodemon\bin\nodemon.js server.coffee --dump cwd: C:\dev\monochro.me

OS: win32 x64

{ run: false, system: { cwd: 'C:\dev\monochro.me', useFind: false, useWatch: false, useWatchFile: true }, required: false, dirs: [ 'C:\dev\monochro.me' ], timeout: 1000, options: { dump: true, execMap: { coffee: 'node_modules/.bin/coffee', py: 'python', rb: 'ruby' }, ignore: [ '.git', 'node_modules', 'bower_components', '.sass-cache', re: /.git|node_modules|bowercomponents|.sass-cache/ ], watch: [ '.', re: /..._/ ], restartable: 'rs', stdin: true, verbose: false, stdout: true, execOptions: { script: 'server.coffee', exec: 'nodemodules/.bin/coffee', args: [], scriptPosition: 0, nodeArgs: undefined, ext: 'coffee', env: {}, execArgs: [] }, monitor: [ '._', '!C:\dev\monochro.me.git/*/', '!C:\dev\monochro.me\nodemodules/**/', '!C:\dev\monochro.me\bower_components/_/', '!.sass-cache' ] }, load: [Function], reset: [Function: reset], lastStarted: 0, loaded: [ 'C:\dev\monochro.me\nodemon.json' ], command: { raw: { executable: 'node_modules/.bin/coffee', args: [ 'server.coffee' ] }, string: 'node_modules/.bin/coffee server.coffee' },

offset: 0 }

creeperyang commented 9 years ago

Wow, same problem in win7. Everything is ok with osx.

3masks commented 7 years ago

this helped me https://github.com/remy/nodemon/issues/616

peter73ru commented 7 years ago

The same problem but I can't solve it with #616.

stale[bot] commented 6 years ago

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up. Thank you for contributing <3