Update Failed - Critical Alert!

[STREBLO]

I recieved the following email after updating and am not sure what to do.

"Update failed. Check /data/update.failed for further details."

Here's /data/update.failed:

Code:

FATAL ERROR - The following SQL query failed: ALTER TABLE "services_fiberchanneltotarget" RENAME TO "services_fibrechanneltotarget";
The error was: no such table: services_fiberchanneltotarget
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 vcp:
- Nothing to migrate.
- Loading initial data for vcp.
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:
- Nothing to migrate.
- Loading initial data for account.
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 directoryservice:
- Migrating forwards to 0054_auto__add_field_activedirectory_ad_allow_dns_updates.
> directoryservice:0054_auto__add_field_activedirectory_ad_allow_dns_updates
- 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 system:
- Migrating forwards to 0099_email_pwenc.
> system:0099_email_pwenc
- Migration 'system:0099_email_pwenc' is marked for no-dry-run.
- Loading initial data for system.
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 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 services:
- Migrating forwards to 0184_auto__del_fiberchanneltotarget__add_fibrechanneltotarget.
> services:0184_auto__del_fiberchanneltotarget__add_fibrechanneltotarget
! 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:   = ALTER TABLE "services_fibrechanneltotarget" RENAME TO "services_fiberchanneltotarget"; []

! 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: services:0184_auto__del_fiberchanneltotarget__add_fibrechanneltotarget
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/services/migrations/0184_auto__del_fiberchanneltotarget__add_fibrechanneltotarget.py", line 11, in forwards
    db.rename_table(u'services_fiberchanneltotarget', u'services_fibrechanneltotarget')
  File "/usr/local/lib/python2.7/site-packages/south/db/generic.py", line 47, in _cache_clear
    return func(self, table, *args, **opts)
  File "/usr/local/lib/python2.7/site-packages/south/db/generic.py", line 375, in rename_table
    self.execute(self.rename_table_sql % params)
  File "/usr/local/lib/python2.7/site-packages/south/db/generic.py", line 282, in execute
    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 386, in execute
    return Database.Cursor.execute(self, query, params)
django.db.utils.OperationalError: no such table: services_fiberchanneltotarget

 

[rsquared]

Someone else had that same error earlier this week and submitted a bug ticket against it. I don't think the thread has had an update, but if you can find the thread, maybe the ticket will have some info.

Sent from my Nexus 6 using Tapatalk

 

[dlavigne]

That would be #12618 which has this workaround: https://bugs.freenas.org/issues/12618#note-12.

 

[STREBLO]

That would be #12618 which has this workaround: https://bugs.freenas.org/issues/12618#note-12.

Thanks, i'll try that. Why would this happen? I'm on the stable branch.

 

[STREBLO]

okay, I applied the patch but still have the critical alert warning. Do I need to do something to get rid of it? How do I know if everything is working?

 

[dlavigne]

Why would this happen?

Even the developer is scratching his head over that one...

 

[STREBLO]

So I went ahead and reinstalled, it fixed my problem

 

[STREBLO]

After restoring my config I got the blinking light back . Damn it

 

[dlavigne]

Even after applying the workaround?

 

[STREBLO]

Even after applying the workaround?

Yup. I ended up reinstalling from a fresh ISO and updating, then I restored to config I had from a few days ago and it worked fine. When I restored to an up-to-date config it brought me back the blinking light though so if someone has this problem don't restore to a current config, restore from one a bit older if you reinstall FreeNAS

 

[Easygoer]

I have had the same problem for the past 2 days. I DID NOT get the "red critical" warning light flashing on the first try. But a day later the system emailed me saying that an update was available. So i updated via the GUI today and now the "red critical" light is always flashing. I also tried updating via the shell menu #10, but it does not do anything. I have tried rebooting several times also.

i have had no problems at all updating via GUI in the past. Can someone be kind enough to point me in the direction of how to access the "/data/update.failed"
file so I can post a bug report.

i am currently running FreeNAS-9.3-STABLE-201511280648

Many thanks.

 

[Redcoat]

Have you tried the posted workaround per the link above? https://bugs.freenas.org/issues/12618#note-12

Redcoat

 

[Easygoer]

No, I have not. I'm still trying to figure out the location of the "/data/update.failed" file.

Any help would be appreciated. Thanks.

 

[STREBLO]

No, I have not. I'm still trying to figure out the location of the "/data/update.failed" file.

Any help would be appreciated. Thanks.

Thats the location. ssh into your freenas and do ''cat /data/update.failed"

 

[depasseg]

According to this bug post, you can manually delete the /data/update.failed for the error to go away.
https://bugs.freenas.org/issues/12618#note-23