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.

kolibri start command can't detect if the port is not available.

See original GitHub issue

Observed behavior

I have running KA LIte server on port 8008 then I run the kolibri start command at the command prompt and I used the same port 8008 then kolibri say it running on that port but when I check it it’s not, still KA Lite using that port.

Expected behavior

kolibri start command should have an error that the port is not available.

Errors and logs

screen shot 2018-08-24 at 10 53 13 am

Context

Tell us about your environment, including:

Kolibri version: 0.10.1
Operating system: Windows 10
Browser

Issue Analytics

State:
Created 5 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

lyw07commented, Sep 26, 2018

thank you! @mrpau-richard That makes sense to me. I will find ways to let the error show up at the terminal.

0reactions

mrpau-richardcommented, Sep 26, 2018

@lyw07 your right, it did show in log file that the port is not available. But the logs appear only in the server.log not in the kolibri.log. I think, we should propagate those error logs at the command prompt or terminal to notify that the port is not available.

Here are my log files: server.log kolibri.log