Quote from: bible_pay on November 10, 2019, 02:53:35 PM

Quote from: zupernovato on November 10, 2019, 08:12:00 AM

I am using under Windows 10:

Code:

bbpminer-x86 -o stratum+tcp://nomp.biblepay.org:3032 -u MINING_WALLET -p x

Or:

Code:

bbpminer-x86 -o stratum+tcp://5.135.183.202:3032 -u MINING_WALLET -p x

Both returns rightaway:

Code:

KJV Loaded
Using bbpminer version 1009

solo mining 0
[2019-11-10 08:57:12] Starting Stratum on stratum+tcp://5.135.183.202
[2019-11-10 08:57:12] 4 miner threads started, using 'pobh' algorithm.
[2019-11-10 08:57:12] Binding thread 3 to cpu 3
[2019-11-10 08:57:31] stratum_recv_line failed
[2019-11-10 08:57:31] ...retry after 30 seconds

Last two lines in a loop (new line every 30 seconds).
Perhaps my hashrate is slow as I've been disconnected since 4th of November. But I cannot mine with the wallet client as well since then. The biblepay.conf file:

Code:

gen=1
genproclimit=3
minersleep=0
pool=tcp://5.135.183.202:3032
workerid=zupernovato1
workeridfunded=zupernovato2

But with getmining info:

Code:

...
"poolinfo3": "POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; ",
"poolmining": false
...

Do I need to register workerids on the new pools hosts?

Do I need to turn onh WCG-BOINC once again in team BiblePay? (I've read something about it in the recent pages of this thread).

1) I've tested your bbpminer-x86 external miner config and it seems OK, it works for me. I dont think you need the "-p x" at the end, but it should not be a concern.
2) I don't think its your hashrate; it doesn't sound like you ever get to the point where the miner is showing the hashmeter. After a couple minutes you should see 'thread 1: nn KH/S'. You can try adding "-t1" to mine on a single core (this would put more availability to one thread) and see if anything happens, but imo I dont think its the hashrate.
3) You can take out the workerid, workeridfunded, and pool settings in the biblepay.conf as currently pool.biblepay.org is out of play in favor of nomp. Basically the internal miner in the core wallet is not being used for mining, but we are using the external miner now. (I do have a side project to fix that, so they are equal, but for now lets all use the external miner to be equal in speed).
4) You do not need to register any workerid now, you can just use a valid BBP receive address. Please do verify the receive address you use is valid (you get it from the core client Receiving address, or, from 'getnewaddress' . <- I would look at this as this could be the problem, nomp may be hanging up on you if its a bad address.
5) You don't need to have boinc on *yet*, but, we are going to require users to be on team BBP for WCG very soon - IE within 30 days - to earn PODC2.0 credits. See this thread if you want to help us: https://forum.biblepay.org/index.php?topic=465.msg6515#msg6515

6) If none of this helps, please try the external miner on another machine and see if it works with the same settings. If it does, you might have a bad binary on win10, just re-download it.
7) You can also try this: telnet nomp.biblepay.org 3032
Verify the screen clears. This shows you have a connection to the stratum port. There is a remote chance you have a blocked firewall in win10?