Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8892203
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T22:56:25+00:00 2026-06-14T22:56:25+00:00

I am asking the following question here, because it involves developer tools. I have

  • 0

I am asking the following question here, because it involves developer tools.

I have upgraded my Ubuntu 10.04 LTS workstation to 12.04 LTS (32-bit). Today I went to try a Django web application that has been working without errors. It is running on Apache.

The application no longer works and returns an error. I have been working through a series of errors all located in /var/log/apache2/error.log.

The first error involved UCS2 and UCS4 (lines trimmed for readability).

ImportError: /usr/local/lib/python2.7/lib-dynload/_io.so: 
undefined symbol: PyUnicodeUCS2_FromObject
mod_wsgi (pid=9246): Target WSGI script 
'/usr/local/www/wsgi-scripts/wsgi_amr_handler.py' 
cannot be loaded as Python module.

That was cleared by rebuilding and re-installing the latest version of mod_wsgi.

The current error involves mysqldb not being a valid backend. Here is the error (timestamps removed for clarity):

backend = load_backend(db['ENGINE'])
File "/usr/local/lib/python2.7/site-packages/django/db/utils.py", line 51, 
in load_backend
raise ImproperlyConfigured(error_msg)
ImproperlyConfigured: 'mysql' isn't an available database backend.
Try using django.db.backends.mysql instead.
Error was: No module named mysql.base

Is this a configuration problem in the Django application’s settings.py or something else?

Is there an installation order for Python 2.7, mod_wsgi, Django, and mysqldb, and could that be the problem?

Here is my current (after receiving comments) settings.py

DATABASES = {
'default': {
'ENGINE': ' django.db.backends.mysql', 
'NAME': 'server',      # Or path to database file if using sqlite3.
'USER': 'ox',          # Not used with sqlite3.
'PASSWORD': 'xxxx',                  # Not used with sqlite3.
'HOST': '',     
'PORT': '',  
    }
}

Here are the errors:

ImproperlyConfigured: ' django.db.backends.mysql' isn't an available database backend.
Try using django.db.backends.XXX, where XXX is one of:
'dummy', 'mysql', 'oracle', 'postgresql_psycopg2', 'sqlite3'
Error was: No module named  django.db.backends.mysql.base
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-14T22:56:27+00:00Added an answer on June 14, 2026 at 10:56 pm

    You apparently upgraded you Django installation as well. Recent Django versions need the full name of the backend module. The way you specify databases was changed in version 1.2 and you’ll need to follow the upgrade notes to update your Django project codebase.

    For MySQL the correct backend is now django.db.backends.mysql; open settings.py and update your DATABASES entry.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Asking this question here because in CakePHP google group got no answer.I have the
I feel a bit silly for asking such a simple question but here goes...
Before asking my question, let me explain the context. CONTEXT: I have a web
Before asking a question, and before you all get mad because there are a
I struggled asking that question but here it is. I am using source control
I'm quite new to Java EE and I was asking myself the following question:
I am asking this question here as I could not find any conclusive results
In one form or another I encounter the following question often (posed, here, in
I'm re-asking a question that was previously deleted here in SO for not being
this is my first time asking a question here so apologies if I am

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.