Incredibly long Deadlines?

  • Why is it that I've been recently getting extremely long Deadlines (ofc they can't be submitted):
    alt text

    I never had this issue until now. I've been ignoring it but when I find a great DL and I get an incredibly long DL that can't be submitted.

  • admin

    @p0int_scale If it's intermittent don't worry about it, if it repeatedly happens - you have a bad plot - delete and replot.

  • If this problem has been recurring it might just be time to replot. Wait a little bit for someone else to reply. Not 100% sure if theres a fix for this.

  • @haitch I get this once about every 15 minutes.


    It started when I updated Blago miner to the latest and started using AVX2 which is supported by my CPU.

  • admin

    @p0int_scale Check the log files to determine which file the nonces are coming from, delete that file and replot it.

  • @haitch Checked my logs from a few hours ago:
    22:18:21 Read file : 2758679861088131964_302659073_366720_366720

    22:18:22 Sender: Received: HTTP/1.0 400 Bad Request\r\nContent-Length: 188\r\nContent-Type: text/html; charset=UTF-8\r\nDate: Sat, 17 Jun 2017 02:18:20 GMT\r\n\r\n{"errorCode":1007,"errorDescription":"The deadline for your nonce is REALLY BAD: 408549 years, 7 months, 26 days, 10 hours, 49 mins, 44 secs - wrong block? are your plot files corrupted?"}

    22:18:22 Sender: Close socket. Code = 0

    22:18:22 Close file: 2758679861088131964_302659073_366720_366720 [@ 252 ms]

    Is this the plot file that could be getting me this error?

  • admin

    @p0int_scale Probably. Are there any "submitting" lines ?

  • @haitch Couldn't find any "submitting" lines but I did fine "submit" lines:

    22:28:38 ------------------------ New block: 371891
    22:28:38 Sender: started thread
    22:28:38 Start thread: [0] E:\Burst\plots
    22:28:38 Read file : 2758679861088131964_500000001_449152_449152
    22:28:38 Start thread: [1] D:\Burst\plots
    22:28:38 Read file : 2758679861088131964_400000001_1676544_1676544
    22:28:38 Start thread: [2] C:\Burst\plots
    22:28:38 Read file : 2758679861088131964_300000001_2659072_2659072
    22:28:38 Start thread: [3] F:\Burst\plots
    22:28:38 Read file : 2758679861088131964_600000001_29752_29752
    22:28:38 Close file: 2758679861088131964_600000001_29752_29752 [@ 105 ms]
    22:28:39 found deadline=570538 nonce=400641925 for account: 2758679861088131964 file: 2758679861088131964_400000001_1676544_1676544
    22:28:39 * GMI: Sent: POST /burst?requestType=getMiningInfo HTTP/1.0\r\nHost:\r\nContent-Length: 0\r\nConnection: close\r\n\r\n
    22:28:39 Sender: Sent: POST /burst?requestType=submitNonce&accountId=2758679861088131964&nonce=400641925&deadline=204614905338 HTTP/1.0\r\nHost:\r\nX-Miner: Blago v1.170603_AVX2\r\nX-Capacity: 1413\r\nContent-Length: 0\r\nConnection: close\r\n\r\n
    22:28:39 * GMI: Received: HTTP/1.0 200 OK\r\nContent-Length: 182\r\nContent-Type: text/html; charset=UTF-8\r\nDate: Sat, 17 Jun 2017 02:28:38 GMT\r\n\r\n{"generationSignature":"920a92881c5fd6ca55e8f127407ae97c8e574fcd84e0170d11f7762ba0430a14","baseTarget":"358635","requestProcessingTime":0,"height":"371891","targetDeadline":43200000}
    22:28:40 Sender: Received: HTTP/1.0 200 OK\r\nContent-Length: 157\r\nContent-Type: text/html; charset=UTF-8\r\nDate: Sat, 17 Jun 2017 02:28:39 GMT\r\n\r\n{"requestProcessingTime":0,"result":"success","block":371891,"deadline":570538,"deadlineString":"6 days, 14 hours, 28 mins, 58 secs","targetDeadline":570538}
    22:28:40 Sender: confirmed deadline: 570538
    22:28:40 Sender: Close socket. Code = 0

  • admin

    @p0int_scale The submitnonce is the nonce you submitted, if it comes back as a really bad deadline, then the file containing that nonce is the one you need to delete and recreate.

  • @haitch Ah ok.
    The plot file that is doing this is on my C: drive and I ofc used XPlotter. I find that odd since most of the time I never have plotting issues and I don't recall having any issues with plotting.

  • admin

    @p0int_scale Can't explain it, I'm not aware of having plotting issues, but I've had plots that did the same.

  • @haitch 1 more un-related question to this:

    Why does this happen sometimes?:
    alt text

    I submit nothing.

  • admin

    @p0int_scale You didn't find a deadline that the pool would accept. Depending on the pool, that limit can be as low as one day, other pools accept much longer deadlines.

  • @haitch Then with 1.5TB should I still mine on or consider a different pool that has either a higher DL limit or an unlimited DL limit?

  • admin

    @p0int_scale BCA accepts very long DL's, so you'll be fine there. To earn more and get more regular deadlines, you need to expand your plot.