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
The following problem has occurred in several cases in previous weeks. The docker container stopped without any error. If I check the docker log I just see normal console informations, like "Chain extended". There is no any reason what it is stopped. After I restart it a long "maintenance" has started (postgres DELETE is running for 1-2 hours in the process list), and after the db-sync-node started to work on the backlog and after 8-12 hours the container will stop again.
Any guess, how can I get better information why cardano-rosetta stop in my environment?
I also try to drop all the postgres database and rerun the db-sync, but when it synced, it stops again after a while.
cardano-rosetta version: 1.5.0
The text was updated successfully, but these errors were encountered:
Please try with 1.6.1, which is due to be released shortly. There's a number of optimisations in the new version of cardano-db-sync, which may resolve the issue.
The following problem has occurred in several cases in previous weeks. The docker container stopped without any error. If I check the docker log I just see normal console informations, like "Chain extended". There is no any reason what it is stopped. After I restart it a long "maintenance" has started (postgres DELETE is running for 1-2 hours in the process list), and after the db-sync-node started to work on the backlog and after 8-12 hours the container will stop again.
Any guess, how can I get better information why cardano-rosetta stop in my environment?
I also try to drop all the postgres database and rerun the db-sync, but when it synced, it stops again after a while.
cardano-rosetta version: 1.5.0
The text was updated successfully, but these errors were encountered: