One other thing to flag is that by default kolibri-server (and the kolibri debian package it supports) runs kolibri as the kolibri user rather than as your default user account. So it’s possible that by running things from your default david user account it may be causing issues - in particular, they will have separate KOLIBRI_HOME folders (and hence databases), so tasks created by the service would not get picked up by task runners run from your user account.
Not clear if that’s what is happening here, but worth making sure everything is being run by the kolibri user account.
Hi Richard,
It is just that the system had been running for some months without any problem and suddenly this cropped from no where.
How do I change the default user kolibri-server is running in? Also, how do I post that long log file here in a manageable way.. because I have kolibri.txt log and one other directly from the server.
Hi @david_ally
Can you share the log files (preferably zipped) over email to support@learningequality.org? I can take a closer look at them there and report back.
Kind Regards,
Richard
Hi @david_ally
Thanks for sharing the logic files - I can see that task runners are running, from those log files. Were those from the .david user folder or from the .kolibri user folder?
Also, when you went to import these channels, did the initial channel database import step run fine? This would also indicate that the task runners are running correctly, but something else is happening.
If you’re unsure about this, could you try browsing a completely new channel from Kolibri Studio in the Device Channel import flow, and see if you are able to browser the channel to select resources to import?
Kind Regards,
Richard
The logs are from .kolibri logs.
David
And just to check in about this?
If you’re unsure about this, could you try browsing a completely new channel from Kolibri Studio in the Device Channel import flow, and see if you are able to browser the channel to select resources to import?
Hi Richard,
The problem seems to have been resolved even though I do not know what exactly was responsible for the problem. The last import that was queued was completed and I tried importing new contents and it is progressing fine.
Thank you for your support.
David