pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
Output is this for mining info:
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
I have created the worker on the pool site. Any clue why this isn't working?
Could you please paste the output of 'exec createabn 125000'?
Adding 'minersleep=-1' to your config will also help speed up the miner.
On a side note, if you tail the end of debug.log and search for 'miner' there is probably an error (that is supposed to be bubbled to getmininginfo however).
EDIT2: You may need to run with an unlocked wallet for now (we have a new command for headless unlocking that you can script if you want); but this unlocked wallet allows the core to create an ABN for the miner.
is everything ok after the superblock was generated.. Started getting alerts from my miners like this
2019-08-28 19:18:00 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:00 ERROR: invalid header received
2019-08-28 19:18:00 ProcessMessages(headers, 2269 bytes) FAILED peer=4
2019-08-28 19:18:00 Misbehaving: 23.95.70.118:40000 peer=3 (0 -> 20)
2019-08-28 19:18:00 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:00 ERROR: invalid header received
2019-08-28 19:18:00 ProcessMessages(headers, 2269 bytes) FAILED peer=3
2019-08-28 19:18:00 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:00 ERROR: invalid header received
2019-08-28 19:18:00 ProcessMessages(headers, 2269 bytes) FAILED peer=13
2019-08-28 19:18:00 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:00 ERROR: invalid header received
2019-08-28 19:18:00 ProcessMessages(headers, 2269 bytes) FAILED peer=8
2019-08-28 19:18:00 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:00 ERROR: invalid header received
2019-08-28 19:18:00 ProcessMessages(headers, 2269 bytes) FAILED peer=18
2019-08-28 19:18:00 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:00 ERROR: invalid header received
2019-08-28 19:18:00 ProcessMessages(headers, 2269 bytes) FAILED peer=15
2019-08-28 19:18:01 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:01 ERROR: invalid header received
2019-08-28 19:18:01 ProcessMessages(headers, 2269 bytes) FAILED peer=16
I have tried zapping wallet and no changes..
Ill run my new hash report. Hang on.