Weblate: Module not found: 'django', no module named 'phply', etc

Created on 21 Nov 2020  路  22Comments  路  Source: WeblateOrg/weblate

Describe the issue

The console logs say that module 'phply' is not not found.

On the web server side side there is a bunch of error logs saying no module named 'django'. My setup is a wsgi.py file in /var/www/html to avoid possible permission issues as I've read that parent directories should be accessible as well. The errors continue further like "wsgi.py cannot be loaded as Python module" and so on.

I've wasted 20+ hours with a bunch of critical bugs of Weblate that "were fixed" (like the examples/ indicating that python-path be used instead of python-home which made me add up lot of more hours of googling). I'm now having the error no module named django in Apache. When I visit the website it returns a 500 Internal Server Error.

I already tried

I have already searched the docs and many of the information, not to sound rude, misinformation. I've had to Google many things that the documentation didn't detail.

To Reproduce

Steps to reproduce the behavior:

  1. Login to SSH.
  2. Go to /home/weblate-env where Weblate is installed.
  3. Go down to the bin subdirectory.
  4. Activate the virtual environment with source activate.
  5. See the error in the console.

Expected behavior

I should be able to access Weblate website normally.

Server configuration and status

  • Weblate: 4.3.2

    • Django: 3.1.3

    • siphashc: 2.1

    • Whoosh: 2.7.4

    • translate-toolkit: 3.2.0

    • lxml: 4.6.1

    • Pillow: 8.0.1

    • bleach: 3.2.1

    • python-dateutil: 2.8.1

    • social-auth-core: 3.3.3

    • social-auth-app-django: 4.0.0

    • django-crispy-forms: 1.9.2

    • oauthlib: 3.1.0

    • django-compressor: 2.4

    • djangorestframework: 3.12.2

    • django-filter: 2.4.0

    • django-appconf: 1.0.4

    • user-agents: 2.2.0

    • filelock: 3.0.12

    • setuptools: 50.3.2

    • jellyfish: 0.8.2

    • openpyxl: 3.0.5

    • celery: 4.4.7

    • kombu: 4.6.11

    • translation-finder: 2.5

    • weblate-language-data: 2020.11

    • html2text: 2020.1.16

    • pycairo: 1.20.0

    • pygobject: 3.38.0

    • diff-match-patch: 20200713

    • requests: 2.24.0

    • Platform: Linux 4.15.0-123-generic (x86_64)

Weblate deploy checks


SystemCheckError: System check identified some issues:
at: No module named 'phply'
        HINT: https://docs.weblate.org/en/weblate-4.3.2/admin/install.html
#optional-deps
?: (weblate.W025.php) Failure in loading handler for php file format: No m
odule named 'phply'
        HINT: https://docs.weblate.org/en/weblate-4.3.2/admin/install.html
#optional-deps
?: (weblate.W025.srt) Failure in loading handler for srt file format: aeid
on or gaupol package required for Subtitle support
        HINT: https://docs.weblate.org/en/weblate-4.3.2/admin/install.html
#optional-deps
?: (weblate.W025.ssa) Failure in loading handler for ssa file format: aeid
on or gaupol package required for Subtitle support
        HINT: https://docs.weblate.org/en/weblate-4.3.2/admin/install.html
#optional-deps
?: (weblate.W025.sub) Failure in loading handler for sub file format: aeid
on or gaupol package required for Subtitle support
        HINT: https://docs.weblate.org/en/weblate-4.3.2/admin/install.html
#optional-deps
?: (weblate.W033.Gerrit) Failure in loading VCS module for Gerrit: git: 'r
eview' is not a git command. See 'git --help'.
 (1)
        HINT: https://docs.weblate.org/en/weblate-4.3.2/vcs.html
?: (weblate.W033.Mercurial) Failure in loading VCS module for Mercurial: [
Errno 2] No such file or directory: 'hg': 'hg'
        HINT: https://docs.weblate.org/en/weblate-4.3.2/vcs.html
?: (weblate.W033.Subversion) Failure in loading VCS module for Subversion:
 git: 'svn' is not a git command. See 'git --help'.
The most similar commands are
        fsck
        mv
        show
 (1)
        HINT: https://docs.weblate.org/en/weblate-4.3.2/vcs.html
INFOS:
?: (weblate.I021) Error collection is not set up, it is highly recommended
 for production use
        HINT: https://docs.weblate.org/en/weblate-4.3.2/admin/install.html
#collecting-errors
?: (weblate.I028) Backups are not configured, it is highly recommended for
 production use
        HINT: https://docs.weblate.org/en/weblate-4.3.2/admin/backup.html
System check identified 19 issues (1 silenced).

Exception traceback

Additional context

Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-123-generic x86_64)

question
Source
picture ecokevinkevin

All 22 comments

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you!

github-actions[bot] picture github-actions[bot] on 21 Nov 2020
👎1

The errors are module phply not found, and so on.

Please read the docs on the optional deps, it's linked from the warning: https://docs.weblate.org/en/weblate-4.3.2/admin/install.html#optional-deps

On the Apache side there is a bunch of erorr logs saying "no module named 'django'"

