karma: Karma doesn't start server in browsers

I’m having a problem where karma never actually starts the server. It seems to start the browsers, but never the server. I’ve tested in Chrome, and after it’s launched the http://localhost:9876/ never loads. Running on windows 8, and node 0.10.33

The weird part is, I have the same exact configuration for grunt-karma, and it works no problem.

I get the error below:

INFO [karma]: Karma v0.12.28 server started at http://localhost:9876/
INFO [launcher]: Starting browser PhantomJS
INFO [launcher]: Starting browser Chrome
WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.
WARN [launcher]: Chrome have not captured in 60000 ms, killing.
WARN [launcher]: PhantomJS was not killed in 2000 ms, sending SIGKILL
WARN [launcher]: Chrome was not killed in 2000 ms, sending SIGKILL.

Here is my package.json for karma

"karma": "^0.12.3",
"karma-chrome-launcher": "^0.1.3",
"karma-coverage": "^0.2.1",
"karma-jasmine": "^0.1.5",
"karma-ng-html2js-preprocessor": "^0.1.0",
"karma-phantomjs-launcher": "^0.1.4",

About this issue

Original URL
State: closed
Created 10 years ago
Comments: 30 (6 by maintainers)

Most upvoted comments

I’m having the same issue on debian:

06 04 2016 14:30:43.056:WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.
06 04 2016 14:30:45.062:WARN [launcher]: PhantomJS was not killed in 2000 ms, sending SIGKILL.
06 04 2016 14:30:47.068:WARN [launcher]: PhantomJS was not killed by SIGKILL in 2000 ms, continuing.

Did anyone solve this?

+32

nicopeeters on Apr 6, 2016

I encountered the same issue. What helped me:

Remove node_modules folder completely.
Run npm install.

Apparently karma files got corrupted and couldn’t be fixed automatically.

ivanyurchenko1 on May 27, 2020