I'am trying to start full mainnet Eos node. Due to this link https://eosnodes.privex.io/ I've copied first 25 producers addresses and paste it to conifg.ini. But when i started node I got an error
2416134ms thread-0 net_plugin.cpp:2008 operator() ] connection failed to 18.221.255.38:9876: Connection refused
2416205ms thread-0 net_plugin.cpp:2008 operator() ] connection failed to 18.191.125.105:9876: Connection refused
2416220ms thread-0 net_plugin.cpp:2154 operator() ] Error reading message from 130.211.59.178:9876: Connection reset by peer
2416290ms thread-0 net_plugin.cpp:2154 operator() ] Error reading message from 159.65.214.150:9876: Connection reset by peer
2416290ms thread-0 net_plugin.cpp:2154 operator() ] Error reading message from 34.252.209.121:5556: Connection reset by peer
2416322ms thread-0 net_plugin.cpp:2154 operator() ] Error reading message from 34.226.76.22:9876: Connection reset by peer
2416322ms thread-0 net_plugin.cpp:2156 operator() ] Peer api.eosuk.io:12000 closed connection
2416408ms thread-0 net_plugin.cpp:2154 operator() ] Error reading message from 18.188.4.97:9876: Connection reset by peer
2416408ms thread-0 net_plugin.cpp:2154 operator() ] Error reading message from 18.188.38.175:9876: Connection reset by peer
2416470ms thread-0 net_plugin.cpp:2154 operator() ] Error reading message from 45.33.60.65:9820: Connection reset by peer
2416470ms thread-0 net_plugin.cpp:2154 operator() ] Error reading message from 54.153.59.31:9999: Connection reset by peer
2416750ms thread-0 net_plugin.cpp:2154 operator() ] Error reading message from boot.eostitan.com:9876: Connection reset by peer
2416750ms thread-0 net_plugin.cpp:2154 operator() ] Error reading message from 13.230.91.225:9865: Connection reset by peer
2416832ms thread-0 net_plugin.cpp:2154 operator() ] Error reading message from 123.59.116.52:49876: Connection reset by peer
2416833ms thread-0 net_plugin.cpp:2156 operator() ] Peer 807534da.eosnodeone.io:19872 closed connection
2425902ms thread-0 net_plugin.cpp:2154 operator() ] Error reading message from api-full1.eoseoul.io:9876: Bad file descriptor
2441503ms thread-0 net_plugin.cpp:2154 operator() ] Error reading message from 106.10.42.238:9876: Bad file descriptor
2446919ms thread-0 net_plugin.cpp:1966 connect ] host: 106.10.42.238 port: 9876
2446919ms thread-0 net_plugin.cpp:1966 connect ] host: 123.59.116.52 port: 49876
2446919ms thread-0 net_plugin.cpp:1966 connect ] host: 13.230.91.225 port: 9865
2446919ms thread-0 net_plugin.cpp:1966 connect ] host: 130.211.59.178 port: 9876
2446919ms thread-0 net_plugin.cpp:1966 connect ] host: 159.65.214.150 port: 9876
2446919ms thread-0 net_plugin.cpp:1966 connect ] host: 18.188.38.175 port: 9876
2446919ms thread-0 net_plugin.cpp:1966 connect ] host: 18.188.4.97 port: 9876
2446919ms thread-0 net_plugin.cpp:1966 connect ] host: 18.191.125.105 port: 9876
2446920ms thread-0 net_plugin.cpp:1966 connect ] host: 18.221.255.38 port: 9876
2446920ms thread-0 net_plugin.cpp:1966 connect ] host: 34.226.76.22 port: 9876
2446920ms thread-0 net_plugin.cpp:1966 connect ] host: 34.252.209.121 port: 5556
2446920ms thread-0 net_plugin.cpp:1966 connect ] host: 45.33.60.65 port: 9820
2446920ms thread-0 net_plugin.cpp:1966 connect ] host: 54.153.59.31 port: 9999
2446920ms thread-0 net_plugin.cpp:1966 connect ] host: 807534da.eosnodeone.io port: 19872
2446920ms thread-0 net_plugin.cpp:1966 connect ] host: api-full1.eoseoul.io port: 9876
2446920ms thread-0 net_plugin.cpp:1966 connect ] host: api.eosuk.io port: 12000
2446920ms thread-0 net_plugin.cpp:1966 connect ] host: boot.eostitan.com port: 9876
2450308ms thread-0 net_plugin.cpp:2008 operator() ] connection failed to 18.221.255.38:9876: Connection refused
2450308ms thread-0 net_plugin.cpp:2008 operator() ] connection failed to 18.191.125.105:9876: Connection refused
2450309ms thread-0 net_plugin.cpp:2156 operator() ] Peer 54.153.59.31:9999 closed connection
2450309ms thread-0 net_plugin.cpp:2156 operator() ] Peer 807534da.eosnodeone.io:19872 closed connection
2450309ms thread-0 net_plugin.cpp:2156 operator() ] Peer api.eosuk.io:12000 closed connection
2450309ms thread-0 net_plugin.cpp:2156 operator() ] Peer boot.eostitan.com:9876 closed connection
2450309ms thread-0 net_plugin.cpp:2156 operator() ] Peer 130.211.59.178:9876 closed connection
2450309ms thread-0 net_plugin.cpp:2156 operator() ] Peer 159.65.214.150:9876 closed connection
2450309ms thread-0 net_plugin.cpp:2156 operator() ] Peer 34.252.209.121:5556 closed connection
2450309ms thread-0 net_plugin.cpp:2156 operator() ] Peer 34.226.76.22:9876 closed connection
2450309ms thread-0 net_plugin.cpp:2156 operator() ] Peer 18.188.4.97:9876 closed connection
2450309ms thread-0 net_plugin.cpp:2156 operator() ] Peer 18.188.38.175:9876 closed connection
2450309ms thread-0 net_plugin.cpp:2156 operator() ] Peer 45.33.60.65:9820 closed connection
2450309ms thread-0 net_plugin.cpp:2156 operator() ] Peer 13.230.91.225:9865 closed connection
2450309ms thread-0 net_plugin.cpp:2156 operator() ] Peer 123.59.116.52:49876 closed connection
2466814ms thread-0 producer_plugin.cpp:290 on_incoming_block ] Received block 773442461081ec11... #8000 @ 2018-06-09T13:05:06.000 signed by eosio [trxs: 0, lib: 7999, conf: 0, latency: 516960814 ms]
The strange thing that syncing of node going not bad but this log looks really scary. Is it mean that I'am using wrong node addresses?
The public nodes do not allow unlimited numbers of connections. Many of the initial public endpoints are likely to have reached their limits. The network does not self-organize, so you'll need to find alternative links, and remove those that are refusing to stay connected.
Since you're using net_plugin, you can do this without restarting, as long as you've also loaded net_api_plugin. With net_api_plugin loaded, you can use cleos to issue net connect, net disconnect, and net peers commands to add new connections, remove bad connections, and examine the status of all configured connections, respectively.
If you don't have net_api_plugin in your config file, wait until your nodeos has completed synchronizing with the public network, then shut it down and restart it with net_api_plugin added. You can cull your config file of unresponsive peers while you're at it.
Note that net disconnect does not remove a peer from config.ini. If a configured peer persistently refuses connections, you can net disconnect it to stop the errors in the log without restarting, but you'll also need to edit the config.ini file to remove the entry for the next time you restart.
I also met this problem, have you solved it๏ผ
same issue. how can I tell if the node is syncing and its progress?
@r3lik The nodeos console prints logging information during sync. You may also use cleos get info to retrieve your local node information. Both the head_block_num and the last_irreversible_block_num will track with the progress the local node is making. Here's a sample of a node just beginning mainnet synchronization:
{
"server_version": "d9982e3f",
"chain_id": "aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906",
"head_block_num": 1756,
"last_irreversible_block_num": 1755,
"last_irreversible_block_id": "000006db1e043a53136fa42fbbed30d4de48adb443ecbee48dd81cadfc6e6253",
"head_block_id": "000006dc094383b4a60bbaaba53f26522d472eb2ec118263127b5d76219eef74",
"head_block_time": "2018-06-09T12:12:51.000",
"head_block_producer": "eosio",
"virtual_block_cpu_limit": 377976295,
"virtual_block_net_limit": 6067352,
"block_cpu_limit": 100000000,
"block_net_limit": 1048576,
"server_version_string": "v1.3.1-86-gd9982e3-dirty"
}
Most helpful comment
The public nodes do not allow unlimited numbers of connections. Many of the initial public endpoints are likely to have reached their limits. The network does not self-organize, so you'll need to find alternative links, and remove those that are refusing to stay connected.
Since you're using net_plugin, you can do this without restarting, as long as you've also loaded net_api_plugin. With net_api_plugin loaded, you can use cleos to issue
net connect,net disconnect, andnet peerscommands to add new connections, remove bad connections, and examine the status of all configured connections, respectively.If you don't have net_api_plugin in your config file, wait until your nodeos has completed synchronizing with the public network, then shut it down and restart it with net_api_plugin added. You can cull your config file of unresponsive peers while you're at it.
Note that
net disconnectdoes not remove a peer from config.ini. If a configured peer persistently refuses connections, you cannet disconnectit to stop the errors in the log without restarting, but you'll also need to edit the config.ini file to remove the entry for the next time you restart.