a lot of "NOT confirmed DL" messages when mining



  • @FlippyCakes
    @haitch didn't mention: When the pool receives a lot of deadlines, it uses all of the CPU power it got to confirm them. If pool got more then normal, it might delay the confirmation messages to save work. They can happen to be delayed so much you never receive them with your current config.
    This is why they can be seen on the pool, but you won't get any messages back.'

    Only your best deadline shows up on the pool webpage. They can also be below the limit, which might make them invisible on the pool scoreboard. They should not be sent, but I don't know the exact details.



  • @FrilledShark said in a lot of "NOT confirmed DL" messages when mining:

    This is why they can be seen on the pool, but you won't get any messages back.

    Good to know. What I'm experiencing seems to be the exact opposite, though. I get a message saying it wasn't accepted, and the pool doesn't list the deadline.



  • @FlippyCakes
    Are you able to show a screenshot?
    Of course, if the pool told you the deadlines wasn't confirmed it doesn't show it.



  • @FrilledShark

    I've got some screenshots at the top of the thread. For checking the pool, I'm only CTRL-Fing my username on the pool's stats page. That seems to be fairly accurate.



  • @FlippyCakes
    The both screenshots are working on the same block. The only difference is that they are 10 min apart. The means the last screenshot is while the pool experiences almost no load and the first is when the pool experiences loan. Edit: and as you see, it was able to confirm the deadlines on the last screenshot, but not the first one.

    I don't think there is anything to worry about.



  • @FrilledShark

    I think it is worrisome. I'm getting a lot of these messages, and not being credited by the pool for a lot of deadlines that I send. I can't babysit the miner and manually restart it to force resend a sweet deadline just because when I originally sent it the pool was busy.



  • @FlippyCakes If you are still on burst-team.us know that it's recommended plot size is 14.166. If you are still working with only 7.4TB that might be the reason why you are not getting good DL's.

    https://docs.google.com/spreadsheets/d/1KHu9BWwy_QXIYAx2m_Tzs9BqPoTYUDhEDbHihZEXGsE/edit#gid=81124645



  • @socalguy Thanks! Yeah, I'll probably try switching pools tonight.



  • im having the same issue but also im going multiple blocks without finding any deadlines at all ... been that way all day. The file size error is from a plot im currently ploting. 0_1476925154661_Untitled.png


  • admin

    @Gibsalot With 3TB, you shouldn't be mining on pool.burst-team.us - you'll find very few deadlines. Move to pool.burstcoin.biz or pool.burstcoin.eu or one of the other pools that are set up for smaller plots.



  • i moved to pool.burstmining.club just after i posted that message im finding plenty of deadlines now about like i was when i started with burst-team.us atm i have 3TB mining but will have just under 10TB after i get everything ploted



  • Maybe there is a way to edit .cpp file from source code to force miner to restart on Not confirmed DL ?
    I'm currently mining on burstneon and got the same issue.
    On logs there is no proper confirmation from pool:

    10:52:07 ------------------------    New block: 356963
    10:52:07 Sender: started thread
    10:52:07 Start thread: [0]  Q:\plots\
    10:52:07 Read file : 1403xxx_0_1720320_1720320
    10:52:08 * GMI: Sent: POST /burst?requestType=getMiningInfo HTTP/1.0\r\nConnection: close\r\n\r\n
    10:52:08 found deadline=416472 nonce=678986 for account: 1403xxx file: 1403xxx_0_1720320_1720320
    10:52:08 * GMI: Received: HTTP/1.1 200 OK\r\nContent-Type: application/json\r\nDate: Sat, 06 May 2017 08:52:13 GMT\r\nConnection: close\r\n\r\n{"generationSignature":"9aa3a83141238d4b3ad0de87052da3c661a708048ece4f49000ac82d89db2dc8","baseTarget":"779401","requestProcessingTime":0,"height":"356963"}
    10:52:08 Sender: Sent: POST /burst?requestType=submitNonce&accountId=1403xxx&nonce=678986&deadline=324599121813 HTTP/1.0\r\nX-Miner: Blago v1.160705_AVX\r\nX-Capacity: 460\r\nConnection: close\r\n\r\n
    10:52:09 * GMI: Sent: POST /burst?requestType=getMiningInfo HTTP/1.0\r\nConnection: close\r\n\r\n
    10:52:10 * GMI: Received: HTTP/1.1 200 OK\r\nContent-Type: application/json\r\nDate: Sat, 06 May 2017 08:52:15 GMT\r\nConnection: close\r\n\r\n{"generationSignature":"9aa3a83141238d4b3ad0de87052da3c661a708048ece4f49000ac82d89db2dc8","baseTarget":"779401","requestProcessingTime":0,"height":"356963"}
    10:52:10 Close file: 1403xxx_0_1720320_1720320 [@ 2294 ms]
    
    10:52:10 Read file : 1403xxx_1720321_163840_163840
    10:52:10 Close file: 1403xxx_1720321_163840_163840 [@ 229 ms]
    
    10:52:10 Sender: Received: 
    10:52:10 Sender: wrong message for DL: 1403xxx
    10:52:10 Sender: Close socket. Code = 0
    
    10:52:11 * GMI: Sent: POST /burst?requestType=getMiningInfo HTTP/1.0\r\nConnection: close\r\n\r\n
    10:52:11 * GMI: Received: HTTP/1.1 200 OK\r\nContent-Type: application/json\r\nDate: Sat, 06 May 2017 08:52:16 GMT\r\nConnection: close\r\n\r\n{"generationSignature":"9aa3a83141238d4b3ad0de87052da3c661a708048ece4f49000ac82d89db2dc8","baseTarget":"779401","requestProcessingTime":0,"height":"356963"}
    10:52:12 * GMI: Sent: POST /burst?requestType=getMiningInfo HTTP/1.0\r\nConnection: close\r\n\r\n
    10:52:13 * GMI: Received: HTTP/1.1 200 OK\r\nContent-Type: application/json\r\nDate: Sat, 06 May 2017 08:52:18 GMT\r\nConnection: close\r\n\r\n{"generationSignature":"9aa3a83141238d4b3ad0de87052da3c661a708048ece4f49000ac82d89db2dc8","baseTarget":"779401","requestProcessingTime":0,"height":"356963"}
    
    



Log in to reply
 

Looks like your connection to Burst - Efficient HDD Mining was lost, please wait while we try to reconnect.