Freenas 9.3 Restoring Config DB fails after fresh install

Status
Not open for further replies.
Joined
Oct 13, 2013
Messages
8
Hi,
I am running into a brick wall it seems.
I currently have Freenas 9.3 20141209 running and need to move it to a new USB.
Had not noticed I inadvertently installed on a 4gb flash drive.

The reason I am updating is because lately boot time is very long, delta updates in GUI get stuck at 67% and I am unable to toggle services in the Services tab.
I feared a dying USB and when checking it realized the size problem.

I figured I would ease both fears and buy a new 16gb drive.
I backed up the config. Installed latest Freenas 9.3 20150121 stable build on the new drive.
After first boot, I upload the config and reboot.
On boot, indicates db upgrade fails and reverts.
On GUI after boot tells me that details are in the update.failed file in /data..

I attached the 'update.failed' file.

It seems to crash after
"Running migrations for directoryservice"

I also tried installing the stable Freenas 9.3 20141209 version to match the backup config db but did not fix issue.

Please help.


Code:
Running migrations for api:
- Nothing to migrate.
- Loading initial data for api.
Installed 0 object(s) from 0 fixture(s)
Running migrations for freeadmin:
- Nothing to migrate.
- Loading initial data for freeadmin.
Installed 0 object(s) from 0 fixture(s)
Running migrations for support:
- Nothing to migrate.
- Loading initial data for support.
Installed 0 object(s) from 0 fixture(s)
Running migrations for network:
- Nothing to migrate.
- Loading initial data for network.
Installed 0 object(s) from 0 fixture(s)
Running migrations for account:
- Migrating forwards to 0023_auto__add_field_bsdusers_bsdusr_microsoft_account.
> account:0023_auto__add_field_bsdusers_bsdusr_microsoft_account
- Loading initial data for account.
Installed 0 object(s) from 0 fixture(s)
Running migrations for directoryservice:
- Migrating forwards to 0041_auto__add_field_ldap_ldap_schema.
> directoryservice:0035_pwencrypt
- Migration 'directoryservice:0035_pwencrypt' is marked for no-dry-run.
! 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:   (migration cannot be dry-run; cannot discover commands)
! The South developers regret this has happened, and would
! like to gently persuade you to consider a slightly
! easier-to-deal-with DBMS (one that supports DDL transactions)
! NOTE: The error which caused the migration to fail is further up.
Error in migration: directoryservice:0035_pwencrypt
Traceback (most recent call last):
  File "/usr/local/www/freenasUI/manage.py", line 42, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 392, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python2.7/site-packages/django/core/management/base.py", line 242, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/local/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python2.7/site-packages/south/management/commands/migrate.py", line 111, in handle
    ignore_ghosts = ignore_ghosts,
  File "/usr/local/lib/python2.7/site-packages/south/migration/__init__.py", line 220, in migrate_app
    success = migrator.migrate_many(target, workplan, database)
  File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 256, in migrate_many
    result = migrator.__class__.migrate_many(migrator, target, migrations, database)
  File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 331, in migrate_many
    result = self.migrate(migration, database)
  File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 133, in migrate
    result = self.run(migration, database)
  File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 114, in run
    return self.run_migration(migration, database)
  File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 84, in run_migration
    migration_function()
  File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 60, in <lambda>
    return (lambda: direction(orm))
  File "/usr/local/www/freenasUI/../freenasUI/directoryservice/migrations/0035_pwencrypt.py", line 31, in forwards
    do_encrypt(orm['directoryservice.ActiveDirectory'], 'ad_bindpw')
  File "/usr/local/www/freenasUI/../freenasUI/directoryservice/migrations/0035_pwencrypt.py", line 15, in do_encrypt
    for obj in model.objects.all():
  File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line 96, in __iter__
    self._fetch_all()
  File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line 857, in _fetch_all
    self._result_cache = list(self.iterator())
  File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line 220, in iterator
    for row in compiler.results_iter():
  File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 713, in results_iter
    for rows in self.execute_sql(MULTI):
  File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 786, in execute_sql
    cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/site-packages/django/db/backends/util.py", line 53, in execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/site-packages/django/db/utils.py", line 99, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/usr/local/lib/python2.7/site-packages/django/db/backends/util.py", line 53, in execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/site-packages/django/db/backends/sqlite3/base.py", line 452, in execute
    return Database.Cursor.execute(self, query, params)
django.db.utils.OperationalError: no such column: directoryservice_activedirectory.ad_use_keytab
 

Attachments

  • update.failed.txt
    5.1 KB · Views: 289
D

dlavigne

Guest
Please create a bug report at bugs.freenas.org and post the issue number here.
 
Joined
Oct 13, 2013
Messages
8
dlavigne thank you for your response.
However, I capitalized on my day off from work and installed fresh on the new drive I purchased.
I would be unable to reproduce the issue.
With that said, would opening a bug report still be recommended ?
 
D

dlavigne

Guest
That's up to you. A bug report would alert the devs of a migration script issue, however you wouldn't be able to assist with troubleshooting/testing unless you recreated the scenario in a vm.
 
Status
Not open for further replies.
Top