-1

I am new to ethereum and right now getting the ethereum blockchain using geth with

geth --port 3000 --networkid 58342 --rpc --rpcport 8545 --rpcaddr 10.0.0.2 --rpccorsdomain "*" console

INFO [03-20|11:41:12] Block synchronisation started 
WARN [03-20|11:41:12] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:41:12] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
> net.peerCount
1
> net.listeningWARN [03-20|11:41:22] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:41:22] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"

true
> WARN [03-20|11:41:32] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:41:32] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:41:42] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:41:42] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:41:52] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:41:52] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:42:02] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:42:02] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:42:12] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:42:12] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:42:22] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:42:22] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:42:32] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:42:32] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:42:42] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:42:42] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:42:52] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:42:52] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:43:02] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:43:02] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:43:12] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:43:12] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:43:22] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:43:22] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:43:32] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:43:32] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:43:42] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
WARN [03-20|11:43:42] Synchronisation failed, retrying         err="state node c56d5a…f2fb4a failed with all peers (1 tries, 1 peers)"
> admin.nodeInfo.enoWARN [03-20|11:43:52] Node data write error                    err="state node c56d5a…f2fb4a failed with all peers (1 tries,
14
  • What is you geth version? Are you syncing mainnet or some testnet? Do you have enough disk space?
    – Ismael
    Mar 20, 2018 at 7:50
  • my geth version is Mar 20, 2018 at 8:04
  • Geth Version: 1.8.2-stable Git Commit: b8b9f7f4476a30a0aaf6077daade6ae77f969960 Architecture: amd64 Protocol Versions: [63 62] Network Id: 1 Go Version: go1.9.4 Operating System: linux GOPATH=/go GOROOT=/usr/local/go testnet Mar 20, 2018 at 8:04
  • Geth version:1.8 stable and running testnet Mar 20, 2018 at 10:02
  • What is the command line used to launch geth? It seems you do not have enough peers and the version of geth seems correct.
    – Ismael
    Mar 20, 2018 at 14:36

2 Answers 2

0

trying using geth --testnet for the ropsten test net, it will take a few hours to sync or maybe days depending on your connection. otherwise if you want a cop of the main chain you can use geth --light this will give you a light sync of the blockchain that allows you to interact with the main-net. Syncing time should only be about 5-10 mins for --light. you can check sync percentage by opening up a new terminal and using geth --attach for light sync or geth --testnet attach for ropsten. this will allow you to check sync status by using "eth.syncing" you can then compare your current block size against etherscan or ether chain.org.

there are also other options to get a node running on your machine such as testrpc, ganache-cli but these are just local nodes that are a representation of the Ethereum blockchain.

5
  • Sorry to say this,I tried this one whatever you given geth attach for light sync or geth --testnet attach but i am getting same above error only in my peer system Mar 21, 2018 at 9:48
  • Sorry to say this,I tried this one whatever you given geth attach for light sync or geth --testnet attach but i am getting same above error only in my peer system(I connected one system as node and another system as a peer) Mar 21, 2018 at 9:56
  • u must have a bad connection, (and a node is a peer)
    – conwise17
    Mar 21, 2018 at 14:47
  • geth --light is fully synced once u start getting 1 block header around every 15 seconds
    – conwise17
    Mar 21, 2018 at 14:48
  • I got same problem in two systems.If one connection is bad connection, another connection is also i am getting same error ,i connected with two peers (another system also same problem only) Mar 22, 2018 at 4:43
0

Probably you have two different nodes trying to sync their own versions of chain databases with yours. If that is the case, disconnect the other nodes and try to resync them with the correct node .

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.