apparently installing mod_wsgi was not the instant get out of trouble
card.
For a while i had problem with mod_wsgi settings. Now the trouble with
modules continues. I think i must somehow finally fix all the paths.
current error is :
[Sun Aug 16 12:38:22 2009] [error] [client 127.0.0.1] raise
ImproperlyConfigured("Error loading MySQLdb module: %s" % e)
[Sun Aug 16 12:38:22 2009] [error] [client 127.0.0.1]
ImproperlyConfigured: Error loading MySQLdb module: No module named
MySQLdb
Alan
On Aug 16, 2:56 pm, zayatzz <alan.kesselm...@gmail.com> wrote:
> z...@zayatzz:/var/log/apache2$ ls -las /usr/local/lib/python2.6/site-
> packages
> total 27
> 0 drwxrwsr-x 3 root staff 144 2009-08-16 12:09 .
> 19 drwxrwsr-x 26 root staff 19392 2009-08-16 10:54 ..
> 1 drwxr-sr-x 17 root staff 496 2009-08-16 12:09 django
> 4 -rw-r--r-- 1 root staff 947 2009-08-16 12:09 Django-1.1-
> py2.6.egg-info
> 4 -rw-r--r-- 1 root staff 119 2009-08-16 10:53 README
>
> I reinstalled it with ubuntu's aptitude. So as i get it,. i should
> recompile mod_python
>
> I was thinking about using mod_wsgi myself...
>
> I'll investigate mod_wsgi setup.
>
> Should i keep something in mind now that i have stackless instead of
> regular python?
>
> Alan.
>
> On Aug 16, 2:37 pm, Graham Dumpleton <graham.dumple...@gmail.com>
> wrote:
>
> > On Aug 16, 9:24 pm, zayatzz <alan.kesselm...@gmail.com> wrote:
>
> > > I did reinstall mod_python indeed.
>
> > Then you can't have installed it for that version of Python. Did you
> > use the --with-python option to 'configure' for mod_python to tell it
> > to use your alternate Python installation? That or the installed
> > mod_python is not readable to the user that Apache runs as. What do
> > you get for:
>
> > ls -las /usr/local/lib/python2.6/site-packages
>
> > You might want to also consider using mod_wsgi instead as simpler to
> > get working than mod_python.
>
> > Graham
>
> > > when i do import mod_python then :
>
> > > >>> import mod_python
>
> > > Traceback (most recent call last):
> > > File "<stdin>", line 1, in <module>
> > > ImportError: No module named mod_python
>
> > > so nope.... :(
>
> > > Alan
>
> > > On Aug 16, 2:01 pm, Graham Dumpleton <graham.dumple...@gmail.com>
> > > wrote:
>
> > > > Did you actually bother to reinstall mod_python after you nuked your
> > > > original Python installation. Likely when reinstalling it you lost
> > > > everything that was in prior site-packages and so are missing the
> > > > Python module component bits of mod_python, ie., no longer installed.
>
> > > > If from command line stackless Python you go:
>
> > > > import mod_python
>
> > > > does it actually find the module?
>
> > > > Graham
>
> > > > On Aug 16, 8:51 pm, zayatzz <alan.kesselm...@gmail.com> wrote:
>
> > > > > i begun to think about the same thing when i went through the log.
>
> > > > > Couldnt find anything useful why mod_python is failing atm, so i
> > > > > anyone can think of why this is not working - i still could use your
> > > > > help. Otherwise since it has nothing to do with django, i'll try to
> > > > > get help though stackoverflow and google :)
>
> > > > > Alan
>
> > > > > On Aug 16, 1:19 pm, Austin Gabel <aga...@gmail.com> wrote:
>
> > > > > > It looks like the issue is occurring when Apache tries to load
> > > > > > mod_python.
> > > > > > This doesn't have anything to do with Django at this point. You
> > > > > > may need to
> > > > > > do a bit more research on how Stackless Python works with Apache and
> > > > > > mod_python.
>
> > > > > > On Sun, Aug 16, 2009 at 5:04 AM, zayatzz
> > > > > > <alan.kesselm...@gmail.com> wrote:
>
> > > > > > > apache error log shows such stuff:
>
> > > > > > >http://dpaste.com/81241/
>
> > > > > > > Alan.
>
> > > > > > > On Aug 16, 12:12 pm, zayatzz <alan.kesselm...@gmail.com> wrote:
> > > > > > > > Hello
>
> > > > > > > > I installed stackless pyton 2.6.2 after reading several sites
> > > > > > > > that
> > > > > > > > said its fully compatible with vanilla python. After installing
> > > > > > > > i
> > > > > > > > found that my django applications do not work any more.
>
> > > > > > > > I did reinstall django (1.1) again and now im kind of lost. The
> > > > > > > > error
> > > > > > > > that i get is 500:
>
> > > > > > > > Internal Server Error
>
> > > > > > > > The server encountered an internal error or misconfiguration
> > > > > > > > and was
> > > > > > > > unable to complete your request.
>
> > > > > > > > Please contact the server administrator, webmas...@localhost and
> > > > > > > > inform them of the time the error occurred, and anything you
> > > > > > > > might
> > > > > > > > have done that may have caused the error.
>
> > > > > > > > More information about this error may be available in the
> > > > > > > > server error
> > > > > > > > log.
> > > > > > > > Apache/2.2.11 (Ubuntu) DAV/2 PHP/5.2.6-3ubuntu4.1 with
> > > > > > > > Suhosin-Patch
> > > > > > > > mod_python/3.3.1 Python/2.6.2 mod_ruby/1.2.6
> > > > > > > > Ruby/1.8.7(2008-08-11)
> > > > > > > > mod_ssl/2.2.11 OpenSSL/0.9.8g Server at 127.0.0.1 Port 80
>
> > > > > > > > Alan
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
