Update failure

[RoboKaren]

Trying to run a posted update to 9.3, I was given the following error. Thoughts on what to do?


CRITICAL: Update failed. Check /data/update.failed for further details.


>> more /data/update.failed
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 jails:
- Nothing to migrate.
- Loading initial data for jails.
Installed 0 object(s) from 0 fixture(s)
Running migrations for services:
- Migrating forwards to 0158_auto__add_field_afp_afp_srv_homename.
> services:0158_auto__add_field_afp_afp_srv_homename
- Loading initial data for services.
Installed 0 object(s) from 0 fixture(s)
Running migrations for tasks:
- Nothing to migrate.
- Loading initial data for tasks.
Installed 0 object(s) from 0 fixture(s)
Running migrations for storage:
- Nothing to migrate.
- Loading initial data for storage.
Installed 0 object(s) from 0 fixture(s)
Running migrations for account:
- Nothing to migrate.
- Loading initial data for account.
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 plugins:
- Nothing to migrate.
- Loading initial data for plugins.
Installed 0 object(s) from 0 fixture(s)
Running migrations for sharing:
- Migrating forwards to 0033_add_periodic_snapshot_task.
> sharing:0032_auto__add_field_cifs_share_cifs_storage_task
> sharing:0033_add_periodic_snapshot_task
- Migration 'sharing:0033_add_periodic_snapshot_task' is marked for no-dry-run.
- Loading initial data for tasks.
Installed 0 object(s) from 0 fixture(s)
Running migrations for storage:
- Nothing to migrate.
- Loading initial data for storage.
Installed 0 object(s) from 0 fixture(s)
Running migrations for account:
- Nothing to migrate.
- Loading initial data for account.
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 plugins:
- Nothing to migrate.
- Loading initial data for plugins.
Installed 0 object(s) from 0 fixture(s)
Running migrations for sharing:
- Migrating forwards to 0033_add_periodic_snapshot_task.
> sharing:0032_auto__add_field_cifs_share_cifs_storage_task
> sharing:0033_add_periodic_snapshot_task
- Migration 'sharing:0033_add_periodic_snapshot_task' 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: sharing:0033_add_periodic_snapshot_task
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/sharing/migrations/0033_add_periodic_snapshot_task.py", line 28, in forwards
)[0]
File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line 132, in __getitem__
return list(qs)[0]
IndexError: list index out of range
[nakamura@bethel] ~%

 

[BigDave]

Trying to run a posted update to 9.3, I was given the following error. Thoughts on what to do?

Assuming your boot device is working, go back to your previous stable version before your upgrade started.
If your boot device is pooched, just replace it. If your able to revert to the previous stable version, try
the upgrade again. There's a reported bug that sounds a bit like this...

 

[RoboKaren]

Many thanks, I totally forgot that our boot drives now had versioning. How useful! It's almost like it was designed just in case something happened with an update!

 

[carleycr]

I also ran the update via GUI on fresh install of 9.3 yesterday and got some errors. Now I'm unable to see available plugins. How do I access the versioning that you're speaking of?

 

[BigDave]

How do I access the versioning that you're speaking of?

Check out the manual regarding Boot

 

[John5788]

Just reporting in that I am seeing the same exact message when trying to boot into FreeNAS-9.3-STABLE-201502070132. I'm reverting back to FreeNAS-9.3-STABLE-201501212031

 

[tstorm]

this is a bug and hopefully will be squashed soon https://bugs.freenas.org/issues/7884

 

[Anderath]

Same issue here. I'm using the "default" boot volume. It seems as though the current environment replaces the default boot volume when there's a new update available that is installed. Am I correct in that assumption?


Here is log file:
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 storage:
- Nothing to migrate.
- Loading initial data for storage.
Installed 0 object(s) from 0 fixture(s)
Running migrations for system:
- Nothing to migrate.
- Loading initial data for system.
Installed 0 object(s) from 0 fixture(s)
Running migrations for directoryservice:
- Nothing to migrate.
- Loading initial data for directoryservice.
Installed 0 object(s) from 0 fixture(s)
Running migrations for plugins:
- Nothing to migrate.
- Loading initial data for plugins.
Installed 0 object(s) from 0 fixture(s)
Running migrations for services:
- Migrating forwards to 0158_auto__add_field_afp_afp_srv_homename.
> services:0158_auto__add_field_afp_afp_srv_homename
- Loading initial data for services.
Installed 0 object(s) from 0 fixture(s)
Running migrations for jails:
- Nothing to migrate.
- Loading initial data for jails.
Installed 0 object(s) from 0 fixture(s)
Running migrations for sharing:
- Migrating forwards to 0033_add_periodic_snapshot_task.
> sharing:0032_auto__add_field_cifs_share_cifs_storage_task
> sharing:0033_add_periodic_snapshot_task
- Migration 'sharing:0033_add_periodic_snapshot_task' 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: sharing:0033_add_periodic_snapshot_task
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/sharing/migrations/0033_add_periodic_snapshot_task.py", line 28, in forwards
)[0]
File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line 132, in __getitem__
return list(qs)[0]
IndexError: list index out of range

 

[Anderath]

So I tried rolling back to "default" and then trying to redo all updates.

I still get the alert saying the updates failed notice but I can login to the UI and everything appears to run as normal.

Here's my available boot options:

Can anyone make a recommendation? Should I just backup config and reflash my USB?

 

[RoboKaren]

Fixed with the latest release. I can now update without errors.

 

[John5788]

Confirmed fixed, thanks!