Most likely Apache mod_wsgi is not configured to use virtualenv. Check python-home setting there, see https://docs.weblate.org/en/latest/admin/install.html#apache

nijel picture nijel on 21 Nov 2020

Thank you, the warning can be ignored then. but I can confirm that python-path is set. python-home errors a wsgi not found error, which would be further behind the error I am reporting if I'm not wrong.

ecokevinkevin picture ecokevinkevin on 22 Nov 2020

These configure different things, check mod_wsgi docs for more info. In case you are using virtualenv, you need to set python-home to point to it. If that leads to other errors, these have to be fixed and not hiding them by not using it...

nijel picture nijel on 22 Nov 2020

I've tried a few times with virtualenv and it still errored, but as you say we can't ignore other errors. The error that i get with and withot virtualenv is now:

Sun Nov 22 14: 19: 12.314821 2020] [wsgi: error] [pid 22375] (13) Permission denied: [remote 186.106.169.35:62999] mod_wsgi (pid = 22375, process = 'weblate', application = '') : Call to fopen () failed for '/var/www/html/wsgi.py'.

After granting permissions I took off, the error log is back to:

[Sun Nov 22 14:27:36.531823 2020] [wsgi:error] [pid 22375] [remote X:63190] mod_wsgi (pid=22375): Exception occurred processing WSGI script '/var/www/html/wsgi.py'.
[Sun Nov 22 14:27:36.538946 2020] [wsgi:error] [pid 22375] [remote X:63190] Traceback (most recent call last):
[Sun Nov 22 14:27:36.538974 2020] [wsgi:error] [pid 22375] [remote X:63190]   File "/var/www/html/wsgi.py", line 35, in <module>
[Sun Nov 22 14:27:36.538977 2020] [wsgi:error] [pid 22375] [remote X:63190]     from django.core.wsgi import get_wsgi_application
[Sun Nov 22 14:27:36.539011 2020] [wsgi:error] [pid 22375] [remote X:63190] ModuleNotFoundError: No module named 'django'
ecokevinkevin picture ecokevinkevin on 22 Nov 2020

/var/www/html/wsgi.py

Seems wrong, it should be weblate/wsgi.py. Copying single file out of installation will not make it magically work.

No module named 'django'

It still is not using the virtualenv where all the dependencies are installed.

Please start from the example configuration and adjust paths and Python version there.

In case you cannot configure Apache to run wsgi, install Weblate using Docker way fewer things can go wrong there...

nijel picture nijel on 23 Nov 2020

I moved the wsgi.py file back to the virtualenv. Now I'm getting a 403 forbidden error, and the same I started with, added to these logs:

Tue Nov 24 03:09:44.787367 2020] [core:error] [pid 30947] (13)Permission denied: [client X:60557] AH00035: access to / denied (filesystem path '/root/weblate-env') because search permissions are missing on a component of the path
ecokevinkevin picture ecokevinkevin on 24 Nov 2020

The issue you have reported is resolved now. If you don鈥檛 feel it鈥檚 right, please follow it鈥檚 labels to get a clue and take further steps.

  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, don鈥檛 hesitate to support Weblate by making a donation.
github-actions[bot] picture github-actions[bot] on 24 Nov 2020

@nijel I am thinking of opening a separate issue for the permission error. Should I or can we continue here?

ecokevinkevin picture ecokevinkevin on 24 Nov 2020

Installing things in /root/ which can be only opened by the root user is usually bad idea. Create separate user for that or install things elsewhere (for example /opt/weblate).

nijel picture nijel on 24 Nov 2020
👍1

@nijel I have done everything you said. I am back to the same scheme, I've fixed the 403 Forbidden error, and now we are back to the same 500 Internal Server Error in the new directory. "No module named django" is the error that I'm getting. I've given permissions to Apache, chmod'ed, changed from /root to /var, from /var to /home now.

ecokevinkevin picture ecokevinkevin on 1 Dec 2020

The error tells that Python interpreter in wsgi can not find django module. As you've installed it in a virtual env, something in the configuration is broken. Do you have set python-home=/home/weblate-env?

nijel picture nijel on 1 Dec 2020

@nijel I set again python-home, the error is the same:

[Tue Dec 01 15:21:26.944408 2020] [wsgi:error] [pid 30882] [remote X:62220] ModuleNotFoundError: No module named 'django'
[Tue Dec 01 15:21:27.420578 2020] [authz_core:error] [pid 30883] [client X:62221] AH01630: client denied by server configuration: /home/weblate-env/data, referer: http://198.50.157.155:8001/

The virtual host:

