DatabaseError: current transaction is aborted, commands ignored until end of transaction block

I'm getting this error on my Django site.

My question is equivalent to this question on Stack Overflow: http://stackoverflow.com/questions/2979369/databaseerror-current-transaction-is-aborted-commands-ignored-until-end-of-tran

The answer given there was to look at the PostgreSQL logs to see what query was failing.

My question is how to find the PostgreSQL logs, or otherwise debug this issue, on WebFaction hosting?

postgresql logs django

asked Mar 04 '11 at 07:26

anentropic
8●2●7

3 Answers:

oldest newest most voted

The Postgre server on our side does almost no logging, and the its logs are common for all users hosted on the same machine - this is why you do not have access to them.

Please verify that the database name/username/password that you have in your settings.py are correct (you should be able to use the 'psql' connad-line utility to connect using the same settings).

answered Mar 04 '11 at 07:33

tie
1391●1●3

thanks, my db settings are correct and I can connect via psql command line... is there some way to monitor the query errors occurring in django from the psql command line?

(Mar 04 '11 at 07:38) anentropic

No, you can't see the queries from the psql console, but you can use some plugin like Django Debugtoolbar to monitor all your queries generated by your application. Instructions on installing DebugToolbar can be found at http://docs.webfaction.com/software/django/troubleshooting.html#using-the-django-debug-toolbar

(Mar 04 '11 at 08:02) tie

thanks, DebugToolbar wouldn't help in this case as the db error is causing an (Apache) 500 error and Django doesn't get to render anything to the browser. In the end I have been able to debug it by turning suspect apps off (django-denorm) in settings.py until I could get a Django error page which showed where my sql error was. Not a universal solution...

(Mar 04 '11 at 08:09) anentropic

agreed with anentropic here. no way to debug with django debug tool bar since the page doesn't get rendered. can webfaction allow logging on account basis at least for 24 hours for development purposes?

(Jul 17 '12 at 08:02) pubmedly

If you're getting an error 500 in the browser, then you can turn DEBUG on in your settings.py, which should render an error page to the browser. You can also look at your error logs under ~/logs/user/error_<appname>.log

(Jul 17 '12 at 08:15) todork

0	ok see this link https://docs.djangoproject.com/en/dev/ref/databases/ you can turn on this option in database settings temporarily to debug 'OPTIONS': { 'autocommit': True, } this will show you the sql error answered Jul 17 '12 at 08:22 pubmedly 1

I just had a simmilar error in an OSQA server I was trying to stand up. It turned out that I had the wrong password in the local_settings.py file for the database. Make sure you password is correct! After changing the password, make sure you restart apache, or the changes will not take effect

answered Jul 24 '12 at 11:58

dykeag
1

Your answer

If you have an answer to the above question, then use the form below. Otherwise, use the appropriate 'add new comment' button above to post your feedback.

toggle preview

community wiki

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Tags:

django ×643
postgresql ×69
logs ×16

Asked: Mar 04 '11 at 07:26

Seen: 3,790 times

Last updated: Jul 24 '12 at 11:58

DatabaseError: current transaction is aborted, commands ignored until end of transaction block

Follow this question

Got questions? We have answers!

Related questions