Make Kolibri 24/7

I was wondering if there is a way to have Kolibri always running. We’ve managed to get it working on our windows 2008 server; but the software only runs when I remote desktop to the server in question. Ideally, we would like Kolibri to constantly be running, any suggestions? Apologies if this has been answered somewhere and I’ve missed it.

It sounds as if Windows 2008 server might be blocking incoming requests for Kolibri. If so, you may need to allow Kolibri’s port in your firewall rules to let Windows 2008 know it’s okay to let requests on this port go through. If you haven’t tried this before, a short tutorial on that can be found here:

I saw in another message that this worked on other computers, it may be because their firewall rules were more relaxed. What OS are the other computers running?

Hope this helps!

We are currently running Win 7 but will be upgrading to Win 10 come the end of the year. I will follow the instructions provided w/ regard to the firewall; I appreciate the help! We had stopped the firewall service the other day to see if that would resolve the issue but no luck, and prior to that I did try to add the port as a new inbound rule but may have missed the mark w/ respect to getting the settings right.

Additionally, we continuously get the message “The server is starting… please wait”. I know this insinuates that something is blocking the connection, but what’s odd is that I am still able to connect from all of our various workstations once my administrator PC is remote desktop’d to the windows server we are running the software on (still getting the “server is starting… please wait” message during this time)

Below I will post the current log files found in .Kolibri–>Logs–>Kolibri.txt/Daemon.txt

INFO 2019-07-18 09:52:33,976 apps Running Kolibri with the following settings: kolibri.deployment.default.settings.base
INFO 2019-07-18 09:52:34,834 vacuumsqlite Sqlite database Vacuum finished.
INFO 2019-07-18 09:52:34,834 cli Running ‘kolibri start’ as daemon (system service)
INFO 2019-07-18 09:52:34,881 cli Kolibri running on:

INFO 2019-07-18 09:52:34,881 cli Going to daemon mode, logging to C:\Users\Administrator.EDUMIA.kolibri\logs\kolibri.txt
INFO 2019-07-18 09:52:34,897 ping Attempting a ping.
INFO 2019-07-18 09:52:34,928 vacuumsqlite Sqlite database Vacuum finished.
INFO 2019-07-18 09:52:34,928 vacuumsqlite Next Vacuum at 3AM local server time (in 1027.4166666666667 minutes).
INFO 2019-07-18 09:52:35,162 utils Started new JOBCHECKER thread ID#b876a5b40a1a45088afe0973e7624bc8
INFO 2019-07-18 09:52:35,271 annotation Updating num_coach_content on existing channels
INFO 2019-07-18 09:52:35,271 server Starting Kolibri 0.12.5
INFO 2019-07-18 09:52:39,140 ping Ping succeeded! (response: {‘messages’: [], ‘id’: 283188})
INFO 2019-07-18 09:52:39,811 ping Sleeping for 1440.0 minutes.
INFO 2019-07-18 09:52:39,920 cherrypy.error ENGINE Bus STARTING
INFO 2019-07-18 09:52:40,138 cherrypy.error ENGINE Serving on http://0.0.0.0:8080
INFO 2019-07-18 09:52:40,138 cherrypy.error ENGINE Bus STARTED
INFO 2019-07-18 10:28:03,567 apps Running Kolibri with the following settings: kolibri.deployment.default.settings.base
INFO 2019-07-18 10:28:04,129 vacuumsqlite Sqlite database Vacuum finished.
INFO 2019-07-18 10:28:04,144 cli Running ‘kolibri start’ as daemon (system service)
INFO 2019-07-18 10:28:04,176 cli Kolibri running on:

INFO 2019-07-18 10:28:04,176 cli Going to daemon mode, logging to C:\Users\Administrator.EDUMIA.kolibri\logs\kolibri.txt
INFO 2019-07-18 10:28:04,191 ping Attempting a ping.
INFO 2019-07-18 10:28:04,238 vacuumsqlite Sqlite database Vacuum finished.
INFO 2019-07-18 10:28:04,238 vacuumsqlite Next Vacuum at 3AM local server time (in 991.9166666666666 minutes).
INFO 2019-07-18 10:28:04,472 utils Started new JOBCHECKER thread ID#feb5f1070cac42cca17fdcb08eb99022
INFO 2019-07-18 10:28:04,566 annotation Updating num_coach_content on existing channels
INFO 2019-07-18 10:28:04,581 server Starting Kolibri 0.12.5
INFO 2019-07-18 10:28:08,341 ping Ping succeeded! (response: {‘id’: 283224, ‘messages’: []})
INFO 2019-07-18 10:28:08,980 ping Sleeping for 1440.0 minutes.
INFO 2019-07-18 10:28:09,230 cherrypy.error ENGINE Bus STARTING
INFO 2019-07-18 10:28:09,448 cherrypy.error ENGINE Serving on http://0.0.0.0:8080
INFO 2019-07-18 10:28:09,448 cherrypy.error ENGINE Bus STARTED

e[37mINFO Attempting a ping.e[0m
e[37mINFO Sqlite database Vacuum finished.e[0m
e[37mINFO Next Vacuum at 3AM local server time (in 991.9166666666666 minutes).e[0m
e[37mINFO Started new JOBCHECKER thread ID#feb5f1070cac42cca17fdcb08eb99022e[0m
e[37mINFO Updating num_coach_content on existing channelse[0m
e[37mINFO Starting Kolibri 0.12.5e[0m
e[37mINFO Ping succeeded! (response: {‘id’: 283224, ‘messages’: []})e[0m
e[37mINFO Sleeping for 1440.0 minutes.e[0m
e[37mINFO ENGINE Bus STARTINGe[0m
e[37mINFO ENGINE Serving on http://0.0.0.0:8080e[0m
e[37mINFO ENGINE Bus STARTEDe[0m

Ah, sorry, I misunderstood about the remote desktop issue - I thought you meant that when you ran remote desktop, you could see Kolibri running on the server. It sounds, though, like Kolibri becomes accessible to all the computers on your network once you remote desktop in to the server?

Could you give me more information on how exactly you start Kolibri on the windows 2008 server machine? Also, are you seeing the “server is starting… please wait” message on the Windows 2008 server machine, or do you see it in the browser on the client machines when they try to connect to Kolibri?

Yes, apologies on the confusing post. It becomes accessible to all computers once I remote desktop into the server.

As for more information, I start the software by running the program as an administrator off of our D drive. I see server is starting… on the server machine. I went ahead and added port 8080 as a new inbound rule on the firewall but nothing has changed as of yet. I’ve also tried adding an options.ini to change the port and see if that resolved the issue but to no avail.

Okay, thanks for the clarification! When you say you run it, could you walk me through the steps you take?

One possible theory I have as to what is happening is that, if you remote desktop into windows 2008 server and start Kolibri from the command line, when you log out of the server, it also shuts down Kolibri as it closes out any processes you started. (e.g. it’s as if you logged out of the server, and anything you were running quits) This may not be the case depending on how you are starting Kolibri though, so this is why I would like to know more in detail.

When I remote desktop the server usually attempts to start on its own, without me running anything. I end the Kolibri processes (there are 2, one with a capital K).

Then: Computer --> D drive --> Folder called “Installs” --> folder where I directed Kolibri to install --> right click on Kolibri.exe --> Run as administrator.

So Kolibri starts when you remote desktop in? Can you see it starting up, or is it possible it was running before you signed in? Also, have you selected the “Run Kolibri at system startup” option in the Kolibri tray icon?

If you sign out with Kolibri still running, and sign back in again, does it get restarted? That would indicate that Kolibri stops running whenever you sign out.