New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kolibri not starting after reboot [after downloading Kolibri Channels, on RPi] #1648
Comments
@arky @jredrejo @KW4NP are you familiar with The only real difference (I know of) between @kananigit's Kolibri failure and my own working — "systemctl status kolibri" works on my pre-release of IIAB 7.0 on RPi 3 B+ — is that he downloaded a few Kolibri channels — whereas I did not. Is this possibly connected to learningequality/kolibri-installer-debian#66 ? |
I did run into this issue when I had a problem with a malformed content database. Deleting the database seemed to be successful, but Kolibri would not start with systemd. I started it manually and let it run through the migrations and stopped it again, but on the next boot it did the same thing. The solution I found was to start it manually, make sure everything was set up (facility, etc.), and reboot the machine. I don't remember it just not starting with no prior problem, however. |
This one seems to be running an update routine for a new version - does Kolibri automatically update? |
Not that I know of! (What evidence of a Kolibri "update routine for a new version" are you seeing?) |
In the second picture
|
What kind of (presumably offline?) update Kolibri is running on start is unclear. Googling "Running update routines for new version" does not give an immediate answer as to what this means. Hopefully @jredrejo can shed more light... |
Thanks for the quick reply Tim. Id like to know what commands you ran to
start kolibri manually . I ran systemctl start kolibri but that did not
help as it timed out. Check the screenshot where I did systemctl status
kolibri
…On Sat, May 11, 2019, 01:38 KW4NP ***@***.***> wrote:
I did run into this issue when I had a problem with a malformed content
database. Deleting the database seemed to be successful, but Kolibri would
not start with systemd. I started it manually and let it run through the
migrations and stopped it again, but on the next boot it did the same
thing. The solution I found was to start it manually, make sure everything
was set up (facility, etc.), and reboot the machine. I don't remember it
just not starting with no prior problem, however.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1648 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADRZ36AQOTIYSJAWU3AFFI3PUZSXJANCNFSM4HMHITEQ>
.
|
I found the instructions here https://github.com/iiab/iiab/blob/master/roles/kolibri/README.rst |
No, it does not. The routine you mention is to update the database models after a kolibri update. |
@kananigit can you please try @benjaoming's suggestion at learningequality/kolibri-installer-debian#66 (comment) ? Specifically, can you install a smaller-than-MIN-sized IIAB 7.0 pre-release — but first set most all apps' variables to (Or if you prefer Either way please let us know whether Kolibri's service continues to fail or not, Thanks ! |
@kananigit have you experienced this in the last 7 months? Thanks for clarifying please — whether your experiences are in Kenya, UK, or USA or wherever! |
I installed Kolibri 0.12.2 by running the latest [pre-release of] IIAB 7.0 on a Raspberry Pi Model 3B. After the first reboot upon successful IIAB intall, i used Kolibri and even downloaded a couple channels to it. I later shut down the server and when i started it the next day kolibri did not start. Here are some of the screenshots.
/usr/local/kolibri/bin/kolibri start
Contents of /library/kolibri/server.log
The text was updated successfully, but these errors were encountered: