Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 17.3K All Categories
- 9.4K Mining
- 573 Pool Discussion
- 372 Promotional
- 1.4K General Project Discussion (non-technical)
- 485 Education
- 810 Protocol and Client discussion
- 169 web3-js
- 29 Whisper
- 16 Swarm
- 3 RLP
- 303 IoT & Hardware
- 1.2K Smart Contracts and Dapps
- 28 Serpent
- 358 Solidity
- 662 Projects
- 1.2K Reference clients code and builds
- 249 Eth & AlethZero- Cpp Implementation
- 470 Geth - Go Implementation
- 242 Mist
- 15 Node.js Implementation
- 36 Python Implementation
- 49 Mix
- 36 Other Implementations
- 170 Meetups
- 40 Other Events
- 225 Jobs & Skills
- 281 Press and Articles
- 75 Audio/Video
- 296 Ether Sale
- 1.2K Other Languages
- 96 Chinese
- 255 German
- 33 Italian
- 110 French
- 3 Hebrew
- 42 Japanese
- 75 Portugese
- 46 Romanian
- 184 Russian
- 230 Spanish
- 47 Turkish
- 125 Watercooler
Have been trying to run a node for more than 3 weeks - still synching 24/7
ldrapeau
Member Posts: 89 ✭
Hi,
Can anyone explain why my node is still synching (I'm at block 2319873 - as of 2016-11-10_17:50 EST), I have a fresh install of linux 16.04, a 500G WD black drive, 2G of RAM and fiber to the home ethernet connection that is really good. It is taking for ever to sync, I can confirm the iotop is in the roof with 1000+ K/S on the reads all the time. At the current rate I will never catch up because new clocks are added faster than the ones I'm catching up with. Am I the only one with this issue? I must be missing something major. Thanks, Louis
Can anyone explain why my node is still synching (I'm at block 2319873 - as of 2016-11-10_17:50 EST), I have a fresh install of linux 16.04, a 500G WD black drive, 2G of RAM and fiber to the home ethernet connection that is really good. It is taking for ever to sync, I can confirm the iotop is in the roof with 1000+ K/S on the reads all the time. At the current rate I will never catch up because new clocks are added faster than the ones I'm catching up with. Am I the only one with this issue? I must be missing something major. Thanks, Louis
Comments
I1123 10:16:42.432032 core/blockchain.go:1001] imported 1 block(s) (0 queued 0 ignored) including 4 txs in 13m11.033082301s. #2335707 [d5b19d58 / 3c1b0faa]