Kolibri feature was working effectively at the beginning and then it stopped and began displaying this message making it inaccessible. the message reads " Sorry, Kolibri is currently unavailable. Please try again later, or restart the RACHEL." all other features are working except the Kolibri
We tried restarting but nothing seem to change.
Please let us know how to solve this problem
order number #2362
Thank you!
Hello @Mnasir_Jr - Sorry to hear you’re having this problem. Can you please tell me the RACHEL Installer Version, as well as the Kolibri version installed? Here is how to find it.
For Example.
James
Hello Jamesk!
We sorry for the delay but here are the details requested
!
Screenshot 2022-01-06 101744|510x456
Hi @Mnasir_Jr - Thank you for providing the screenshot.
I want to confirm that Kolibri is not running. Can you please follow these steps and tell me if you can access Kolibri.
I would also like to know, did you by any chance install the module called zz-kolibri-upgrade?
If this doesn’t work, we may need to log in to the device using SSH and Putty to get more information, which I will help you with if possible.
James
Hi,
The address http://192.168.88.1:9090 was not accessible via wifi. I keep receiving " This site can’t be reached"
zz-kolibri-upgrade doesn’t show in the install section of RACHEL-Plus admin page
Thank you!
Hi @Mnasir_Jr - Thank you. I will need some more information to diagnose the problem.
Does zz-kolibri-upgrade show as available to download, or as available to delete?
Have you ever run a recovery on the device to bring it to 3.2.0, or was it shipped to you with RACHEL 3.2.0?
When you look at the back of the device, do you see any swelling of the battery area?
Do you have any experience connecting to the device over SSH? If not I can show you how, if you do, please connect to your RACHEL-Plus and run the command “sudo systemctl status kolibri” and paste the output.
thank you
Hi @jamesk
zz-kolibri-upgrade neither shows as any of the aforementioned.
No recovery attempts were made on the device to bring it to 3.2.0 it was shipped like that.
There is no swelling observed at the back of the device.
I’d be grateful if you guide me through the process of connecting the device over SSH.
Thank you!
Hi @Mnasir_Jr - Lets try an easier way. Please follow these steps if possible.
Download zz-diagnose_kolibri from this link
Connect to your RACHEL-Plus with your device.
Press the admin button to log in to the admin interface
Save this file to your PC and then share here if possible
Check Kolirbi again and see if it works
This can be done with a mobile phone if the device is in a remote location. If you have any issues with this process please let me know. Thanks!
Hi @jamesk,
Here’s the content of the log saved:
======= Uploading zz-diagnose_kolibri.zip =======
======= Beginning Installation =======
======= Verifying zz-diagnose_kolibri.zip =======
======= zz-diagnose_kolibri.zip Verified =======
======= Starting Extraction =======
Archive: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zz-diagnose_kolibri.zip
creating: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zip/zz-diagnose_kolibri/
extracting: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zip/zz-diagnose_kolibri/finish_install.sh
extracting: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zip/zz-diagnose_kolibri/rachel-index.php
======= Running finish_install.sh =======
SETUP: Starting Kolibri diagnostic
SETUP: Checking mounted drives
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0rpmb 179:24 0 4M 0 disk
mmcblk0boot0 179:8 0 4M 1 disk
sda 8:0 0 447.1G 0 disk
-sda1 8:1 0 447.1G 0 part /.data mmcblk0boot1 179:16 0 4M 1 disk mmcblk0 179:0 0 28.8G 0 disk |-mmcblk0p2 179:2 0 20.5G 0 part / |-mmcblk0p3 179:3 0 7.9G 0 part [SWAP] -mmcblk0p1 179:1 0 512M 0 part /boot/efi
SETUP: Getting Kolibri version
kolibri, version 0.14.7
SETUP: Getting Kolibri status
● kolibri.service - LSB: kolibri daemon, an offline education platform
Loaded: loaded (/etc/init.d/kolibri; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2022-01-11 10:09:53 WAT; 7min ago
Process: 877 ExecStart=/etc/init.d/kolibri start (code=exited, status=1/FAILURE)
Jan 11 10:09:53 CMAL-871f kolibri[877]: return callback(*args, **kwargs)
Jan 11 10:09:53 CMAL-871f kolibri[877]: File “/usr/lib/python3/dist-packages/kolibri/utils/cli.py”, line 518, in start
Jan 11 10:09:53 CMAL-871f kolibri[877]: recreate_diskcache()
Jan 11 10:09:53 CMAL-871f kolibri[877]: File “/usr/lib/python3/dist-packages/kolibri/deployment/default/cache.py”, line 27, in recreate_diskcache
Jan 11 10:09:53 CMAL-871f kolibri[877]: os.mkdir(diskcache_location)
Jan 11 10:09:53 CMAL-871f kolibri[877]: FileExistsError: [Errno 17] File exists: ‘/root/.kolibri/process_cache’
Jan 11 10:09:53 CMAL-871f systemd[1]: kolibri.service: Control process exited, code=exited status=1
Jan 11 10:09:53 CMAL-871f systemd[1]: Failed to start LSB: kolibri daemon, an offline education platform.
Jan 11 10:09:53 CMAL-871f systemd[1]: kolibri.service: Unit entered failed state.
Jan 11 10:09:53 CMAL-871f systemd[1]: kolibri.service: Failed with result ‘exit-code’.
SETUP: Removing process cache
rm: cannot remove ‘/.data/RACHEL/.kolibri/process_cache/cache.db-wal’: Structure needs cleaning
rm: cannot remove ‘/.data/RACHEL/.kolibri/process_cache/cache.db-shm’: Structure needs cleaning
SETUP: Restarting Kolibri
Job for kolibri.service failed because the control process exited with error code. See “systemctl status kolibri.service” and “journalctl -xe” for details.
SETUP: Checking Kolibri status
● kolibri.service - LSB: kolibri daemon, an offline education platform
Loaded: loaded (/etc/init.d/kolibri; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2022-01-11 10:17:34 WAT; 29ms ago
Process: 5495 ExecStart=/etc/init.d/kolibri start (code=exited, status=1/FAILURE)
Jan 11 10:17:34 CMAL-871f kolibri[5495]: return callback(*args, **kwargs)
Jan 11 10:17:34 CMAL-871f kolibri[5495]: File “/usr/lib/python3/dist-packages/kolibri/utils/cli.py”, line 518, in start
Jan 11 10:17:34 CMAL-871f kolibri[5495]: recreate_diskcache()
Jan 11 10:17:34 CMAL-871f kolibri[5495]: File “/usr/lib/python3/dist-packages/kolibri/deployment/default/cache.py”, line 27, in recreate_diskcache
Jan 11 10:17:34 CMAL-871f kolibri[5495]: os.mkdir(diskcache_location)
Jan 11 10:17:34 CMAL-871f kolibri[5495]: FileExistsError: [Errno 17] File exists: ‘/root/.kolibri/process_cache’
Jan 11 10:17:34 CMAL-871f systemd[1]: kolibri.service: Control process exited, code=exited status=1
Jan 11 10:17:34 CMAL-871f systemd[1]: Failed to start LSB: kolibri daemon, an offline education platform.
Jan 11 10:17:34 CMAL-871f systemd[1]: kolibri.service: Unit entered failed state.
Jan 11 10:17:34 CMAL-871f systemd[1]: kolibri.service: Failed with result ‘exit-code’.
SETUP: Finished Kolibri Diagnostic
======= Upload and Install Complete =======
The error message persisted despite executing the above instructions
Thank you @Mnasir_Jr . I have made a change to the same zip file that may help. Can you please download it again and repeat the same process. You will have to delete zz-diagnose_kolibri first from the install tab before uploading again.
The link is here zz-diagnose_kolibri.zip
Thanks
Hi @jamesk
It still did not work, and the log is pretty much the same as the previous one after installation.
I deleted the previous package from the installation list, but I have one “en-kolibri-index” though, does that need to be deleted too?
No the en-kolibri-index can stay.
Can you please send me the new output log as a whole file?
Also, please reboot the device to see if it works now.
Authorization is required for rebooting from the hardware settings under the “Advanced settings” section, and we keep getting “wrong username or password.”
Please find below the output log.
======= Uploading zz-diagnose_kolibri.zip =======
======= Beginning Installation =======
======= Verifying zz-diagnose_kolibri.zip =======
======= zz-diagnose_kolibri.zip Verified =======
======= Starting Extraction =======
Archive: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zz-diagnose_kolibri.zip
creating: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zip/zz-diagnose_kolibri/
extracting: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zip/zz-diagnose_kolibri/finish_install.sh
extracting: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zip/zz-diagnose_kolibri/rachel-index.php
======= Running finish_install.sh =======
SETUP: Starting Kolibri diagnostic
SETUP: Checking mounted drives
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0rpmb 179:24 0 4M 0 disk
mmcblk0boot0 179:8 0 4M 1 disk
sda 8:0 0 447.1G 0 disk
-sda1 8:1 0 447.1G 0 part /.data mmcblk0boot1 179:16 0 4M 1 disk mmcblk0 179:0 0 28.8G 0 disk |-mmcblk0p2 179:2 0 20.5G 0 part / |-mmcblk0p3 179:3 0 7.9G 0 part [SWAP] -mmcblk0p1 179:1 0 512M 0 part /boot/efi
SETUP: Getting Kolibri version
kolibri, version 0.14.7
SETUP: Getting Kolibri status
● kolibri.service - LSB: kolibri daemon, an offline education platform
Loaded: loaded (/etc/init.d/kolibri; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2022-01-11 20:56:44 WAT; 4min 21s ago
Process: 1100 ExecStart=/etc/init.d/kolibri start (code=exited, status=1/FAILURE)
Jan 11 20:56:44 CMAL-871f kolibri[1100]: return callback(*args, **kwargs)
Jan 11 20:56:44 CMAL-871f kolibri[1100]: File “/usr/lib/python3/dist-packages/kolibri/utils/cli.py”, line 518, in start
Jan 11 20:56:44 CMAL-871f kolibri[1100]: recreate_diskcache()
Jan 11 20:56:44 CMAL-871f kolibri[1100]: File “/usr/lib/python3/dist-packages/kolibri/deployment/default/cache.py”, line 27, in recreate_diskcache
Jan 11 20:56:44 CMAL-871f kolibri[1100]: os.mkdir(diskcache_location)
Jan 11 20:56:44 CMAL-871f kolibri[1100]: FileExistsError: [Errno 17] File exists: ‘/root/.kolibri/process_cache’
Jan 11 20:56:44 CMAL-871f systemd[1]: kolibri.service: Control process exited, code=exited status=1
Jan 11 20:56:44 CMAL-871f systemd[1]: Failed to start LSB: kolibri daemon, an offline education platform.
Jan 11 20:56:44 CMAL-871f systemd[1]: kolibri.service: Unit entered failed state.
Jan 11 20:56:44 CMAL-871f systemd[1]: kolibri.service: Failed with result ‘exit-code’.
SETUP: Stopping Kolibri
Failed to stop Kolibri.service: Unit Kolibri.service not loaded.
SETUP: Removing process cache
rm: cannot remove ‘/.data/RACHEL/.kolibri/process_cache/cache.db-wal’: Structure needs cleaning
rm: cannot remove ‘/.data/RACHEL/.kolibri/process_cache/cache.db-shm’: Structure needs cleaning
SETUP: Restarting Kolibri
Job for kolibri.service failed because the control process exited with error code. See “systemctl status kolibri.service” and “journalctl -xe” for details.
SETUP: Checking Kolibri status
● kolibri.service - LSB: kolibri daemon, an offline education platform
Loaded: loaded (/etc/init.d/kolibri; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2022-01-11 21:01:13 WAT; 40ms ago
Process: 5519 ExecStart=/etc/init.d/kolibri start (code=exited, status=1/FAILURE)
Jan 11 21:01:12 CMAL-871f kolibri[5519]: return callback(*args, **kwargs)
Jan 11 21:01:12 CMAL-871f kolibri[5519]: File “/usr/lib/python3/dist-packages/kolibri/utils/cli.py”, line 518, in start
Jan 11 21:01:12 CMAL-871f kolibri[5519]: recreate_diskcache()
Jan 11 21:01:12 CMAL-871f kolibri[5519]: File “/usr/lib/python3/dist-packages/kolibri/deployment/default/cache.py”, line 27, in recreate_diskcache
Jan 11 21:01:12 CMAL-871f kolibri[5519]: os.mkdir(diskcache_location)
Jan 11 21:01:12 CMAL-871f kolibri[5519]: FileExistsError: [Errno 17] File exists: ‘/root/.kolibri/process_cache’
Jan 11 21:01:13 CMAL-871f systemd[1]: kolibri.service: Control process exited, code=exited status=1
Jan 11 21:01:13 CMAL-871f systemd[1]: Failed to start LSB: kolibri daemon, an offline education platform.
Jan 11 21:01:13 CMAL-871f systemd[1]: kolibri.service: Unit entered failed state.
Jan 11 21:01:13 CMAL-871f systemd[1]: kolibri.service: Failed with result ‘exit-code’.
SETUP: Finished Kolibri Diagnostic
======= Upload and Install Complete =======
Thank you @Mnasir_Jr - I have updated the zip at zz-diagnose_kolibri.zip. Please delete the previously installed one from the install tab and upload this one, then paste the log.
Unfortunately to attempt to fix Kolibri without restoring the entire device, this process is required. It is slow but we may be able to fix it.
Thanks.
Hello, here’s the log.
======= Uploading zz-diagnose_kolibri.zip =======
======= Beginning Installation =======
======= Verifying zz-diagnose_kolibri.zip =======
======= zz-diagnose_kolibri.zip Verified =======
======= Starting Extraction =======
Archive: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zz-diagnose_kolibri.zip
creating: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zip/zz-diagnose_kolibri/
extracting: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zip/zz-diagnose_kolibri/finish_install.sh
extracting: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zip/zz-diagnose_kolibri/rachel-index.php
======= Running finish_install.sh =======
SETUP: Starting Kolibri diagnostic
SETUP: Checking mounted drives
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0rpmb 179:24 0 4M 0 disk
mmcblk0boot0 179:8 0 4M 1 disk
sda 8:0 0 447.1G 0 disk
-sda1 8:1 0 447.1G 0 part /.data mmcblk0boot1 179:16 0 4M 1 disk mmcblk0 179:0 0 28.8G 0 disk |-mmcblk0p2 179:2 0 20.5G 0 part / |-mmcblk0p3 179:3 0 7.9G 0 part [SWAP] -mmcblk0p1 179:1 0 512M 0 part /boot/efi
SETUP: Getting Kolibri version
kolibri, version 0.14.7
SETUP: Getting Kolibri status
● kolibri.service - LSB: kolibri daemon, an offline education platform
Loaded: loaded (/etc/init.d/kolibri; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2022-01-12 09:15:15 WAT; 8min ago
Process: 1126 ExecStart=/etc/init.d/kolibri start (code=exited, status=1/FAILURE)
Jan 12 09:15:14 CMAL-871f kolibri[1126]: return callback(*args, **kwargs)
Jan 12 09:15:14 CMAL-871f kolibri[1126]: File “/usr/lib/python3/dist-packages/kolibri/utils/cli.py”, line 518, in start
Jan 12 09:15:14 CMAL-871f kolibri[1126]: recreate_diskcache()
Jan 12 09:15:14 CMAL-871f kolibri[1126]: File “/usr/lib/python3/dist-packages/kolibri/deployment/default/cache.py”, line 27, in recreate_diskcache
Jan 12 09:15:14 CMAL-871f kolibri[1126]: os.mkdir(diskcache_location)
Jan 12 09:15:14 CMAL-871f kolibri[1126]: FileExistsError: [Errno 17] File exists: ‘/root/.kolibri/process_cache’
Jan 12 09:15:15 CMAL-871f systemd[1]: kolibri.service: Control process exited, code=exited status=1
Jan 12 09:15:15 CMAL-871f systemd[1]: Failed to start LSB: kolibri daemon, an offline education platform.
Jan 12 09:15:15 CMAL-871f systemd[1]: kolibri.service: Unit entered failed state.
Jan 12 09:15:15 CMAL-871f systemd[1]: kolibri.service: Failed with result ‘exit-code’.
SETUP: Stopping Kolibri
Failed to stop Kolibri.service: Unit Kolibri.service not loaded.
SETUP: Deleting root Kolibri cache
rm: cannot remove ‘/root/.kolibri/process_cache’: Is a directory
SETUP: Removing process cache
rm: cannot remove ‘/.data/RACHEL/.kolibri/process_cache/cache.db-wal’: Structure needs cleaning
rm: cannot remove ‘/.data/RACHEL/.kolibri/process_cache/cache.db-shm’: Structure needs cleaning
SETUP: Restarting Kolibri
Job for kolibri.service failed because the control process exited with error code. See “systemctl status kolibri.service” and “journalctl -xe” for details.
SETUP: Checking Kolibri status
● kolibri.service - LSB: kolibri daemon, an offline education platform
Loaded: loaded (/etc/init.d/kolibri; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2022-01-12 09:23:31 WAT; 31ms ago
Process: 5680 ExecStart=/etc/init.d/kolibri start (code=exited, status=1/FAILURE)
Jan 12 09:23:30 CMAL-871f kolibri[5680]: return callback(*args, **kwargs)
Jan 12 09:23:30 CMAL-871f kolibri[5680]: File “/usr/lib/python3/dist-packages/kolibri/utils/cli.py”, line 518, in start
Jan 12 09:23:30 CMAL-871f kolibri[5680]: recreate_diskcache()
Jan 12 09:23:30 CMAL-871f kolibri[5680]: File “/usr/lib/python3/dist-packages/kolibri/deployment/default/cache.py”, line 27, in recreate_diskcache
Jan 12 09:23:30 CMAL-871f kolibri[5680]: os.mkdir(diskcache_location)
Jan 12 09:23:30 CMAL-871f kolibri[5680]: FileExistsError: [Errno 17] File exists: ‘/root/.kolibri/process_cache’
Jan 12 09:23:31 CMAL-871f systemd[1]: kolibri.service: Control process exited, code=exited status=1
Jan 12 09:23:31 CMAL-871f systemd[1]: Failed to start LSB: kolibri daemon, an offline education platform.
Jan 12 09:23:31 CMAL-871f systemd[1]: kolibri.service: Unit entered failed state.
Jan 12 09:23:31 CMAL-871f systemd[1]: kolibri.service: Failed with result ‘exit-code’.
SETUP: Finished Kolibri Diagnostic
======= Upload and Install Complete =======
Thank you @Mnasir_Jr . I had made a mistake in this last one. Please try this process again zz-diagnose_kolibri.zip
if the issue/output hasn’t changed after running this, we will have to look at another method
Hi @jamesk
I’m sorry to inform you that the output still hasn’t changed.
Here’s the log as usual
======= Uploading zz-diagnose_kolibri.zip =======
======= Beginning Installation =======
======= Verifying zz-diagnose_kolibri.zip =======
======= zz-diagnose_kolibri.zip Verified =======
======= Starting Extraction =======
Archive: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zz-diagnose_kolibri.zip
creating: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zip/zz-diagnose_kolibri/
extracting: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zip/zz-diagnose_kolibri/finish_install.sh
extracting: /.data/RACHEL/rachel/modules/upload_tmp/zz-diagnose_kolibri/zip/zz-diagnose_kolibri/rachel-index.php
======= Running finish_install.sh =======
SETUP: Starting Kolibri diagnostic
SETUP: Checking mounted drives
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0rpmb 179:24 0 4M 0 disk
mmcblk0boot0 179:8 0 4M 1 disk
sda 8:0 0 447.1G 0 disk
-sda1 8:1 0 447.1G 0 part /.data mmcblk0boot1 179:16 0 4M 1 disk mmcblk0 179:0 0 28.8G 0 disk |-mmcblk0p2 179:2 0 20.5G 0 part / |-mmcblk0p3 179:3 0 7.9G 0 part [SWAP] -mmcblk0p1 179:1 0 512M 0 part /boot/efi
SETUP: Getting Kolibri version
kolibri, version 0.14.7
SETUP: Getting Kolibri status
● kolibri.service - LSB: kolibri daemon, an offline education platform
Loaded: loaded (/etc/init.d/kolibri; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2022-01-12 20:57:17 WAT; 10min ago
Process: 817 ExecStart=/etc/init.d/kolibri start (code=exited, status=1/FAILURE)
Jan 12 20:57:16 CMAL-871f kolibri[817]: return callback(*args, **kwargs)
Jan 12 20:57:16 CMAL-871f kolibri[817]: File “/usr/lib/python3/dist-packages/kolibri/utils/cli.py”, line 518, in start
Jan 12 20:57:16 CMAL-871f kolibri[817]: recreate_diskcache()
Jan 12 20:57:16 CMAL-871f kolibri[817]: File “/usr/lib/python3/dist-packages/kolibri/deployment/default/cache.py”, line 27, in recreate_diskcache
Jan 12 20:57:16 CMAL-871f kolibri[817]: os.mkdir(diskcache_location)
Jan 12 20:57:16 CMAL-871f kolibri[817]: FileExistsError: [Errno 17] File exists: ‘/root/.kolibri/process_cache’
Jan 12 20:57:17 CMAL-871f systemd[1]: kolibri.service: Control process exited, code=exited status=1
Jan 12 20:57:17 CMAL-871f systemd[1]: Failed to start LSB: kolibri daemon, an offline education platform.
Jan 12 20:57:17 CMAL-871f systemd[1]: kolibri.service: Unit entered failed state.
Jan 12 20:57:17 CMAL-871f systemd[1]: kolibri.service: Failed with result ‘exit-code’.
SETUP: Stopping Kolibri
Failed to stop Kolibri.service: Unit Kolibri.service not loaded.
SETUP: Deleting root Kolibri cache
rm: cannot remove ‘/root/.kolibri/process_cache/cache.db-wal’: Structure needs cleaning
rm: cannot remove ‘/root/.kolibri/process_cache/cache.db-shm’: Structure needs cleaning
SETUP: Removing process cache
rm: cannot remove ‘/.data/RACHEL/.kolibri/process_cache/cache.db-wal’: Structure needs cleaning
rm: cannot remove ‘/.data/RACHEL/.kolibri/process_cache/cache.db-shm’: Structure needs cleaning
SETUP: Restarting Kolibri
Job for kolibri.service failed because the control process exited with error code. See “systemctl status kolibri.service” and “journalctl -xe” for details.
SETUP: Checking Kolibri status
● kolibri.service - LSB: kolibri daemon, an offline education platform
Loaded: loaded (/etc/init.d/kolibri; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2022-01-12 21:08:08 WAT; 30ms ago
Process: 5883 ExecStart=/etc/init.d/kolibri start (code=exited, status=1/FAILURE)
Jan 12 21:08:07 CMAL-871f kolibri[5883]: diskcache_cache.clear()
Jan 12 21:08:07 CMAL-871f kolibri[5883]: File “/usr/lib/python3/dist-packages/kolibri/dist/diskcache/core.py”, line 2194, in clear
Jan 12 21:08:07 CMAL-871f kolibri[5883]: return self._select_delete(select, args, retry=retry)
Jan 12 21:08:07 CMAL-871f kolibri[5883]: File “/usr/lib/python3/dist-packages/kolibri/dist/diskcache/core.py”, line 2205, in _select_delete
Jan 12 21:08:07 CMAL-871f kolibri[5883]: rows = sql(select, args).fetchall()
Jan 12 21:08:07 CMAL-871f kolibri[5883]: sqlite3.OperationalError: no such table: Cache
Jan 12 21:08:08 CMAL-871f systemd[1]: kolibri.service: Control process exited, code=exited status=1
Jan 12 21:08:08 CMAL-871f systemd[1]: Failed to start LSB: kolibri daemon, an offline education platform.
Jan 12 21:08:08 CMAL-871f systemd[1]: kolibri.service: Unit entered failed state.
Jan 12 21:08:08 CMAL-871f systemd[1]: kolibri.service: Failed with result ‘exit-code’.
SETUP: Finished Kolibri Diagnostic
======= Upload and Install Complete =======
Unfortunately I think we may be seeing filesystem errors. Is it possible the power went out at any point or the device was not shut down properly?
To try to fix this you will need a computer on the same network as the RACHEL-Plus. From there, we will need to access the device and run some commands to see if there are filesystem errors. Is it possible to connect this device to your network with a PC?
The other option is to do a USB recovery to factory state.
Hi, @jamesk
Is connecting the device to a network with a PC the same as connecting to the RACHEL-Plus using a PC? If not, can you please walk me through how to make the connection?
Does the option of USB recovery to factory state require us to re-download the entire content the device was pre-loaded with?
