BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[bible_pay]

Vader still has not started.  Getmininginfo shows the same error, although the abn number has changed.

Ok, Please leave it in that state, let me see if my desktop can reproduce.

It does not have a locked wallet correct?

[1714143012]

1714143012

[Borgholio]

Vader still has not started.  Getmininginfo shows the same error, although the abn number has changed.

Ok, Please leave it in that state, let me see if my desktop can reproduce.

It does not have a locked wallet correct?

Correct, it is currently unlocked.  The other workers are locked since funded abn doesn't seem to require an unlocked wallet.  Thanks!

[bible_pay]

Vader still has not started.  Getmininginfo shows the same error, although the abn number has changed.

Ok, Please leave it in that state, let me see if my desktop can reproduce.

It does not have a locked wallet correct?

Correct, it is currently unlocked.  The other workers are locked since funded abn doesn't seem to require an unlocked wallet.  Thanks!

Right, I should have asked another way;  Correct, that is one nice thing we can tell anon-sensitive users who don't want to deal with the headless password- they can mine as funded miners.

Anyway, let me check something on vader -can you please see if 'exec getabnweight 125000 1' actually returns > 125000 abn weight?  Because if it has enough funds it could be trying to mine with the ABN.

[Borgholio]

"Command": "getabnweight",
  "version": 2.6,
  "weight": 0,
  "total_required": 0,
  "coin_age_data_pre_select": "<TOTALREQ>0.00</TOTALREQ><TOTALAGE>0</TOTALAGE>",
  "weight 125000.00": 0,
  "total_required 125000.00": 0
}

[bible_pay]

"Command": "getabnweight",
  "version": 2.6,
  "weight": 0,
  "total_required": 0,
  "coin_age_data_pre_select": "<TOTALREQ>0.00</TOTALREQ><TOTALAGE>0</TOTALAGE>",
  "weight 125000.00": 0,
  "total_required 125000.00": 0
}

I see Vader 2 has contacted the pool 289 times in the last 15 mins, so I can see it cant get what it wants but it is trying; has Vader 2 ever worked properly?

(As a funded miner)?

[Borgholio]

"Command": "getabnweight",
  "version": 2.6,
  "weight": 0,
  "total_required": 0,
  "coin_age_data_pre_select": "<TOTALREQ>0.00</TOTALREQ><TOTALAGE>0</TOTALAGE>",
  "weight 125000.00": 0,
  "total_required 125000.00": 0
}

I see Vader 2 has contacted the pool 289 times in the last 15 mins, so I can see it cant get what it wants but it is trying; has Vader 2 ever worked properly?

(As a funded miner)?

Yeah it has worked fine for when I ran low on abn or forgot to unlock my wallet.

[bible_pay]

"Command": "getabnweight",
  "version": 2.6,
  "weight": 0,
  "total_required": 0,
  "coin_age_data_pre_select": "<TOTALREQ>0.00</TOTALREQ><TOTALAGE>0</TOTALAGE>",
  "weight 125000.00": 0,
  "total_required 125000.00": 0
}

I see Vader 2 has contacted the pool 289 times in the last 15 mins, so I can see it cant get what it wants but it is trying; has Vader 2 ever worked properly?

(As a funded miner)?

Yeah it has worked fine for when I ran low on abn or forgot to unlock my wallet.

Yeah, this is very interesting, because I was able to boot up my dev miner in funded mode and get an abn, while yours didnt get it so thats very strange.

Have you changed the name of the miner from "Vader" to "Vader 2" recently, or was it always "Vader 2"?

(Just want to rule out spaces in the name).

[Borgholio]

Since originally setting up for dual mining it is always been Vader for non-funded and Vader for funded.

[bible_pay]

Since originally setting up for dual mining it is always been Vader for non-funded and Vader for funded.

Ok, I think I have enough info then, I believe this is the same problem MIP had yesterday in testnet; we have a situation where the invalid ABN gets cached, and in the next version this is fixed (where the cache gets cleared when the log says "no block to mine").

So I make the assumption that if you reboot the node, and restart the miner it will get a valid ABN from the pool; can you please try that?

[Borgholio]

Since originally setting up for dual mining it is always been Vader for non-funded and Vader for funded.

Ok, I think I have enough info then, I believe this is the same problem MIP had yesterday in testnet; we have a situation where the invalid ABN gets cached, and in the next version this is fixed (where the cache gets cleared when the log says "no block to mine").

