Databases
StackOverflow2013
Postsdbo
PODjango: Manage.py runserver no error, but mod_wsgi report cannot import name connection
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango: Manage.py runserver no error, but mod_wsgi report cannot import name connection
    primarykey
    data
    text
    <p>When testing my django website by <code>python manage.py runserver 0.0.0.0:8000</code>, there is no error.</p> <p>But if I deploy it to production with apache and mod_wsgi, it reports error <code>cannot import name connection</code>.</p> <p>I find some other questions like <a href="https://stackoverflow.com/questions/11711536/django-1-4-database-router-cannot-import-name-connection">django 1.4 database router - &quot;cannot import name connection&quot;</a> suggesting adding <code>from django.db import connections</code> into settings.py.<br/></p> <p>But I found adding this import can prevent this error, but it also disables database router.</p> <p>I think it may due to different running environment between <code>manage.py runserver</code> and WSGI. This is how my wsgi.py looks like</p> <pre><code>import os import sys sys.path.insert(0,"/home/my/myweb") os.environ.setdefault("DJANGO_SETTINGS_MODULE", "mywebsite.settings") from django.core.wsgi import get_wsgi_application application = get_wsgi_application() </code></pre> <p>How can I fix this bug?</p> <p>My python version is 2.7 and django version is 1.4.3</p> <p><b>Edit 1:</b></p> <p>My OS is CentOS 6.4, on this server:</p> <p>If I run it using <code>python manage.py runserver 0.0.0.0:8000</code>, no error.</p> <p>If I remove database router, it can work under WSGI.</p> <p>But database router and WSGI cannot work together.</p> <p>Any advice is appreciated.</p> <p><b>Edit 2:</b></p> <p>Thanks to @Graham Dumpleton, I figured it out by myself.</p> <p>This is the wsgy.py that works for me.</p> <pre><code>import sys sys.path.insert(0, '/home/my/myweb') from mywebsite import settings import django.core.management django.core.management.setup_environ(settings) utility = django.core.management.ManagementUtility() command = utility.fetch_command('runserver') command.validate() import django.conf import django.utils django.utils.translation.activate(django.conf.settings.LANGUAGE_CODE) import django.core.handlers.wsgi application = django.core.handlers.wsgi.WSGIHandler() </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USshaun shia
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COwhat is your operating system?
      singulars
      1. PODjango: Manage.py runserver no error, but mod_wsgi report cannot import name connection
      1. USGianfranco Lemmo
    2. COCentOS release 6.4
      singulars
      1. PODjango: Manage.py runserver no error, but mod_wsgi report cannot import name connection
      1. USshaun shia
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload