I issue eth.syncing and get false even when at the same time blocks are imported. Is this correct behaviour?
Using geth version 1.4.6
[Ethereum] In geth, `eth.syncing` gives `false` even when blocks are imported
go-ethereum
Related Solutions
I've seen this "looping" behavior in the past and I would suggest deleting the chaindata and then running geth --fast --cache=1024.
The default datadir is:
Mac: ~/Library/Ethereum
Linux: ~/.ethereum
Windows: %APPDATA%/Ethereum
Delete the chaindata subdirectory that you find.
You are on the non-forked chain.
From http://fork.ethstats.net/:
The non-forked chain (Ethereum Classic / ETC) does not have many clients or miners and you would therefore experience the slow syncing.
If you intend to be on the hard-forked chain, you will have to specify the geth option:
geth --support-dao-fork console
If you want to fast sync, you will firstly have to remove your current chain:
geth removedb
The start the fast sync:
geth --support-dao-fork --fast console
Also, you will need to be using geth v 1.4.10 or above
geth version
Geth
Version: 1.4.10-stable
...
You can check which chain geth is configured to use by typing:
geth console
...
I0726 13:16:17.848871 cmd/utils/flags.go:842] ------------------------------------------------------------------------------------------------
I0726 13:16:17.848917 cmd/utils/flags.go:843] Geth is currently configured to SUPPORT the DAO hard-fork!
I0726 13:16:17.848936 cmd/utils/flags.go:844] You can change your choice prior to block #1920000 with --support-dao-fork or --oppose-dao-fork.
I0726 13:16:17.848955 cmd/utils/flags.go:845] After the hard-fork block #1920000 passed, changing chains requires a resync from scratch!
I0726 13:16:17.848973 cmd/utils/flags.go:846] ------------------------------------------------------------------------------------------------
See also:
Best Answer
Yes, correct behavior.
falsemeans that your Geth is up to date and is not currently syncing. It keeps importing the latest block to remain up to date. Checketh.blockNumberagainst a block explorer if you want to double-check.EDIT:
web3.eth.isSyncing()will also returnfalsewhen syncing has not yet started (or is currently not running). If this is the case, you need to check your networking that you are connecting to peers: Why doesn't my Ethereum node have any peers?