Cnode 1.34.1 sync stuck - mux error

The node has been happily running for weeks and suddenly this after a restart. No sync and these logs, we are running a docker instance

[84488b42:cardano.node.DnsSubscription:Notice:1577] [2022-10-10 22:45:07.17 UTC] Domain: "relays-new.cardano-mainnet.iohk.io" Connection Attempt Start, destination 52.58.171.193:3001
[84488b42:cardano.node.DnsSubscription:Notice:1572] [2022-10-10 22:45:07.19 UTC] Domain: "relays-new.cardano-mainnet.iohk.io" Connection Attempt End, destination 13.114.93.89:3001 outcome: ConnectSuccessLast
[84488b42:cardano.node.ErrorPolicy:Notice:415] [2022-10-10 22:45:07.19 UTC] IP 54.179.126.222:3001 ErrorPolicySuspendConsumer (Just (ConnectionExceptionTrace (SubscriberError {seType = SubscriberParallelConnectionCancelled, seMessage = "Parallel connection cancelled", seStack = []}))) 1s
[84488b42:cardano.node.ErrorPolicy:Notice:415] [2022-10-10 22:45:07.19 UTC] IP 52.74.189.190:3001 ErrorPolicySuspendConsumer (Just (ConnectionExceptionTrace (SubscriberError {seType = SubscriberParallelConnectionCancelled, seMessage = "Parallel connection cancelled", seStack = []}))) 1s
[84488b42:cardano.node.ErrorPolicy:Notice:415] [2022-10-10 22:45:07.19 UTC] IP 18.132.127.241:3001 ErrorPolicySuspendConsumer (Just (ConnectionExceptionTrace (SubscriberError {seType = SubscriberParallelConnectionCancelled, seMessage = "Parallel connection cancelled", seStack = []}))) 1s
[84488b42:cardano.node.ErrorPolicy:Notice:415] [2022-10-10 22:45:07.19 UTC] IP 52.58.171.193:3001 ErrorPolicySuspendConsumer (Just (ConnectionExceptionTrace (SubscriberError {seType = SubscriberParallelConnectionCancelled, seMessage = "Parallel connection cancelled", seStack = []}))) 1s
[84488b42:cardano.node.DnsSubscription:Error:1575] [2022-10-10 22:45:08.26 UTC] Domain: "relays-new.cardano-mainnet.iohk.io" Application Exception: 18.188.75.201:3001 MuxError MuxBearerClosed "<socket: 39> closed when reading data, waiting on next header True"
[84488b42:cardano.node.ErrorPolicy:Warning:415] [2022-10-10 22:45:08.26 UTC] IP 18.188.75.201:3001 ErrorPolicySuspendPeer (Just (ApplicationExceptionTrace (MuxError MuxBearerClosed "<socket: 39> closed when reading data, waiting on next header True"))) 20s 20s
[84488b42:cardano.node.DnsSubscription:Error:1572] [2022-10-10 22:45:08.79 UTC] Domain: "relays-new.cardano-mainnet.iohk.io" Application Exception: 13.114.93.89:3001 MuxError MuxBearerClosed "<socket: 36> closed when reading data, waiting on next header True"
[84488b42:cardano.node.ErrorPolicy:Warning:415] [2022-10-10 22:45:08.79 UTC] IP 13.114.93.89:3001 ErrorPolicySuspendPeer (Just (ApplicationExceptionTrace (MuxError MuxBearerClosed "<socket: 36> closed when reading data, waiting on next header True"))) 20s 20s

Why don’t you upgrade to 1.35.3?

1 Like

Thanks will use a new Docker image with 1.35.3 although seems its not really stable for very long, so do you upgrade each time auto or manual whenever a new version comes out

If people talk about an upgrade that is mandatory for a hard fork for months, yes, then you should upgrade.

1 Like

For sure I knew about the hard fork, but 1.34.1 was still being supported will have to keep up more with the announcements, which is the best channel to view important dates like deprecation announcements , Telegram ?

There’s an IOG telegram group and the discord. There are also announcements on their twitter feed too.

It’s a blockchain—not a Docker instance!

Yes, upgrading to Cardano Node 1.35.3 may help solve the problem:

Please do not ask me who wrote the procedure,

CHG