Skip to Content.

djnro - Re: [djnro] Problem installing, ie. migration fails

Subject: DjNRO discussion

Text archives


Re: [djnro] Problem installing, ie. migration fails


Archive: Chronological Thread 
  • From: Zenon Mousmoulas <>
  • To: Kurt Bauer <>
  • Cc:
  • Subject: Re: [djnro] Problem installing, ie. migration fails
  • Date: Thu, 21 Feb 2013 20:01:22 +0200
  • Delivery-date: Thu, 21 Feb 2013 20:01:35 +0200
  • Envelope-to:
Hi Kurt,

On 21/02/2013 4:20 μ.μ., Kurt Bauer wrote:
first of all let me thank you for your efforts. It seems this is exactly
what we were searching for at ACOnet to keep records for the Austrian
eduroam footprint.

Thanks for the kind words. We feel we are still in the first steps but we hope this project can be useful for the community; this will help in the direction of improving and further developing the software.

Unfortunately I ran into an error whilst the migration [1] - syncdb went
fine. Is there smth. obvious I've done wrong, a table named
'#sql-22fe_2d ' looks a little weird to me anyhow. Could it be that
there is something wrong with the character-set?

After a lot of tests, we are confident this is caused by a conflict between MySQL 5.5 and earlier versions of South, which has been addressed in South 0.7.5.

See this for some more insight:
http://south.aeracode.org/ticket/523

So the question is, what does your environment look like? Are you by any chance running MySQL 5.5 and South 0.7.3? Is it possible to install South >= 0.7.5 or use MySQL 5.1?

Thanks for the heads-up. Sorry that your first experience was not as good as we'd hope it to be...

Best regards,
Z.

[1]
  .....
  > edumanage:0027_auto__del_monlocaleapoldata__add_monlocalauthnparam
  >
edumanage:0028_auto__chg_field_monlocalauthnparam_instrealmmonid__add_unique_monlocal
  ! Error found during real run of migration! Aborting.

  ! Since you have a database that does not support running
  ! schema-altering statements in transactions, we have had
  ! to leave it in an interim state between migrations.

! You *might* be able to recover with:
  ! The South developers regret this has happened, and would
  ! like to gently persuade you to consider a slightly
  ! easier-to-deal-with DBMS.
  ! NOTE: The error which caused the migration to fail is further up.
Traceback (most recent call last):
   File "./manage.py", line 11, in <module>
     execute_manager(settings)
   File
"/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 438, in execute_manager
     utility.execute()
   File
"/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 379, in execute
     self.fetch_command(subcommand).run_from_argv(self.argv)
   File
"/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
191, in run_from_argv
     self.execute(*args, **options.__dict__)
   File
"/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
220, in execute
     output = self.handle(*args, **options)
   File
"/usr/lib/python2.7/dist-packages/south/management/commands/migrate.py",
line 105, in handle
     ignore_ghosts = ignore_ghosts,
   File "/usr/lib/python2.7/dist-packages/south/migration/__init__.py",
line 191, in migrate_app
     success = migrator.migrate_many(target, workplan, database)
   File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py",
line 221, in migrate_many
     result = migrator.__class__.migrate_many(migrator, target,
migrations, database)
   File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py",
line 292, in migrate_many
     result = self.migrate(migration, database)
   File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py",
line 125, in migrate
     result = self.run(migration)
   File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py",
line 99, in run
     return self.run_migration(migration)
   File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py",
line 81, in run_migration
     migration_function()
   File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py",
line 57, in <lambda>
     return (lambda: direction(orm))
   File
"/opt/djnro/edumanage/migrations/0028_auto__chg_field_monlocalauthnparam_instrealmmonid__add_unique_monlocal.py",
line 12, in forwards
     db.alter_column('edumanage_monlocalauthnparam', 'instrealmmonid_id',
self.gf('django.db.models.fields.related.OneToOneField')(to=orm['edumanage.InstRealmMon'],
unique=True))
   File "/usr/lib/python2.7/dist-packages/south/db/generic.py", line 397,
in alter_column
     field.rel.to._meta.get_field(field.rel.field_name).column
   File "/usr/lib/python2.7/dist-packages/south/db/generic.py", line 150,
in execute
     cursor.execute(sql, params)
   File
"/usr/lib/python2.7/dist-packages/django/db/backends/mysql/base.py",
line 86, in execute
     return self.cursor.execute(query, args)
   File "/usr/lib/python2.7/dist-packages/MySQLdb/cursors.py", line 174,
in execute
     self.errorhandler(self, exc, value)
   File "/usr/lib/python2.7/dist-packages/MySQLdb/connections.py", line
36, in defaulterrorhandler
     raise errorclass, errorvalue
_mysql_exceptions.OperationalError: (1005, "Can't create table
'djnro.#sql-22fe_2d' (errno: 121)")




Top of Page