Help Pls: Kolibri disconnecting and error "The server is starting.. please wait"

Support
1

I installed Kolibri 0.11.0 in Dec 2018 on a windows laptop for a rural village. It used to work fine. Now, it does not auto-start. When I go to http://127.0.0.1:8080, the site cannot be reached and I get the message, “The server is starting… please wait”. After a long time waiting, I decided to re-install the kolibri.exe and I am getting the same error message.

I also installed Kolibri on my MacBook Pro in Dec 2018. Today I was able to log in to Kolibri to export the content from my Mac to an external drive. After an hour of data transfer, I got a message that the server is disconnected and it will try and reconnect. It never reconnected.

Please help. Thank you.

2

I upgraded to the latest version of Kolibri, 0.11.1, but I still get the same error, “The Server is starting… please wait”.

I added the Kolibri and Python apps to Windows Firewall list of apps that are allowed. I restarted Windows. Kolibri did not launch automatically so I started it from the …/python/scripts folder. I got the same error “The Server is starting… please wait”.

I have Kolibri setup and running on a Chromebook at a rural school and I really need to get this Windows laptop running Kolibri at another rural school today. I am 11 hrs ahead of PST, any help is much appreciated. Thank you!

3

Hi @jane_ed can you attach the *.log files that you can find in the .kolibri directory?

Also, would it be possible you are running another application in that windows machine that’s using the same port (8080) Kolibri uses?

If that’s the case we can change kolibri port to avoid the conflict.

4

Hi Jose,

Thanks for your email. Attached is the kolibri.log file. The debug file was empty as I did not use the debug flag to run Kolibri.

Some background: I had Kolibri running properly in December, but for some reason it stopped running.

I tried to attach the kolibri.log file, but I get the message “Sorry, the file you are trying to upload is not authorized (authorized extensions: jpg, jpeg, png, gif).” Do you have a shared folder where I can place it? The last entry in the Kolibri.log is from Feb 26, 2019.

Can you send me an email where I can send you the log file since it is not uploading here? Here is a screen shot from today.

Screenshot_Kolibri Not Starting_2019-03-06_07-50-38
Screenshot_Kolibri Not Starting_2019-03-06_07-50-381279×731 30.3 KB

Btw, if there is a conflict with the port number 8080, what other port number is recommended to use?

Thanks,
Jane

5

Jose,

Here is a cut and paste of the last entries in the kolibri.log file:
INFO 2019-02-25 07:35:09,158 apps Running Kolibri with the following settings: kolibri.deployment.default.settings.base
INFO 2019-02-25 07:35:52,059 vacuumsqlite Sqlite database Vacuum finished.
INFO 2019-02-25 07:35:52,263 cli Running update routines for new version…
INFO 2019-02-25 07:35:59,810 cli Running ‘kolibri start’ as daemon (system service)
ERROR 2019-02-25 07:36:00,404 cli Could not detect an IP address that Kolibri binds to, but try opening up the following addresses:

INFO 2019-02-25 07:36:00,560 cli Going to daemon mode, logging to C:\Users\Bugandika Primary 1.kolibri\server.log
INFO 2019-02-25 07:36:00,607 ping Attempting a ping.
INFO 2019-02-25 07:36:01,919 utils Started new MESSAGEPROCESSOR thread ID#hydrogen-cup-music-orange
INFO 2019-02-25 07:36:01,935 utils Started new SCHEDULER thread ID#bravo-oven-mexico-victor
INFO 2019-02-25 07:36:01,935 utils Started new WORKERMESSAGEHANDLER thread ID#april-crazy-mockingbird-michigan
INFO 2019-02-25 07:45:05,976 vacuumsqlite Sqlite database Vacuum finished.
INFO 2019-02-25 07:45:05,976 vacuumsqlite Next Vacuum at 3AM local server time (in 1154.9 minutes).
WARNING 2019-02-25 07:45:06,257 ping Ping failed (could not connect). Trying again in 15.0 minutes.
INFO 2019-02-25 10:14:31,403 apps Running Kolibri with the following settings: kolibri.deployment.default.settings.base
INFO 2019-02-25 10:15:24,530 vacuumsqlite Sqlite database Vacuum finished.
INFO 2019-02-25 10:15:24,670 cli Running update routines for new version…
INFO 2019-02-25 10:15:30,077 cli Running ‘kolibri start’ as daemon (system service)
ERROR 2019-02-25 10:15:30,436 cli Could not detect an IP address that Kolibri binds to, but try opening up the following addresses:

INFO 2019-02-25 10:15:30,561 cli Going to daemon mode, logging to C:\Users\Bugandika Primary 1.kolibri\server.log
INFO 2019-02-25 10:15:30,608 ping Attempting a ping.
INFO 2019-02-25 10:15:31,717 utils Started new MESSAGEPROCESSOR thread ID#bulldog-california-table-avocado
INFO 2019-02-25 10:15:31,733 utils Started new SCHEDULER thread ID#november-snake-florida-september
INFO 2019-02-25 10:15:31,733 utils Started new WORKERMESSAGEHANDLER thread ID#alabama-iowa-pluto-louisiana
INFO 2019-02-25 10:16:24,215 vacuumsqlite Sqlite database Vacuum finished.
INFO 2019-02-25 10:16:24,215 vacuumsqlite Next Vacuum at 3AM local server time (in 1003.5833333333334 minutes).
WARNING 2019-02-25 10:16:24,465 ping Ping failed (could not connect). Trying again in 15.0 minutes.
INFO 2019-02-25 10:33:24,764 apps Running Kolibri with the following settings: kolibri.deployment.default.settings.base
INFO 2019-02-25 14:37:10,355 apps Running Kolibri with the following settings: kolibri.deployment.default.settings.base
INFO 2019-02-26 06:50:56,486 apps Running Kolibri with the following settings: kolibri.deployment.default.settings.base
INFO 2019-02-26 06:51:38,642 vacuumsqlite Sqlite database Vacuum finished.
INFO 2019-02-26 06:51:38,767 cli Running update routines for new version…
INFO 2019-02-26 06:51:48,455 cli Running ‘kolibri start’ as daemon (system service)
ERROR 2019-02-26 06:51:48,830 cli Could not detect an IP address that Kolibri binds to, but try opening up the following addresses:

INFO 2019-02-26 06:51:48,986 cli Going to daemon mode, logging to C:\Users\Bugandika Primary 1.kolibri\server.log
INFO 2019-02-26 06:51:49,002 ping Attempting a ping.
INFO 2019-02-26 06:51:51,127 utils Started new MESSAGEPROCESSOR thread ID#magazine-oscar-wolfram-football
INFO 2019-02-26 06:51:51,142 utils Started new SCHEDULER thread ID#speaker-zulu-rugby-bulldog
INFO 2019-02-26 06:51:51,142 utils Started new WORKERMESSAGEHANDLER thread ID#johnny-cat-failed-sad

6

Hello Jane
I think the key of your problem is here:

Something has changed in the network address of your machine, and kolibri can’t find the IP you have.
can you paste the output of executing
ipconfig
in your server?

In case you don’t know how to execute ipconfig you can find a small tutorial at https://oit.ncsu.edu/my-it/resnet/ipconfig-in-windows/