Hi Ihar, ar., 2011.eko marren 15a 19:26(e)an, Ihar Hrachyshka(e)k idatzi zuen: > Hi all, > recently I've updated (with svn update) 2.1 branch to fresh code from > svn and now I get the following error in my apache error_log: > >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] mod_python >> (pid=28605, interpreter='pootle', phase='PythonHandler', >> handler='django.core.handlers.modpython'): Application error >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] ServerName: >> 'mounik.org' >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] DocumentRoot: >> '/home/booxter/public_html' >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] URI: '/pootle/' >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] Location: None >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] Directory: >> '/home/booxter/public_html/pootle/' >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] Filename: >> '/home/booxter/public_html/pootle/' >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] PathInfo: '' >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] Traceback (most >> recent call last): >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] File >> "/usr/lib64/python2.6/site-packages/mod_python/importer.py", line 1537, in >> HandlerDispatch\n default=default_handler, arg=req, silent=hlist.silent) >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] File >> "/usr/lib64/python2.6/site-packages/mod_python/importer.py", line 1229, in >> _process_target\n result = _execute_target(config, req, object, arg) >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] File >> "/usr/lib64/python2.6/site-packages/mod_python/importer.py", line 1128, in >> _execute_target\n result = object(arg) >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] File >> "/usr/lib64/python2.6/site-packages/django/core/handlers/modpython.py", line >> 228, in handler\n return ModPythonHandler()(req) >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] File >> "/usr/lib64/python2.6/site-packages/django/core/handlers/modpython.py", line >> 219, in __call__\n for chunk in response: >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] File >> "/usr/lib64/python2.6/site-packages/django/http/__init__.py", line 408, in >> next\n chunk = self._iterator.next() >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] File >> "/home/booxter/public_html/pootle/local_apps/pootle_misc/dbupdate.py", line >> 269, in staggered_update\n yield update_qualitychecks_21040() >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] File >> "/home/booxter/public_html/pootle/local_apps/pootle_misc/dbupdate.py", line >> 154, in update_qualitychecks_21040\n flush_quality_checks() >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] File >> "/home/booxter/public_html/pootle/local_apps/pootle_misc/dbupdate.py", line >> 38, in flush_quality_checks\n for store in >> Store.objects.filter(state=CHECKED).iterator(): >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] File >> "/usr/lib64/python2.6/site-packages/django/db/models/query.py", line 271, in >> iterator\n for row in compiler.results_iter(): >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] File >> "/usr/lib64/python2.6/site-packages/django/db/models/sql/compiler.py", line >> 677, in results_iter\n for rows in self.execute_sql(MULTI): >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] File >> "/usr/lib64/python2.6/site-packages/django/db/models/sql/compiler.py", line >> 732, in execute_sql\n cursor.execute(sql, params) >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] File >> "/usr/lib64/python2.6/site-packages/django/db/backends/postgresql_psycopg2/base.py", >> line 44, in execute\n return self.cursor.execute(query, args) >> [Tue Mar 15 19:55:46 2011] [error] [client 178.120.3.217] DatabaseError: >> current transaction is aborted, commands ignored until end of transaction >> block\n >
I haven't seen this error before and I don't have lots of experience with PostgreSQL, but from what I've read[1], that means the database operation has ended with error and there has been another query without rolling back the previous transaction. > And here is what I have on my web site: http://mounik.org/pootle > > The message tell smth like 'Database tables have build version 21010. > Pootle will update the database now.' Yes, that's a check done for upgrading purposes (schema changes etc.). If you look at the traceback you'll see it's trying to update the existing quality checks to a change introduced in Pootle 2.1.4, which was (quoting from the release announcement): "This release fixes a nasty bug where quality checks failed to update on file uploads. the upgrade screen will flash on first visit after upgrade for a minute or two to correct this problem (might take longer if you used the quality checks feature extensively)." > Any suggestions? > Well, I would try to shut down Pootle and rerun the updating process from the django shell. $ python manage.py shell (or django-admin shell) >>> from pootle_misc.dbupdate import flush_quality_checks >>> flush_quality_checks() Depending on the size of your installation, the operation may take a while. HTH. Julen. [1] http://stackoverflow.com/questions/2979369/databaseerror-current-transaction-is-aborted-commands-ignored-until-end-of-tran ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
