Cardano node runs into a series of warnings and errors that involve DNS Subscription and inability to connect to "relays-new.cardano-testnet.iohkdev.io”

After running the cardano node for a while, it seems to run into a series of warnings and errors that involve DNS Subscription and inability to connect to "[relays-new.cardano-testnet.iohkdev.io] (http://relays-new.cardano-testnet.iohkdev.io)”.

The warnings and errors appear at around 99.4% sync in the Babbage era.

The following has been attempted to resolve this issue:

  1. Upgraded cardano-node to 1.35.0 (from 1.30.1)
  2. Upgraded cardano-wallet to a version consistent with the new node

I get the warnings / error messages below:
image

1.35.0 should not be used:

As announced yesterday, the team is deprecating node versions 1.35.0 and 1.35.1. If you are running either of these versions, or 1.35.2 , on mainnet please roll back to 1.34.1 as soon as possible.
Thank you to all of the SPOs that have already done so. You can continue testing the Vasil functions ON THE TESTNET ONLY using the node version 1.35.2.
Telegram: Contact @SPOannouncements

2 Likes

Thanks so much for the fast response HeptaSean :slight_smile:

So if I am reading this right, if I want to run some tests on the testnet, I need cardano-node 1.35.2? It seems the latest version available for macos is 1.35.0 Hydra - Build 17255627 of job Cardano:cardano-node:macos.cardano-node-macos

Must I wait till a 1.35.2 macos version is available?

Seems they have pulled 1.35.0 from https://github.com/input-output-hk/cardano-node/releases, but not from the Hydra build cluster. …

They did not make a release for 1.35.2 and I do not know if they will, before it goes to mainnet.

You can always install from source:
https://developers.cardano.org/docs/get-started/installing-cardano-node/#macos

