Very high deadlines?



  • Hi,

    first of all, iam totally new to burst mining. Now i setup my system (details follwing) an get this message every round:

    "errorCode":1007,"errorDescription":"The deadline for your nonce is REALLY BAD: 255941 years, 5 days, 15 hours, 50 mins, 21 secs - wrong block? are your plot files corrupted?"

    Of course the time isnยดt the same each round, but every time i get thousend of years. What went wrong?

    Here is my setup: I run my wallet on a 32bit Linux machine and use this for mining (with burst-miner). I plot my drives on another 64bit machine (with dcct, no wallet is running here). I create the plots with 20000 Staggersize and have 1,1TB of plots for testing.



  • I figure out some intersiting informations:
    According to the output of ./burstminer my Deadlines arent so bad. In this block for example ~28days for nonce n:3664966.

    block#248164 s#:1187 bt:3020213 a6ddc9b0f1c37e05626ce59c9269ca2abeda99670b1006f6d004fc7cd12f237d
    MVSE-LLUM-6NW4-7JMXZ dl:15168 days 03:43:03 n:0
    MVSE-LLUM-6NW4-7JMXZ dl:44490 days 10:30:14 n:1
    MVSE-LLUM-6NW4-7JMXZ dl:40503 days 15:57:33 n:6
    MVSE-LLUM-6NW4-7JMXZ dl:41878 days 13:42:15 n:20
    MVSE-LLUM-6NW4-7JMXZ dl:3548 days 23:35:30 n:38
    MVSE-LLUM-6NW4-7JMXZ dl:28676 days 12:19:32 n:50
    MVSE-LLUM-6NW4-7JMXZ dl:17530 days 03:11:00 n:54
    MVSE-LLUM-6NW4-7JMXZ dl:43381 days 09:27:30 n:364
    MVSE-LLUM-6NW4-7JMXZ dl:14171 days 06:11:39 n:389
    MVSE-LLUM-6NW4-7JMXZ dl:19080 days 07:47:35 n:712
    MVSE-LLUM-6NW4-7JMXZ dl:37453 days 20:59:00 n:1210
    MVSE-LLUM-6NW4-7JMXZ dl:14397 days 07:13:32 n:1682
    MVSE-LLUM-6NW4-7JMXZ dl:3081 days 13:28:03 n:12701
    MVSE-LLUM-6NW4-7JMXZ dl:335 days 23:42:48 n:511091
    MVSE-LLUM-6NW4-7JMXZ dl:175 days 13:17:10 n:399431
    plot read done. 6914838061871918860_0_500000_20000 = 520000 nonces 
    MVSE-LLUM-6NW4-7JMXZ dl:64 days 02:03:08 n:1462486
    MVSE-LLUM-6NW4-7JMXZ dl:57 days 04:11:53 n:3217375
    MVSE-LLUM-6NW4-7JMXZ dl:28 days 05:43:51 n:3664966
    plot read done. 6914838061871918860_500000_3800000_20000 = 3820000 nonces 
    submitting nonce 3664966 for MVSE-LLUM-6NW4-7JMXZ
    {"errorCode":1007,"errorDescription":"The deadline for your nonce is REALLY BAD: 180390 years, 2 months, 28 days, 3 hours, 25 mins, 50 secs - wrong block? are your plot files corrupted?"}
    

    Nethertheless i get the Error, that my deadline is REALLY BAD (several years). Whats the problem here? ๐Ÿ˜•

    Thanks...


  • admin

    Maybe a new block has started, after you send it. However this info is from pool, not from network itself ... you could try another pool or solo. I also have this issue from time to time, but not very often ... also you plot data may be corrupted, i guess. Do you always get this error on same plotfile? try mining without ...



  • With the poc_pool_miner i have no Problems with the same plots and the same pool. And as you can see the deadlines with burstminer arent the Problem. Something must go wrong while sending the best nonce to the Pool but i dont know what exactly. ๐Ÿ˜•


  • admin

    What pool? dev2 pool?





  • Your setup appears to working as expected, I just ran your Burst ID through the burst-team.us pool and your most recent block showed a response of 2 Days and X hours which is very good/reasonable based on the size of your plot (100GB).

    I can see you have already accumulated your first 2 coins in the pool. Enjoy mining.

    -IceBurst


  • admin

    @piezo said:

    poc_pool_miner

    hmm, i thought, poc-pool-miner does only work with dev v2 pool and not with others.



  • I have set up 1,1TB an the earnings i only reached with the poc_miner. ๐Ÿ™‚

    The problem is that i would like to use the burst-miner because there i only need 1 instance to run.
    I plan to plug in 3 HDDs and i run it on an little odroid to have low power consumtion.
    So i donยดt know if this little machine could handle 3 instances of the poc-miner.

    And i also dont like the output of the poc-miner. It has to less information. ๐Ÿ™‚



  • @luxe said:

    hmm, i thought, poc-pool-miner does only work with dev v2 pool and not with others.

    To be exactly it is the burst-pool-miner which is according to the readme "a modified version of POCMiner ver 1 by [email protected]"
    "


  • admin

    @piezo The reason you get the Really Bad message is that the POC miner ignores the pools minimum deadline request. And send in the ones it find, each incrementally better than the last. However you initial submit will be in the ten to thousands of years, and then they start getting better.


  • admin

    @piezo Don't use the uray miner original code - use the slightly improved uray's miner code by dpreyl:
    https://forums.burst-team.us/topic/113/uray-s-c-crossplatform-miner-64bit-ultra-low-ram-usage/2



  • @daWallet said:

    @piezo Don't use the uray miner original code - use the slightly improved uray's miner code by dpreyl:
    https://forums.burst-team.us/topic/113/uray-s-c-crossplatform-miner-64bit-ultra-low-ram-usage/2

    I use a 32bit machine for mining. So i download and compile dpreyl's modification (https://github.com/dpreyl/burst-miner/) like mentioned in your link. And this is exactly the version i got problems with and this topic is about.

    Even if i put "submissionMaxDeadline" : 3888000, in my config file i get the same problem. ๐Ÿ˜•



  • @piezo - I see you are still successfully mining and have increased your total mined from the initial 2 coins to 30 now. Are you still trying to switch mining packages due to the output of poc-miner not being desirable?

    -IceBurst



  • This post is deleted!


  • @IceBurst said:

    @piezo - I see you are still successfully mining and have increased your total mined from the initial 2 coins to 30 now. Are you still trying to switch mining packages due to the output of poc-miner not being desirable?

    -IceBurst

    This 30coins i mined with the modified poc-pool-miner.

    @haitch said:

    @piezo The reason you get the Really Bad message is that the POC miner ignores the pools minimum deadline request. And send in the ones it find, each incrementally better than the last. However you initial submit will be in the ten to thousands of years, and then they start getting better.

    The Error message i got with the burst-miner (https://github.com/dpreyl/burst-miner/), not the poc-miner.

    As i understand it, the tool reads all plots and looks for the best deadlines.

    block#248164 s#:1187 bt:3020213 a6ddc9b0f1c37e05626ce59c9269ca2abeda99670b1006f6d004fc7cd12f237d
    MVSE-LLUM-6NW4-7JMXZ dl:15168 days 03:43:03 n:0
    MVSE-LLUM-6NW4-7JMXZ dl:44490 days 10:30:14 n:1
    MVSE-LLUM-6NW4-7JMXZ dl:40503 days 15:57:33 n:6
    MVSE-LLUM-6NW4-7JMXZ dl:41878 days 13:42:15 n:20
    MVSE-LLUM-6NW4-7JMXZ dl:3548 days 23:35:30 n:38
    MVSE-LLUM-6NW4-7JMXZ dl:28676 days 12:19:32 n:50
    MVSE-LLUM-6NW4-7JMXZ dl:17530 days 03:11:00 n:54
    MVSE-LLUM-6NW4-7JMXZ dl:43381 days 09:27:30 n:364
    MVSE-LLUM-6NW4-7JMXZ dl:14171 days 06:11:39 n:389
    MVSE-LLUM-6NW4-7JMXZ dl:19080 days 07:47:35 n:712
    MVSE-LLUM-6NW4-7JMXZ dl:37453 days 20:59:00 n:1210
    MVSE-LLUM-6NW4-7JMXZ dl:14397 days 07:13:32 n:1682
    MVSE-LLUM-6NW4-7JMXZ dl:3081 days 13:28:03 n:12701
    MVSE-LLUM-6NW4-7JMXZ dl:335 days 23:42:48 n:511091
    MVSE-LLUM-6NW4-7JMXZ dl:175 days 13:17:10 n:399431
    plot read done. 6914838061871918860_0_500000_20000 = 520000 nonces 
    MVSE-LLUM-6NW4-7JMXZ dl:64 days 02:03:08 n:1462486
    MVSE-LLUM-6NW4-7JMXZ dl:57 days 04:11:53 n:3217375
    MVSE-LLUM-6NW4-7JMXZ dl:28 days 05:43:51 n:3664966
    plot read done. 6914838061871918860_500000_3800000_20000 = 3820000 nonces 
    submitting nonce 3664966 for MVSE-LLUM-6NW4-7JMXZ
    

    Than it looks for the best nonce (in this example nonce 3664966 with a deadline of 28 days 05:43:51.
    Than it submitt this nonce with a deadline of ~28days and get the answer from the server that the deadline is x-thounsend of years.

    {"errorCode":1007,"errorDescription":"The deadline for your nonce is REALLY BAD: 180390 years, 2 months, 28 days, 3 hours, 25 mins, 50 secs - wrong block? are your plot files corrupted?"}
    

    And i donยดt know why. ๐Ÿ˜•



  • Sry for spamming, but now i figured out some interesting information.

    If let mine my plots by the two different tools (1. burst-miner / 2. midified poc-pool-miner) on the same block, i get different results in:
    1: Which nonce has the lowest deadline
    2: How high is this deadline

    Is this normal? I would assume that the result should be the same? Maybe the burst-miner do some wrong calculations and thats why the deadline from the pool and the burst-miner are so different. Is this possible?



  • @piezo That is a problem. Your deadlines are determined by two things.

    1. Your plot generated by your system which is seeded with your numeric ID
    2. The scoop provided by the pool server for pulling from your plot

    If you are getting different deadlines from different miners the possibilities are:

    1. One miner is working on stale data (meaning an older scoop)
    2. One miner is busted in it's ability to mine
    3. The miners are on different networks (DEV VS Prod)

    Hope this helps,

    -IceBurst



  • Thanks for the answere, but iam still a bit confused as iam new to all of this. ๐Ÿ™‚

    So this means, that burst-miner (https://github.com/dpreyl/burst-miner/) is not campatible with the pool http://pool.burst-team.us:80 in general because of the different scoop?
    Or could it be may compatible if i use another plotter? (i used dcct-cpu-plotter for my plots)?


  • admin

    @piezo Did you compare the miners on same block/round? If yes, at least the best deadline should be the same. Additional deadlines may vary, depending on miner plotfile read strategy/order.