Hi,
I migrated my project to a new infrastructure but i kept the same versions
Apache 2.2 + mod_wsgi + python 2.6.1 + Django 1.2.1
I am trying to run my project and i am getting the below exception that
seems to be from Django and i need help pin pointing the exact cause,
because i think th
Hi,
I have migrated my project to a new installation of Apache + mod_wsgi 3.2.1
+ python 2.6.1 + Django 1.2.1, i kept the same versions just to be sure
that i do not have any problems with my project.
I am trying to run the project and i am getting this Oracle exception...
The DB is fine be
Hi Andreas,
I can connect using "python manage.py dbshell" it connects without any
error.
Is there a difference, if i am not mistaken the dbshell test shows that the
configuration of the DB is correct and that i can connect from the machine,
correct ?? From the stack trace it seems that the
Is there any way to find out where the problem occurs ?? Is there a way to
enable some debugging or trace in order to see which python scripts are
called in Django and find out where the whole process is failing ??
In the last lines of the stack trace it tries to close the connection and
for s
Well i have created the below test script to check if i am able to connect
to the DB using mod_wsgi and i get back the sysdate from the DB.. I have
configured mod_wsgi under the alias /test to execute the below script and i
always get the time.. So it seems that the configuration in mod_wsgi is
Hi Andreas,
I did the following test... i used "python manage.py runserver" and i was
able to use the admin page (http://127.0.0.1:8000/admin/) of Django and log
into the DB.
So that means the apache and the mod_wsgi as you said have a problem,
correct ???
Regars,
Alex
On Tuesday, Februa
6 matches
Mail list logo
