Author Topic: Solo mining hang  (Read 5664 times)

0 Members and 1 Guest are viewing this topic.

Offline gnarl

  • Full Member
  • ***
  • Posts: 72
    • View Profile
Solo mining hang
« Reply #1 on: November 09, 2013, 01:56:51 am »
I have noticed a problem with the Protoshares-qt miner when solomining.  The problem occurs after it finds a block and determines that it will reject it due to being found within a few seconds of another. The mining process seems to hang up and stop connecting to the network after getting a 'not accepted' block. The protoshares-qt program keeps using cpu\memory, but does not connect to the network anymore, and just shows repeated hashtarget\testhash log entries.
I have seen this problem a couple times now on 2 different machines, and have saved the log if devs need it.

Here are the details:
This occurred each time while Mining 3 Processes, and setgenerate true 3, no other settings changes.

A block is found and placed in the Immature category.
Listtransactions shows
account" : "",
"address" : "PY4pRRpyhDn1Uf4VpzrwZgNantbpTZnQgZ",
"category" : "immature",
"amount" : 42.86875000,
"confirmations" : 1,
"generated" : true,
"blockhash" : "00028edad5886a66fecc7f4ecda60e954c5320fcdf6aba54522521f7bfe9127e",
"blockindex" : 0,
"blocktime" : 1383947664,
"txid" : "e30f8e6a0ecc8c7e4c0c83fdccedd033b44a080a806cf7d0fc84060e3995fec1",
"time" : 1383947664,
"timereceived" : 1383947686

The confirmations never update past 1, no matter how many hours you wait.

The protoshares-qt miner appears to be mining\doing work (processor and memory use is shown in windows task manager), but the log shows nothing but pages of Hash Target and testhashes.

Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 9bae1c286298d10d6e6d4231b43c110fddbe317a3a7f87b8b2457df1d1aa0800
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 0396d9bb17f49f49af80b0e4ee32c2a319579c507b1dd08556eb92dd0b4d6580
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 32582d39b79f2d779d516b6c1eff9708e5817bf80972ada2f39d0080cb481c44
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash d5b2960fd161bf13874e8c4e112be5967a8b9603e63c858c6c58241d35253c46
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
hashmeter      0 khash/s
testHash 6c1e69de4af3dd2361d31e80544e301e1bae931f918b32baa46a97a41923dd34
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 36b316a4182cc9ff23d83bcdc21ddf44995577d10222684573d4f8bbf35b25f3
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 3d01df93e6d5bbffc45fd1f559ff5c39d53ea74a6dfebde7744ade51cc0693d2
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff

There are no accepted or rejected blocks after this happens. You must restart protoshares-qt to mine successfully again.

After restarting protoshares-qt the transaction will be removed from the immature listing and placed in a transaction. Details now show
Status 0/unconfirmed
Date: 11/8/2013 13:54
Source: Generated
Credit: (not accepted)
Net amount: 0.00 PTS

The 1 confirmation is lost, and the credit is not accepted.

The transaction details say:
When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.
This is fine, except that the miner log looks like its not actually mining correctly anymore, just chewing on processor\memory.

Has anyone else seen the miner hang like this?