search

EOSIO / eos

An open source smart contract platform
https://developers.eos.io/manuals/eos
MIT License
11.27k stars 3.6k forks source link

nodeos on 1.7.3 stops syncing on Jungle network #7382

Closed bert2002 closed 5 years ago

bert2002 commented 5 years ago

Hi, my nodeos with 1.7.3 suddenly stopped synchronizing and I dont't see any error.

$ curl -s http://localhost:8888/v1/chain/get_info | jq
{
  "server_version": "448287d5",
  "chain_id": "e70aaab8997e1dfce58fbfac80cbbb8fecec7b99cf982a9444273cbc64c41473",
  "head_block_num": 27790597,
  "last_irreversible_block_num": 27778492,
  "last_irreversible_block_id": "01a7ddbc7f5898d2afb4c90400d3c06f9bd69588dd6058231675c027865a9821",
  "head_block_id": "01a80d056e33a4ed9c677fb1fb9e7b624f1d551004f2b2c7b5fd2bf7e18e590b",
  "head_block_time": "2019-05-10T07:29:11.500",
  "head_block_producer": "blockchained",
  "virtual_block_cpu_limit": 200000000,
  "virtual_block_net_limit": 524288000,
  "block_cpu_limit": 200000,
  "block_net_limit": 524288,
  "server_version_string": "v1.7.3"
}

Config:

$ grep -v "#" /home/nodeos/.local/share/eosio/nodeos/config/config.ini 
bnet-endpoint = 0.0.0.0:4321
bnet-no-trx = false
blocks-dir = "blocks"
chain-state-db-size-mb = 8192
reversible-blocks-db-size-mb = 340
contracts-console = false
https-client-validate-peers = 1
http-server-address = 0.0.0.0:8888
access-control-allow-credentials = false
p2p-listen-endpoint = 0.0.0.0:9876
p2p-peer-address = jungle2.cryptolions.io:9876
p2p-peer-address = jungle2.cryptolions.io:19876
p2p-peer-address = jungle.eosn.io:9876
p2p-peer-address = peer.eos-jungle.eosblocksmith.io:9876
p2p-peer-address = jungle.eosbcn.com:2095
p2p-peer-address = jungle.eosmetal.io:19876
p2p-peer-address = jungle2-eos.blckchnd.com:9876
p2p-peer-address = 88.99.193.44:9876
p2p-peer-address = junglepeer.eossweden.se:9876
p2p-peer-address = bp4-d3.eos42.io:9876
p2p-peer-address = jungle2.cryptolions.io:9876
p2p-peer-address = jungle.eosamsterdam.net:9876
p2p-max-nodes-per-host = 1
agent-name = "UltimateEOS"
allowed-connection = any
max-clients = 25
connection-cleanup-period = 30
network-version-match = 0
sync-fetch-span = 100
enable-stale-production = false
pause-on-startup = false
max-transaction-time = 30
max-irreversible-block-age = -1
verbose-http-errors = true
http-validate-host = 0
signature-provider = SOMETHING=KEY:SOMETHINGELSE
keosd-provider-timeout = 5
txn-reference-block-lag = 0
plugin = eosio::chain_api_plugin
plugin = eosio::history_api_plugin
plugin = eosio::history_plugin
plugin = eosio::chain_plugin
plugin = eosio::http_plugin
filter-on=*

Any idea why this can be cause or how I can dig for more logs/problems?

Many thanks, bert

benjamintshi commented 5 years ago

I have the same problem. at 27778814 block hight 3030000 block_validate_exception: Block exception bad signed_block : Unlinkable block

heifner commented 5 years ago

Jungle upgraded to 1.8 rc2 and enabled a consensus change. Therefore, only 1.8 versions of eosio will work with Jungle.