sprint app error upgrading schema
ActivePublic
Actions

Authored by • chasemp on Jan 13 2015, 5:52 PM.

Tags

None

Referenced Files

	F28481: sprint_app_error_upgrading_schema
	Jan 13 2015, 5:52 PM

Subscribers

None

	root@phab-01:/var/log# /srv/phab/phabricator/bin/storage upgrade
	Before running storage upgrades, you should take down the Phabricator web
	interface and stop any running Phabricator daemons (you can disable this
	warning with --force).

	Are you ready to continue? [y/N] y

	Applying patch 'phabricator:20141210.maniphestsubscribersmig.2.sql'...
	Applying patch 'phabricator:20141210.reposervice.sql'...
	Applying patch 'phabricator:20141212.conduittoken.sql'...
	Applying patch 'phabricator:20141215.almanacservicetype.sql'...
	Applying patch 'phabricator:20141217.almanacdevicelock.sql'...
	Applying patch 'phabricator:20141217.almanaclock.sql'...
	Applying patch 'phabricator:20141218.maniphestcctxn.php'...
	Converting Maniphest CC transactions to modern SUBSCRIBER transactions...
	Done.
	Applying patch 'phabricator:20141222.maniphestprojtxn.php'...
	Converting Maniphest project transactions to modern EDGE transactions...
	Done.
	Applying patch 'phabricator:20141223.daemonloguser.sql'...
	Applying patch 'phabricator:20141223.daemonobjectphid.sql'...
	Applying patch 'phabricator:20141230.pasteeditpolicycolumn.sql'...
	Applying patch 'phabricator:20141230.pasteeditpolicyexisting.sql'...
	Applying patch 'phabricator:20150102.policyname.php'...
	Migrating policies...
	Applying patch 'phabricator:20150102.tasksubscriber.sql'...
	Applying patch 'phabricator:20150105.conpsearch.sql'...
	Storage is up to date. Use 'storage status' for details.
	Verifying database schemata...


	Database Table Name Issues
	phabricator_worker worker_activetask key_object Missing Key
	phabricator_worker worker_archivetask key_object Missing Key

	Found 2 issues(s) with schemata, detailed above.

	You can review issues in more detail from the web interface, in Config > Database Status. To better understand the adjustment workflow, see "Managing Storage Adjustments" in the documentation.

	MySQL needs to copy table data to make some adjustments, so these migrations may take some time.


	Fix these schema issues? [y/N] y

	Dropping caches, for faster migrations...
	Purging remarkup cache...done.
	Purging changeset cache...done.
	Purging general cache...done.
	Fixing schema issues...
	Done.
	Completed fixing all schema issues.

	Target Error
	phabricator_sprint Missing

	SCHEMATA ERRORS

	The schemata have errors (detailed above) which the adjustment workflow can
	not fix.

	If you are not developing Phabricator itself, report this issue to the
	upstream.

	If you are developing Phabricator, these errors usually indicate that your
	schema specifications do not agree with the schemata your code actually
	builds.
	root@phab-01:/var/log#

Event Timeline

• chasemp edited the content of this paste. (Show Details)Jan 13 2015, 5:52 PM

• chasemp changed the title of this paste from untitled to sprint app error upgrading schema.

• chasemp updated the paste's language from autodetect to autodetect.

• chasemp mentioned this in T78679: Sprint projects load slowly.

Multichill mentioned this in T230569: General SDC data modelling session.Sep 29 2019, 4:39 PM

sprint app error upgrading schemaActivePublicActions

Event Timeline

sprint app error upgrading schema
ActivePublic
Actions