Page MenuHomePhabricator
Create Task
Maniphest T12198

Database seen as uninitialized after upgrade....cannot recover
Closed, InvalidPublic
Actions

Description

Hi guys,

I'm in dip...hit it seems after an upgrade (git pull). The storage seems to think the db is not initialized at it whats to do it & failing of course...

phabricator@m:~$ bin/storage status
Database Not Initialized: Run **./bin/storage upgrade** to initialize.

phabricator@m:~$ bin/storage upgrade --force
Loading quickstart template onto "localhost:3306"...
[2017-02-03 12:21:52] EXCEPTION: (AphrontQueryException) #1050: Table 'audit_transaction' already exists at [<phutil>/src/aphront/storage/connection/mysql/AphrontBaseMySQLDatabaseConnection.php:355]
arcanist(head=stable, ref.master=ccbaee585e1a, ref.stable=bb276740e7a8), phabricator(head=stable, ref.master=d76175285e96, ref.stable=2604c5af55f6), phutil(head=stable, ref.master=d20d6e725037, ref.stable=10963f771f11)
  #0 AphrontBaseMySQLDatabaseConnection::throwQueryCodeException(integer, string) called at [<phutil>/src/aphront/storage/connection/mysql/AphrontBaseMySQLDatabaseConnection.php:289]
  #1 AphrontBaseMySQLDatabaseConnection::throwQueryException(mysqli) called at [<phutil>/src/aphront/storage/connection/mysql/AphrontBaseMySQLDatabaseConnection.php:185]
  #2 AphrontBaseMySQLDatabaseConnection::executeRawQuery(string) called at [<phutil>/src/xsprintf/queryfx.php:8]
  #3 queryfx(AphrontMySQLiDatabaseConnection, string, string) called at [<phabricator>/src/infrastructure/storage/management/PhabricatorStorageManagementAPI.php:268]
  #4 PhabricatorStorageManagementAPI::applyPatchSQL(string) called at [<phabricator>/src/infrastructure/storage/management/workflow/PhabricatorStorageManagementWorkflow.php:922]
  #5 PhabricatorStorageManagementWorkflow::doUpgradeSchemata(array, NULL, boolean, boolean) called at [<phabricator>/src/infrastructure/storage/management/workflow/PhabricatorStorageManagementWorkflow.php:840]
  #6 PhabricatorStorageManagementWorkflow::upgradeSchemata(array, NULL, boolean, boolean) called at [<phabricator>/src/infrastructure/storage/management/workflow/PhabricatorStorageManagementUpgradeWorkflow.php:78]
  #7 PhabricatorStorageManagementUpgradeWorkflow::didExecute(PhutilArgumentParser) called at [<phabricator>/src/infrastructure/storage/management/workflow/PhabricatorStorageManagementWorkflow.php:107]
  #8 PhabricatorStorageManagementWorkflow::execute(PhutilArgumentParser) called at [<phutil>/src/parser/argument/PhutilArgumentParser.php:438]
  #9 PhutilArgumentParser::parseWorkflowsFull(array) called at [<phutil>/src/parser/argument/PhutilArgumentParser.php:330]
  #10 PhutilArgumentParser::parseWorkflows(array) called at [<phabricator>/scripts/sql/manage_storage.php:249]

Any ideas on how to recover from this?

Event Timeline

valentinul renamed this task from Database seens as uninitialized after upgrade.... to Database seen as uninitialized after upgrade.....Feb 3 2017, 12:22 PM
valentinul renamed this task from Database seen as uninitialized after upgrade.... to Database seen as uninitialized after upgrade....cannot recover.
valentinul created this task.
epriestley edited projects, added Bug Report (Needs Information); removed Bug Report.Feb 3 2017, 12:31 PM
epriestley added a subscriber: epriestley.

This isn't a bug report we can accept upstream. See Contributing Bug Reports for help. In particular:

We do not offer free installation or configuration support, see Support Resources for details.

It is very likely that this is a configuration problem unique to your install, not a bug in Phabricator. If you need help resolving configuration or administration problems unique to your install, this is not the right place to get it. Instead:

  • You can try to get free help by asking in one of the community support channels described in Support Resources, like StackOverflow.
  • You can get help directly from us for a fee; see Consulting.

To move forward:

  • provide version information; and
  • provide complete reproduction steps which allow us to recreate this bug in a clean, local environment, starting from scratch.

If we do not receive this information in a few days, we will close this report.

epriestley closed this task as Invalid.Feb 10 2017, 4:57 PM

We haven't received information that lets us reproduce this in about a week.

Feel free to file a new report if you can figure out a set of steps which will let us reproduce this issue in a clean environment.

Phabricator · Built by Phacility