I am trying to setup my local box to run my site with fastcgi. I want
to do this to mirror the way we have the site set up on our live
servers so I can work on implementing something like
http://soyrex.com/blog/django-nginx-and-memcached/.
I can run my site fine using django's test server, no errors or
anything. However if I do the following I get a ProgrammingError:
SAVEPOINT can only be used in transaction blocks error.
1. ./manage.py runfcgi host=127.0.0.1 port=3000 pidfile=/usr/local/
nginx/logs/byp.pid
2. start nginx
3. hit the same url that works with runserver.
Here is the error that shows up in nginx error logs:
2009/03/23 15:05:34 [error] 11755#0: *5 FastCGI sent in stderr:
"Traceback (most recent call last):
File "build/bdist.macosx-10.3-i386/egg/flup/server/fcgi_base.py",
line 558, in run
protocolStatus, appStatus = self.server.handler(self)
File "build/bdist.macosx-10.3-i386/egg/flup/server/fcgi_base.py",
line 1116, in handler
result = self.application(environ, start_response)
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/
python2.5/site-packages/django/core/handlers/wsgi.py", line 245, in
__call__
response = middleware_method(request, response)
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/
python2.5/site-packages/django/contrib/sessions/middleware.py", line
36, in process_response
request.session.save()
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/
python2.5/site-packages/django/contrib/sessions/backends/db.py", line
56, in save
sid = transaction.savepoint()
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/
python2.5/site-packages/django/db/transaction.py", line 190, in
savepoint
connection._savepoint(sid)
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/
python2.5/site-packages/django/db/backends/__init__.py", line 62, in
_savepoint
self.connection.cursor().execute(self.ops.savepoint_create_sql
(sid))
ProgrammingError: SAVEPOINT can only be used in transaction blocks"
while reading response header from upstream, client: 127.0.0.1,
server: byp, request: "GET /realestate/ HTTP/1.1", upstream:
"fastcgi://127.0.0.1:3000", host: "byp"
Here is what is happening in PostgreSQL:
LOG: duration: 0.365 ms statement: SELECT
"django_session"."session_key", "django_session"."session_data",
"django_session"."expire_date" FROM "django_session" WHERE
("django_session"."session_key" = '24259c268a8eddd4a32b5b0475ff6be9'
AND "django_session"."expire_date" > '2009-03-23 15:05:34.123882' )
ERROR: SAVEPOINT can only be used in transaction blocks
STATEMENT: SAVEPOINT s1610559488_x7
The error I was getting before was just a "connection already closed
error" until I changed the following in wsgi.py line 235-248:
# try:
try:
request = self.request_class(environ)
except UnicodeDecodeError:
response = http.HttpResponseBadRequest()
else:
response = self.get_response(request)
# Apply response middleware
for middleware_method in self._response_middleware:
response = middleware_method(request, response)
response = self.apply_response_fixes(request, response)
# finally:
# signals.request_finished.send(sender=self.__class__)
I am on trunk and using flup version flup-1.0.1 but the problem also
existed on django_1.0.2 and flup_0.5.
Thanks,
Peter
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
