You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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:
./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
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.
The text was updated successfully, but these errors were encountered: