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

[mrpau-richard]

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

Context

Tell us about your environment, including:

• Kolibri version: 0.10.1
• Operating system: Windows 10
• Browser

[benjaoming]

This should be addressed in #3285

[indirectlylit]

also related and targeted to 0.11.0: #1707

[benjaoming]

@indirectlylit this was previously fixed in #3048, so the issue is a regression in 0.10 - not sure when, why etc :)

[lyw07]

@mrpau-richard Hi! I'm wondering if you still have the kolibri.log file when this error happened. Thank you! My guess is that it detected the port was not available, but the error went to the log file, since the program checks the port availability right before the server starts.

[mrpau-richard]

@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

[lyw07]

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