So I make the assumption that if you reboot the node, and restart the miner it will get a valid ABN from the pool; can you please try that?

I've already tried rebooting the client, but what do you mean by node? Do you mean restarting the entire PC?

[bible_pay]

Since originally setting up for dual mining it is always been Vader for non-funded and Vader for funded.

Ok, I think I have enough info then, I believe this is the same problem MIP had yesterday in testnet; we have a situation where the invalid ABN gets cached, and in the next version this is fixed (where the cache gets cleared when the log says "no block to mine").

So I make the assumption that if you reboot the node, and restart the miner it will get a valid ABN from the pool; can you please try that?

I've already tried rebooting the client, but what do you mean by node? Do you mean restarting the entire PC?

Oh ok, interesting that you rebooted the client.  I did mean client in this case.  What OS is this, btw? 

[Borgholio]

Windows 10 64 bit

[bible_pay]

Windows 10 64 bit

Ok, I just deployed 1.4.4.3b (Windows only).  It has that fix in it that supposedly clears the cached abn.

Could you please try it now?

[Borgholio]

Windows 10 64 bit

Ok, I just deployed 1.4.4.3b (Windows only).  It has that fix in it that supposedly clears the cached abn.

Could you please try it now?

Sure, will try on a few machines and let you know.  Thanks!

[bible_pay]

So far no luck, upgraded Vader to the latest build and it still says the blocks are stale.

Could you please paste or PM me the main part of the log that is complaining about the block?

[bible_pay]

is this related to the abn problems?
seems I cannot pool mine without this happening after only a few minutes:

Code:

ContextualCheckBlockHeader::FAILED incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000 (code 16)

I dont see a miner by the name of Nipar, please share miner name.

[Nipar]

is this related to the abn problems?
seems I cannot pool mine without this happening after only a few minutes:

Code:

ContextualCheckBlockHeader::FAILED incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000 (code 16)

I dont see a miner by the name of Nipar, please share miner name.

nickname=nichaols1
miner names are  np-01F and np-L2-F

I also downloaded the windows version with the updated getabnweight version 2.7 and it still happens
thanks.

[bible_pay]

is this related to the abn problems?
seems I cannot pool mine without this happening after only a few minutes:

Code:

ContextualCheckBlockHeader::FAILED incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000 (code 16)

I dont see a miner by the name of Nipar, please share miner name.

nickname=nichaols1
miner names are  np-01F and np-L2-F

I also downloaded the windows version with the updated getabnweight version 2.7 and it still happens
thanks.

I made a change to the pool to attempt to reveal the problem, did it just resolve (try to 'setgenerate true N') on one of the nodes?

[bible_pay]

is this related to the abn problems?
seems I cannot pool mine without this happening after only a few minutes:

Code:

ContextualCheckBlockHeader::FAILED incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000 (code 16)

I dont see a miner by the name of Nipar, please share miner name.

nickname=nichaols1
miner names are  np-01F and np-L2-F

I also downloaded the windows version with the updated getabnweight version 2.7 and it still happens
thanks.

I made a change to the pool to attempt to reveal the problem, did it just resolve (try to 'setgenerate true N') on one of the nodes?

Waiting for the leader board to update and show only 1 miner

No, I mean to see if the problem miner now has a valid ABN?

[Nipar]

is this related to the abn problems?
seems I cannot pool mine without this happening after only a few minutes:

Code:

ContextualCheckBlockHeader::FAILED incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000 (code 16)

I dont see a miner by the name of Nipar, please share miner name.

nickname=nichaols1
miner names are  np-01F and np-L2-F

I also downloaded the windows version with the updated getabnweight version 2.7 and it still happens
thanks.

I made a change to the pool to attempt to reveal the problem, did it just resolve (try to 'setgenerate true N') on one of the nodes?

Waiting for the leader board to update and show only 1 miner

No, I mean to see if the problem miner now has a valid ABN?

"poolinfo5": "Internal ABN: Invalid 1563578281; ",
  "abninfo": "Mining with funded Valid ABN 475241571a003cb33dc9c3b71304aea27e6c6d2d1cf221178ef8a39a31ba2bc1; Mining with funded Valid ABN 475241571a003cb33dc9c3b71304aea27e6c6d2d1cf221178ef8a39a31ba2bc1; " and still produces that fail error