Just do git checkout 1.35.3-testnetonly instead of git checkout $(curl -s https://api.github.com/repos/input-output-hk/cardano-node/releases/latest | jq -r .tag_name).

EDIT: You should use version 1.35.3-testnetonly as per @Neo_Spank’s post below.

You can always see the latest tags at:
https://github.com/input-output-hk/cardano-node/tags

1 Like

Charles announced on August 1st that upcoming 1.35.3 is going to be a functional one, since there are bugs in previous versions. :point_down:

2 Likes

Well, cool that that is not in the @SPOannouncements Telegram channel that they have specifically for that and the last message there still says that 1.35.2 should be used on testnet. …

Seems SPOs also have to subscribe to Charles’ YouTube channel. …

Even though we should rollback to 1.34.1 on mainnet, we’re currently running a 1.35.0 while we get the other version ready, and its submitting transactions successfully.

Testnet on 1.35.0 is not able to start the node at all. That one forced us to stop the service. Can I still use the immutable and ledger directories from 1.35.0 when rolling back to 1.34.1?

Thanks so much Sean. Normally I would download a pre-built node from hydra and just use that so I wouldn’t have to mess with the whole cabal business (being a noob). I followed the instruction link you sent me on downloading cardano-node / cli, and after updating my operating system and many troublesome detours later I managed to get the cardano-node running again for the test-net using 1.35.3-testnetonly.

However, at 98% sync, I run into the same DNS error with the same error/warning messages as my original post. Very weird.

I am using the node below:
cardano-node 1.35.3 - darwin-x86_64 - ghc-8.10
git rev b443f540133888442e5475c05890dc2eee13d43e

Any other thoughts?

No, sorry.

Doesn’t really look like a DNS problem, though. The first warning in your screenshot just seems to be that your server cannot deal with IPv6. That’s not good, but also not fatal.

The errors below – “HeaderError” – seem to be the culprit.

Okay, sorry, should have checked that first.

According to Telegram: Contact @SPOannouncements, you will need to use 1.35.2 on the current testnet, not one of the 1.35.3s.

EDIT: If you are running a node on testnet, it is a good idea to join that Telegram announcement channel and/or IOG’s Discord at https://discord.com/invite/78G5WDRP47.

1 Like

Happy news at long last! 1.35.2 seems to be doing the trick all thanks to you Sean. Seriously, thank you so much!

{
    "block": 3759559,
    "epoch": 221,
    "era": "Babbage",
    "hash": "cac49fdf0fdb70cdcfeaa1d79bd2f1e65a9fc4397b42bd02ed98e867decd96c5",
    "slot": 65358895,
    "syncProgress": "100.00"
}
3 Likes

running cardano-node version 1.35.3 and it was working fine for a while but recently when I tried rerun the script to get latest config files from cardano, that were I see the same error above

cardano.node.DnsSubscription:Notice and cardano.node.ErrorPolicy:Warning:6901 issues

Both block producer and relay node communicate on port 3001 and each container is showing healthy status but both Guild LiveView Status: starting Total Tx : 0 and doesn’t looks right

2023-03-23T16:52:14.211881400Z [eed5c50f:cardano.node.DnsSubscription:Notice:14602012] [2023-03-23 16:52:14.13 UTC] Domain: "germany.cardanopool.xyz" Connection Attempt Start, destination 184.174.37.22:3001,
2023-03-23T16:52:14.391805711Z [eed5c50f:cardano.node.DnsSubscription:Warning:6922] [2023-03-23 16:52:14.31 UTC] Domain: "cerp-relay1.cerp.dev" Failed to start all required subscriptions,
2023-03-23T16:52:14.391859489Z [eed5c50f:cardano.node.DnsSubscription:Error:14601816] [2023-03-23 16:52:14.37 UTC] Domain: "adarelay01.psilobyte.io" Application Exception: 132.226.14.112:3001 HeaderError (At (Block {blockPointSlot = SlotNo 84844885, blockPointHash = 942543dbe4f324d8ac302f3844c1ce331d671b1dadb850990b3a8ffb7292bb0f})) (HeaderEnvelopeError (OtherHeaderEnvelopeError (HardForkEnvelopeErrFromEra S (S (S (S (S (Z (WrapEnvelopeErr {unwrapEnvelopeErr = ObsoleteNode 8 7}))))))))) (Tip (SlotNo 84844799) c001ccbfeaf34e101d63026145db80a6b739bd64ab04378517297e817035c17e (BlockNo 8400207)) (Tip (SlotNo 88023989) dd54b9154fe5611a80ecfa726297451036f961c8c89c2928254a8c02495debd4 (BlockNo 8554636)),
2023-03-23T16:52:14.471772126Z [eed5c50f:cardano.node.ErrorPolicy:Warning:6901] [2023-03-23 16:52:14.39 UTC] IP 132.226.14.112:3001 ErrorPolicySuspendPeer (Just (ApplicationExceptionTrace (HeaderError (At (Block {blockPointSlot = SlotNo 84844885, blockPointHash = 942543dbe4f324d8ac302f3844c1ce331d671b1dadb850990b3a8ffb7292bb0f})) (HeaderEnvelopeError (OtherHeaderEnvelopeError (HardForkEnvelopeErrFromEra S (S (S (S (S (Z (WrapEnvelopeErr {unwrapEnvelopeErr = ObsoleteNode 8 7}))))))))) (Tip (SlotNo 84844799) c001ccbfeaf34e101d63026145db80a6b739bd64ab04378517297e817035c17e (BlockNo 8400207)) (Tip (SlotNo 88023989) dd54b9154fe5611a80ecfa726297451036f961c8c89c2928254a8c02495debd4 (BlockNo 8554636))))) 200s 200s,
2023-03-23T16:52:14.471796762Z [eed5c50f:cardano.node.DnsSubscription:Notice:14602012] [2023-03-23 16:52:14.43 UTC] Domain: "germany.cardanopool.xyz" Connection Attempt End, destination 184.174.37.22:3001 outcome: ConnectSuccessLast,
2023-03-23T16:52:15.911641363Z [eed5c50f:cardano.node.DnsSubscription:Notice:14602048] [2023-03-23 16:52:15.81 UTC] Domain: "adarelay01.psilobyte.io" Connection Attempt Start, destination 132.226.14.112:3001,
2023-03-23T16:52:16.153165823Z [eed5c50f:cardano.node.DnsSubscription:Notice:14602048] [2023-03-23 16:52:16.03 UTC] Domain: "adarelay01.psilobyte.io" Connection Attempt End, destination 132.226.14.112:3001 outcome: ConnectSuccessLast,
2023-03-23T16:52:17.076435025Z [eed5c50f:cardano.node.ErrorPolicy:Warning:6929] [2023-03-23 16:52:16.95 UTC] IP 5.161.114.127:9041 ErrorPolicySuspendPeer (Just (ApplicationExceptionTrace (MuxError (MuxIOException writev: resource vanished (Connection reset by peer)) "(sendAll errored)"))) 20s 20s,
2023-03-23T16:52:21.881818366Z [eed5c50f:cardano.node.ErrorPolicy:Warning:6929] [2023-03-23 16:52:21.76 UTC] IP 92.204.53.48:42485 ErrorPolicySuspendPeer (Just (ApplicationExceptionTrace (MuxError (MuxIOException writev: resource vanished (Connection reset by peer)) "(sendAll errored)"))) 20s 20s,
2023-03-23T16:52:22.161676027Z [eed5c50f:cardano.node.ErrorPolicy:Warning:6929] [2023-03-23 16:52:22.04 UTC] IP 161.97.94.111:43723 ErrorPolicySuspendPeer (Just (ApplicationExceptionTrace (MuxError (MuxIOException Network.Socket.recvBuf: resource vanished (Connection reset by peer)) "(recv errored)"))) 20s 20s

ChatGPT response!

qn: issue on my cardano stack pool relay node cardano.node.DnsSubscription?

The cardano.node.DnsSubscription error typically indicates that your Cardano relay node is unable to resolve the DNS name of one or more of the nodes in your topology file. This can occur if the DNS servers your node is configured to use are not functioning correctly or if there is an issue with the DNS record for the node in question.

To troubleshoot this issue, you can try the following steps:

Check your topology file: Make sure that the IP addresses or domain names listed in your topology file are correct and up-to-date. You can also try replacing domain names with IP addresses to see if that resolves the issue.

Check your DNS servers: Verify that your DNS servers are functioning correctly and that your node is configured to use them. You can try using a different set of DNS servers to see if that resolves the issue.

Check DNS resolution on your server: Verify that your server is able to resolve DNS names by running the nslookup command. For example, you can try running nslookup relay-node.example.com to see if your server is able to resolve the DNS name for your relay node.

Restart your node: If all else fails, try restarting your Cardano node. This can sometimes resolve issues related to DNS resolution.

If the above steps do not resolve the issue, you may want to reach out to the Cardano community or seek assistance from a technical expert who is familiar with Cardano nodes and DNS resolution.