Kolibri 0.13. and Kolibri-server 0.3.6 not running correctly after upgrading from 0.12.9

Support
1

OS: Ubuntu 16.04
Kolibri: v 0.13
kolibri-server: 0.3.6

You get through to setup up until “finish” then it says ‘something went wrong’

Please let me know if you came across this.

Thank you kindly.

Screenshot (261)Screenshot (262)

2

Hello Bryan,

Could you please provide the version of PostgreSQL you are using?

Thanks,
Blaine
Software Developer at Learning Equality

3

Hi @blaine,

We have version PostgreSQL 9.5.19.

Kind regards,
Bryan

4

Hi Bryan,

Thank you for that information. Could you please try the following:

  1. Stop the Kolibri server.
  2. Find the KOLIBRI_HOME directory for the server (here are the default locations for that directory).
  3. Inside the KOLIBRI_HOME directory, delete the .data_version file.
  4. Start the Kolibri server.

Let me know if Kolibri then starts successfully.
-Blaine

5

Good day @blaine,

I have already done it previously and upon your request just now. Please output (attached)Screenshot (264)

Please see log files:
https://drive.google.com/drive/folders/1fIE5Nk8DAF1z76UDDsMsK51Hb8uozUSH?usp=sharing

6

Hi @blaine do you have any updates please?

7

@blaine,

I have removed the Postgresql DB.

When I logged on to kolibri, Setup wizard was displayed ( i uninstalled the previous install) after clicking finish, a message displayed …“something went wrong etc…”
I have removed the .data_version file. Rebooted server then it starting doing this (please see video both on different browsers)
I have commented all lines under ‘Database’ in options.ini file. Rebooted server. The issue still persist as in video)
I have commented redis under Cache. rebooted the server. Logged on again and it successfully followed through the setup wizard. seem to be working now. Only downside is with no PostgreSQL DB connected.

8

I think this looks like an issue with Kolibri: When it updates, it’s supposed to run database migrations BEFORE accessing the database. Judging from below, it’s accessing the database prematurely:


INFO 2020-01-15 15:46:44,554 apps Running Kolibri with the following settings: kolibri.deployment.default.settings.base
WARNING 2020-01-15 15:46:45,022 cli Skipped automatic database backup, not compatible with this DB engine.
INFO 2020-01-15 15:46:45,022 cli Version was 0.12.9, new version: 0.13.0
INFO 2020-01-15 15:46:45,023 cli Running update routines for new version...
INFO 2020-01-15 15:48:46,088 cli Already stopped: Stopped (1)
INFO 2020-01-15 15:48:55,056 apps Running Kolibri with the following settings: kolibri.deployment.default.settings.base
WARNING 2020-01-15 15:48:55,526 cli Skipped automatic database backup, not compatible with this DB engine.
INFO 2020-01-15 15:48:55,526 cli Version was 0.12.9, new version: 0.13.0
INFO 2020-01-15 15:48:55,527 cli Running update routines for new version...
ERROR 2020-01-15 15:54:28,887 exception Internal Server Error: /api/device/deviceprovision/
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/kolibri/dist/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
psycopg2.ProgrammingError: column "registered" of relation "kolibriauth_facilitydataset" does not exist
LINE 1: ...th_no_password", "show_download_button_in_learn", "registere...
                                                             ^

@Bryan_Fisher you also mentioned this:

It looks like incompatibility of some sort, I have disconnected the DB and used the default SQLite DB.

There is no incompatibility in general, the message you see in the log saying “Skipped automatic database backup, not compatible with this DB engine” only refers to the automatic backup database dumps. This does, however, mean that updating on Postgres is a bit more risky than on SQLite, as there isn’t an automated backup taking place.