Re: BiblePay | 10% to Orphan-Charity | POBH CPU

Where do people download the bbp xmrig software again?

https://github.com/biblepay/xmrig/tree/master/binaries

Is this the best location?

Yeah normally i just download directly from github, all about your taste i guess. Directly from pool page also a option.

I am using port 3001 on rx.biblepay.org - the block height says 2062258

Height should be 184675. Am I mining on the correct chain? That block height looks awfully high, like it is testnet chain or something...

I haven't tried xmrig in a long time, so I could be mistaken too.

What are the huge pages and 1gb pages in your miner? They both show as unavailable for me.

Oh wow, we could be on to something with that (I've got your IP and I have been collecting some data btw).

Anyway, my numbers arent exactly correct but I believe you need 1 gig of ram per huge page. The miner will automatically use them if it can.

I believe you need 256meg of free ram per thread, minimum. How much ram does your machine have?

I have 16gb total. Task manager is showing the miner is using 2.3gb for a single thread.

Ok thats not it then, anything more than 4gb is probably fine.

On a side note the only strange problem I see from your machine so far, is your machine constantly reconnects (about once every 10 minutes), authorizes in the pool successfully, we get your BBP address and Monero address (the correct ones) successfully and give you something to mine, but then we never hear from your machine again (it basically never knows when it solves a BBP share). So either it discards the reply, or, it cant contact us with a solution. Since you dont see rejects on your screen, it sounds as if its not really mining on the bbp side.

I did extend the pool server timeout to 10 minutes to try to accomodate that behavior and it appears that did not help your case.

Ill have to give you some commands to enable verbose logging.

In the mean time is there any way you can try windows mining from another machine, just to ensure that it fails only on one machine? That will help isolating network issues and binary issues.

Tried from another machine, no change in behavior.

Hmm, that really points to your network then, I would think, since its not happening with anyone else yet.

The good news is since we are only on block #2, we can still try to figure other things out.

Do you have any strange networking setup, like VPN, and are your machines running any proxies, I mean do the tcp packets flow straight out of the LAN through a normal router?