13.0 beta 7, problem while installing #6388

miyer03 · 2019-12-18T07:04:48Z

Observed behavior

After complete installation the kolibri page 127.0.0.1:8080 is not opening.

Expected behavior

Kolibri should open and give the login page at 127.0.0.1:8080

User-facing consequences

Cannot use Kolibri

Errors and logs

daemon.txt

kolibri.txt

Steps to reproduce

Try installing Kolibri using 13.0 beta 7 debian vesion

Context

Kolibri version 13.0 b7
Operating system Linux Mint 19.2 Tina
Browser Chrome and Firefox

miyer03 · 2019-12-18T07:05:50Z

This was done after complete uninstall of the previous version 12.9

lyw07 · 2019-12-18T18:37:49Z

I installed the unsigned kolibri 0.13.0 beta 7 Debian installer on a Linux Mint 19.2 VM but was unable to reproduce this issue

jonboiser · 2019-12-18T19:49:21Z

In the logs I'm seeing this error that might explain why there's a blank screen on the browser. I think these are very recent, since they appear at the bottom of daemon.txt.

I'm guessing the JS bundle isn't being built.

AttributeError: module 'kolibri.core.webpack.hooks' has no attribute 'WebpackInclusionHook'

In the code the main export of this module is called "WebpackBundleHook". But there is an export WebpackInclusionMixin? Is there code in the debian packager that's outdated?

jonboiser · 2019-12-18T20:04:33Z

@lyw07 Do you think it's relevant that this was done after uninstalling 0.12.9? That branch does have a kolibri.core.webpack.hooks.WebpackInclusionHook, but this was renamed or deleted in the 0.13 branch.

https://github.com/learningequality/kolibri/blob/release-v0.12.x/kolibri/core/webpack/hooks.py#L444

https://github.com/learningequality/kolibri/blob/release-v0.13.x/kolibri/core/webpack/hooks.py#L415

lyw07 · 2019-12-18T20:22:42Z

ah yeah it could be. I will test this on my VM. Thank you for the info!

lyw07 · 2019-12-18T21:00:25Z

I tried to install and uninstall 0.12.9 before installing 0.13.0beta7, but the file /usr/lib/python3/dist-packages/kolibri/plugins/learn/hooks.py that is causing the error doesn't exist after uninstalling 0.12.9.
I checked both the unsigned debian installer from github and the signed installer from PPA for 0.13.0beta7, but both of them don't contain this file.

rtibbles · 2019-12-18T21:05:22Z

@miyer03 was this server running just Kolibri or also the Kolibri server package? I wonder if uwsgi was still initialized and nginx not properly restarted, and hence looking for non existent python modules from the previous version.

miyer03 · 2019-12-19T06:06:01Z

@rtibbles I had kolibri-server running in the system. I tried to uninstall completey by running sudo apt-get remove kolibri-server , sudo apt-get remove kolibri, pip uninstall kolibri and pip uninstall kolibri-server. Please let me know if anything else needed to be done. Since, most of the classroom currently are on 12.8 or 0.9.5b3 any specific steps need to be followed to uninstall the previous version and install the new version when we go to schools so that the DB is not corrupted.

jredrejo · 2019-12-19T07:56:52Z

hi @miyer03 , don't do pip uninstall kolibri-server as kolibri-server is not a pip package.
In any case, in order to try to reproduce it, let me know if I understood correctly the steps you did:

You had kolibri-server + kolibri 0.12.9 installed (using deb packages, not pip)
You did apt-get remove kolibri-server kolibri
You installed the kolibri 0.13.0 beta 7 deb package

and then, the package didn't start kolibri and you saw the blank screen in the browser
is it correct?

also , can you try to do sudo kolibri stop , sudo service nginx restart to ensure there's not a remaining config from kolibri-server active, and then sudo kolibri start

I will try to reproduce the problem if you can confirm the above steps are correct.

miyer03 · 2019-12-19T08:05:34Z

@jredrejo You are correct. I don't think nginx is there in my system now. 12.9 was not completely uninstalled hence tried pip uninstall. I could be wrong there. If you are available now. I can try giving remote access if that works for you to understand better.

Its still showing blank page

jredrejo · 2019-12-19T10:46:31Z

f you are available now. I can try giving remote access if that works for you to understand better.

I don't think I will have a chance to connect before 15:30 pm GMT. Having a remote access would make it much easier, would it be possible to access at that time?

miyer03 · 2019-12-20T09:45:42Z

@jredrejo @indirectlylit not sure if this is a bug or installation issue. To make sure this doesn't happen could be please highlight the steps if the current server is either using a older version of pex or deb file and also, if it uses the kolibri-server. This is because once we roll out in school, the upgradation happens smoothly and we also don't end up loosing any data.

indirectlylit · 2019-12-20T16:52:18Z

Thanks @miyer03

Yes we've been testing various upgrade paths to make things smooth, but so far we haven't been able to reproduce this. I'll talk with the team and see if there are any "best practices" we can advise on for upgrading

miyer03 · 2020-01-06T06:38:08Z

