Cannot get past this error message after login

Status
Not open for further replies.

Tharp94895

Cadet
Joined
Jan 5, 2015
Messages
9
I'm getting the following error message after I upgraded last night and am able to login. But after login get the following error message:

{"error": true, "events": [], "message": "Error: no such column: account_bsdusers.bsdusr_microsoft_account"}

I am able to get to my jails but samba shares are down. Has anyone ran into this error message before or know a resolution for this? I have ssh access so I can get my info just need to know the commands to run.

Running the following release:
FreeBSD 9.3-RELEASE-p8 (FREENAS.amd64) #1 r275790+18ab2bc: Wed Jan 21 12:32:31 P

Thanks,
Tim
 
Last edited:

Tharp94895

Cadet
Joined
Jan 5, 2015
Messages
9
Logging in with incorrect credentials I still get this error so this leads me to believe the users/pass DB is corrupted or something of that nature. Seems like this update broke local authentication.

Also looking at the log file /data/update.failed dated last night around the time the update failed:

Code:
FATAL ERROR - The following SQL query failed: CREATE TABLE "system_backup" ("id" integer NOT NULL PRIMARY KEY, "bak_finished" bool NOT NULL, "bak_failed" bool NOT NULL, "bak_acknowledged" bool NOT NULL, "bak_worker_pid" integer NULL, "bak_started_at" datetime NOT NULL, "bak_finished_at" datetime NULL, "bak_destination" varchar(1024) NOT NULL, "bak_status" varchar(1024) NOT NULL)
The error was: table "system_backup" already exists
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 directoryservice:
- Migrating forwards to 0041_auto__add_field_ldap_ldap_schema.
> directoryservice:0041_auto__add_field_ldap_ldap_schema
- Loading initial data for directoryservice.
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 plugins:
- Nothing to migrate.
- Loading initial data for plugins.
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 system:
- Migrating forwards to 0094_add_model_backup.
> system:0093_auto__add_field_advanced_adv_boot_scrub
> system:0094_add_model_backup
! 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:   = DROP TABLE "system_backup"; []

! 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: system:0094_add_model_backup
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/system/migrations/0094_add_model_backup.py", line 21, in forwards
    ('bak_status', self.gf('django.db.models.fields.CharField')(max_length=1024, blank=True)),
  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 361, in create_table
    "columns": ', '.join([col for col in columns if col]),
  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/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: table "system_backup" already exists
 

puregreen59

Cadet
Joined
Feb 12, 2015
Messages
2
Logging in with incorrect credentials I still get this error so this leads me to believe the users/pass DB is corrupted or something of that nature. Seems like this update broke local authentication.

Also looking at the log file /data/update.failed dated last night around the time the update failed:

Code:
FATAL ERROR - The following SQL query failed: CREATE TABLE "system_backup" ("id" integer NOT NULL PRIMARY KEY, "bak_finished" bool NOT NULL, "bak_failed" bool NOT NULL, "bak_acknowledged" bool NOT NULL, "bak_worker_pid" integer NULL, "bak_started_at" datetime NOT NULL, "bak_finished_at" datetime NULL, "bak_destination" varchar(1024) NOT NULL, "bak_status" varchar(1024) NOT NULL)
The error was: table "system_backup" already exists
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 directoryservice:
- Migrating forwards to 0041_auto__add_field_ldap_ldap_schema.
> directoryservice:0041_auto__add_field_ldap_ldap_schema
- Loading initial data for directoryservice.
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 plugins:
- Nothing to migrate.
- Loading initial data for plugins.
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 system:
- Migrating forwards to 0094_add_model_backup.
> system:0093_auto__add_field_advanced_adv_boot_scrub
> system:0094_add_model_backup
! 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:   = DROP TABLE "system_backup"; []

! 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: system:0094_add_model_backup
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/system/migrations/0094_add_model_backup.py", line 21, in forwards
    ('bak_status', self.gf('django.db.models.fields.CharField')(max_length=1024, blank=True)),
  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 361, in create_table
    "columns": ', '.join([col for col in columns if col]),
  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/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: table "system_backup" already exists

This is what i am stuck at too rather annoying
 

Tharp94895

Cadet
Joined
Jan 5, 2015
Messages
9
I ended up grabbing my config DB file and re-installing the system to save time trying to troubleshoot this error.
 

PhoenixGI

Cadet
Joined
Apr 4, 2015
Messages
1
Ran into this issue last night, fortunitly rolling back to the previous boot environment allowed me back into the system. Not only was the webGUI unavailable, my data sets also. I am hoping that there is a solution for this other then just reinstall. In /data there is a database file that was created during the time of the update that's about 10k larger then the factory-v1.db. Would deleting this and rerunning the patches work? What was wrong with the conversion script that caused it to fail, or is there some way to edit and fix the current DB so the conversion script will work right?
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Bugs are not going to get fixed without bug reports.
 
Status
Not open for further replies.
Top