Hi @mrdavidhaag,
Thank you for the kind words! The Learning Equality team is happy to hear that Kolibri has made a difference.
the report shows a 100% score with 14 of 11 questions answered.
This seems clearly a bug that we need to investigate further. We’ll followup when we have more information.
Regarding your other questions:
-
There shouldn’t be any need for ‘repair’ of the database. Although, the size of the database might be contributing to the other issue you posted. The larger database may cause longer request times and even request timeouts. With larger database sizes we recommend using PostgreSQL, but that’s a fairly advanced procedure and management.
-
Such a Kolibri feature to reduce the database size does not exist, unfortunately. Going forward, you may consider creating a new Kolibri instance for every new school year, and archiving the previous database file.
-
That
uwsgi.loglog file can be safely removed. It would appear that log file was perhaps copied from thelogs/directory? It hasn’t been modified since 2021. Generally, it’s safe to delete log files while Kolibri is stopped. Any deleted log files should be recreated (without contents) as they’re only for application logging and auditing purposes.
Regards,
Blaine