Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Getting unexpected error and KA lite does not start up - Version 0.16.5 #5132
We want to start KA lite on port 9500 and we are using the following command:
We encounter this problem very frequently, but other wise the same command works and KA lite starts up.
What is the work around and how to fix this problem and get KA lite working?
Branch or installer method
OS: Ubuntu version 14.04 LTS
Traceback or relevant snippet from server.log
How to reproduce
This will have an huge impact since we have to deployment for 6000+ students on 15th June and if KA lite does not start up then it might cause a huge setback in classrooms.
That's interesting. The
@harishbalachandran thanks for the report!
I haven't encountered this issue before, but my theory judging from the traceback is this:
When KA Lite starts, it maintains its "process ID" in a file. That way, we know which process is currently running if KA Lite is running. The file is located in
After this, everything should be fine, and the KA Lite daemon (server) starts.
It seems, however, that an uncaught
Thanks for reporting!
Thanks also for the suggestion @quozl however it should be noted that there isn't a significant difference between the PIP and .deb/PPA distributions, all of this is tightly sync'ed, and latest releases are the same. Major differences exist in the ka-lite-raspberry-pi debian build's behaviour, but the others are fairly aligned.
added a commit
Jun 4, 2016
referenced this issue
Jun 4, 2016
@harishbalachandran - if you have time, you are most welcome to try out our latest 0.16.6dev0 prerelease on PyPi:
This should install a version of KA Lite on top of the Debian/Ubuntu version. You can remove it again with
Hey @benjaoming like I mentioned this issue does not occur in all the instance, but very few times. I did install the pre release you had given, did no face this issue. You can go ahead and add the same in 0.16.6, we will upgrade and keep you posted if we face the same problem.