Db_sync Issue

Staking & Delegation Operate a Stake Pool
1

Hello all - hoping somewhere here has some experience with db_sync. I have a new node running 9.1 and am going through the guild installation of db_sync. I initially tried loading a snapshot but it stalled out, so I decided to try and just create a fresh db and run db_sync to see what happens. When I do, I get this error:


cardano-db-sync: UnknownMigrationsFound {missingMigrations = [MigrationValidate {mvHash = "defe6519a4122239c0d679c01677be44a40aef674640d3fcfc192f3d786a3a6c", mvFilepath = "migration-3-0001-20190816.sql"}], extraMigrations = [MigrationValidate {mvHash = "5819d9031521f491cfc7cb563cb2ffa07e05406a2d5c15a057412caf276f069d", mvFilepath = "migration-1-0015-20240724.sql"},MigrationValidate {mvHash = "e865ed25a6d1034b4bd5465dc92199cb2f7638815603df856a3d009d53cfa9c4", mvFilepath = "migration-2-0042-20240808.sql"},MigrationValidate {mvHash = "f72a91481738952051e3d534f0f2d7dea1609f0f646b51f8d2810d2317632d2f", mvFilepath = "migration-3-0001-20190816.sql"}]}
2

I have also faced this issue. Did you figure it out?

3

I did… I had a mismatch between the db_sync version I was using and the schema file that were referenced in my git directory. Does that make sense?

4

After the fork I just upgraded the node to 9.1.1 and reinstalleed DBSync using a snapshot - everything was up and running again in a couple of days - I found this to be the most efficient way of getting everything going

5

Update and sync a backup server first, then run it as a block producer after disabling the original node. Then you can switch them back, and have almost no downtime.