Open BomaxChen opened 3 years ago
Sorry for the delay in response @BomaxChen
That's a curious error you're seeing. Do you have any logs reported from a service named cardano-node
?
I am also facing the same issue the cardano-node error logs are showing this,
[0d885e8a:cardano.node.DnsSubscription:Error:68] [2021-06-15 16:18:07.25 UTC] Domain: "relays-new.cardano-mainnet.iohk.io" Application Exception: 13.52.189.184:3001 SubscriberError {seType = SubscriberWorkerCancelled, seMessage = "SubscriptionWorker exiting", seStack = []}
[0d885e8a:cardano.node.LocalErrorPolicy:Error:58] [2021-06-15 16:18:04.05 UTC] IP LocalAddress "" ErrorPolicyUnhandledApplicationException (MuxError MuxBearerClosed "<socket: 24> closed when reading data, waiting on next header True")
How to resolve this?
@BomaxChen It works when we update the latest Cardano-DB-sync version in rosetta. Currently, they are using the 8.0.0 version of DB-sync, when I updated it to 9.0.0 in Dockerfile then it works.
@BomaxChen It works when we update the latest Cardano-DB-sync version in rosetta. Currently, they are using the 8.0.0 version of DB-sync, when I updated it to 9.0.0 in Dockerfile then it works.
Can you build the docker without errors ?
Thanks for the info. We'll be shipping a new version that will upgrade the internal Cardano services, but it should be compatible now. Are you running this on the mainnet
@tech-lcx?
@rhyslbw Yes, I am running it on mainnet.
@BomaxChen Yes, I build the docker without any error.
I dont have this issue, i'm using a volume for the /ipc to communicate with cardano-wallet
volumes:
- node-db:/data:delegated
- node-ipc:/ipc:delegated
But i have another bug in the db-sync, that i open here #386
I suspect this is a bug in cardano-db-sync@8.0.0
, and will be addressed when we release a new version that includes cardano-db-sync@8.0.0
. It's in the final stages of the release process now, so it shouldn't be too long now.
Was this ever corrected?
Hi, all When I start cardano-rosetta on mainnet, this is my build step