from django.db import connection, DatabaseError try: ...... except DatabaseError: connection._rollback()
On Wed, Jun 13, 2012 at 5:49 PM, Daniel França <daniel.fra...@gmail.com>wrote: > I recreated the database and still get the same error when executing a > simple "syncdb". > > Tried to change the database connection to sqlite.... and now I got the > error that the sqlite3 module isn't installed... I think my installation > is messed up. > > > On Tue, Jun 12, 2012 at 7:29 PM, Daniel França <daniel.fra...@gmail.com>wrote: > >> More information: >> I'd put a break point just before the crash >> then I've tested some database queries... and all of them crash with the >> error: **** DatabaseError: current transaction is aborted, commands >> ignored until end of transaction block* >> >> But if I access the database using psql it's working fine. >> >> >> On Tue, Jun 12, 2012 at 4:51 PM, Daniel França >> <daniel.fra...@gmail.com>wrote: >> >>> Thanks for the anwser >>> I've installed Haystack, and it was working fine local, but at the >>> server I got this error. >>> First I've tried to install haystack like I did local, using pip pip >>> install -e git+ >>> https://github.com/toastdriven/django-haystack.git@master#egg=django-haystack >>> >>> But at the server I got this error: >>> *Obtaining django-haystack from git+ >>> https://github.com/toastdriven/django-haystack.git@master#egg=django-haystack >>> * >>> * Cloning https://github.com/toastdriven/django-haystack.git (to >>> master) to /home/gemini/workspace/gemini_virtualenv/src/django-haystack* >>> *Cannot get remote repository information.* >>> *Perhaps git-update-server-info needs to be run there?* >>> * Complete output from command /usr/bin/git clone -q >>> https://github.com/toastdriven/django-haystack.git/home/gemini/workspace/gemini_virtualenv/src/django-haystack: >>> * >>> * * >>> *----------------------------------------* >>> *Command /usr/bin/git clone -q >>> https://github.com/toastdriven/django-haystack.git/home/gemini/workspace/gemini_virtualenv/src/django-haystack >>> failed with >>> error code 1 in None* >>> *Storing complete log in /root/.pip/pip.log* >>> >>> I don't know if it has something todo... but ok, I installed haystack >>> 2.0 manually from source. >>> >>> then I start to get that error, >>> then I've tried to enter admin page... I got the same error from >>> migrate... but with stacktrace so I could better analyse what's wrong. >>> and the site was aborting at a load data in db method in admin.py. >>> So I did comment that. >>> >>> The error persists, but now at a middleware from mezzanine CMS(I'm using >>> Mezzanine CMS) >>> So I commented this middleware too... the same error persists, now in a >>> view from a app that I use, when it tries to get the currente site data >>> from Site. >>> So I gave up, I don't believe that commenting code would solve anything, >>> I think there's something wrong before that, that is causing all this >>> problems... but I can't figure out what is wrong. >>> It starts to happen when I installed haystack, but I'm not sure if it's >>> the problem... >>> I've tried to run syncdb and migrate... but I got the same db error... >>> >>> The strange thing is that it's working fine on my local machine. >>> >>> >>> On Tue, Jun 12, 2012 at 3:52 PM, James Pyrich <ja...@pyrich.com> wrote: >>> >>>> You've got a database error lurking somewhere. >>>> >>>> I usually encounter this when syncdb needs to be run (to whit, >>>> ./manage.py syncdb). >>>> >>>> Have you added anything to installed apps that is not managed with >>>> South? >>>> >>>> If that's a dead end, see if you can enable SQL logging in the database >>>> (in PostgreSQL, the configuration directive is log_statement: >>>> http://www.postgresql.org/docs/9.1/static/runtime-config-logging.html#GUC-LOG-STATEMENT). >>>> Then you can watch the log while you execute the migrate command to see >>>> what's missing. >>>> >>>> Just be careful that doing this on a live system can cause downtime and >>>> chew up disk space if your logs aren't being rotated and you forget to >>>> disable logging. >>>> >>>> >>>> On 6/12/12 11:25 AM, Daniel França wrote: >>>> >>>> Hi all, >>>> I'm using South and it was working fine, >>>> but suddenly I start to get this error on the server that's driving me >>>> crazy: >>>> >>>> *(virtualenv)[root@localhost]# ./manage.py migrate accounts* >>>> *Traceback (most recent call last):* >>>> * File "./manage.py", line 35, in <module>* >>>> * execute_manager(settings)* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/django/core/management/__init__.py", >>>> line 459, in execute_manager* >>>> * utility.execute()* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/django/core/management/__init__.py", >>>> line 382, in execute* >>>> * self.fetch_command(subcommand).run_from_argv(self.argv)* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/django/core/management/base.py", >>>> line 196, in run_from_argv* >>>> * self.execute(*args, **options.__dict__)* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/django/core/management/base.py", >>>> line 232, in execute* >>>> * output = self.handle(*args, **options)* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/south/management/commands/migrate.py", >>>> line 107, in handle* >>>> * ignore_ghosts = ignore_ghosts,* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/south/migration/__init__.py", >>>> line 199, in migrate_app* >>>> * applied_all = check_migration_histories(applied_all, >>>> delete_ghosts, ignore_ghosts)* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/south/migration/__init__.py", >>>> line 72, in check_migration_histories* >>>> * for h in histories:* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/django/db/models/query.py", >>>> line 118, in _result_iter* >>>> * self._fill_cache()* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/django/db/models/query.py", >>>> line 875, in _fill_cache* >>>> * self._result_cache.append(self._iter.next())* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/django/db/models/query.py", >>>> line 291, in iterator* >>>> * for row in compiler.results_iter():* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/django/db/models/sql/compiler.py", >>>> line 763, in results_iter* >>>> * for rows in self.execute_sql(MULTI):* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/django/db/models/sql/compiler.py", >>>> line 818, in execute_sql* >>>> * cursor.execute(sql, params)* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/django/db/backends/util.py", >>>> line 40, in execute* >>>> * return self.cursor.execute(sql, params)* >>>> * File >>>> "/home/gemini/workspace/gemini_virtualenv/lib/python2.7/site-packages/django/db/backends/postgresql_psycopg2/base.py", >>>> line 52, in execute* >>>> * return self.cursor.execute(query, args)* >>>> *django.db.utils.DatabaseError: current transaction is aborted, >>>> commands ignored until end of transaction block* >>>> >>>> It's happening for every application that I try to migrate and I >>>> can't figure out why, >>>> I can't see anything clear in the error messages. >>>> Anyone has any idea about what's happening and how can I solve that?? >>>> >>>> Best Regards, >>>> Daniel França >>>> -- >>>> 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. >>>> >>>> -- >>>> 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. >>>> >>> >>> >> > -- > 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. > -- 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.
