Hi All,
This evening I noticed there was an update waiting to install. So I installed it as I always do. After the install and reboot I noticed the Alerts button was flashing red.
My current train is :- Current Train: FreeNAS-9.10-STABLE (...)
This was the message : - CRITICAL: Sept. 28, 2016, 12:04 a.m. - Update failed. Check /data/update.failed for further details.
Under Boot it shows that I am now running 9.10.1-U1 I was on 9.10.1.
The system appears to be running OK, all my SMB shares are available, all my plugins up and running (Plex, Transmission, SickRage & Sabnzbd).
I made 9.10.1 my active boot, re-booted deleted 9.10.1-U1 all OK no error. Re checked for updates again told one was available so updated and got the same error message after re-booting.
Here are the contents of update.failed
Do I have a real problem, should I go back to 9.10.1 any advice pointers would be welcome
My system specs are in my signature
Many thanks Grant
	
		
			
		
		
	
			
			This evening I noticed there was an update waiting to install. So I installed it as I always do. After the install and reboot I noticed the Alerts button was flashing red.
My current train is :- Current Train: FreeNAS-9.10-STABLE (...)
This was the message : - CRITICAL: Sept. 28, 2016, 12:04 a.m. - Update failed. Check /data/update.failed for further details.
Under Boot it shows that I am now running 9.10.1-U1 I was on 9.10.1.
The system appears to be running OK, all my SMB shares are available, all my plugins up and running (Plex, Transmission, SickRage & Sabnzbd).
I made 9.10.1 my active boot, re-booted deleted 9.10.1-U1 all OK no error. Re checked for updates again told one was available so updated and got the same error message after re-booting.
Here are the contents of update.failed
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 jails:
- Nothing to migrate.
 - Loading initial data for jails.
Installed 0 object(s) from 0 fixture(s)
Running migrations for vcp:
- Nothing to migrate.
 - Loading initial data for vcp.
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:
- Nothing to migrate.
 - Loading initial data for sharing.
Installed 0 object(s) from 0 fixture(s)
Running migrations for services:
 - Migrating forwards to 0198_iscsi_expunge_lun_auto.
 > services:0198_iscsi_expunge_lun_auto
 - Migration 'services:0198_iscsi_expunge_lun_auto' is marked for no-dry-run.
 - Loading initial data for services.
Installed 0 object(s) from 0 fixture(s)
Running migrations for account:
 - Migrating forwards to 0024_add_media_user_and_group.
 > account:0024_add_media_user_and_group
 - Migration 'account:0024_add_media_user_and_group' 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: account:0024_add_media_user_and_group
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/account/migrations/0024_add_media_user_and_group.py", line 14, in forwards
    group.save()
  File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 545, in save
    force_update=force_update, update_fields=update_fields)
  File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 573, in save_base
    updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields)
  File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 654, in _save_table
    result = self._do_insert(cls._base_manager, using, fields, update_pk, raw)
  File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 687, in _do_insert
    using=using, raw=raw)
  File "/usr/local/lib/python2.7/site-packages/django/db/models/manager.py", line 232, in _insert
    return insert_query(self.model, objs, fields, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line 1514, in insert_query
    return query.get_compiler(using=using).execute_sql(return_id)
  File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 903, 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/www/freenasUI/../freenasUI/freeadmin/sqlite3_ha/base.py", line 376, in execute
    execute = Database.Cursor.execute(self, query, params)
django.db.utils.IntegrityError: UNIQUE constraint failed: account_bsdgroups.bsdgrp_group
Do I have a real problem, should I go back to 9.10.1 any advice pointers would be welcome
My system specs are in my signature
Many thanks Grant