Author

Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 114. (Read 243386 times)

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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?

newbie
Activity: 99
Merit: 0
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!
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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?

newbie
Activity: 99
Merit: 0
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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? 

newbie
Activity: 99
Merit: 0
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?
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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?

newbie
Activity: 99
Merit: 0
Since originally setting up for dual mining it is always been Vader for non-funded and Vader for funded.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
"Command": "getabnweight",
  "version": 2.6,
  "weight": 0,
  "total_required": 0,
  "coin_age_data_pre_select": "0.000",
  "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).

newbie
Activity: 99
Merit: 0
"Command": "getabnweight",
  "version": 2.6,
  "weight": 0,
  "total_required": 0,
  "coin_age_data_pre_select": "0.000",
  "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.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
"Command": "getabnweight",
  "version": 2.6,
  "weight": 0,
  "total_required": 0,
  "coin_age_data_pre_select": "0.000",
  "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)?

newbie
Activity: 99
Merit: 0
"Command": "getabnweight",
  "version": 2.6,
  "weight": 0,
  "total_required": 0,
  "coin_age_data_pre_select": "0.000",
  "weight 125000.00": 0,
  "total_required 125000.00": 0
}
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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.

newbie
Activity: 99
Merit: 0
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!
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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?

newbie
Activity: 99
Merit: 0
Vader still has not started.  Getmininginfo shows the same error, although the abn number has changed.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
Its Doom, Hamputer, Vader and Vader 2.  Vader and Vader 2 are the same machine, one worker is funded and then other not.  Thanks!

Oh OK that explains it!  Yeah, I think the issue is this:
The pool can only support One funding type per user at a given time.  So all your active workers have to be in funded mode at the same time (or they work against the non-funded).
They are allowed to switch to non-funded, but then the non-funded work against the funded.

(You can accomplish this synchronization by sending the wallet.dat out to the miners).

This limitation will be removed very soon (IE within a week) when we get the new protoversion out.

Are you trying to mine in funded and non funded at the same time across workers?



Vader is the only machine set to switch between funded and non funded.  All the rest are set to funded since I dont have enough coins to spread around all my hosts.  I didn't know that they would actually compete against each other.

Im working hard to eliminate that asap.  I cant eliminate that yet as it would give too much of the pool away to the top 3 miners.

So aside from the fund switch issue, did vader start working by itself?    Cause Im not receiving any complaints about the fail to get abn.  I know it happens occasionally but it should not be much cpu time in total.  I believe it happens between block changes mostly.

newbie
Activity: 99
Merit: 0
Its Doom, Hamputer, Vader and Vader 2.  Vader and Vader 2 are the same machine, one worker is funded and then other not.  Thanks!

Oh OK that explains it!  Yeah, I think the issue is this:
The pool can only support One funding type per user at a given time.  So all your active workers have to be in funded mode at the same time (or they work against the non-funded).
They are allowed to switch to non-funded, but then the non-funded work against the funded.

(You can accomplish this synchronization by sending the wallet.dat out to the miners).

This limitation will be removed very soon (IE within a week) when we get the new protoversion out.

Are you trying to mine in funded and non funded at the same time across workers?



Vader is the only machine set to switch between funded and non funded.  All the rest are set to funded since I dont have enough coins to spread around all my hosts.  I didn't know that they would actually compete against each other.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
Its Doom, Hamputer, Vader and Vader 2.  Vader and Vader 2 are the same machine, one worker is funded and then other not.  Thanks!

Oh OK that explains it!  Yeah, I think the issue is this:
The pool can only support One funding type per user at a given time.  So all your active workers have to be in funded mode at the same time (or they work against the non-funded).
They are allowed to switch to non-funded, but then the non-funded work against the funded.

(You can accomplish this synchronization by sending the wallet.dat out to the miners).

This limitation will be removed very soon (IE within a week) when we get the new protoversion out.

Are you trying to mine in funded and non funded at the same time across workers?

Jump to: