Mining mostly stale blocks

timothyjcoultertimothyjcoulter Member Posts: 14
edited May 2015 in Mining
I seem to be having an issue with network connectivity, or ensuring my stays up to date with the Ethereum network. I have roughly 75Mh of hashing power, yet still continue to get output like this. Notice most of them are stale:
I0522 08:39:16.962523 19639 worker.go:233] Mined block #414937 (cfa2d102)
I0522 08:44:32.142867 19639 worker.go:233] Mined stale-block #414976 (d09a2643)
I0522 08:48:34.003390 19639 worker.go:233] Mined stale-block #415003 (5183e650)
I0522 08:56:43.517278 19639 worker.go:233] Mined stale-block #415060 (23e80137)
I0522 08:59:25.216364 19639 worker.go:233] Mined stale-block #415083 (1e46d8eb)
I0522 09:00:13.808364 19639 worker.go:233] Mined stale-block #415090 (fc2cca44)
I0522 09:01:12.192435 19639 worker.go:233] Mined stale-block #415098 (ce9a6b00)
I0522 09:09:11.020503 19639 worker.go:233] Mined stale-block #415159 (ae259f67)
I0522 09:11:19.188869 19639 worker.go:233] Mined stale-block #415174 (72e54bf0)
I0522 09:15:56.904933 19639 worker.go:233] Mined stale-block #415210 (7eca1122)
I0522 09:21:07.471138 19639 worker.go:233] Mined block #415250 (6049afc2)
I0522 09:21:53.169252 19639 worker.go:233] Mined stale-block #415254 (88cb44d8)
I0522 09:32:37.262367 19639 worker.go:233] Mined block #415346 (2bd13d2c)
I0522 09:39:32.639950 19639 worker.go:233] Mined stale-block #415395 (ede0fd1c)
I0522 09:48:36.869111 19639 worker.go:233] Mined stale-block #415463 (503c796c)
I0522 10:04:51.704829 19639 worker.go:233] Mined stale-block #415587 (43568f41)
I0522 10:06:30.619789 19639 worker.go:233] Mined stale-block #415600 (8026e28e)
I0522 10:08:37.206093 19639 worker.go:233] Mined stale-block #415616 (d212670d)
I0522 10:11:07.945560 19639 worker.go:233] Mined block #415630 (25813961)
I0522 10:15:56.046998 19749 worker.go:233] Mined stale-block #415668 (7234551e)
I0522 10:32:43.590873 20355 worker.go:233] Mined block #415789 (e79b7bb7)
I0522 10:38:53.252240 20355 worker.go:233] Mined stale-block #415833 (3c5f1d08)
I0522 10:40:31.699225 20355 worker.go:233] Mined stale-block #415844 (f220123e)
I'm running geth on Debian Wheezy built from source, per the instructions on the github repository. I'm using port forwarding on my router to send port 30303 to the Debian box. To mine, I'm running cpp-ethereum on Windows, also built from source, however I *assume* this isn't a cpp-ethereum issue. But who knows.

Here are some errors I see frequently from geth. I have no idea what they mean, but they could help diagnose the issue:
Synchronisation canceled: peer TD too small
Handshake with 86.130.17.33:56162 failed: encryption handshake failed: could not decrypt auth message (ecies: invalid message)
tx error: Known transaction (86f14bf5)
Handshake with 94.242.229.4:36135 failed: Too many peers
In total, I think the above errors are preventing me from staying well-connected to the network. Any ideas are much appreciated.

Comments

  • peter_wallinpeter_wallin Member Posts: 5
    edited July 2015
    i see stale block messages in my logs as well, although I do not have as much hashing power as you. I am running latest geth on Ubuntu with ethminer.

    geth seems to be working fine.....

    > admin.chainSyncStatus
    {
      blocksAvailable: 0,
      blocksWaitingForImport: 0,
      estimate: '0',
      importing: 0
    }
    Post edited by StephanTual on
Sign In or Register to comment.