celery_taskmeta already exists

212 views
Skip to first unread message

nachouve

unread,
Aug 9, 2012, 6:36:36 AM8/9/12
to madron...@googlegroups.com
Hello,

A newby problem... I'm trying to get a madrona from the source-code on a debian server . All installation steps were correct, but when creating new madrona project after some success messages, the following error is thrown [1]. 

Where is my mistake?

Thank you.
Nacho V

[1]
Traceback (most recent call last):
  File "/var/tmp/madrona-env/bin/create-madrona-project.py", line 439, in <module>
    main()
  File "/var/tmp/madrona-env/bin/create-madrona-project.py", line 376, in main
    management.execute_manager(settings, ['manage.py','migrate'])
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/django/core/management/__init__.py", line 459, in execute_manager
    utility.execute()
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/django/core/management/__init__.py", line 382, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/django/core/management/base.py", line 196, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/django/core/management/base.py", line 232, in execute
    output = self.handle(*args, **options)
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/south/management/commands/migrate.py", line 108, in handle
    ignore_ghosts = ignore_ghosts,
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/south/migration/__init__.py", line 213, in migrate_app
    success = migrator.migrate_many(target, workplan, database)
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/south/migration/migrators.py", line 235, in migrate_many
    result = migrator.__class__.migrate_many(migrator, target, migrations, database)
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/south/migration/migrators.py", line 310, in migrate_many
    result = self.migrate(migration, database)
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/south/migration/migrators.py", line 133, in migrate
    result = self.run(migration)
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/south/migration/migrators.py", line 107, in run
    return self.run_migration(migration)
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/south/migration/migrators.py", line 81, in run_migration
    migration_function()
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/south/migration/migrators.py", line 57, in <lambda>
    return (lambda: direction(orm))
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/djcelery/migrations/0002_v25_changes.py", line 32, in forwards
    ('traceback', self.gf('django.db.models.fields.TextField')(null=True, blank=True)),)):
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/djcelery/migrations/0002_v25_changes.py", line 10, in ignore_exists
    fun(*args, **kwargs)
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/south/db/generic.py", line 44, in _cache_clear
    return func(self, table, *args, **opts)
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/south/db/generic.py", line 352, in create_table
    ', '.join([col for col in columns if col]),
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/south/db/generic.py", line 273, in execute
    cursor.execute(sql, params)
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/django/db/backends/util.py", line 40, in execute
    return self.cursor.execute(sql, params)
  File "/var/tmp/madrona-env/lib/python2.6/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 52, in execute
    return self.cursor.execute(query, args)
django.db.utils.DatabaseError: la relación «celery_taskmeta» ya existe



Scott Fletcher

unread,
Aug 13, 2012, 2:56:29 PM8/13/12
to nach...@gmail.com, madron...@googlegroups.com
Hi Nacho.

It looks like the create-madrona-project script is breaking when it tries to migrate the celery tables into the database (reporting that they are already present).  

Madrona uses the django syncdb command along with the South migrate command to construct and populate the database.  The create-madrona-project script calls syncdb first and the migrate command second.  Those tables that are not managed by South will be constructed via the syncdb command, after which those tables that are managed by South will be constructed via the migrate command.  

I'm not sure why the celery_taskmeta table would have been in the database already. I would try dropping and re-creating the database before calling create-madrona-project again and see if that helps.  

Let me know how that goes.

-Scott
Reply all
Reply to author
Forward
0 new messages