Yeoman 'grunt test' fails on clean project with 'port already in use'

Posted by XMLilley on Stack Overflow See other posts from Stack Overflow or by XMLilley
Published on 2013-07-01T02:33:23Z Indexed on 2014/08/23 4:20 UTC
Read the original article Hit count: 191

Filed under:
|
|

With:

  • Mac OS 10.8.4
  • Node 0.10.12
  • npm 1.3.1
  • grunt-cli 0.1.9
  • yo 1.0.0-rc.1
  • bower 0.9.2
  • [email protected]

I encounter the following error with a clean yo angular project, followed by grunt server then grunt test:

Running "connect:test" (connect) task  
Fatal error: Port 9000 is already in use by another process.

I'm new to Yeoman and am stumped. I've deleted my original project and created a new one in a fresh folder just to make sure I wasn't overlooking any invisible configs. I restarted the machine to make sure I wasn't running any temporary server processes I had forgotten about. After all attempts, the basic server starts fine, attaches to Chrome, and the watcher updates the browser on any changes. (Notably, the server is running on 9000, which seems odd for the test-runner to also be trying to use 9000.) But I get that same error on attempting to start the test runner.

Is this something I can fix, or an issue I should report to the Yeoman team? Thanks.

© Stack Overflow or respective owner

Related posts about angularjs

Related posts about gruntjs