<VirtualHost *:8001>
    ServerAdmin [email protected]
    ServerName [email protected]

    Alias /favicon.ico /home/weblate-env/data/static/favicon.ico
    Alias /static/ /home/weblate-env/lib/python3.6/site-packages/data/static/

    <Directory /home/weblate-env/lib/python3.6/site-packages/data/static/>
        Require all granted
    </Directory>

    Alias /media/ /home/weblate-env/lib/python3.6/site-packages/data/media/
    <Directory /home/weblate-env/lib/python3.6/site-packages/data/media/>
        Require all granted
    </Directory>

    WSGIDaemonProcess www-data python-path=/home/weblate-env/lib/python3.6 python-home=/home/weblate-env
    WSGIProcessGroup www-data
    WSGIApplicationGroup %{GLOBAL}

    WSGIScriptAlias / /home/weblate-env/bin/wsgi.py
    WSGIPassAuthorization On

    <Directory /home/weblate-env/bin>
        <Files wsgi.py>
        Require all granted
        </Files>
    </Directory>

</VirtualHost>
ecokevinkevin picture ecokevinkevin on 1 Dec 2020

Are you using wsgi built with same python version as you virtual environment? Most distributions have separate package for the Python 3 version...

nijel picture nijel on 1 Dec 2020

Are you using wsgi built with same python version as you virtual environment? Most distributions have separate package for the Python 3 version...
@nijel I am using Python 2.7.17 CLI version and Python 3.6 in the virtual environment.

ecokevinkevin picture ecokevinkevin on 1 Dec 2020

I'm tasking about wsgi module, it has to be Python 3 version as well.

nijel picture nijel on 2 Dec 2020

I have confirmed to have an older version of Python 2.4 successfully uninstalled 2.4 and installed Python 3.6 after doing a symlink from /usr/bin/python3.6 to /usr/bin/python. After doing that, my config files WSGI* entries started working again. Now, I'm stuck with a syntax error on the apache2.conf which is not really on this file, as it includes all the modules. One of the modules is Python, and that module has anither include, the mod_wsgi.so which is not in my system. I am clueless of what to do now with this missing file because I could only get it to work installing default Python 2.4.

ecokevinkevin picture ecokevinkevin on 3 Dec 2020

The Python 3 version of wsgi is usually in a separate package. For example, in Debian it's libapache2-mod-wsgi-py3.

nijel picture nijel on 3 Dec 2020

@nijel I got this to work.

Error

manage.py is again outdated in all guides. You use django-admin.pyinstead. Even if you create your own django-admin.py file in the bin/ venv folder, it will permanently throw the "environment variable not set" error.

Solution

You have to set DJANGO_SETTINGS_MODULE and PYTHONPATH path set. First, I had to set PYTHONPATH to /home/weblate-env/lib/python3.6/site-packages, and DJANGO_SETTINGS MODULE to weblate.settings.

Error

After fixing that, a new error brought with MySQL:

#1071 - Specified key was too long; max key length is 767 bytes

Solution

I had to go to /etc/mysql/mariadb.cnf and set encoding of databases (actually tables) to UTF8 adding those lines:

character-set-server = utf8
collation-server = utf8_general_ci

Error

After doing migration again, with python-admin.py in /home/weblate/bin, tables already existed.

Solution

I had to delete the whole database and recreate it. After doing so, this command stopped failing.

Error

I was then stuck in a 404 Not Found error.

Solution

To fix it I had to navigate to :8081/weblate instead of :8081

Error

I then saw that CSS didn't load.

Solution

My Apache Alias directive was mapping /static/ when it had to be /weblate/static/ as I was accessing Weblate from /weblate.

Question: how do you set Weblate to be accessed rather in /?

ecokevinkevin picture ecokevinkevin on 4 Dec 2020

manage.py is again outdated in all guides. You use django-admin.pyinstead. Even if you create your own django-admin.py file in the bin/ venv folder, it will permanently throw the "environment variable not set" error.

Maybe it would be easier to follow the installation docs: https://docs.weblate.org/en/latest/admin/install/venv-debian.html#configuring-weblate

The file is present in the repo: https://github.com/WeblateOrg/weblate/blob/master/manage.py and is installed as weblate when installing Weblate. See https://docs.weblate.org/en/latest/admin/management.html

1071 - Specified key was too long; max key length is 767 bytes

Your setup will break once somebody types emojis or other higher Unicode plan chars, see https://docs.weblate.org/en/latest/admin/install.html#mysql-and-mariadb for proper setup.

After doing migration again, with python-admin.py in /home/weblate/bin, tables already existed.

I have no clue what you did, but it seems that you've truncated the tables at some point - the tables were there, but no content (where Django stores what migrations have been applied).

Question: how do you set Weblate to be accessed rather in /?

The easiest approach is usually to read the documentation. We have examples for both setups:

nijel picture nijel on 4 Dec 2020

I didn't type any emojis. I just followed the fix of enabling UTF-8 and it worked. The error hapenned suddenly during installation.

Thanks

ecokevinkevin picture ecokevinkevin on 4 Dec 2020

The issue you have reported is resolved now. If you don鈥檛 feel it鈥檚 right, please follow it鈥檚 labels to get a clue and take further steps.

  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, don鈥檛 hesitate to support Weblate by making a donation.
github-actions[bot] picture github-actions[bot] on 4 Dec 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

asereze picture asereze  路  4Comments
brauliobo picture brauliobo  路  3Comments
nijel picture nijel  路  3Comments
nblock picture nblock  路  5Comments
GabLeRoux picture GabLeRoux  路  3Comments