Closed Scitz0 closed 3 months ago
Seems not to be a general issue. Though I have seen it on multiple instances. What could cause this behavior?
It seems similar to https://github.com/IntersectMBO/cardano-db-sync/issues/1777 where the EnableFutureGenesis
from DBSync config was not enabled. However in 13.3.0.0 it is enabled by default so the issue would appear only if it was manually disabled EnableFutureGenesis : false
Ok thanks, I can see that this is set in DBSync config to false. Thanks for clearing that up. Does db need to be resynced from genesis to fix this?
Would it be enough to copy content from this table from a health instance to this one if I set value correct and restart? Or does it have impact on other tables as well?
Never mind, I solved it with snapshot restore, closing issue.
OS Linux
Versions The
db-sync
version (egcardano-db-sync --version
): cardano-db-sync 13.3.0.0 - linux-x86_64 - ghc-8.10 git revision d21895fec3a9445493b6ff4aa61b8dcb5153de1ePostgreSQL version: 16
Build/Install Method The method you use to build or install
cardano-db-sync
: release binaryRun method The method you used to run
cardano-db-sync
(eg Nix/Docker/systemd/none): systemdAdditional context It seems that epoch_param table is not correctly populated on preview network after Conway HF. IT was synced to tip before HF event occured. As an example, there might be other
Problem Report Parameters are not correctly populated in dbsync epoch_param table.