Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DB migration error #203

Closed
mike-burrage-hedera opened this issue Sep 5, 2019 · 1 comment · Fixed by #213
Closed

DB migration error #203

mike-burrage-hedera opened this issue Sep 5, 2019 · 1 comment · Fixed by #213
Assignees
Labels
bug Type: Something isn't working P2
Milestone

Comments

@mike-burrage-hedera
Copy link
Contributor

mike-burrage-hedera commented Sep 5, 2019

Detailed Description
ERROR [main ] o.f.c.i.c.DbMigrate Migration of schema "public" to version 1.8 - MigrateConfig failed! Changes successfully rolled back.

The issue affects any attempt to migrate the database (which running any of the services does) when:

  • The database had not already migrated v1.8 of the DB, and
  • ./config/config.json is not located relative to the working directory of the running service/app.

This would include anyone trying to install out of the CI-deliverable, using the instructions for installing that, against a fresh/empty database (as ./config/config.json is no longer located at that place relative to the running service's working directory).

Workaround
Ensure that "config.json" is found in the "./config/" directory relative to the working directory of the running processes (any of the downloaders or parsers).

If the working directory of the processes is /usr/lib/mirror-node and the config.json is in /usr/etc/mirror-node, then:

  • sudo ln -s /usr/etc/mirror-node /usr/lib/mirror-node/config
  • restart all downloader and parser processes

Actual Behavior

Expected Behavior

Environment:

Additional Context

Fix will be to remove the v1.8 migration code as it's not needed for a fresh DB, is causing this issue, and was only in place to upgrade from pre-v0.1.0 systems.

@mike-burrage-hedera mike-burrage-hedera added bug Type: Something isn't working P1 labels Sep 5, 2019
@mike-burrage-hedera mike-burrage-hedera added this to the 0.2.0 milestone Sep 5, 2019
@mike-burrage-hedera mike-burrage-hedera added P2 and removed P1 labels Sep 5, 2019
@mike-burrage-hedera mike-burrage-hedera removed this from the 0.2.0 milestone Sep 5, 2019
@mike-burrage-hedera mike-burrage-hedera added this to the 0.2.0 milestone Sep 5, 2019
@mike-burrage-hedera mike-burrage-hedera self-assigned this Sep 6, 2019
@mike-burrage-hedera
Copy link
Contributor Author

Wrong button.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Type: Something isn't working P2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant