django 1.6.5 + python3 wsgi problems

Question

When I try to run my django project as a wsgi application, I get the following error in my app's error log:

Exception ignored in: <module 'threading' from '/usr/lib/python3.4/threading.py'>
Traceback (most recent call last):
File "/usr/lib/python3.4/threading.py", line 1288, in _shutdown
assert tlock is not None
AssertionError:

Versions:

python 3.4
Apache/2.4.7 (Ubuntu)
Django==1.6.5
Ubuntu 14.04 LTS 
libapache2-mod-wsgi-py3 installed

I already tried the following solution: https://code.djangoproject.com/ticket/22948 but it didn't help.

my apache config file looks like this:

    <VirtualHost *:9000>

    ServerName casinoadmin

    DocumentRoot /var/www/

    Alias /media/ /srv/casino-media/
    Alias /static/admin/ "/home/casinoadmin/virtualenvs/casinoadmin/lib/python3.4/site-packages/django/contrib/admin/static/admin/"
    Alias /static/ "/home/casinoadmin/current/casinoadmin/modules/packages/casinoadmin/casinoadminapp/static/"

    Header set Cache-Control "no-cache, must-revalidate"

    <IfModule mod_expires.c>
    <Location /media/status-images>
            ExpiresActive On
            ExpiresByType image/png A0
    </Location>
    </IfModule>


    WSGIDaemonProcess casinoadmin processes=1 threads=5 display-name=%{GROUP} python-path= /home/casinoadmin/virtualenvs/casinoadmin/lib/python3.4/site-packages/:/home/casinoadmin/current/casinoadmin/modules/packages:/home/casinoadmin/current/casinoadmin/conf:/home/casinoadmin/current/common:/home/casinoadmin/current/casinoadimn/modules/packages/casinoadmin
    WSGIScriptAlias /casinoadmin /var/www/casinoadmin/casinoadminwsgi.py process-group=casinoadmin application-group=%{GLOBAL}

    WSGIApplicationGroup %{GLOBAL}


    ErrorLog ${APACHE_LOG_DIR}/casinoadmin_error.log

    LogLevel warn

    CustomLog ${APACHE_LOG_DIR}/casinoadmin_access.log combined

    </VirtualHost>

You are likely using an older mod_wsgi. You should use mod_wsgi 4.2+ with Python 3.4. — Graham Dumpleton
– Graham Dumpleton, Commented Aug 21, 2014 at 0:47

Kompi · Accepted Answer · 2014-08-23 00:21:13Z

1

As Graham Dumpleton pointed out, compiling the latest mod_wsgi solved the problem.

answered Aug 23, 2014 at 0:21

Kompi

4945 silver badges20 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

django 1.6.5 + python3 wsgi problems

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related