Quote from: nananaminer on September 13, 2017, 07:52:01 AM

Quote from: seasonw on September 13, 2017, 07:43:35 AM

Quote from: nananaminer on September 13, 2017, 07:18:25 AM

Quote from: canonical on September 13, 2017, 06:27:21 AM

I've just taken a look at my workers for the first time today and it appears all my workers have been down for sometime. Restarting the daemon (I'm on linux) doesn't restart mining; something is wrong. I nuked one of the instances of biblepay that I have by deleting .biblepaycore (except biblepay.conf) and let the blockchain resync. Once sync'ed, it won't mine and gives "HEALTH_DOWN" when I check 'getmininginfo'.

Here's the latest extract from 'debug.log':

------
2017-09-13 06:17:27 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:17:27 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:17:27 Misbehaving: 45.76.85.130:40000 (50 -> 100) BAN THRESHOLD EXCEEDED
2017-09-13 06:20:53 ERROR: ReadBlockFromDisk: OpenBlockFile failed for CBlockDiskPos(nFile=-1, nPos=0)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7141.000000 pindexPrev 16265e604f37754bec$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (0 -> 50)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7142.000000 pindexPrev be3a96f7b585a3c6e3$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (50 -> 100) BAN THRESHOLD EXCEEDED
------

Reading the previous posts, this isn't quite the same as what other people have reported. I 'clearbanned' like someone else mentioned, but it doesnt seem to change anything. 'Thoughts?

I have both of these problems lol. My miners constantly go off the pool and I think they are not reverting to solo mining, because it still says poolmining=true, but the pool doesn't recognize them. When I restart them, they go on the pool briefly and then drop again.

Same problem for me since yesterday. Been pulling the miners online every half hour before they go offline. Doesn't switch to solo mining either.
Dev is doing a great job but wish all the changes such as algo, difficulty adjustments etc were first tested on the testnet first before multiple mandatory fixes.
Also not sure what the pool's reward system is like right now, seems erratic.

@bible_pay Any chance of fixing the difficulty adjustment sooner, the difficulty is increasing exponentially and block rewards are at 25% now.

Yes, I agreed that fixing of block rewards should be the top priority, because it is too low now.

And I would think after this lesson, dev really have to test any changes in testnet before release it, there are too many unknown issues occurred. I don't mean to criticize and I really appreciate dev's effort, I think dev must be busy on fixing these issues now Grin

Glad all of us are agreeing on this.
Dev is doing a tremendous job, his openness and commitment to the project is the reason I started engaging with BiblePay in the first place.
Hope the dev finds time to get through these fixes.

Alright all, well Im not against sending out a mandatory upgrade that fixes these current issues - since c-cex hasnt upgraded the mandatory yet.

Regarding testing in testnet, we DID test in testnet, but these outlying conditions were not caught. I think what we need to do is during the next testing phase, we need more volunteers (we only had a few faithful volunteers last time) and we need to have more elaborate test cases.

Moving forward, I agree, the subsidy was a big surprise and its getting worse. The node ban problem is an issue also.

Why dont we take advantage of this period while the exchange is down and fix the 3 known issues, have a mandatory and then follow up with c-cex. I see they are down for maintenance now, they will probably be taking BBP offline in 20 mins.

I just ran a simulation on the current diff level, and I am positive of the new value that we need compiled in to put our subsidy back around the 18000 level, so that is solved.

The banning issue in prod is solved with a high degree of certainty, I am doing some testing now regarding the root cause.
I did find an issue in the logs regarding reading blocks from the disk errors, based on the posted logs. If I can integrate these 3 fixes into 1032, Id prefer we just go ahead and knock this out and have a mandatory in 4 hours.

Rob