Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Do sanity checks before launching Kolibri
See original GitHub issueHigh-level tracking issue
This is to track different issues that can cause kolibri start fail. It is originally from the discussion in a PR: https://github.com/learningequality/kolibri/pull/3273#issuecomment-369713552
Over-all requirements for start-up checks: Execution time should be very short, and failures should supply user guidance.
Furthermore, failures in checks should be an actual API that is usable for a UI. Suggesting return codes w/ descriptions available in a dictionary in kolibri.cli or likewise.
We should do several sanity checks before starting Kolibri:
- port is available https://github.com/learningequality/kolibri/issues/2867 and https://github.com/learningequality/kolibri/issues/3048
- database connection successful: Catch corruption / malformed exceptions, show user guidance https://github.com/learningequality/kolibri/issues/3228 #3332
- available disk space
-
KOLIBRI_HOMEis writable
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Request for integrity checks: https://github.com/learningequality/kolibri/issues/4539
@lyw07 thanks for opening this! I’ve edited the description