No server on port 9100
See original GitHub issueHi! I’m getting this error while trying to run karma with grunt-karma
:
Running tasks: karma:unit:run
Running "karma:unit:run" (karma) task
Verifying property karma.unit exists in config...OK
File: [no files]
There is no server listening on port 9100
Seems like grunt-karma
doesn’t start server. While default command does:
karma start karma.conf.coffee
Here is part of grunt
config:
karma:
options:
configFile: 'karma.conf.coffee'
background: true
unit: {}
unit_all:
browsers: ['PhantomJS', 'Chrome', 'Firefox']
I’m 0.9.5
Issue Analytics
- State:
- Created 10 years ago
- Comments:14 (2 by maintainers)
Top Results From Across the Web
Wide Format - Unable to bind the TCP port 9100 server
Error message stating the inability to bind to port 9100, either port is consumed or blocked.
Read more >Enable and Configure Raw TCP/IP Printing (Port 9100)
In the Embedded Web Server, click Connectivity > Port Settings. · For Port 9100, select Enabled. · Click Apply.
Read more >Configure Port 9100 - Fiery Help and Documentation
From Configure, choose Network > Services > Port 9100. Note: If you are connected to a Fiery Server with FS150/150Pro, click Job Submission...
Read more >Port 9100 printing - Hacking Printers
Raw port 9100 printing, also referred to as JetDirect, AppSocket or PDL-datastream actually is not a printing protocol by itself.
Read more >For Network Connection (LPR/Port ... - Konica Minolta Manuals
In Windows 8/Server 2012, you can install the printer driver either by searching for the printer on the network, or by creating a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Make sure the task isn’t
karma:unit:run
like what taktran said.Mine was previously:
Changed it to:
Now everything works nicely with
grunt-contrib-watch
! 💪@oliamb wrote:
Your configuration works fine for me, except that both
karma:watch
andkarma:watch:start
have the same effect – neither runs the tests at startup. I’d rather run the tests at startup – any further suggestions?