Jormungandr 0.8.9 not bootstraping in itn_rewards_v1

Hey!

For weeks I am waiting for more reliable node than jormungandr 0.8.6 but > 0.8.7 including 0.8.9 does not bootstrap in itn_rewards_v1. Config & genesis hash I copied several times from https://hydra.iohk.io/build/1647490/download/1/index.html.

Here is what I am getting & got using fresh setup & jormungandr 0.8.9:

Feb 06 15:53:12.096 WARN unable to reach peer for block download, reason: HTTP/2.0 connection error, peer_address: 3.125.31.84:3000, block: 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, task: init
Feb 06 15:53:12.096 INFO fetching block 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, peer_address: 52.9.77.197:3000, block: 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, task: init
Feb 06 15:53:43.584 WARN unable to reach peer for block download, reason: HTTP/2.0 connection error, peer_address: 52.9.77.197:3000, block: 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, task: init
Feb 06 15:53:43.584 INFO fetching block 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, peer_address: 3.115.154.161:3000, block: 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, task: init
Feb 06 15:53:43.584 WARN unable to reach peer for block download, reason: HTTP/2.0 connection error, peer_address: 52.9.77.197:3000, block: 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, task: init
Feb 06 15:53:43.584 INFO fetching block 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, peer_address: 3.115.154.161:3000, block: 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, task: init
Feb 06 15:53:46.794 WARN failed to download block, error: GetBlocks { source: Error { code: Unknown, source: Status { code: Unknown, message: "connection error: broken pipe" } } }, peer_address: 3.115.154.161:3000, block: 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, task: init
Feb 06 15:53:46.795 INFO fetching block 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, peer_address: 18.182.115.51:3000, block: 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, task: init
Feb 06 15:53:46.795 WARN failed to download block, error: GetBlocks { source: Error { code: Unknown, source: Status { code: Unknown, message: "connection error: broken pipe" } } }, peer_address: 3.115.154.161:3000, block: 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, task: init
Feb 06 15:53:46.795 INFO fetching block 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, peer_address: 18.182.115.51:3000, block: 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676, task: init


Error fetching the genesis block from the network
|-> could not download block hash 8e4d2a343f3dcf9330ad9035b3e8d168e6728904262f2c434a4f8f934ec7b676

Apparently <= 0.8.6 works without any problems with the same config (but saturates cpu within 3 hours).

Any ideas?

hi,

hmm… 0.8.9 is working fine for me here.

i use the following trusted peers in the config.yaml:

[{“address”:"/ip4/3.125.31.84/tcp/3000",“id”:“8f9ff09765684199b351d520defac463b1282a63d3cc99ca”},{“address”:"/ip4/13.112.181.42/tcp/3000",“id”:“52762c49a84699d43c96fdfe6de18079fb2512077d6aa5bc”},{“address”:"/ip4/85.235.66.63/tcp/3000",“id”:“37ebe81f84a9bf3b499cf3972219475e6bb3fa3661d53dc2”},{“address”:"/ip4/54.183.149.167/tcp/3000",“id”:“df02383863ae5e14fea5d51a092585da34e689a73f704613”},{“address”:"/ip4/3.125.75.156/tcp/3000",“id”:“22fb117f9f72f38b21bca5c0f069766c0d4327925d967791”},{“address”:"/ip4/18.177.78.96/tcp/3000",“id”:“fc89bff08ec4e054b4f03106f5312834abdf2fcb444610e9”},{“address”:"/ip4/52.9.77.197/tcp/3000",“id”:“fcdf302895236d012635052725a0cdfc2e8ee394a1935b63”},{“address”:"/ip4/3.124.116.145/tcp/3000",“id”:“99cb10f53185fbef110472d45a36082905ee12df8a049b74”},{“address”:"/ip4/52.8.15.52/tcp/3000",“id”:“18bf81a75e5b15a49b843a66f61602e14d4261fb5595b5f5”},{“address”:"/ip4/52.9.132.248/tcp/3000",“id”:“671a9e7a5c739532668511bea823f0f5c5557c99b813456c”},{“address”:"/ip4/13.56.0.226/tcp/3000",“id”:“7ddf203c86a012e8863ef19d96aabba23d2445c492d86267”},{“address”:"/ip4/13.114.196.228/tcp/3000",“id”:“7e1020c2e2107a849a8353876d047085f475c9bc646e42e9”},{“address”:"/ip4/3.115.154.161/tcp/3000",“id”:“35bead7d45b3b8bda5e74aa12126d871069e7617b7f4fe62”}]

What OS do you run?

1 Like

oh, and have you specified the storage and the topics of interest to high?

{
“log”: [
{
“format”: “plain”,
“level”: “info”,
“output”: “stderr”
}
],
“storage”: “./storage/”,
“p2p”: {
“listen_address”: “/ip4/0.0.0.0/tcp/3000”,
“public_address”: “/ip4/0.0.0.0/tcp/3000”,
“topics_of_interest”: {
“blocks”: “high”,
“messages”: “high”
},

I had the same problem.
I was able to get it to bootstrap by removing all of the trusted peers from the
config file.
I think that will only work if your node was previously on the network and seen
by other nodes who will then reconnect with you.
I have also seen it recommended to set the following config paramter but I have
n’t tried it yet:
max_bootstrap_attempts: 0
I am guessin that will only work for an exiting node as well.
Hope that helps.
Shawn Squid Pool

@ATADA I changed trusted peers to yours with no luck

9bff08ec4e054b4f03106f5312834abdf2fcb444610e9, peer_addr: 18.177.78.96:3000, task: network
Feb 07 06:43:15.017 INFO connection to peer failed, reason: protocol handshake failed: unknown error (grpc-status: Unknown, grpc-message: "connection error: broken pipe"), node_id: fc89bff08ec4e054b4f03106f5312834abdf2fcb444610e9, peer_addr: 18.177.78.96:3000, task: network
Feb 07 06:43:15.057 INFO connection to peer failed, reason: protocol handshake failed: unknown error (grpc-status: Unknown, grpc-message: "connection error: broken pipe"), node_id: 671a9e7a5c739532668511bea823f0f5c5557c99b813456c, peer_addr: 52.9.132.248:3000, task: network
Feb 07 06:43:15.057 INFO connection to peer failed, reason: protocol handshake failed: unknown error (grpc-status: Unknown, grpc-message: "connection error: broken pipe"), node_id: 671a9e7a5c739532668511bea823f0f5c5557c99b813456c, peer_addr: 52.9.132.248:3000, task: network
Feb 07 06:43:15.127 INFO connection to peer failed, reason: protocol handshake failed: unknown error (grpc-status: Unknown, grpc-message: "connection error: broken pipe"), node_id: df02383863ae5e14fea5d51a092585da34e689a73f704613, peer_addr: 54.183.149.167:3000, task: network
Feb 07 06:43:15.127 INFO connection to peer failed, reason: protocol handshake failed: unknown error (grpc-status: Unknown, grpc-message: "connection error: broken pipe"), node_id: df02383863ae5e14fea5d51a092585da34e689a73f704613, peer_addr: 54.183.149.167:3000, task: network
Feb 07 06:43:15.153 INFO connection to peer failed, reason: protocol handshake failed: unknown error (grpc-status: Unknown, grpc-message: "connection error: broken pipe"), node_id: 18bf81a75e5b15a49b843a66f61602e14d4261fb5595b5f5, peer_addr: 52.8.15.52:3000, task: network
Feb 07 06:43:15.153 INFO connection to peer failed, reason: protocol handshake failed: unknown error (grpc-status: Unknown, grpc-message: "connection error: broken pipe"), node_id: 18bf81a75e5b15a49b843a66f61602e14d4261fb5595b5f5, peer_addr: 52.8.15.52:3000, task: network
Feb 07 06:43:15.296 INFO connection to peer failed, reason: protocol handshake failed: unknown error (grpc-status: Unknown, grpc-message: "connection error: broken pipe"), node_id: 99cb10f53185fbef110472d45a36082905ee12df8a049b74, peer_addr: 3.124.116.145:3000, task: network
Feb 07 06:43:15.297 INFO connection to peer failed, reason: protocol handshake failed: unknown error (grpc-status: Unknown, grpc-message: "connection error: broken pipe"), node_id: 99cb10f53185fbef110472d45a36082905ee12df8a049b74, peer_addr: 3.124.116.145:3000, task: network
Feb 07 06:43:16.256 INFO failed to connect to peer, reason: Connection timed out (os error 110), node_id: 7ddf203c86a012e8863ef19d96aabba23d2445c492d86267, peer_addr: 13.56.0.226:3000, task: network
Feb 07 06:43:16.256 INFO failed to connect to peer, reason: Connection timed out (os error 110), node_id: 7ddf203c86a012e8863ef19d96aabba23d2445c492d86267, peer_addr: 13.56.0.226:3000, task: network
Feb 07 06:43:16.256 INFO failed to connect to peer, reason: Connection timed out (os error 110), node_id: fcdf302895236d012635052725a0cdfc2e8ee394a1935b63, peer_addr: 52.9.77.197:3000, task: network
Feb 07 06:43:16.256 INFO failed to connect to peer, reason: Connection timed out (os error 110), node_id: fcdf302895236d012635052725a0cdfc2e8ee394a1935b63, peer_addr: 52.9.77.197:3000, task: network
Feb 07 06:43:16.257 INFO failed to connect to peer, reason: Connection timed out (os error 110), node_id: 7e1020c2e2107a849a8353876d047085f475c9bc646e42e9, peer_addr: 13.114.196.228:3000, task: network
Feb 07 06:43:16.257 INFO failed to connect to peer, reason: Connection timed out (os error 110), node_id: 7e1020c2e2107a849a8353876d047085f475c9bc646e42e9, peer_addr: 13.114.196.228:3000, task: network
Feb 07 06:43:16.257 INFO failed to connect to peer, reason: Connection timed out (os error 110), node_id: 8f9ff09765684199b351d520defac463b1282a63d3cc99ca, peer_addr: 3.125.31.84:3000, task: network
Feb 07 06:43:16.257 INFO failed to connect to peer, reason: Connection timed out (os error 110), node_id: 8f9ff09765684199b351d520defac463b1282a63d3cc99ca, peer_addr: 3.125.31.84:3000, task: network
Feb 07 06:43:16.257 INFO failed to connect to peer, reason: Connection timed out (os error 110), node_id: 22fb117f9f72f38b21bca5c0f069766c0d4327925d967791, peer_addr: 3.125.75.156:3000, task: network
Feb 07 06:43:16.257 INFO failed to connect to peer, reason: Connection timed out (os error 110), node_id: 22fb117f9f72f38b21bca5c0f069766c0d4327925d967791, peer_addr: 3.125.75.156:3000, task: network
F

I run it on Ubuntu 18.04 on Google Cloud Platform VM, what is your os/platform?

Actually my pool node on a different machine which used to work for the last 2 months is not booting since yesterday :frowning:

Did you enter your public and listen IP adress in de config?
Did you open the right ports, trough your router/firewall?

@Micro86 I opened 3000 & 3100 ports and as it is just a node It does not need public IP in config, am I wrong?

No I don’t think so. But could help.
I als had these problems, could not connect after a reboot of Jormungandr.

After I deleted the trusted peers it connected immediately. But that pool-nodewas running a while.
Don’t know if it will connect if it is a new setup.

How long did you wait to connect??

My pool node on 0.8.6 was restarted 9pm UTC yesterday (10 hours ago) and did not bootstrap anymore. (nothing changed there for last 2 weeks when it worked good).

Fresh node on 0.8.9 never booted successfully (I am trying it for 1.5 days now).

I also have the boottrap issue since yesterday night (version 0.8.9):

error:
PullRequestFailed { source: Error { code: Unknown, source: Status { code: Unknown, message: “connection error: broken pipe” } } }

hi,

hmm. you can add my node to the list with id:0 and give it a try…

{"address":"/ip4/185.164.6.221/tcp/54322","id":"000000000000000000000000000000000000000000000000"}

i’am running debian10 on my stakepool, so shouldn’t make a difference at all.

1 Like

@ATADA

It worked after changing your id to {"address":"/ip4/185.164.6.221/tcp/54322","id":"64e8a1acfd065102fe268fd874f00e910e1794eb49ec71d6"}

Pool started immediately, fresh node is fetching block.

So conclusion of this issue that trusted node that can be found in official documentation do not work with most recent jormungandr versions.

Thank you!

ah yes, id 00… was for my internal testing. ok i’am glad you’re bootstrapping now.

my pool starts working as well after updating the trusted peers (from https://adapools.org/peers . Thanks :beers:)

What file is the file name? I did not find max_bootstrap_attempts:0 in the yaml file.

I follow the guide of “https://github.com/input-output-hk/shelley-testnet/blob/master/docs/stake_pool_operator_how_to.md#check-that-the-node-syncing
But, three days went, I haven’t synced all of blocks yet.

It goes in the p2p secion of your config.yaml file.

1 Like

Added and its bootstrapping now…

But why does your address work and the others dont? Also how will i know when its complete, how many MB, GB’s?

hi,

around 250MB i think.

you can bootstrap from any synced node on the net. the trusted peers in the list are IOHK nodes, most of them are currently down or false-marked as quarantined.

i’am glad i can help you out.

ciao
martin

1 Like

I am in trouble with the same problem. Please help me.
What exactly is removing trusted peers?
Would you please show me your config file?