seasonw
|
|
September 12, 2017, 11:30:46 PM |
|
Pool is having problem in last few hours, some of my miners dropped from pool. The message in miner did not show revert to solo mining, but somehow 1 of my machine manage to mine a block I found inconsistent block rewards, usually it was nearly 20000 (199xx), but why sometimes I have 20000, and the last mined block get only 5832?
|
|
|
|
PhaseshiftUK
|
|
September 12, 2017, 11:42:40 PM |
|
Pool is having problem in last few hours, some of my miners dropped from pool. The message in miner did not show revert to solo mining, but somehow 1 of my machine manage to mine a block I found inconsistent block rewards, usually it was nearly 20000 (199xx), but why sometimes I have 20000, and the last mined block get only 5832? It sounds like you are on a fork. In which case this mining is probably not going to count and the amounts will disappear when you get back onto the main chain. You might want to stop and either reindex or delete the existing chain (but not the wallet) and see if you get back onto the proper chain.
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
September 12, 2017, 11:45:28 PM |
|
Pool is having problem in last few hours, some of my miners dropped from pool. The message in miner did not show revert to solo mining, but somehow 1 of my machine manage to mine a block I found inconsistent block rewards, usually it was nearly 20000 (199xx), but why sometimes I have 20000, and the last mined block get only 5832? About 30 minutes ago I was monkeying with the sessionstate and it knocked everyone off for about 15 mins, they are all back, lucking the block was solved 1 minute before they got booted. Anyway, unrelated to that, the low reward is happening now due to the diff > 300. See the prior forum page we were discussing that this morning. One miner pointed 100 servers at the pool today.
|
|
|
|
seasonw
|
|
September 12, 2017, 11:59:33 PM |
|
Pool is having problem in last few hours, some of my miners dropped from pool. The message in miner did not show revert to solo mining, but somehow 1 of my machine manage to mine a block I found inconsistent block rewards, usually it was nearly 20000 (199xx), but why sometimes I have 20000, and the last mined block get only 5832? About 30 minutes ago I was monkeying with the sessionstate and it knocked everyone off for about 15 mins, they are all back, lucking the block was solved 1 minute before they got booted. Anyway, unrelated to that, the low reward is happening now due to the diff > 300. See the prior forum page we were discussing that this morning. One miner pointed 100 servers at the pool today. Oh I see, so any problem with the diff value or this is normal due to large network hashrate now? (Sorry I have searched a few page back on this thread but did not find the discussion about this, just ignore me if it was answered) And wow, big miners are coming now, biblepay is getting popular
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
September 13, 2017, 12:31:22 AM |
|
Pool is having problem in last few hours, some of my miners dropped from pool. The message in miner did not show revert to solo mining, but somehow 1 of my machine manage to mine a block I found inconsistent block rewards, usually it was nearly 20000 (199xx), but why sometimes I have 20000, and the last mined block get only 5832? About 30 minutes ago I was monkeying with the sessionstate and it knocked everyone off for about 15 mins, they are all back, lucking the block was solved 1 minute before they got booted. Anyway, unrelated to that, the low reward is happening now due to the diff > 300. See the prior forum page we were discussing that this morning. One miner pointed 100 servers at the pool today. Oh I see, so any problem with the diff value or this is normal due to large network hashrate now? (Sorry I have searched a few page back on this thread but did not find the discussion about this, just ignore me if it was answered) And wow, big miners are coming now, biblepay is getting popular I think its partially due to the algorithm change. I believe the algorithm change increased the diff from .05 to 100.00. The other part from 100-400 or so is probably the miner with 100 servers. I'll try to add a few more metrics to the pool that show total miner participation, total kh/s, and things like that. Then maybe Happy can jump in and formulate a change for the call to networkhashps. The code was already in GetBlockSubsidy to lower the subsidy when the diff rises, but it was never expected to rise from .01 to 500, I actually expected the subsidy to drop to about 17000 between now and Christmas. So we might have to adjust that slightly in the next mandatory.
|
|
|
|
seasonw
|
|
September 13, 2017, 12:55:27 AM |
|
Pool is having problem in last few hours, some of my miners dropped from pool. The message in miner did not show revert to solo mining, but somehow 1 of my machine manage to mine a block I found inconsistent block rewards, usually it was nearly 20000 (199xx), but why sometimes I have 20000, and the last mined block get only 5832? About 30 minutes ago I was monkeying with the sessionstate and it knocked everyone off for about 15 mins, they are all back, lucking the block was solved 1 minute before they got booted. Anyway, unrelated to that, the low reward is happening now due to the diff > 300. See the prior forum page we were discussing that this morning. One miner pointed 100 servers at the pool today. Oh I see, so any problem with the diff value or this is normal due to large network hashrate now? (Sorry I have searched a few page back on this thread but did not find the discussion about this, just ignore me if it was answered) And wow, big miners are coming now, biblepay is getting popular I think its partially due to the algorithm change. I believe the algorithm change increased the diff from .05 to 100.00. The other part from 100-400 or so is probably the miner with 100 servers. I'll try to add a few more metrics to the pool that show total miner participation, total kh/s, and things like that. Then maybe Happy can jump in and formulate a change for the call to networkhashps. The code was already in GetBlockSubsidy to lower the subsidy when the diff rises, but it was never expected to rise from .01 to 500, I actually expected the subsidy to drop to about 17000 between now and Christmas. So we might have to adjust that slightly in the next mandatory. Noted, thanks for your effort and detailed explanation, dev. Hoping great success to biblepay
|
|
|
|
seasonw
|
|
September 13, 2017, 03:18:33 AM |
|
My ubuntu miner keep banning pool ip, and I always get 0 hashrate in the pool. I have removed the banlist.dat and restart my biblepayd with whitelist: biblepay/src/biblepayd -whitelist=108.61.204.234 -daemon But after some time, I still see 108.61.204.234 being banned in debug.log. Any clue?
|
|
|
|
slovakia
|
|
September 13, 2017, 04:31:20 AM Last edit: September 13, 2017, 04:56:48 AM by slovakia |
|
NetDiff is brutal and growing to the moon hahahaha...... bible_pay pool didnt mine no block? this is real rewards for blocks or cos my wallet is still empty
|
|
|
|
Ginzink
|
|
September 13, 2017, 04:37:35 AM |
|
Hi,
I sendt biblepay from pool and my wallet to C-Cex yesterday but they have not showed up yet. Starting to get worried. I have double checked and wallet address is correct and matching my ledger in C-Cex. It is confirmed with over 80 confirmations according to my wallet. Transaction ID. 28a82d9638da94be05512400d309deb54f5a2a3fb46d48804a07ec0fca28dd06-000
|
|
|
|
slovakia
|
|
September 13, 2017, 04:56:20 AM |
|
Hi,
I sendt biblepay from pool and my wallet to C-Cex yesterday but they have not showed up yet. Starting to get worried. I have double checked and wallet address is correct and matching my ledger in C-Cex. It is confirmed with over 80 confirmations according to my wallet. Transaction ID. 28a82d9638da94be05512400d309deb54f5a2a3fb46d48804a07ec0fca28dd06-000
CCEX Their wallets is Out of sync
|
|
|
|
cryptocurrencyfreak
Newbie
Offline
Activity: 37
Merit: 0
|
|
September 13, 2017, 06:16:35 AM |
|
My linux miners show up briefly once started but eventually disappear from the pool website. These are the last few logs: 2017-09-13 05:49:40 89UpdateTip: new best=13db8243c2bdc0778c90b4570eda7ec1469daf435fa5f9da10e7ae1d9513d84$ 2017-09-13 05:49:40 ProcessNewBlock : ACCEPTED 2017-09-13 05:49:46 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$ 2017-09-13 05:50:45 connection from 175.204.123.147:51971 dropped (banned) 2017-09-13 05:51:34 DGW: Height 7392.000000, NewDiff 1b54a84f nActualTimespan 1134.000000 nTargetT$ 2017-09-13 05:52:09 connection from 218.71.239.70:57766 dropped (banned) 2017-09-13 05:53:41 ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 5478.000000 $ 2017-09-13 05:53:41 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=1999285) ** ProcessGetData:Cannot load block from disk. 2017-09-13 06:01:23 DGW: Height 7392.000000, NewDiff 1b54a84f nActualTimespan 1134.000000 nTargetT$ 2017-09-13 06:02:47 connection from 218.71.239.70:57994 dropped (banned) 2017-09-13 06:05:26 connection from 77.106.146.145:54432 dropped (banned) 2017-09-13 06:05:31 89UpdateTip: new best=e45940fec237f88b0ee2a6f30d89d1875764f6a4ffe4180b52cbf03560ba874$ 2017-09-13 06:05:31 ProcessNewBlock : ACCEPTED 2017-09-13 06:05:37 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$ 2017-09-13 06:09:47 connection from 175.204.123.147:52249 dropped (banned) 2017-09-13 06:12:34 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 7392.00000$ 2017-09-13 06:12:34 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3283261)Upda$ 2017-09-13 06:12:34 ProcessNewBlock : ACCEPTED 2017-09-13 06:12:40 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$ 2017-09-13 06:13:15 ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, pre$ 2017-09-13 06:13:15 ERROR: CheckBlockHeader(): proof of work failed 2017-09-13 06:13:15 Misbehaving: [2001:0:9d38:6abd:30d5:3e2e:5033:846c]:11527 (0 -> 50) 2017-09-13 06:13:15 ERROR: invalid header received 1f317d504e22a10b34d0a48334babd030c96265d5150b0129c9649$ 2017-09-13 06:13:15 ProcessMessages(headers, 28677 bytes) FAILED peer=75 2017-09-13 06:13:44 ERROR: CheckProofOfWork(): hash doesn't meet X11 POW Level, Prod 1.000000, Network main, PrevHeight 0
2017-09-13 06:13:44 ERROR: CheckBlockHeader(): proof of work failed 2017-09-13 06:13:44 Misbehaving: [2001:0:9d38:6abd:30d5:3e2e:5033:846c]:11527 (50 -> 100) BAN THRESHOLD E$ 2017-09-13 06:13:44 ERROR: invalid header received 9002b29834f151df58cd77f3cccb1b34e35c2e1bd1110cffa237ab$ 2017-09-13 06:13:44 ProcessMessages(headers, 82 bytes) FAILED peer=75
|
|
|
|
canonical
|
|
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?
|
|
|
|
inblue
|
|
September 13, 2017, 06:36:23 AM |
|
My linux miners show up briefly once started but eventually disappear from the pool website. These are the last few logs: 2017-09-13 05:49:40 89UpdateTip: new best=13db8243c2bdc0778c90b4570eda7ec1469daf435fa5f9da10e7ae1d9513d84$ 2017-09-13 05:49:40 ProcessNewBlock : ACCEPTED 2017-09-13 05:49:46 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$ 2017-09-13 05:50:45 connection from 175.204.123.147:51971 dropped (banned) 2017-09-13 05:51:34 DGW: Height 7392.000000, NewDiff 1b54a84f nActualTimespan 1134.000000 nTargetT$ 2017-09-13 05:52:09 connection from 218.71.239.70:57766 dropped (banned) 2017-09-13 05:53:41 ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 5478.000000 $ 2017-09-13 05:53:41 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=1999285) ** ProcessGetData:Cannot load block from disk. 2017-09-13 06:01:23 DGW: Height 7392.000000, NewDiff 1b54a84f nActualTimespan 1134.000000 nTargetT$ 2017-09-13 06:02:47 connection from 218.71.239.70:57994 dropped (banned) 2017-09-13 06:05:26 connection from 77.106.146.145:54432 dropped (banned) 2017-09-13 06:05:31 89UpdateTip: new best=e45940fec237f88b0ee2a6f30d89d1875764f6a4ffe4180b52cbf03560ba874$ 2017-09-13 06:05:31 ProcessNewBlock : ACCEPTED 2017-09-13 06:05:37 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$ 2017-09-13 06:09:47 connection from 175.204.123.147:52249 dropped (banned) 2017-09-13 06:12:34 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 7392.00000$ 2017-09-13 06:12:34 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3283261)Upda$ 2017-09-13 06:12:34 ProcessNewBlock : ACCEPTED 2017-09-13 06:12:40 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$ 2017-09-13 06:13:15 ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, pre$ 2017-09-13 06:13:15 ERROR: CheckBlockHeader(): proof of work failed 2017-09-13 06:13:15 Misbehaving: [2001:0:9d38:6abd:30d5:3e2e:5033:846c]:11527 (0 -> 50) 2017-09-13 06:13:15 ERROR: invalid header received 1f317d504e22a10b34d0a48334babd030c96265d5150b0129c9649$ 2017-09-13 06:13:15 ProcessMessages(headers, 28677 bytes) FAILED peer=75 2017-09-13 06:13:44 ERROR: CheckProofOfWork(): hash doesn't meet X11 POW Level, Prod 1.000000, Network main, PrevHeight 0
2017-09-13 06:13:44 ERROR: CheckBlockHeader(): proof of work failed 2017-09-13 06:13:44 Misbehaving: [2001:0:9d38:6abd:30d5:3e2e:5033:846c]:11527 (50 -> 100) BAN THRESHOLD E$ 2017-09-13 06:13:44 ERROR: invalid header received 9002b29834f151df58cd77f3cccb1b34e35c2e1bd1110cffa237ab$ 2017-09-13 06:13:44 ProcessMessages(headers, 82 bytes) FAILED peer=75
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.
|
|
|
|
seasonw
|
|
September 13, 2017, 07:00:24 AM |
|
My linux miners show up briefly once started but eventually disappear from the pool website. These are the last few logs: 2017-09-13 05:49:40 89UpdateTip: new best=13db8243c2bdc0778c90b4570eda7ec1469daf435fa5f9da10e7ae1d9513d84$ 2017-09-13 05:49:40 ProcessNewBlock : ACCEPTED 2017-09-13 05:49:46 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$ 2017-09-13 05:50:45 connection from 175.204.123.147:51971 dropped (banned) 2017-09-13 05:51:34 DGW: Height 7392.000000, NewDiff 1b54a84f nActualTimespan 1134.000000 nTargetT$ 2017-09-13 05:52:09 connection from 218.71.239.70:57766 dropped (banned) 2017-09-13 05:53:41 ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 5478.000000 $ 2017-09-13 05:53:41 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=1999285) ** ProcessGetData:Cannot load block from disk. 2017-09-13 06:01:23 DGW: Height 7392.000000, NewDiff 1b54a84f nActualTimespan 1134.000000 nTargetT$ 2017-09-13 06:02:47 connection from 218.71.239.70:57994 dropped (banned) 2017-09-13 06:05:26 connection from 77.106.146.145:54432 dropped (banned) 2017-09-13 06:05:31 89UpdateTip: new best=e45940fec237f88b0ee2a6f30d89d1875764f6a4ffe4180b52cbf03560ba874$ 2017-09-13 06:05:31 ProcessNewBlock : ACCEPTED 2017-09-13 06:05:37 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$ 2017-09-13 06:09:47 connection from 175.204.123.147:52249 dropped (banned) 2017-09-13 06:12:34 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 7392.00000$ 2017-09-13 06:12:34 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3283261)Upda$ 2017-09-13 06:12:34 ProcessNewBlock : ACCEPTED 2017-09-13 06:12:40 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$ 2017-09-13 06:13:15 ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, pre$ 2017-09-13 06:13:15 ERROR: CheckBlockHeader(): proof of work failed 2017-09-13 06:13:15 Misbehaving: [2001:0:9d38:6abd:30d5:3e2e:5033:846c]:11527 (0 -> 50) 2017-09-13 06:13:15 ERROR: invalid header received 1f317d504e22a10b34d0a48334babd030c96265d5150b0129c9649$ 2017-09-13 06:13:15 ProcessMessages(headers, 28677 bytes) FAILED peer=75 2017-09-13 06:13:44 ERROR: CheckProofOfWork(): hash doesn't meet X11 POW Level, Prod 1.000000, Network main, PrevHeight 0
2017-09-13 06:13:44 ERROR: CheckBlockHeader(): proof of work failed 2017-09-13 06:13:44 Misbehaving: [2001:0:9d38:6abd:30d5:3e2e:5033:846c]:11527 (50 -> 100) BAN THRESHOLD E$ 2017-09-13 06:13:44 ERROR: invalid header received 9002b29834f151df58cd77f3cccb1b34e35c2e1bd1110cffa237ab$ 2017-09-13 06:13:44 ProcessMessages(headers, 82 bytes) FAILED peer=75
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 issue happened to me on my ubuntu. After fixing the pool ip banning issue, now this is the cause that make my miner go off the pool. Same thought as inblue did, I don't think it reverted to solo mining. So, I have stopped some of my miners.
|
|
|
|
inblue
|
|
September 13, 2017, 07:06:02 AM |
|
You dont happen to have that Xubuntu setup do you? Im still unable to run. I could send you some BBP! I keep getting this error: make: *** No targets specified and no makefile found. Stop. Not sure where the holdup is. I tried in /Biblepay and in /SRC..made sure I was sudo.. linux new to me however. Before make you need to run ./autogen.sh and ./configure @inblue , which linux distro are you using for BBP miner ? Ubuntu 16.04.2 LTS (amd64)
|
|
|
|
nananaminer
Newbie
Offline
Activity: 42
Merit: 0
|
|
September 13, 2017, 07:18:25 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.
|
|
|
|
inblue
|
|
September 13, 2017, 07:21:19 AM |
|
One of the miners seem to have switched to solo mining since it found a block, and I've discovered a new error: 2017-09-13 07:15:00 generated 5000.00 2017-09-13 07:15:00 89UpdateTip: new best=e900b62013cea73df955c0edc8f56f56af5439acc8020970191bba58f4760344 height=7374 log2_work=48.185504 tx=11349 date=2017-09-13 07:14:50 progress=0.999999 cache=0.0MiB(1tx) 2017-09-13 07:15:00 CheckForkWarningConditions: Warning: Found invalid chain at least ~6 blocks longer than our best chain. Chain state database corruption likely.
|
|
|
|
inblue
|
|
September 13, 2017, 07:25:15 AM |
|
@bible_pay Any chance of fixing the difficulty adjustment sooner, the difficulty is increasing exponentially and block rewards are at 25% now.
No, it's better that rewards are as small as possible. Because: At this point we are harder to mine, and have less reward per block, so the exchange being a free market should take that into account and BBP may increase in value.
|
|
|
|
nananaminer
Newbie
Offline
Activity: 42
Merit: 0
|
|
September 13, 2017, 07:35:40 AM |
|
@bible_pay Any chance of fixing the difficulty adjustment sooner, the difficulty is increasing exponentially and block rewards are at 25% now.
No, it's better that rewards are as small as possible. Because: At this point we are harder to mine, and have less reward per block, so the exchange being a free market should take that into account and BBP may increase in value.
Definitely understand the supply vs demand side but at the same time the difficulty bug will eventually will be fixed in few months and when its back to 20k rewards, the equation will change. Current situation is good for short time gain but in order for the coin to prolong through years it has to have consistency. Looks like my miners went to solo as well when it got dropped from the pool and mined a few blocks. What's the command to see all the block mined by a certain daemon?
|
|
|
|
seasonw
|
|
September 13, 2017, 07:43:35 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
|
|
|
|
|