question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

No server on port 9100

See original GitHub issue

Hi! 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:closed
  • Created 10 years ago
  • Comments:14 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
cyrusdavidcommented, Nov 2, 2013

Make sure the task isn’t karma:unit:run like what taktran said.

Mine was previously:

grunt.registerTask('default', ['karma:unit:run', 'watch']);

Changed it to:

grunt.registerTask('default', ['karma:unit', 'watch']);

Now everything works nicely with grunt-contrib-watch! 💪

0reactions
geoffreywisemancommented, Nov 27, 2014

@oliamb wrote:

In the server task, you can either run karma:watch or karma:watch:start. The former will run the test at startup while the second will only run the tests after the first file change has been detected.

Your configuration works fine for me, except that both karma:watch and karma:watch:start have the same effect – neither runs the tests at startup. I’d rather run the tests at startup – any further suggestions?

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found