I am not able to install new kolibri in my system. This is a test server and hence not worried on any previous DB. Is there any way to do a clean install or do I need to reformat the system.

daemon.txt
kolibri.txt

jredrejo · 2020-01-06T15:09:22Z

I am not able to install new kolibri in my system. This is a test server and hence not worried on any previous DB. Is there any way to do a clean install or do I need to reformat the system.

daemon.txt
kolibri.txt

Hello @miyer03 about your latest message, looking at the logs I see two problems:

Permissions problems in the /home/kolibri/.kolibri folder
The installation is upgrading the configs from a previous beta to the stable release, and it can't, likely due to the permission problems

If you're not worried for a previous db, can you delete the /home/kolibri/.kolibri and restart the daemon or the application so it creates a new config folder from scratch?

miyer03 · 2020-01-09T05:12:56Z

I dropped kolibri, deleted the folder and started kolibri but still the same issue. I tried to restart both kolibri and kolibri-server.

daemon.txt
kolibri.txt

lyw07 · 2020-01-09T06:07:38Z

thank you so much @miyer03 for checking and helping us debug the issue!
In the log file, I see this:

 File "/usr/lib/python3/dist-packages/kolibri/dist/django/template/backends/django.py", line 126, in get_package_libraries
    module = import_module(entry[1])
  File "/usr/lib/python3.6/import-lib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "./kolibri/plugins/learn/templatetags/learn_tags.py", line 21, in <module>
    from .. import hooks
  File "./kolibri/plugins/learn/hooks.py", line 8, in <module>
    class LearnSyncHook(webpack_hooks.WebpackInclusionHook):
AttributeError: module 'kolibri.core.webpack.hooks' has no attribute 'WebpackInclusionHook'

The issue still comes from the file ./kolibri/plugins/learn/hooks.py, which existed in 0.12.x versions but has been deleted in 0.13.0. but the version in the log file did indicate that you installed 0.13.0.

Do you mind checking the result of the following command?

ls -l /usr/lib/python3/dist-packages/kolibri/plugins/learn/

Also what is the output when you run

> python3.6
>>> import kolibri
>>> kolibri.__file__
>>> kolibri.__version__

thank you!

miyer03 · 2020-01-10T05:44:03Z

Hi @lyw07 attached the screen shot with the output. Have tried to install kolibri server

lyw07 · 2020-01-10T06:13:23Z

thank you! with this, we can confirm that although the version says 0.13.0, somehow part of the code is still 0.12.9.
I tried with installing kolibri 0.13.0 directly on top of 0.12.9, but still unable to reproduce the error.

do you mind trying uninstall kolibri and install it again with the following steps?

sudo apt-get purge kolibri
ls -l /usr/lib/python3/dist-packages/kolibri    <-- to check whether kolibri package has been fully removed
sudo dpkg -i kolibri_0.13.0-0ubuntu1_all.deb (or any kolibri installation you would prefer)

please let us know if you continue to see the issue. thank you so much for your patience!

miyer03 · 2020-01-10T06:19:54Z

@lyw07 for the last step I need to download the package from the website, correct ? Also will the steps remove kolibri-server as well

lyw07 · 2020-01-10T06:26:58Z

@miyer03 I'm sorry I forgot that you also have kolibri-server installed. Then step one would remove kolibri as well as kolibri-server at the same time. Do you have any configurations on kolibri-server that you need to save?
in this case, the last step would be sudo apt-get install kolibri-server.
sorry for the confusion

miyer03 · 2020-01-10T06:27:49Z

Screenshots after the first 2 steps

lyw07 · 2020-01-10T06:32:27Z

could you try

pip3 uninstall kolibri

or if that doesn't work

sudo pip3 uninstall kolibri

does either of these command remove that folder?

miyer03 · 2020-01-10T06:34:59Z

Attached the screenshot. Would you be comfortable with remote access. I can try giving you that now if that works.

lyw07 · 2020-01-10T06:35:59Z

sure that works for me :)

miyer03 · 2020-01-10T06:39:19Z

@lyw07 could you help me with the steps and the your email id. my email is manoj.iyer@motivationforexcellence.org

lyw07 · 2020-01-10T06:41:56Z

@miyer03 oh I'm sorry I can't recall the steps using things such as teamviewer right out of my mind currently.
instead of letting me access to your server remotely, do you mind trying one last thing sudo rm -rf /usr/lib/python3/dist-packages/kolibri and check if you can successfully remove the folder? since we have uninstalled kolibri entirely, it should be safe to remove it.

miyer03 · 2020-01-10T06:45:57Z

Here is the screen shot

lyw07 · 2020-01-10T06:50:45Z

thank you! I have sent you an email with steps to allow me to access your server remotely. My email is lingyi@learningequality.org

miyer03 · 2020-01-10T08:51:42Z

thanks @lyw07 for helping install kolibri

indirectlylit · 2020-01-20T21:05:57Z

@lyw07 would you mind posting a short summary of what the problem was

lyw07 · 2020-01-20T21:40:47Z

