Problem with syncdb about django-celery HOT 14 CLOSED

What version is this?

from django-celery.

djcelery 2.1.0
django 1.2.1
python 2.6.6rc1
modwsgi 3.2
debian testing 32 bits
rabbitmq-server 1.8.1
postgres 8.4

from django-celery.

ok, so the development version then. Do you know what table it's crashing on?

from django-celery.

i print the sql in /usr/lib/pymodules/python2.6/django/db/backends/util.py line 15 and i get this now:

DEBUG SELECT "django_content_type"."id", "django_content_type"."name", "django_content_type"."app_label", "django_content_type"."model" FROM "django_content_type" WHERE ("django_content_type"."model" = %s AND "django_content_type"."app_label" = %s )
DEBUG SELECT "django_content_type"."id", "django_content_type"."name", "django_content_type"."app_label", "django_content_type"."model" FROM "django_content_type" WHERE ("django_content_type"."model" = %s AND "django_content_type"."app_label" = %s )
DEBUG ('intervalschedule', 'djcelery')
DEBUG ('intervalschedule', 'djcelery')
DEBUG
SELECT c.relname
FROM pg_catalog.pg_class c
LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
WHERE c.relkind IN ('r', 'v', '')
AND n.nspname NOT IN ('pg_catalog', 'pg_toast')
AND pg_catalog.pg_table_is_visible(c.oid)
DEBUG
SELECT c.relname
FROM pg_catalog.pg_class c
LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
WHERE c.relkind IN ('r', 'v', '')
AND n.nspname NOT IN ('pg_catalog', 'pg_toast')
AND pg_catalog.pg_table_is_visible(c.oid)
DEBUG ()
DEBUG ()
Traceback (most recent call last):
File "manage.py", line 15, in
execute_manager(settings)
File "/usr/lib/pymodules/python2.6/django/core/management/init.py", line 438, in execute_manager
utility.execute()
File "/usr/lib/pymodules/python2.6/django/core/management/init.py", line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/pymodules/python2.6/django/core/management/base.py", line 191, in run_from_argv
self.execute(_args, *_options.dict)
File "/usr/lib/pymodules/python2.6/django/core/management/base.py", line 218, in execute
output = self.handle(_args, *_options)
File "/usr/lib/pymodules/python2.6/django/core/management/base.py", line 347, in handle
return self.handle_noargs(**options)
File "/usr/lib/pymodules/python2.6/django/core/management/commands/syncdb.py", line 55, in handle_noargs
tables = connection.introspection.table_names()
File "/usr/lib/pymodules/python2.6/django/db/backends/init.py", line 493, in table_names
return self.get_table_list(cursor)
File "/usr/lib/pymodules/python2.6/django/db/backends/postgresql/introspection.py", line 31, in get_table_list
AND pg_catalog.pg_table_is_visible(c.oid)""")
File "/usr/lib/pymodules/python2.6/django/db/backends/util.py", line 20, in execute
return self.cursor.execute(sql, params)
File "/usr/lib/pymodules/python2.6/django/db/backends/postgresql_psycopg2/base.py", line 44, in execute
return self.cursor.execute(query, args)
django.db.utils.DatabaseError: current transaction is aborted, commands ignored until end of transaction block

from django-celery.

could you pull from django-celery to see if the issue is resolved?

If that doesn't work, try removing the djcelery_* tables and syncdb again.

from django-celery.

from what branch? release20-maint

from django-celery.

master branch

from django-celery.

i think i can't because this: http://groups.google.com/group/celery-users/browse_thread/thread/8bdf8a2884be46da/b27e4af5f8a0507b?hl=en#b27e4af5f8a0507b

from django-celery.

Because it's the development branch? You already said you were running 2.1.0 above. I'm thinking this could be because of a short bug that was introduced in the master branch, you were just unlucky enough to pull at that time

from django-celery.

we must deploy the site tomorrow, i think i can test that maybe after the delivey, i really dont want take that risk today, are you agree?

from django-celery.

From your logs above:

DEBUG ('intervalschedule', 'djcelery')

This is a table from django-celery v2.1.0 (master branch),
so either you already are running this version, or this is a left-over
from an old installation.

If you've downgraded from 2.1.0, you need to drop all tables which name
starts with djcelery

from django-celery.

i think must be master branch because i drop the schema and always the table dj* are created in the second syncdb

from django-celery.

i pull from master and the error is corrected

from django-celery.

Great. That's good news. Closing the issue now,

from django-celery.