Miner committing new work, but haven't seen "Mined block" yet

dimfelddimfeld Member Posts: 22
edited July 2015 in Mining
I'm running geth with ethminer on the Frontier network, and everything appears to be working properly. I verified that my latest block numbers are the same as those on http://stats.ethdev.com and I have some peers, so I think I've generated the genesis file properly and am connected to the right network.

I've been running for a few hours , I have yet to see the "Mined block #XXX" log message, and my account balance still reads 0. I'm getting about 7.6M H/s. Is this expected, or might it point to something wrong?

My understanding is that the *first* node to solve the block gets the primary credit for mining it, and there's the concept of an uncle which I haven't looked into yet. This could all mean that everything is ok, but I just want to make sure. The existing guides and screenshots make it look like I should be getting mined blocks all the time, but I can understand if that might be different on the production network given more nodes and higher difficulty. I'm new to blockchains and just not really sure what to expect, so I want to make sure I actually have it set up right.

EDIT: It also occurs to me that most of the people currently running mining setups may have fairly high end rigs with R9s, whereas I'm running an Nvidia GTX 660. That could put me at a relative disadvantage when it comes to block solving speed, which I assume may even out a bit more as Ethereum hopefully becomes more popular.

Here's some output from my geth instance:
I0730 23:48:17.298129   12416 worker.go:489] commit new work on block 8637 with
0 txs & 0 uncles. Took 1ms
I0730 23:48:23.563488   12416 chain_manager.go:672] imported 1 block(s) (0 queue
d 0 ignored) including 0 txs in 2.0001ms. #8637 [6dc702c7 / 6dc702c7]
I0730 23:48:23.564488   12416 worker.go:489] commit new work on block 8638 with
0 txs & 0 uncles. Took 0
I0730 23:48:23.786500   12416 chain_manager.go:672] imported 0 block(s) (0 queue
d 2 ignored) including 0 txs in 3.0001ms. #8637 [544d62de / 6dc702c7]
I0730 23:48:51.229070   12416 chain_manager.go:672] imported 1 block(s) (0 queue
d 0 ignored) including 0 txs in 3.0002ms. #8638 [ba7ef38b / ba7ef38b]
I0730 23:48:51.229070   12416 worker.go:489] commit new work on block 8639 with
0 txs & 0 uncles. Took 0
I0730 23:49:07.227985   12416 chain_manager.go:672] imported 1 block(s) (0 queue
d 0 ignored) including 0 txs in 2.0001ms. #8639 [4b7d14e7 / 4b7d14e7]
I0730 23:49:07.228985   12416 worker.go:489] commit new work on block 8640 with
0 txs & 0 uncles. Took 1.0001ms
I0730 23:49:08.993086   12416 chain_manager.go:672] imported 0 block(s) (0 queue
d 1 ignored) including 0 txs in 3.0002ms. #8638 [ba7ef38b / ba7ef38b]
I0730 23:49:09.022088   12416 chain_manager.go:672] imported 0 block(s) (0 queue
d 1 ignored) including 0 txs in 3.0002ms. #8639 [4b7d14e7 / 4b7d14e7]
I0730 23:49:12.807304   12416 chain_manager.go:672] imported 1 block(s) (0 queue
d 0 ignored) including 0 txs in 3.0002ms. #8640 [f96a8bdf / f96a8bdf]
I0730 23:49:12.808304   12416 worker.go:489] commit new work on block 8641 with
0 txs & 0 uncles. Took 1ms
I0730 23:49:13.163325   12416 chain_manager.go:672] imported 0 block(s) (0 queue
d 1 ignored) including 0 txs in 3.0001ms. #8639 [4b7d14e7 / 4b7d14e7]
I0730 23:49:13.592349   12416 chain_manager.go:672] imported 0 block(s) (0 queue
d 1 ignored) including 0 txs in 3.0002ms. #8640 [f96a8bdf / f96a8bdf]
I0730 23:49:15.970485   12416 chain_manager.go:672] imported 0 block(s) (1 queue
d 0 ignored) including 0 txs in 3.0002ms. #8641 [0316a6a2 / 0316a6a2]
I0730 23:49:17.050547   12416 chain_manager.go:672] imported 1 block(s) (0 queue
d 0 ignored) including 0 txs in 3.0002ms. #8641 [0316a6a2 / 0316a6a2]
I0730 23:49:17.050547   12416 worker.go:489] commit new work on block 8642 with
0 txs & 0 uncles. Took 0
And a bit from ethminer:
miner  00:06:12|main  Got work package:
miner  00:06:12|main    Header-hash: 95d219b372ea87f401dbc4e0611220bac62f39d06c1
591ba06f2670d3d8a0e5a
miner  00:06:12|main    Seedhash: 0000000000000000000000000000000000000000000000
000000000000000000
miner  00:06:12|main    Target: 000000000236b88a7e880c2e48e71e5e0775c99a5ac072a9
fa4831e9efe1ede4
  i  00:06:12|gpuminer0  workLoop 1 #00000000… #00000000…
miner  00:06:13|main  Mining on PoWhash #95d219b3… : 6815744 H/s = 3407872 has
hes / 0.5 s
miner  00:06:13|main  Mining on PoWhash #95d219b3… : 7318077 H/s = 7340032 has
hes / 1.003 s
miner  00:06:14|main  Mining on PoWhash #95d219b3… : 7310788 H/s = 11010048 ha
shes / 1.506 s
miner  00:06:14|main  Mining on PoWhash #95d219b3… : 7433934 H/s = 14942208 ha
shes / 2.01 s
miner  00:06:15|main  Mining on PoWhash #95d219b3… : 7501736 H/s = 18874368 ha
shes / 2.516 s
miner  00:06:15|main  Mining on PoWhash #95d219b3… : 7467500 H/s = 22544384 ha
shes / 3.019 s

Comments

  • gcolbourngcolbourn Member Posts: 48
    Keep going, you should get a block eventually! Even with 2 R9 280Xs (40-48MH/s), I've only mined 7 blocks so far. I think that smaller miners are unfortunately at a relative disadvantage, even on a blocks/MH basis (the biggest miner here seems to be getting at least 1.5x more blocks per MH than me - https://etherchain.org/statistics/miners [devs - is this real, and if so, why is it happening?]
  • timstims Member Posts: 21
    I mined 3 blocks in the last 11 hours with a 80MH/s miner... The statistics are calculating the hashrate based on the found blocks (i think) so this is not the same as the actual hashrate you are mining with. You can be lucky (or not). My hashrate on the statistics page is 47 instead of 80.
  • gcolbourngcolbourn Member Posts: 48
    edited July 2015
    Yeah, mine is lower too (30MH/s); maybe it's a calculation averaged over the the total hashes done. In that way, it would reflect the luck your having (and time away from mining - I've only be online for about 75% of the blocks). Either that, or the big miners really are doing better.. (assuming they're all networked and pooling their resources on the same work blocks etc).
  • timstims Member Posts: 21
    On this growth rate, it shouldn't take long before smaller miners only benefit when they start mining in a pool.
  • gcolbourngcolbourn Member Posts: 48
    Yeah, that's what I was thinking. Not seen anyone talking about it since launch though. Only about 400 people have mined anything so far: https://etherchain.org/statistics/miners
  • o0ragman0oo0ragman0o Member, Moderator Posts: 1,291 mod
    @dimfeld at the current network hashrate of ~50Ghs, your 7.6Mhs should be pulling about a block a day (>5eth)

    Is that 7.6 actual an actual mining figure or benchmarked?
  • dimfelddimfeld Member Posts: 22
    That's 7.6M in actual mining. Thanks everyone. I'll leave it running over the weekend and see how it goes :)
  • cryptoboycryptoboy Member Posts: 74
    edited July 2015
    I tried with 400MH/s and also didn't get any blocks. This is kind of hopeless. I'm wondering if I have the right ethminer version.
  • o0ragman0oo0ragman0o Member, Moderator Posts: 1,291 mod
    @cryptoboy 400MH/s should be raking it in. That's some serious gear unless you mean kH/s?
  • cryptoboycryptoboy Member Posts: 74
    edited July 2015
    @o0ragman0o
    I find it poor that my question hasn't been answered anywhere as to how can we know for sure that the GPU is indeed mining. Some stats on mined blocks would've been nice. I get the feeling my ethminer is not the right version. (Using latest)


  • o0ragman0oo0ragman0o Member, Moderator Posts: 1,291 mod
    @cryptoboy, This is how I run (each in their own terminal)...
    geth --rpc console 2> geth.log
    ethminer -G
    I then monitor for mined blocks with:
    tail -f geth.log | grep "Mined"
    Also make sure you have your coinbase set otherwise all mining will go to address 0, i.e lost.
  • dimfelddimfeld Member Posts: 22
    Hmm, still 0 blocks mined after running for 2 days straight. I have verified that my coinbase matches my account...
  • o0ragman0oo0ragman0o Member, Moderator Posts: 1,291 mod
    @dimfeld, Watching the stats today, the average block time has been pretty long, >15s when there protocol is aiming for 12. So that means only 80% or less ether is being mined per day.

    I've updated my calculator with an average block time field to get a better impression. ATM you should be getting an average of 1 block every ~1.2 days. But remember that average is over weeks so hang in there.
  • dimfelddimfeld Member Posts: 22
    @o0ragman0o Thanks for the info. Yeah, haven't given up yet :)
  • dimfelddimfeld Member Posts: 22
    And sure enough, just a few minutes after my last post I successfully mined a block.
  • gcolbourngcolbourn Member Posts: 48
    @cryptoboy What's your setup to be getting 400MH/s? (e.g. that would be ~16 R9 280Xs, or ~12 7990s) You should be getting around 1 block every 1-200 blocks (1 every 45 mins or so). Easiest way of checking your mined balance is copying your address into https://etherchain.org

    What's the output you get running ethminer -G? After a few seconds it should be something like:

    miner 21:55:43|main Mining on PoWhash #9a3f75a9 : 20971520 H/s = 10485760 hashes / 0.5 s
    miner 21:55:44|main Mining on PoWhash #9a3f75a9 : 21888763 H/s = 22020096 hashes / 1.006 s
    miner 21:55:44|main Mining on PoWhash #9a3f75a9 : 22018708 H/s = 33292288 hashes / 1.512 s
    miner 21:55:45|main Mining on PoWhash #9a3f75a9 : 21964470 H/s = 44302336 hashes / 2.017 s
    miner 21:55:45|main Mining on PoWhash #9a3f75a9 : 21092045 H/s = 53215232 hashes / 2.523 s
    miner 21:55:46|main Mining on PoWhash #9a3f75a9 : 20517875 H/s = 62128128 hashes / 3.028 s
    miner 21:55:46|main Mining on PoWhash #9a3f75a9 : 20176335 H/s = 71303168 hashes / 3.534 s
    miner 21:55:46|main Got work package:
    miner 21:55:46|main Header-hash: ce9a298f7fd601904c4a73fa2436848233c4a5939c71df0b3996ae638a669b0e
    miner 21:55:46|main Seedhash: 0000000000000000000000000000000000000000000000000000000000000000
    miner 21:55:46|main Target: 00000000053a8bbb399f3bcf648addcd2a25887eb067aa9f2c3b16622b50ed70
    i 21:55:46|gpuminer0 workLoop 1 #00000000 #00000000
    miner 21:55:47|main Mining on PoWhash #ce9a298f : 17825792 H/s = 8912896 hashes / 0.5 s
    miner 21:55:47|main Mining on PoWhash #ce9a298f : 17997946 H/s = 18087936 hashes / 1.005 s
    miner 21:55:48|main Mining on PoWhash #ce9a298f : 18228556 H/s = 27525120 hashes / 1.51 s
    miner 21:55:48|main Mining on PoWhash #ce9a298f : 18083382 H/s = 36438016 hashes / 2.015 s
    miner 21:55:48|main Got work package:
    miner 21:55:48|main Header-hash: 2c9112be6c4dbfdfdd5df7077491ae0ab82b61ff14ff078eb0e5674302279956
    miner 21:55:48|main Seedhash: 0000000000000000000000000000000000000000000000000000000000000000
    miner 21:55:48|main Target: 000000000539e47ea9db7793f2522c782e8306d0b6ddbdde7bf85d39d86d773a

    See https://www.reddit.com/r/EtherMining/comments/3f7i1v/am_i_mining_correctly/
  • gcolbourngcolbourn Member Posts: 48
    16 hours and 3500 blocks without mining a block! Running at 48-49MH/s so should really be getting a block every 1500 or so. Is this just bad luck, or are the statistics at https://stats.ethdev.com/ and https://etherchain.org/statistics/miners wrong? (or something with my set-up wrong)
  • arandyarandy Member Posts: 37
    edited August 2015
    same here found 1 in 30mins yesterday but after that nothing. Everything should be working i did restart everything at one point but that shouldn't matter.
    Mining at 25MH/s
  • arandyarandy Member Posts: 37
    Still nothing just rebooted everything watched it build up the DAG again, it didn't do that when i did not reboot the pc but just restarted the programs. Lets see if it will find blocks again now.
  • gcolbourngcolbourn Member Posts: 48
    Ok, so I'm now running 2 miners with a combined hashrate of 190MH/s. I found 3 blocks in an hour yesterday, but now been 17 hours without a block! I should be averaging 1 every 2 hours or so! Can any devs weigh in on whether mining is biased towards the huge farms? Is it worth me joining my miners together into a farm? It just seems to me that I'm getting some very big droughts for a supposedly random distribution of blocks (i.e. if I should be getting a block every 1,460,000MH/(190MH/s) = 7684s = 2.13 hours, not getting one in 17 hours has odds of 0.5^(17/2.13)=0.004 or 0.4%! Is that the right calculation?)
  • dimfelddimfeld Member Posts: 22
    @gcolbourn Don't know if it's actually related to what you're seeing, but this comment about problems mining was interesting: https://www.reddit.com/r/EtherMining/comments/3g64le/ether_mining_propability/ctv8ngi
  • gcolbourngcolbourn Member Posts: 48
    Interesting. What seems to happen for me is I get a couple of blocks in short succession (an hour or so), and then nothing for 24 hours! Mining at well below my hashrate. https://etherchain.org/statistics/miners says 40MH/s when eth says 120MH/s!
  • gcolbourngcolbourn Member Posts: 48
    I'm going away soon, and it looks like leaving them on isn't going to get me much if they need babysitting all the time (also having Wifi issues where it keeps disconnecting) :-(
  • Marvell9Marvell9 Member Posts: 593 ✭✭✭
    I had some bad days too turns out it was due to my node database being out of sync.
  • Marvell9Marvell9 Member Posts: 593 ✭✭✭
    take a close look at you node log and make sure its actually in sync with the blockchain, I had to do the 'upgradedb' command and ive been good for the past few days actually mining over my hashrate. I have 2 boxes 240 mh/s but I got 17 blocks yesterday.

    Also mining on WIFI is a no-no , you should hook up Ethernet so your bandwitth is steady.

    also use the maxpeers flag to get access to the maximum number of peers that way you have a chance on being assigned work faster.
  • PythonDadPythonDad Member Posts: 3

    @cryptoboy, This is how I run (each in their own terminal)...

    geth --rpc console 2> geth.log
    ethminer -G
    I then monitor for mined blocks with:
    tail -f geth.log | grep "Mined"
    Also make sure you have your coinbase set otherwise all mining will go to address 0, i.e lost.
    Could you possibly clarify a bit about exactly how you did this? I'm on Windows 8 and I think I may have been mining to 0x0, but I am not sure. I started geth through the cmd console (because the js console is literally garbage for me) with the command geth --etherbase --rpc, and then started ethminer in another terminal. How exactly are you doing what you're doing to get notification of a mined block?

  • xiaopowxiaopow Member Posts: 15
    edited August 2015
    @Marvell9 Hey, I got 5 rigs running 1 ethminer instance each doing 58MH/s pointing to one Geth instance. Ethminers are all doing work but haven't been able to mine a block for the past 2 days. The only thing that changed is installation of a TPLink switch to handle the new ethernet ports needed. Got any idea what to check?
    geth --rpc --rpcaddr "0.0.0.0" --rpcport 8545 --rpccorsdomain localhost --autodag console
    ethminer -G -F xxx.xxx.x.xxx:8545 --no-precompute -t 3
  • Marvell9Marvell9 Member Posts: 593 ✭✭✭
    sorry missed this , what do you your miners say are they actually mining the same current bock ? also check your geth node , that's where your trouble shooting should start do you see spam like this-
    0816 20:48:49.198437    3674 chain_manager.go:662] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 2.842644ms. #98621 [56c47c47 / 56c47c47]
    I0816 20:48:49.421423    3674 chain_manager.go:662] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 2.718645ms. #98622 [83b1b5b1 / 83b1b5b1]
    I0816 20:48:53.067732    3674 fdtrack.go:109] fd usage 97/1024, tracked 84 [ipc:1 leveldb:67 p2p:14 rpc:2]
    I0816 20:49:06.017609    3674 chain_manager.go:662] imported 1 block(s) (0 queued 0 ignored) including 2 txs in 5.106363ms. #98623 [a26d8446 / a26d8446]
    I0816 20:49:06.028139    3674 worker.go:537] commit new work on block 98624 with 0 txs & 1 uncles. Took 9.896387ms
    I0816 20:49:06.395133    3674 chain_manager.go:662] imported 0 block(s) (0 queued 2 ignored) including 0 txs in 3.097791ms. #98623 [83b1b5b1 / a26d8446]
    I0816 20:49:08.067729    3674 fdtrack.go:109] fd usage 97/1024, tracked 84 [ipc:1 leveldb:67 p2p:14 rpc:2]
    I0816 20:49:16.442703    3674 chain_manager.go:662] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 6.141223ms. #98624 [127f4ed3 / 127f4ed3]
    I0816 20:49:16.452635    3674 worker.go:537] commit new work on block 98625 with 0 txs & 0 uncles. Took 9.662018ms
    I0816 20:49:23.067737    3674 fdtrack.go:109] fd usage 97/1024, tracked 84 [ipc:1 leveldb:67 p2p:14 rpc:2]
    I0816 20:49:30.104123    3674 chain_manager.go:662] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.41453ms. #98625 [889b209a / 889b209a]
    I0816 20:49:30.113977    3674 worker.go:537] commit new work on block 98626 with 0 txs & 0 uncles. Took 9.659852ms
    I0816 20:49:38.067749    3674 fdtrack.go:109] fd usage 97/1024, tracked 84 [ipc:1 leveldb:67 p2p:14 rpc:2]
    I0816 20:49:53.067708    3674 fdtrack.go:109] fd usage 97/1024, tracked 84 [ipc:1 leveldb:67 p2p:14 rpc:2]
    I0816 20:50:08.067753    3674 fdtrack.go:109] fd usage 97/1024, tracked 84 [ipc:1 leveldb:67 p2p:14 rpc:2]
    
    the imported blocks should match the current block count on etherchain.org

    I suspect if you look at the log you will see some errors.

    doing a geth upgradedb fixes it usually

  • Marvell9Marvell9 Member Posts: 593 ✭✭✭
    PythonDad said:

    @cryptoboy, This is how I run (each in their own terminal)...

    geth --rpc console 2> geth.log
    ethminer -G
    I then monitor for mined blocks with:
    tail -f geth.log | grep "Mined"
    Also make sure you have your coinbase set otherwise all mining will go to address 0, i.e lost.
    Could you possibly clarify a bit about exactly how you did this? I'm on Windows 8 and I think I may have been mining to 0x0, but I am not sure. I started geth through the cmd console (because the js console is literally garbage for me) with the command geth --etherbase --rpc, and then started ethminer in another terminal. How exactly are you doing what you're doing to get notification of a mined block?

    thtose are Linux commands you need to view the logs differently on DOS/windows
  • xiaopowxiaopow Member Posts: 15
    edited August 2015
    @Marvell9 Is any of the following spam?
    I0817 18:16:29.822718 3465 chain_manager.go:662] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 5.598581ms. #100431 [d71a698d / d71a698d]
    I0817 18:16:30.644165 3465 fdtrack.go:109] fd usage 100/1024, tracked 85 [ipc:1 leveldb:64 p2p:19 rpc:1]
    I0817 18:16:45.644356 3465 fdtrack.go:109] fd usage 100/1024, tracked 85 [ipc:1 leveldb:64 p2p:19 rpc:1]
    I0817 18:16:58.901641 3465 chain_manager.go:662] imported 1 block(s) (0 queued 0 ignored) including 3 txs in 17.808773ms. #100432 [3f1e0af5 / 3f1e0af5]
    I0817 18:16:58.913356 3465 worker.go:537] commit new work on block 100433 with 2 txs & 0 uncles. Took 11.291529ms
    I0817 18:17:00.346723 3465 chain_manager.go:662] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 3.480714ms. #100431 [d71a698d / d71a698d]
    I0817 18:17:00.644236 3465 fdtrack.go:109] fd usage 100/1024, tracked 85 [ipc:1 leveldb:64 p2p:19 rpc:1]
    I0817 18:17:01.055793 3465 chain_manager.go:662] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 5.224015ms. #100432 [3f1e0af5 / 3f1e0af5]
    I0817 18:17:15.644375 3465 fdtrack.go:109] fd usage 100/1024, tracked 85 [ipc:1 leveldb:64 p2p:19 rpc:1]
    I0817 18:17:22.099542 3465 chain_manager.go:662] imported 1 block(s) (0 queued 0 ignored) including 2 txs in 15.221569ms. #100433 [08c98ab7 / 08c98ab7]
    I0817 18:17:22.105861 3465 worker.go:537] commit new work on block 100434 with 0 txs & 0 uncles. Took 6.065679ms
    I0817 18:17:23.285182 3465 chain_manager.go:662] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 5.609414ms. #100432 [3f1e0af5 / 3f1e0af5]
    I0817 18:17:24.283480 3465 chain_manager.go:662] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 4.369861ms. #100433 [08c98ab7 / 08c98ab7]
    I0817 18:17:30.644351 3465 fdtrack.go:109] fd usage 100/1024, tracked 85 [ipc:1 leveldb:64 p2p:19 rpc:1]
    I0817 18:17:40.681369 3465 chain_manager.go:662] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 5.280597ms. #100434 [af839a26 / af839a26]
    I0817 18:17:40.685105 3465 worker.go:537] commit new work on block 100435 with 0 txs & 0 uncles. Took 3.540621ms
    I0817 18:17:40.839794 3465 chain_manager.go:662] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 2.951004ms. #100434 [3097bc83 / 3097bc83]
    I0817 18:17:41.895350 3465 chain_manager.go:662] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 3.027354ms. #100433 [08c98ab7 / 08c98ab7]
    I0817 18:17:42.384867 3465 chain_manager.go:662] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 2.519648ms. #100434 [af839a26 / af839a26]
    I0817 18:17:45.644213 3465 fdtrack.go:109] fd usage 100/1024, tracked 85 [ipc:1 leveldb:64 p2p:19 rpc:1]
    I0817 18:17:48.309820 3465 chain_manager.go:662] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 6.62345ms. #100435 [86a01e56 / 86a01e56]
    I0817 18:17:48.317017 3465 worker.go:537] commit new work on block 100436 with 0 txs & 1 uncles. Took 6.924108ms
    I0817 18:17:51.677394 3465 chain_manager.go:662] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 3.397165ms. #100434 [af839a26 / af839a26]
    I0817 18:17:52.175271 3465 chain_manager.go:662] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 5.638392ms. #100435 [86a01e56 / 86a01e56]
    I0817 18:17:55.901625 3465 chain_manager.go:662] imported 1 block(s) (0 queued 0 ignored) including 2 txs in 5.674483ms. #100433 [be3e60ac / be3e60ac]
    I0817 18:18:00.431744 3465 chain_manager.go:662] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 5.614076ms. #100436 [5ce2afda / 5ce2afda]
    I0817 18:18:00.433595 3465 worker.go:537] commit new work on block 100437 with 0 txs & 1 uncles. Took 1.723424ms
    I0817 18:18:00.644179 3465 fdtrack.go:109] fd usage 102/1024, tracked 87 [ipc:1 leveldb:64 p2p:21 rpc:1]
Sign In or Register to comment.