@indirectlylit I'm sorry I'm not too sure what caused the problem, but the issue was that when 0.13.0 was installed, the old version of 0.12.9 was uninstalled uncleanly with sudo apt-get purge kolibri. To resolve this issue, I uninstalled 0.13.0, removed the remaining kolibri files for 0.12.9 in /usr/lib/python3/dist-packages/kolibri and reinstalled kolibri 0.13.0.

I'm not able to reproduce this error when upgrading from 0.12.9 to 0.13.0 on my Linux Mint VM though

indirectlylit · 2020-01-21T01:38:36Z

thank you!

indirectlylit added this to the 0.13.0 milestone Dec 18, 2019

indirectlylit added bug Behavior is wrong or broken P0 - critical Priority: Release blocker or regression labels Dec 18, 2019

indirectlylit added P1 - important Priority: High impact on UX and removed P0 - critical Priority: Release blocker or regression labels Dec 19, 2019

indirectlylit modified the milestones: 0.13.0, 0.13.1 Dec 19, 2019

indirectlylit mentioned this issue Dec 20, 2019

document any best practices related to upgrading and trying new versions and installation methods learningequality/kolibri-docs#148

Closed

indirectlylit removed this from the 0.13.1 milestone Dec 20, 2019

indirectlylit added the TODO: needs clarification Insufficient information to proceed label Dec 20, 2019

miyer03 closed this as completed Jan 12, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

13.0 beta 7, problem while installing #6388

13.0 beta 7, problem while installing #6388

miyer03 commented Dec 18, 2019

miyer03 commented Dec 18, 2019

lyw07 commented Dec 18, 2019

jonboiser commented Dec 18, 2019 •

edited

jonboiser commented Dec 18, 2019

lyw07 commented Dec 18, 2019

lyw07 commented Dec 18, 2019 •

edited

rtibbles commented Dec 18, 2019

miyer03 commented Dec 19, 2019

jredrejo commented Dec 19, 2019

miyer03 commented Dec 19, 2019 •

edited

jredrejo commented Dec 19, 2019

miyer03 commented Dec 20, 2019

indirectlylit commented Dec 20, 2019

miyer03 commented Jan 6, 2020

jredrejo commented Jan 6, 2020

miyer03 commented Jan 9, 2020 •

edited

lyw07 commented Jan 9, 2020

miyer03 commented Jan 10, 2020 •

edited

lyw07 commented Jan 10, 2020 •

edited

miyer03 commented Jan 10, 2020 •

edited

lyw07 commented Jan 10, 2020

miyer03 commented Jan 10, 2020

lyw07 commented Jan 10, 2020

miyer03 commented Jan 10, 2020

lyw07 commented Jan 10, 2020

miyer03 commented Jan 10, 2020

lyw07 commented Jan 10, 2020 •

edited

miyer03 commented Jan 10, 2020

lyw07 commented Jan 10, 2020

miyer03 commented Jan 10, 2020

indirectlylit commented Jan 20, 2020

lyw07 commented Jan 20, 2020

indirectlylit commented Jan 21, 2020

13.0 beta 7, problem while installing #6388

13.0 beta 7, problem while installing #6388

Comments

miyer03 commented Dec 18, 2019

Observed behavior

Expected behavior

User-facing consequences

Errors and logs

Steps to reproduce

Context

miyer03 commented Dec 18, 2019

lyw07 commented Dec 18, 2019

jonboiser commented Dec 18, 2019 • edited

jonboiser commented Dec 18, 2019

lyw07 commented Dec 18, 2019

lyw07 commented Dec 18, 2019 • edited

rtibbles commented Dec 18, 2019

miyer03 commented Dec 19, 2019

jredrejo commented Dec 19, 2019

miyer03 commented Dec 19, 2019 • edited

jredrejo commented Dec 19, 2019

miyer03 commented Dec 20, 2019

indirectlylit commented Dec 20, 2019

miyer03 commented Jan 6, 2020

jredrejo commented Jan 6, 2020

miyer03 commented Jan 9, 2020 • edited

lyw07 commented Jan 9, 2020

miyer03 commented Jan 10, 2020 • edited

lyw07 commented Jan 10, 2020 • edited

miyer03 commented Jan 10, 2020 • edited

lyw07 commented Jan 10, 2020

miyer03 commented Jan 10, 2020

lyw07 commented Jan 10, 2020

miyer03 commented Jan 10, 2020

lyw07 commented Jan 10, 2020

miyer03 commented Jan 10, 2020

lyw07 commented Jan 10, 2020 • edited

miyer03 commented Jan 10, 2020

lyw07 commented Jan 10, 2020

miyer03 commented Jan 10, 2020

indirectlylit commented Jan 20, 2020

lyw07 commented Jan 20, 2020

indirectlylit commented Jan 21, 2020

jonboiser commented Dec 18, 2019 •

edited

lyw07 commented Dec 18, 2019 •

edited

miyer03 commented Dec 19, 2019 •

edited

miyer03 commented Jan 9, 2020 •

edited

miyer03 commented Jan 10, 2020 •

edited

lyw07 commented Jan 10, 2020 •

edited

miyer03 commented Jan 10, 2020 •

edited

lyw07 commented Jan 10, 2020 •

edited