The Kolibri app on Android is failing to connect to the Linux Ubuntu server hosting the LMS. Both devices can ping each other though.
During Kolibri app (on Android) configuration for a learner, if I select the import user option, it says that the first user to be imported will be assigned Super User permissions. How can this be avoided?
In order to better understand the situation, it would be helpful if you could answer a few questions. First, in regards to your items:
Does the Kolibri app on the Android device automatically discover the Ubuntu server on the network? Are you able to access the address for the Kolibri server in the Android device’s web browser?
Just in case it isn’t clear, the super-user permissions on the learner-only device allow management of things like importing or removing channels on the device, and enabling or disabling automatic content import during syncs. It does not allow modification of facility settings or data. Although, there is a way to control access to the aforementioned device’s configuration for learners in a facility, through its settings. In the facility settings on the server, you’ll find a section like that in the screenshot below, where you can set a PIN. Only with that PIN can those device settings be accessed on the learner-only device.
I’ve since cleared it with a bit of help from Gemini
However Ive hit another roadblock:
In the Kolibri app configuration (android version) I’ve hit another issue - I cannot get past the ‘Import one or more existing user accounts from an existing facility’ or ‘Create a new user account for an existing facility’
When IN come to importing a user, I’m selecting Use the Admin Account and when I log in, I get the list of users on he server.
When I select a user to import, it loops for about 20 seconds then gives the error message: “Error in importing user”
Could it be that Android is preventing the app from writing to the device files? Kolibri is part of the list of apps that “Can always use data” but when I check the permissions under the app, there’s no file access permission.
Thank you for the additional info. I don’t believe permissions are an issue at this time.
To continue investigating the issue you’re experiencing, we’ll need the Kolibri logs from your Android device. The following instructions will guide you on how to retrieve the logs from a Windows device. If you’ll be using Linux to access the Android device, steps 1-3 should be the same, but steps 4-5 should be adjusted for your Linux platform.
Close the Kolibri app if it is running.
Connect your device to a computer using a USB cable.
Select File transfer in the USB options on your device.
Wait for your computer to recognize the Android device as an external drive.
On Windows it should look something like this:
Copy the kolibri.txt file to your computer and send it as attachment to support@learningequality.org (include the link to this forum conversation for easier tracking).
Thank you for following up. Let me investigate whether I can find the logs with my own Android devices.
In the meantime, with this new error, the logs from the server itself might be helpful, and those should be easier to find. The logs should be found at /home/<username>/.kolibri for the <username> user that Kolibri was installed with. If you used the kolibri-server package, that might have installed kolibri to a different user: /home/kolibri/.kolibri.
Hi Blaine,
Thanks very much for your help - much appreciated!
Ive located the server Kolibri log file but I can’t find a way of attaching it to this thread - how can I achieve this ? Or can I use email? Pls let me have the email address.
Thanks.
Hi Blaine,
I managed to get Android log files - I had to buy a USB data cable because all along I was using charging only cables
I’ve emailed the Android data files.
I’m using a Samsung S21 smartphone with Android version 15 and One UI version 7.0
This is the error dump from the Android phone when it fails to import a user from an existing facility, during Kolibri app initial configuration:
{
Hi Blaine,
An update:
I uploaded the log files into Gemini for it to help me diagnose and resolve the problem. Somewhere along the series on commands Gemini was giving me to execute, I corrupted the Kolibri database. We ended up going round in circles in trying to resolve this too. I ended up re-installing Kolibri and recreated Facility data (I’m still in development/Test mode fortunately). After the clean re-installation I tried the Android Kolibri app again and it went through, and it synced ie. downloaded the lesson resources assigned to the class.
I’m not sure if its advisable to use LLMs to try to resolve technical issues.
Thanks for your help again!
Nyasha.
Thanks for sending over those other log files. They appear to be related to Android itself and don’t have much Kolibri information that I can see.
Although, that error you sent over (Cannot restart job with state: QUEUED) gives me an idea for creating a scenario that might reproduce the whole issue. I suspect that some transient error occurred, then a bug in the setup wizard (which I’ll try to reproduce) prevented completion of Kolibri’s setup after the error occurred.
So to double check, the issue is indeed resolved? The re-installation of the Kolibri app sounds like a sensible workaround for anyone else encountering this, although we’ll certainly investigate making this more robust.
Finally, I think it’s absolutely fine to use an LLM to investigate issues, with the caveat of knowing that LLMs can lead you down rabbit holes. So you should always take its analysis with some level of skepticism.