Search content
Sort by
Showing 17 of 17 results by hvdb
which exchanges wants coin when its nonstop updating? 
confirmed too
my miners got very low HPS2
and no all is online
confirmed too
my miners got very low HPS2
and no all is onlineMine too..Low hps2
I also dropped Quite a lot on the leaderboard.
And As a result my shares are lower
Do where I was in top 10 I am no at 20 or so.
And there is a big differenws between my miners although hardware is rhe Same.
One has hps of 1500 other 13000 which was the lowesr before the update.
So there is some flakyness at least. If All would be at the samelevel then there wouldnt be a problem.
But as there is difference between the Same hardware it most likely is a big or something somewheew Right?
No, not the case.
First thing you need to do is run solo for an hour on each of the two machines and post the wallets HPS, and be descriptive about what you tested and label the value something descriptive, like "procname, location, threads, core-wallet HPS". Then let us see how that compares to the other "exact" proc before talking about the pool layer.
Also take into account the HPS2 is generated over time.
Hello,
I will start a miner in solo.
And report it tomorrow!
My setup: 4 core xeon (8 threads)
8 bible pay instances running with 1 thread.
They should give more or less the same numbers, they did at least. (some differences but not that much)
name. hps hps2
hvdbWorld6_1 537.58 2475.94
hvdbWorld6_2 537.42 3533.94
hvdbWorld6_3 537.06 1247.75
hvdbWorld6_4 537.16 6084.77
hvdbWorld6_5 537.26 3770.02
hvdbWorld6_6 537.4 5763.09
hvdbWorld6_7 537.65 7096.88
hvdbWorld6_8 537.62 4592.51
And other identical server:
hvdbWorld7_1 164.84 3724.04
Missing
hvdbWorld7_3 658.04 9770.68
hvdbWorld7_4 657.72 15507.6
hvdbWorld7_6 658.34 3643.06
hvdbWorld7_5 658.35 12560.54
hvdbWorld7_7 657.41 7274.45
hvdbWorld7_8 658.34 7751.4
I will look at any differences between the setup of the servers.
Edit:
After I got the numbers and refreshed the page most of the miners disappeared.
They are not in missing miner section.
And after a new refresh some are back.
I will look on the nodes if I see something,.
which exchanges wants coin when its nonstop updating?
confirmed too
my miners got very low HPS2 and no all is online
confirmed too
my miners got very low HPS2
and no all is onlineMine too..Low hps2
I also dropped Quite a lot on the leaderboard.
And As a result my shares are lower
Do where I was in top 10 I am no at 20 or so.
And there is a big differenws between my miners although hardware is rhe Same.
One has hps of 1500 other 13000 which was the lowesr before the update.
So there is some flakyness at least. If All would be at the samelevel then there wouldnt be a problem.
But as there is difference between the Same hardware it most likely is a big or something somewheew Right?
Hi,
Regarding minning on the pool it looks like many users went solo, so the pool does not have powerful machines any more and it is missing most of the blocks. If this goes on for a while, some others might leave too.
What should we do? I am giving it all in a pool, but it looks pointless for now - yes I know, if we all think like that, than we can leave and pool can close till block difficulty it too high to solve in a reasonable time and most come back to pool.
Any thoughts?
Best regards,
Simon
Regarding minning on the pool it looks like many users went solo, so the pool does not have powerful machines any more and it is missing most of the blocks. If this goes on for a while, some others might leave too.
What should we do? I am giving it all in a pool, but it looks pointless for now - yes I know, if we all think like that, than we can leave and pool can close till block difficulty it too high to solve in a reasonable time and most come back to pool.
Any thoughts?
Best regards,
Simon
The thing is, the pool solves enough blocks per day to make it a pool, IE more than One, so in my eyes we dont have an issue. You get compensated in the pool based on how much HPS you bring to the table.
Once this botnet gets hit below 50%, things are going to get interesting for them.
Is it a problem that the AVG HPS is 500?
Does it help if we add more high power miners? instead of x number of small once?
(having multiple miners (1 cpu) gives more hps2 then running one instance with 8cpu. But does that really help the pool? or is it better to have also big miners?)
Guys,
Let's be reasonable and have a good look at the mining of the coin.
I don't think it is a scam or there is a bit problem with the pool.
Ofcourse there maybe some tricks and tweaks to get a better performing pool, but that's not our issue now as far as I see it.
If we go back a few weeks:
there where less miner on the pool (half) less mining power also.
Network hash was also low.
Then a mandatory update came, resulting in the pool hitting lots more blocks with almost the same hash power.
Network hash was low since not everybody updated.
From what I understand Rob received lots of complains from China about the mandatory update.
They are running botnet to mine bbp and needed to update their botnet (right?)
If we look at how much interest there is for the project (low), volume trading is low (even when exchange is up)
Pool did gain some more interest, although I think the increase of miners is because the existing users added more nodes and some new people entered but not a lot.
There could be a second pool, but I dare to believe that since it's such a small coin and running a 'hidden' pool for it is not really ideal, or you need to have a lot of money to get enough machines. (and they will run into the same issue as we have, low return)
The idea of the coin is that people can use there old/decent pc to mine the coin and help charity (and well themselves for a bit)
This is a great idea and a very good part of the coin, however it also is the biggest downside now.
Making the entry and mine ability that easy means that it can be a very easy target for criminals/greedy people/people with other interest so to speak
And I think that is going on now.
I cannot imagine that there are some much solo miners on purpose for such a small coin, joining the pool would help them get more so why would you mine solo?
Unless you have something to hide...
Someone made a botnet that is (unwanted) using the computers of affected people to mine BiblePay.
The income does not go to the owner of the machine but to the owner(s) of the botnet. And that is I think a very bad idea.
It means that someone is earning money over the back of harmless people. People that get a higher electric bill (pc is always at full power) and maybe even a faster broken pc/frusterated about there slow pc.
some facts for now:
The pool hs is about 2,5gh, network is 70gh. (54 according to my miner)
That is a Hugh! difference, and that also means that the likelihood that we hid a block is very low of course.
And could mean that we don't hit one for a couple of hours/days even.
And with the increased hashes/miners on the pool everybody gets less share of it.
Although if it was not increased I think we would hit even less...
conclusion:
Rob, can you have a look at the pool and see if there are tweaks/fixes that can help distribute the blocks like you did earlier. Maybe you spot something.
Or anybody else that can I will also see if I can find something (c++ is not really my thing... but should be able)
And with the latest mandatory update, did you get a lot of complains from solo miners ('legit' solo miners) ?
second:
I think we need to find a way to 'block' the botnet.
I am not against solo mining. I am against solo mining with the profit going to wrong people. I think that's not the idea of the coin.
It feels pretty wrong and bad.
But, I also know it is quite hard/maybe even impossible. Are there coins that prevent solo mining??
Some suggestions:
New mandatory update, that would cripple there botnet for a while.
And we can find out if the theory is correct.
Make some 'registration' for solo miners.
If you are solo mining you need to provide a identification token that can be validated. The identification token must be requested 'by hand' via the pool/block chain.
ie: preventing automatic setup, users need todo some steps in order to be able to mine the coin. This way legit users can solo mine but botnet are likely to stop since it's lots of manual labour.
Could be something like a hash that need to be requested via a webpage with a captcha on it so that it can't be automated. Or anything.
Or block all solo mining (if possible). But that would be the least favourite option.
(although I think that if you have a low power cpu there is no reason not to join the pool, and we can prevent users from running there pc without any reason. Since the users with low cpu are probably less experienced miners)
What do you guys think?
p.s.
I can help with some work, I work as a javascript (nodejs/polymer) and java developer. C++ is a while ago, but at least I can help testing and think about solution maybe.
Let's be reasonable and have a good look at the mining of the coin.
I don't think it is a scam or there is a bit problem with the pool.
Ofcourse there maybe some tricks and tweaks to get a better performing pool, but that's not our issue now as far as I see it.
If we go back a few weeks:
there where less miner on the pool (half) less mining power also.
Network hash was also low.
Then a mandatory update came, resulting in the pool hitting lots more blocks with almost the same hash power.
Network hash was low since not everybody updated.
From what I understand Rob received lots of complains from China about the mandatory update.
They are running botnet to mine bbp and needed to update their botnet (right?)
If we look at how much interest there is for the project (low), volume trading is low (even when exchange is up)
Pool did gain some more interest, although I think the increase of miners is because the existing users added more nodes and some new people entered but not a lot.
There could be a second pool, but I dare to believe that since it's such a small coin and running a 'hidden' pool for it is not really ideal, or you need to have a lot of money to get enough machines. (and they will run into the same issue as we have, low return)
The idea of the coin is that people can use there old/decent pc to mine the coin and help charity (and well themselves for a bit)
This is a great idea and a very good part of the coin, however it also is the biggest downside now.
Making the entry and mine ability that easy means that it can be a very easy target for criminals/greedy people/people with other interest so to speak
And I think that is going on now.
I cannot imagine that there are some much solo miners on purpose for such a small coin, joining the pool would help them get more so why would you mine solo?
Unless you have something to hide...
Someone made a botnet that is (unwanted) using the computers of affected people to mine BiblePay.
The income does not go to the owner of the machine but to the owner(s) of the botnet. And that is I think a very bad idea.
It means that someone is earning money over the back of harmless people. People that get a higher electric bill (pc is always at full power) and maybe even a faster broken pc/frusterated about there slow pc.
some facts for now:
The pool hs is about 2,5gh, network is 70gh. (54 according to my miner)
That is a Hugh! difference, and that also means that the likelihood that we hid a block is very low of course.
And could mean that we don't hit one for a couple of hours/days even.
And with the increased hashes/miners on the pool everybody gets less share of it.
Although if it was not increased I think we would hit even less...
conclusion:
Rob, can you have a look at the pool and see if there are tweaks/fixes that can help distribute the blocks like you did earlier. Maybe you spot something.
Or anybody else that can
I will also see if I can find something (c++ is not really my thing... but should be able)And with the latest mandatory update, did you get a lot of complains from solo miners ('legit' solo miners) ?
second:
I think we need to find a way to 'block' the botnet.
I am not against solo mining. I am against solo mining with the profit going to wrong people. I think that's not the idea of the coin.
It feels pretty wrong and bad.
But, I also know it is quite hard/maybe even impossible. Are there coins that prevent solo mining??
Some suggestions:
New mandatory update, that would cripple there botnet for a while.
And we can find out if the theory is correct.
Make some 'registration' for solo miners.
If you are solo mining you need to provide a identification token that can be validated. The identification token must be requested 'by hand' via the pool/block chain.
ie: preventing automatic setup, users need todo some steps in order to be able to mine the coin. This way legit users can solo mine but botnet are likely to stop since it's lots of manual labour.
Could be something like a hash that need to be requested via a webpage with a captcha on it so that it can't be automated. Or anything.
Or block all solo mining (if possible). But that would be the least favourite option.
(although I think that if you have a low power cpu there is no reason not to join the pool, and we can prevent users from running there pc without any reason. Since the users with low cpu are probably less experienced miners)
What do you guys think?
p.s.
I can help with some work, I work as a javascript (nodejs/polymer) and java developer. C++ is a while ago, but at least I can help testing and think about solution maybe.
Interesting growth in BBP!
I took a screen-shot of pool miners and HPS a few days ago, just after the first superblock (I think it was block 24601). Then we had 2953 miners and a HPS of 2247655.52.
As on just now we have
3771 miners, a 28% increase in # of miners in 2 days
2606630.32 HPS, a 16% increase in pool HPS in 2 days!
The BiblePay subreddit has been undergoing steady growth in subscribers (approx. double in the last month).
A Google trends search for "BiblePay" shows a massive increase in interest since late Nov
https://i.imgur.com/txww8vu.png
https://i.imgur.com/LSC2gvL.png
Nice work!
I took a screen-shot of pool miners and HPS a few days ago, just after the first superblock (I think it was block 24601). Then we had 2953 miners and a HPS of 2247655.52.
As on just now we have
3771 miners, a 28% increase in # of miners in 2 days
2606630.32 HPS, a 16% increase in pool HPS in 2 days!
The BiblePay subreddit has been undergoing steady growth in subscribers (approx. double in the last month).
A Google trends search for "BiblePay" shows a massive increase in interest since late Nov
https://i.imgur.com/txww8vu.png
https://i.imgur.com/LSC2gvL.png
Nice work!
Indeed, good to see.
Odd part is that we dont hit More blocks.
Clearly we should hit More if the Power is increqsed Right?
Changes to the Pool to help investigate the percentage of blocks Solved by the Pool miners:
I've been investigating the distinct solved blocks by the pool over 24 hours and see that the pools percent dropped to 17% from approx. 45% two weeks ago, despite having an increase in hashpower and an increase in distinct miner count.
Looking at the mining template that is given to every miner, I came to the conclusion that one possibility is everyone together is trying to solve the same block (since the pool only has one address, and our distinct transaction count in the block is relatively low). I was thinking maybe everyone is doing the same work without realizing it, and that means as we increase the load on the pool, the problem actually gets worse (as diff increases, more miners do exactly the same work).
So to investigate this I analyzed the top 1000 solutions in the last 15 minutes and sure enough, about 15% of the solutions appear to be exactly the same.
So in light of this I am adding two new features to the pool to attempt to "potentially" measure and or solve this problem:
#1: We now require unique solutions for every miner. So any miner who sends the same solution as another miner, the early bird gets the share, the later solution gets marked as SOLUTION_STALE and then the core asks the pool for a new piece of work. (This will probably cause the big dogs in the pool to lose some shares, relatively speaking compared to small dogs, but we'll see).
#2: Since I want to eliminate the possibility of a duplicated block template across the pool, I have requested the pool to have 7 receiving addresses, starting now. Now, the pool will check its receive address list whenever doing block checking. It will also issue a random receiving address in the block template, thereby creating a more unique template per miner. This is now in prod.
Let us monitor the pool for the next 24 hours and see if we have an uptick in pool based solutions.
I've been investigating the distinct solved blocks by the pool over 24 hours and see that the pools percent dropped to 17% from approx. 45% two weeks ago, despite having an increase in hashpower and an increase in distinct miner count.
Looking at the mining template that is given to every miner, I came to the conclusion that one possibility is everyone together is trying to solve the same block (since the pool only has one address, and our distinct transaction count in the block is relatively low). I was thinking maybe everyone is doing the same work without realizing it, and that means as we increase the load on the pool, the problem actually gets worse (as diff increases, more miners do exactly the same work).
So to investigate this I analyzed the top 1000 solutions in the last 15 minutes and sure enough, about 15% of the solutions appear to be exactly the same.
So in light of this I am adding two new features to the pool to attempt to "potentially" measure and or solve this problem:
#1: We now require unique solutions for every miner. So any miner who sends the same solution as another miner, the early bird gets the share, the later solution gets marked as SOLUTION_STALE and then the core asks the pool for a new piece of work. (This will probably cause the big dogs in the pool to lose some shares, relatively speaking compared to small dogs, but we'll see).
#2: Since I want to eliminate the possibility of a duplicated block template across the pool, I have requested the pool to have 7 receiving addresses, starting now. Now, the pool will check its receive address list whenever doing block checking. It will also issue a random receiving address in the block template, thereby creating a more unique template per miner. This is now in prod.
Let us monitor the pool for the next 24 hours and see if we have an uptick in pool based solutions.
That sounds like a very possible cause. Right now I'm seeing quite the effect on the shares: overall I think shares dropped a little bit, but the more significant change is that my small miners (genproclimit=1) have completely disappeared from the list (despite still mining and showing hashps>200 in "getmininginfo"). So it seems that the slow machines currently drop out completely from time to time because they don't hit legit shares fast enough? Let's see how it all works out in a couple of hours or tomorrow.
I am having the same problem
Same here...
Look at the work list the small miners are there but looking at the leaderboard, they are gone...
Also shares is indeed a (lot) lower, but if we hit more blocks it should in the end be the same right?
So I tried logging on and off several times, this didn't help. Having logged in I can open another tab and don't need to log in again, so this is working.
Then I checked the cookies my browser saved from pool.biblepay.org and I think I found the mistake: the credentials_password cookie saves a wrong value for my pw (double-checked this by deleting it, logging off and on again, same mistake). The problem seems to be that my pool-pw uses a semicolon ( ; ) in the middle of the word and this seems to create a problem for the cookie, because the cookie-pw stops at the letter before the ";". I will try and change my pw again without diacritical signs and see if that helps.
One of my computers just crashed again, I disabled SSL, let's hope for the best. :-D
Edit:
Oh, you beat me to it by posting the update, I'm gonna give this a try then, let's see how it works out over night.
Seems to have worked as expected over night. I tried 3 different things:
a) one machine with 1.0.7.5 and SSL enabled --> crashed
b) one machine with 1.0.7.5 and SSL disabled --> worked
c) one machine with 1.0.7.6 and SSL enabled --> worked
So this was definitely and solely an SSL issue, which is fixed in 76; thanks again.
Regarding the pool login: now without the semicolon in my password the pool page works like a charm and does not kick me out every couple of minutes, so problem solved I guess.
Only "problem" remaining is: why is the (only existing) pool hitting less than 20% of the blocks.
So I updated to 1.0.7.6 and most miners keeped working.
However some crashed.
I don't see a direct reason why... there is no error or exception.
Any idea?
Code:
2018-01-04 23:02:32 CMasternodePayments::FillBlockPayee -- Masternode payment 693702923735.000000 to BNidV9kWAZECM1sEtg7ZiQyYn2ghDY6mN9
2018-01-04 23:02:32 CMasternodePayments::FillBlockPayee -- Masternode payment 693702923735.000000 to BNidV9kWAZECM1sEtg7ZiQyYn2ghDY6mN9
2018-01-04 23:03:47 CMasternodePayments::FillBlockPayee -- Masternode payment 693702926015.000000 to BNidV9kWAZECM1sEtg7ZiQyYn2ghDY6mN9
2018-01-04 23:04:07 CMasternodePayments::FillBlockPayee -- Masternode payment 693702926015.000000 to BNidV9kWAZECM1sEtg7ZiQyYn2ghDY6mN9
2018-01-04 23:04:26 CMasternodePayments::FillBlockPayee -- Masternode payment 693702926015.000000 to BNidV9kWAZECM1sEtg7ZiQyYn2ghDY6mN9
2018-01-04 23:04:31 CMasternodePayments::FillBlockPayee -- Masternode payment 693702926015.000000 to BNidV9kWAZECM1sEtg7ZiQyYn2ghDY6mN9
2018-01-04 23:07:38 msghand thread interrupt
2018-01-04 23:07:38 addcon thread interrupt
2018-01-04 23:07:38 opencon thread interrupt
2018-01-04 23:07:38 net thread interrupt
2018-01-04 23:07:38 scheduler thread interrupt
2018-01-04 23:07:38 mnbcon thread interrupt
2018-01-04 23:07:39 PrepareShutdown: In progress...
2018-01-04 23:07:39 StopNode()
2018-01-04 23:07:51 Verifying mncache.dat format...
2018-01-04 23:07:51 Loaded info from mncache.dat 93ms
2018-01-04 23:07:51 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 15347
2018-01-04 23:07:51 Writting info to mncache.dat...
2018-01-04 23:07:51 Written info to mncache.dat 690ms
2018-01-04 23:07:51 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 7, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 15472
2018-01-04 23:07:51 mncache.dat dump finished 784ms
2018-01-04 23:07:51 Verifying mnpayments.dat format...
2018-01-04 23:07:52 Loaded info from mnpayments.dat 484ms
2018-01-04 23:07:52 Votes: 24388, Blocks: 2541
2018-01-04 23:07:52 Writting info to mnpayments.dat...
2018-01-04 23:07:54 Written info to mnpayments.dat 1807ms
2018-01-04 23:07:54 Votes: 25812, Blocks: 2684
2018-01-04 23:07:54 mnpayments.dat dump finished 2293ms
2018-01-04 23:07:54 Verifying governance.dat format...
2018-01-04 23:07:55 Loaded info from governance.dat 1295ms
2018-01-04 23:07:55 Governance Objects: 15 (Proposals: 13, Triggers: 1, Watchdogs: 1/1, Other: 0; Seen: 69), Votes: 0
2018-01-04 23:07:55 Writting info to governance.dat...
2018-01-04 23:07:56 Written info to governance.dat 773ms
2018-01-04 23:07:56 Governance Objects: 15 (Proposals: 13, Triggers: 1, Watchdogs: 1/1, Other: 0; Seen: 70), Votes: 691
2018-01-04 23:07:56 governance.dat dump finished 2068ms
2018-01-04 23:07:56 Verifying netfulfilled.dat format...
2018-01-04 23:07:56 Loaded info from netfulfilled.dat 40ms
2018-01-04 23:07:56 Nodes with fulfilled requests: 8
2018-01-04 23:07:56 Writting info to netfulfilled.dat...
2018-01-04 23:07:56 Written info to netfulfilled.dat 0ms
2018-01-04 23:07:56 Nodes with fulfilled requests: 9
2018-01-04 23:07:56 netfulfilled.dat dump finished 40ms
2018-01-04 23:08:17 Shutdown: done
2018-01-04 23:02:32 CMasternodePayments::FillBlockPayee -- Masternode payment 693702923735.000000 to BNidV9kWAZECM1sEtg7ZiQyYn2ghDY6mN9
2018-01-04 23:03:47 CMasternodePayments::FillBlockPayee -- Masternode payment 693702926015.000000 to BNidV9kWAZECM1sEtg7ZiQyYn2ghDY6mN9
2018-01-04 23:04:07 CMasternodePayments::FillBlockPayee -- Masternode payment 693702926015.000000 to BNidV9kWAZECM1sEtg7ZiQyYn2ghDY6mN9
2018-01-04 23:04:26 CMasternodePayments::FillBlockPayee -- Masternode payment 693702926015.000000 to BNidV9kWAZECM1sEtg7ZiQyYn2ghDY6mN9
2018-01-04 23:04:31 CMasternodePayments::FillBlockPayee -- Masternode payment 693702926015.000000 to BNidV9kWAZECM1sEtg7ZiQyYn2ghDY6mN9
2018-01-04 23:07:38 msghand thread interrupt
2018-01-04 23:07:38 addcon thread interrupt
2018-01-04 23:07:38 opencon thread interrupt
2018-01-04 23:07:38 net thread interrupt
2018-01-04 23:07:38 scheduler thread interrupt
2018-01-04 23:07:38 mnbcon thread interrupt
2018-01-04 23:07:39 PrepareShutdown: In progress...
2018-01-04 23:07:39 StopNode()
2018-01-04 23:07:51 Verifying mncache.dat format...
2018-01-04 23:07:51 Loaded info from mncache.dat 93ms
2018-01-04 23:07:51 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 15347
2018-01-04 23:07:51 Writting info to mncache.dat...
2018-01-04 23:07:51 Written info to mncache.dat 690ms
2018-01-04 23:07:51 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 7, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 15472
2018-01-04 23:07:51 mncache.dat dump finished 784ms
2018-01-04 23:07:51 Verifying mnpayments.dat format...
2018-01-04 23:07:52 Loaded info from mnpayments.dat 484ms
2018-01-04 23:07:52 Votes: 24388, Blocks: 2541
2018-01-04 23:07:52 Writting info to mnpayments.dat...
2018-01-04 23:07:54 Written info to mnpayments.dat 1807ms
2018-01-04 23:07:54 Votes: 25812, Blocks: 2684
2018-01-04 23:07:54 mnpayments.dat dump finished 2293ms
2018-01-04 23:07:54 Verifying governance.dat format...
2018-01-04 23:07:55 Loaded info from governance.dat 1295ms
2018-01-04 23:07:55 Governance Objects: 15 (Proposals: 13, Triggers: 1, Watchdogs: 1/1, Other: 0; Seen: 69), Votes: 0
2018-01-04 23:07:55 Writting info to governance.dat...
2018-01-04 23:07:56 Written info to governance.dat 773ms
2018-01-04 23:07:56 Governance Objects: 15 (Proposals: 13, Triggers: 1, Watchdogs: 1/1, Other: 0; Seen: 70), Votes: 691
2018-01-04 23:07:56 governance.dat dump finished 2068ms
2018-01-04 23:07:56 Verifying netfulfilled.dat format...
2018-01-04 23:07:56 Loaded info from netfulfilled.dat 40ms
2018-01-04 23:07:56 Nodes with fulfilled requests: 8
2018-01-04 23:07:56 Writting info to netfulfilled.dat...
2018-01-04 23:07:56 Written info to netfulfilled.dat 0ms
2018-01-04 23:07:56 Nodes with fulfilled requests: 9
2018-01-04 23:07:56 netfulfilled.dat dump finished 40ms
2018-01-04 23:08:17 Shutdown: done
1.0.7.5 version seem have problem.
It is the second times occurred , I am re-indexing again.
I worry it will happen again....
Hello all!
I have been following this thread and this project for several weeks now and I am really excited to see the hard work and dedication going into developing all of this. However the last couple of days it seems to me that the only concern you have regarding troubleshooting is with the MN owners, not the miners.
Several people reported the above mentioned error and I also experience it regularly since updating to 1.0.7.5 on different machines, different networks, even different cities across Germany. So the error is definitely not on my side, because also the configurations on these machines differ from each other and each and every one gets this error after a few hours of mining.
However, no one has offered any permanent solution or even explained where this is coming from. I think the only reason so few people have this problem is because judging by the connected peers on my systems most people are still on the working version 1.0.7.1.
So when will this annoying problem be fixed? Another question you never answered was how this new "competitive mining" feature really works. Right now it seems to me that all the update did was giving an even bigger malus to the faster CPUs and DualCPU-systems and more and more degrading mining output. For example my 10 year old Core2 laptop with proclimit 1 is sometimes producing almost as many shares as my Dual-hexacore-Xeon server on proclimit 12, which is absolutely ridiculous.
I understand that your main priority right now are your precious masternodes, but please don't forget about us small-time miners and remember that without the miners your blockchain wouldn't really work either. Comparing the output from before Christmas or even from last week I'm currently at approx. 10%, which barely - if at all - covers my electricity bill.
Thanks for your time and effort and God bless this project!
Edit: For clarification: up to now it seems that the error only occurs with the linux client (Ubuntu 16.04 LTS in my case), the windows wallet doesn't seem to be affected.
It is the second times occurred , I am re-indexing again.
I worry it will happen again....
Hello all!
I have been following this thread and this project for several weeks now and I am really excited to see the hard work and dedication going into developing all of this. However the last couple of days it seems to me that the only concern you have regarding troubleshooting is with the MN owners, not the miners.
Several people reported the above mentioned error and I also experience it regularly since updating to 1.0.7.5 on different machines, different networks, even different cities across Germany. So the error is definitely not on my side, because also the configurations on these machines differ from each other and each and every one gets this error after a few hours of mining.
However, no one has offered any permanent solution or even explained where this is coming from. I think the only reason so few people have this problem is because judging by the connected peers on my systems most people are still on the working version 1.0.7.1.
So when will this annoying problem be fixed? Another question you never answered was how this new "competitive mining" feature really works. Right now it seems to me that all the update did was giving an even bigger malus to the faster CPUs and DualCPU-systems and more and more degrading mining output. For example my 10 year old Core2 laptop with proclimit 1 is sometimes producing almost as many shares as my Dual-hexacore-Xeon server on proclimit 12, which is absolutely ridiculous.
I understand that your main priority right now are your precious masternodes, but please don't forget about us small-time miners and remember that without the miners your blockchain wouldn't really work either. Comparing the output from before Christmas or even from last week I'm currently at approx. 10%, which barely - if at all - covers my electricity bill.
Thanks for your time and effort and God bless this project!
Edit: For clarification: up to now it seems that the error only occurs with the linux client (Ubuntu 16.04 LTS in my case), the windows wallet doesn't seem to be affected.
Hi Dave,
Its just not true that we only care about precious masternodes.
Here is the way I view the priorities right now just so you know: I want to ensure we are ready for block 24600, so we can pay our orphans.
Next, I want to maintain production support levels. That includes any critical errors with 1075. And finally, I place a very low priority level personally on any "hash speed discussions". So maybe thats the point of contention. We only have enough resources to talk about the prod support and the critical errors and not about peoples mining speed, unless its an inconsistency in the pool that affects everyone.
Of course we have time to talk about how competetive mining works.
But first:
So, Im not aware of a critical bug in 1075, and have not received a log. Can someone please give us a log so we can see what stopped the node in 1075??
There is no way to even look at a problem without a log.
Can we have a look after we hit the 24600 block at the pool?
I can help investigating and testing etc, no problem.
It feels weird that we only hit 20-25% with nearly 2800 miners and 2390627.92 hps.
Are there really lots of people solo mining, could be but I find it hard to believe if we look at the numbers and interest here on the forum.
Hi Dave,
Its just not true that we only care about precious masternodes.
Here is the way I view the priorities right now just so you know: I want to ensure we are ready for block 24600, so we can pay our orphans.
Next, I want to maintain production support levels. That includes any critical errors with 1075. And finally, I place a very low priority level personally on any "hash speed discussions". So maybe thats the point of contention. We only have enough resources to talk about the prod support and the critical errors and not about peoples mining speed, unless its an inconsistency in the pool that affects everyone.
Of course we have time to talk about how competetive mining works.
But first:
So, Im not aware of a critical bug in 1075, and have not received a log. Can someone please give us a log so we can see what stopped the node in 1075??
There is no way to even look at a problem without a log.
Thank you for your explanations (also in your other posts about the competitive mining. Indeed that makes sense. I have copied the last lines from the debug.log, where the error occurs (wasn't really sure where to start...):
Code:
2018-01-04 13:15:15 Resetting mining tithe 259.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:15:28 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:15:39 Resetting mining tithe 260.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:15:52 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:16:41 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:17:37 Resetting mining tithe 261.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:00 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:18 Resetting mining tithe 262.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:58 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:48 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:48 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:51 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:56 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:08 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:12 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:27 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:32 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:57 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:21:17 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:21:45 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:23 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:38 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:23:46 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:24:42 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:08 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:11 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:05 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:33 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:52 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:27:34 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:28:10 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:28:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:06 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:25 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:24 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:44 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:31:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:10 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:29 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:50 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:33:55 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:22 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:53 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:35:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:35:49 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:36:16 ERROR: Write: Failed to open file /home/david/.biblepaycore/peers.dat.add3
2018-01-04 13:36:18 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:36:23 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:37:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:38:25 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:38:32 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:00 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:26 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:58 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:41:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:41:44 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:14 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/blk00000.dat
2018-01-04 13:42:14 ERROR: WriteBlockToDisk: OpenBlockFile failed
2018-01-04 13:42:14 *** Failed to write block
2018-01-04 13:42:14 Error: Error: A fatal internal error occurred, see debug.log for details
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/blk00000.dat
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/rev00000.dat
2018-01-04 13:42:14 tor: Thread interrupt
2018-01-04 13:42:14 torcontrol thread exit
2018-01-04 13:42:14 opencon thread interrupt
2018-01-04 13:42:14 addcon thread interrupt
2018-01-04 13:42:14 mnbcon thread interrupt
2018-01-04 13:42:14 scheduler thread interrupt
2018-01-04 13:42:14 net thread interrupt
2018-01-04 13:42:16 ProcessNewBlock : ACCEPTED
2018-01-04 13:42:16 msghand thread interrupt
2018-01-04 13:42:16 PrepareShutdown: In progress...
2018-01-04 13:42:16 StopNode()
2018-01-04 13:42:16
BiblepayMiner -- terminated
2018-01-04 13:42:16 Verifying mncache.dat format...
2018-01-04 13:42:16 Loaded info from mncache.dat 6ms
2018-01-04 13:42:16 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 2149
2018-01-04 13:42:16 Writting info to mncache.dat...
2018-01-04 13:42:16 Written info to mncache.dat 6ms
2018-01-04 13:42:16 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 2856
2018-01-04 13:42:16 mncache.dat dump finished 12ms
2018-01-04 13:42:16 Verifying mnpayments.dat format...
2018-01-04 13:42:16 Loaded info from mnpayments.dat 135ms
2018-01-04 13:42:16 Votes: 24615, Blocks: 2564
2018-01-04 13:42:16 Writting info to mnpayments.dat...
2018-01-04 13:42:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:16 Written info to mnpayments.dat 121ms
2018-01-04 13:42:16 Votes: 25214, Blocks: 2624
2018-01-04 13:42:16 mnpayments.dat dump finished 259ms
2018-01-04 13:42:16 Verifying governance.dat format...
2018-01-04 13:42:16 Loaded info from governance.dat 16ms
2018-01-04 13:42:16 Governance Objects: 22 (Proposals: 19, Triggers: 2, Watchdogs: 1/1, Other: 0; Seen: 24), Votes: 0
2018-01-04 13:42:16 Writting info to governance.dat...
2018-01-04 13:42:16 Written info to governance.dat 5ms
2018-01-04 13:42:16 Governance Objects: 22 (Proposals: 19, Triggers: 2, Watchdogs: 1/1, Other: 0; Seen: 26), Votes: 847
2018-01-04 13:42:16 governance.dat dump finished 21ms
2018-01-04 13:42:16 Verifying netfulfilled.dat format...
2018-01-04 13:42:16 Loaded info from netfulfilled.dat 0ms
2018-01-04 13:42:16 Nodes with fulfilled requests: 10
2018-01-04 13:42:16 Writting info to netfulfilled.dat...
2018-01-04 13:42:16 Written info to netfulfilled.dat 0ms
2018-01-04 13:42:16 Nodes with fulfilled requests: 9
2018-01-04 13:42:16 netfulfilled.dat dump finished 0ms
2018-01-04 13:42:16
BiblepayMiner -- terminated
2018-01-04 13:42:16 Shutdown: done
2018-01-04 13:15:28 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:15:39 Resetting mining tithe 260.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:15:52 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:16:41 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:17:37 Resetting mining tithe 261.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:00 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:18 Resetting mining tithe 262.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:58 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:48 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:48 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:51 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:56 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:08 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:12 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:27 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:32 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:57 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:21:17 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:21:45 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:23 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:38 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:23:46 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:24:42 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:08 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:11 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:05 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:33 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:52 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:27:34 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:28:10 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:28:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:06 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:25 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:24 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:44 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:31:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:10 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:29 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:50 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:33:55 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:22 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:53 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:35:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:35:49 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:36:16 ERROR: Write: Failed to open file /home/david/.biblepaycore/peers.dat.add3
2018-01-04 13:36:18 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:36:23 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:37:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:38:25 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:38:32 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:00 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:26 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:58 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:41:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:41:44 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:14 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/blk00000.dat
2018-01-04 13:42:14 ERROR: WriteBlockToDisk: OpenBlockFile failed
2018-01-04 13:42:14 *** Failed to write block
2018-01-04 13:42:14 Error: Error: A fatal internal error occurred, see debug.log for details
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/blk00000.dat
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/rev00000.dat
2018-01-04 13:42:14 tor: Thread interrupt
2018-01-04 13:42:14 torcontrol thread exit
2018-01-04 13:42:14 opencon thread interrupt
2018-01-04 13:42:14 addcon thread interrupt
2018-01-04 13:42:14 mnbcon thread interrupt
2018-01-04 13:42:14 scheduler thread interrupt
2018-01-04 13:42:14 net thread interrupt
2018-01-04 13:42:16 ProcessNewBlock : ACCEPTED
2018-01-04 13:42:16 msghand thread interrupt
2018-01-04 13:42:16 PrepareShutdown: In progress...
2018-01-04 13:42:16 StopNode()
2018-01-04 13:42:16
BiblepayMiner -- terminated
2018-01-04 13:42:16 Verifying mncache.dat format...
2018-01-04 13:42:16 Loaded info from mncache.dat 6ms
2018-01-04 13:42:16 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 2149
2018-01-04 13:42:16 Writting info to mncache.dat...
2018-01-04 13:42:16 Written info to mncache.dat 6ms
2018-01-04 13:42:16 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 2856
2018-01-04 13:42:16 mncache.dat dump finished 12ms
2018-01-04 13:42:16 Verifying mnpayments.dat format...
2018-01-04 13:42:16 Loaded info from mnpayments.dat 135ms
2018-01-04 13:42:16 Votes: 24615, Blocks: 2564
2018-01-04 13:42:16 Writting info to mnpayments.dat...
2018-01-04 13:42:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:16 Written info to mnpayments.dat 121ms
2018-01-04 13:42:16 Votes: 25214, Blocks: 2624
2018-01-04 13:42:16 mnpayments.dat dump finished 259ms
2018-01-04 13:42:16 Verifying governance.dat format...
2018-01-04 13:42:16 Loaded info from governance.dat 16ms
2018-01-04 13:42:16 Governance Objects: 22 (Proposals: 19, Triggers: 2, Watchdogs: 1/1, Other: 0; Seen: 24), Votes: 0
2018-01-04 13:42:16 Writting info to governance.dat...
2018-01-04 13:42:16 Written info to governance.dat 5ms
2018-01-04 13:42:16 Governance Objects: 22 (Proposals: 19, Triggers: 2, Watchdogs: 1/1, Other: 0; Seen: 26), Votes: 847
2018-01-04 13:42:16 governance.dat dump finished 21ms
2018-01-04 13:42:16 Verifying netfulfilled.dat format...
2018-01-04 13:42:16 Loaded info from netfulfilled.dat 0ms
2018-01-04 13:42:16 Nodes with fulfilled requests: 10
2018-01-04 13:42:16 Writting info to netfulfilled.dat...
2018-01-04 13:42:16 Written info to netfulfilled.dat 0ms
2018-01-04 13:42:16 Nodes with fulfilled requests: 9
2018-01-04 13:42:16 netfulfilled.dat dump finished 0ms
2018-01-04 13:42:16
BiblepayMiner -- terminated
2018-01-04 13:42:16 Shutdown: done
Hope this helps.
Code:
018-01-04 17:24:33 Unable to open file /root/.biblepaycore3/blocks/blk00000.dat
2018-01-04 17:24:33 ERROR: WriteBlockToDisk: OpenBlockFile failed
2018-01-04 17:24:33 *** Failed to write block
2018-01-04 17:24:33 Error: Error: A fatal internal error occurred, see debug.log for details
2018-01-04 17:24:33 ProcessNewBlock : ACCEPTED
2018-01-04 17:24:33 libevent: Error from accept() call: Too many open files
2018-01-04 17:24:33 libevent: Error from accept() call: Too many open files
2018-01-04 17:24:33 libevent: Error from accept() call: Too many open files
2018-01-04 17:24:33 scheduler thread interrupt
2018-01-04 17:24:33 opencon thread interrupt
2018-01-04 17:24:33 mnbcon thread interrupt
2018-01-04 17:24:33 msghand thread interrupt
2018-01-04 17:24:33 addcon thread interrupt
2018-01-04 17:24:33 net thread interrupt
2018-01-04 17:24:33 PrepareShutdown: In progress...
2018-01-04 17:24:33 StopNode()
2018-01-04 17:24:34 Verifying mncache.dat format...
2018-01-04 17:24:34 Loaded info from mncache.dat 0ms
2018-01-04 17:24:34 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2018-01-04 17:24:34 Writting info to mncache.dat...
2018-01-04 17:24:34 Written info to mncache.dat 4ms
2018-01-04 17:24:34 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 23119
2018-01-04 17:24:34 mncache.dat dump finished 4ms
2018-01-04 17:24:34 Verifying mnpayments.dat format...
2018-01-04 17:24:34 Loaded info from mnpayments.dat 0ms
2018-01-04 17:24:34 Votes: 0, Blocks: 0
2018-01-04 17:24:34 Writting info to mnpayments.dat...
2018-01-04 17:24:34 Written info to mnpayments.dat 473ms
2018-01-04 17:24:34 Votes: 25442, Blocks: 2647
2018-01-04 17:24:34 mnpayments.dat dump finished 502ms
2018-01-04 17:24:34 Verifying governance.dat format...
2018-01-04 17:24:34 Loaded info from governance.dat 0ms
2018-01-04 17:24:34 Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2018-01-04 17:24:34 Writting info to governance.dat...
2018-01-04 17:24:34 Written info to governance.dat 3ms
2018-01-04 17:24:34 Governance Objects: 19 (Proposals: 17, Triggers: 1, Watchdogs: 1/1, Other: 0; Seen: 84), Votes: 831
2018-01-04 17:24:34 governance.dat dump finished 3ms
2018-01-04 17:24:34 Verifying netfulfilled.dat format...
2018-01-04 17:24:34 Loaded info from netfulfilled.dat 0ms
2018-01-04 17:24:34 Nodes with fulfilled requests: 0
2018-01-04 17:24:34 Writting info to netfulfilled.dat...
2018-01-04 17:24:34 Written info to netfulfilled.dat 0ms
2018-01-04 17:24:34 Nodes with fulfilled requests: 9
2018-01-04 17:24:34 netfulfilled.dat dump finished 0ms
2018-01-04 17:24:35 Shutdown: done
2018-01-04 17:24:33 ERROR: WriteBlockToDisk: OpenBlockFile failed
2018-01-04 17:24:33 *** Failed to write block
2018-01-04 17:24:33 Error: Error: A fatal internal error occurred, see debug.log for details
2018-01-04 17:24:33 ProcessNewBlock : ACCEPTED
2018-01-04 17:24:33 libevent: Error from accept() call: Too many open files
2018-01-04 17:24:33 libevent: Error from accept() call: Too many open files
2018-01-04 17:24:33 libevent: Error from accept() call: Too many open files
2018-01-04 17:24:33 scheduler thread interrupt
2018-01-04 17:24:33 opencon thread interrupt
2018-01-04 17:24:33 mnbcon thread interrupt
2018-01-04 17:24:33 msghand thread interrupt
2018-01-04 17:24:33 addcon thread interrupt
2018-01-04 17:24:33 net thread interrupt
2018-01-04 17:24:33 PrepareShutdown: In progress...
2018-01-04 17:24:33 StopNode()
2018-01-04 17:24:34 Verifying mncache.dat format...
2018-01-04 17:24:34 Loaded info from mncache.dat 0ms
2018-01-04 17:24:34 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2018-01-04 17:24:34 Writting info to mncache.dat...
2018-01-04 17:24:34 Written info to mncache.dat 4ms
2018-01-04 17:24:34 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 23119
2018-01-04 17:24:34 mncache.dat dump finished 4ms
2018-01-04 17:24:34 Verifying mnpayments.dat format...
2018-01-04 17:24:34 Loaded info from mnpayments.dat 0ms
2018-01-04 17:24:34 Votes: 0, Blocks: 0
2018-01-04 17:24:34 Writting info to mnpayments.dat...
2018-01-04 17:24:34 Written info to mnpayments.dat 473ms
2018-01-04 17:24:34 Votes: 25442, Blocks: 2647
2018-01-04 17:24:34 mnpayments.dat dump finished 502ms
2018-01-04 17:24:34 Verifying governance.dat format...
2018-01-04 17:24:34 Loaded info from governance.dat 0ms
2018-01-04 17:24:34 Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2018-01-04 17:24:34 Writting info to governance.dat...
2018-01-04 17:24:34 Written info to governance.dat 3ms
2018-01-04 17:24:34 Governance Objects: 19 (Proposals: 17, Triggers: 1, Watchdogs: 1/1, Other: 0; Seen: 84), Votes: 831
2018-01-04 17:24:34 governance.dat dump finished 3ms
2018-01-04 17:24:34 Verifying netfulfilled.dat format...
2018-01-04 17:24:34 Loaded info from netfulfilled.dat 0ms
2018-01-04 17:24:34 Nodes with fulfilled requests: 0
2018-01-04 17:24:34 Writting info to netfulfilled.dat...
2018-01-04 17:24:34 Written info to netfulfilled.dat 0ms
2018-01-04 17:24:34 Nodes with fulfilled requests: 9
2018-01-04 17:24:34 netfulfilled.dat dump finished 0ms
2018-01-04 17:24:35 Shutdown: done
I need to restart some of my miners once/twice per day (reindex fixes them)
The miners that are failing use HTTPS.
The few miners that are running using http seems to be not affected (I haven't needed to restart them, but they are also slower machines)
@Dave, are you using HTTPS or http?
Thanks a lot for the logs guys.
Huge question, the machine that is running over HTTP successfully without restarting, is it running 1075 also?
This way, I can isolate this down to the HTTPS feature.
Thanks!
Yes they run successfully with 1075 without a restart.
And there is one fast machine there also so I yes the problems look to be at the https feature.
Edit:
Before crashing the log is spammed with:
socket error accept failed: Too many open files (24)
10-100 per second.
Hello
I would like to ask you something about mining. For couple hours i've mined 0 bbp... What could be wrong? I am mining via https ...
Thanks for advices
I would like to ask you something about mining. For couple hours i've mined 0 bbp... What could be wrong? I am mining via https ...
Thanks for advices
Are you mining via the pool?
We seem to not hit any blocks last couple of hours.
In general we mine about 20-25% of all blocks with the pool.
So it could be that we hit no blocks for 3 hours and then 3 hours a lot of blocks.
Hi Dave,
Its just not true that we only care about precious masternodes.
Here is the way I view the priorities right now just so you know: I want to ensure we are ready for block 24600, so we can pay our orphans.
Next, I want to maintain production support levels. That includes any critical errors with 1075. And finally, I place a very low priority level personally on any "hash speed discussions". So maybe thats the point of contention. We only have enough resources to talk about the prod support and the critical errors and not about peoples mining speed, unless its an inconsistency in the pool that affects everyone.
Of course we have time to talk about how competetive mining works.
But first:
So, Im not aware of a critical bug in 1075, and have not received a log. Can someone please give us a log so we can see what stopped the node in 1075??
There is no way to even look at a problem without a log.
Thank you for your explanations (also in your other posts about the competitive mining. Indeed that makes sense. I have copied the last lines from the debug.log, where the error occurs (wasn't really sure where to start...):
Code:
2018-01-04 13:15:15 Resetting mining tithe 259.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:15:28 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:15:39 Resetting mining tithe 260.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:15:52 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:16:41 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:17:37 Resetting mining tithe 261.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:00 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:18 Resetting mining tithe 262.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:58 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:48 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:48 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:51 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:56 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:08 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:12 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:27 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:32 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:57 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:21:17 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:21:45 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:23 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:38 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:23:46 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:24:42 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:08 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:11 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:05 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:33 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:52 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:27:34 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:28:10 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:28:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:06 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:25 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:24 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:44 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:31:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:10 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:29 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:50 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:33:55 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:22 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:53 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:35:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:35:49 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:36:16 ERROR: Write: Failed to open file /home/david/.biblepaycore/peers.dat.add3
2018-01-04 13:36:18 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:36:23 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:37:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:38:25 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:38:32 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:00 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:26 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:58 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:41:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:41:44 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:14 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/blk00000.dat
2018-01-04 13:42:14 ERROR: WriteBlockToDisk: OpenBlockFile failed
2018-01-04 13:42:14 *** Failed to write block
2018-01-04 13:42:14 Error: Error: A fatal internal error occurred, see debug.log for details
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/blk00000.dat
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/rev00000.dat
2018-01-04 13:42:14 tor: Thread interrupt
2018-01-04 13:42:14 torcontrol thread exit
2018-01-04 13:42:14 opencon thread interrupt
2018-01-04 13:42:14 addcon thread interrupt
2018-01-04 13:42:14 mnbcon thread interrupt
2018-01-04 13:42:14 scheduler thread interrupt
2018-01-04 13:42:14 net thread interrupt
2018-01-04 13:42:16 ProcessNewBlock : ACCEPTED
2018-01-04 13:42:16 msghand thread interrupt
2018-01-04 13:42:16 PrepareShutdown: In progress...
2018-01-04 13:42:16 StopNode()
2018-01-04 13:42:16
BiblepayMiner -- terminated
2018-01-04 13:42:16 Verifying mncache.dat format...
2018-01-04 13:42:16 Loaded info from mncache.dat 6ms
2018-01-04 13:42:16 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 2149
2018-01-04 13:42:16 Writting info to mncache.dat...
2018-01-04 13:42:16 Written info to mncache.dat 6ms
2018-01-04 13:42:16 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 2856
2018-01-04 13:42:16 mncache.dat dump finished 12ms
2018-01-04 13:42:16 Verifying mnpayments.dat format...
2018-01-04 13:42:16 Loaded info from mnpayments.dat 135ms
2018-01-04 13:42:16 Votes: 24615, Blocks: 2564
2018-01-04 13:42:16 Writting info to mnpayments.dat...
2018-01-04 13:42:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:16 Written info to mnpayments.dat 121ms
2018-01-04 13:42:16 Votes: 25214, Blocks: 2624
2018-01-04 13:42:16 mnpayments.dat dump finished 259ms
2018-01-04 13:42:16 Verifying governance.dat format...
2018-01-04 13:42:16 Loaded info from governance.dat 16ms
2018-01-04 13:42:16 Governance Objects: 22 (Proposals: 19, Triggers: 2, Watchdogs: 1/1, Other: 0; Seen: 24), Votes: 0
2018-01-04 13:42:16 Writting info to governance.dat...
2018-01-04 13:42:16 Written info to governance.dat 5ms
2018-01-04 13:42:16 Governance Objects: 22 (Proposals: 19, Triggers: 2, Watchdogs: 1/1, Other: 0; Seen: 26), Votes: 847
2018-01-04 13:42:16 governance.dat dump finished 21ms
2018-01-04 13:42:16 Verifying netfulfilled.dat format...
2018-01-04 13:42:16 Loaded info from netfulfilled.dat 0ms
2018-01-04 13:42:16 Nodes with fulfilled requests: 10
2018-01-04 13:42:16 Writting info to netfulfilled.dat...
2018-01-04 13:42:16 Written info to netfulfilled.dat 0ms
2018-01-04 13:42:16 Nodes with fulfilled requests: 9
2018-01-04 13:42:16 netfulfilled.dat dump finished 0ms
2018-01-04 13:42:16
BiblepayMiner -- terminated
2018-01-04 13:42:16 Shutdown: done
2018-01-04 13:15:28 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:15:39 Resetting mining tithe 260.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:15:52 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:16:41 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:17:37 Resetting mining tithe 261.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:00 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:18 Resetting mining tithe 262.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:58 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:48 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:48 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:51 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:56 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:08 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:12 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:27 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:32 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:57 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:21:17 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:21:45 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:23 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:38 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:23:46 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:24:42 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:08 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:11 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:05 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:33 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:52 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:27:34 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:28:10 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:28:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:06 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:25 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:24 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:44 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:31:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:10 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:29 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:50 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:33:55 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:22 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:53 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:35:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:35:49 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:36:16 ERROR: Write: Failed to open file /home/david/.biblepaycore/peers.dat.add3
2018-01-04 13:36:18 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:36:23 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:37:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:38:25 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:38:32 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:00 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:26 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:58 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:41:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:41:44 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:14 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/blk00000.dat
2018-01-04 13:42:14 ERROR: WriteBlockToDisk: OpenBlockFile failed
2018-01-04 13:42:14 *** Failed to write block
2018-01-04 13:42:14 Error: Error: A fatal internal error occurred, see debug.log for details
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/blk00000.dat
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/rev00000.dat
2018-01-04 13:42:14 tor: Thread interrupt
2018-01-04 13:42:14 torcontrol thread exit
2018-01-04 13:42:14 opencon thread interrupt
2018-01-04 13:42:14 addcon thread interrupt
2018-01-04 13:42:14 mnbcon thread interrupt
2018-01-04 13:42:14 scheduler thread interrupt
2018-01-04 13:42:14 net thread interrupt
2018-01-04 13:42:16 ProcessNewBlock : ACCEPTED
2018-01-04 13:42:16 msghand thread interrupt
2018-01-04 13:42:16 PrepareShutdown: In progress...
2018-01-04 13:42:16 StopNode()
2018-01-04 13:42:16
BiblepayMiner -- terminated
2018-01-04 13:42:16 Verifying mncache.dat format...
2018-01-04 13:42:16 Loaded info from mncache.dat 6ms
2018-01-04 13:42:16 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 2149
2018-01-04 13:42:16 Writting info to mncache.dat...
2018-01-04 13:42:16 Written info to mncache.dat 6ms
2018-01-04 13:42:16 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 2856
2018-01-04 13:42:16 mncache.dat dump finished 12ms
2018-01-04 13:42:16 Verifying mnpayments.dat format...
2018-01-04 13:42:16 Loaded info from mnpayments.dat 135ms
2018-01-04 13:42:16 Votes: 24615, Blocks: 2564
2018-01-04 13:42:16 Writting info to mnpayments.dat...
2018-01-04 13:42:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:16 Written info to mnpayments.dat 121ms
2018-01-04 13:42:16 Votes: 25214, Blocks: 2624
2018-01-04 13:42:16 mnpayments.dat dump finished 259ms
2018-01-04 13:42:16 Verifying governance.dat format...
2018-01-04 13:42:16 Loaded info from governance.dat 16ms
2018-01-04 13:42:16 Governance Objects: 22 (Proposals: 19, Triggers: 2, Watchdogs: 1/1, Other: 0; Seen: 24), Votes: 0
2018-01-04 13:42:16 Writting info to governance.dat...
2018-01-04 13:42:16 Written info to governance.dat 5ms
2018-01-04 13:42:16 Governance Objects: 22 (Proposals: 19, Triggers: 2, Watchdogs: 1/1, Other: 0; Seen: 26), Votes: 847
2018-01-04 13:42:16 governance.dat dump finished 21ms
2018-01-04 13:42:16 Verifying netfulfilled.dat format...
2018-01-04 13:42:16 Loaded info from netfulfilled.dat 0ms
2018-01-04 13:42:16 Nodes with fulfilled requests: 10
2018-01-04 13:42:16 Writting info to netfulfilled.dat...
2018-01-04 13:42:16 Written info to netfulfilled.dat 0ms
2018-01-04 13:42:16 Nodes with fulfilled requests: 9
2018-01-04 13:42:16 netfulfilled.dat dump finished 0ms
2018-01-04 13:42:16
BiblepayMiner -- terminated
2018-01-04 13:42:16 Shutdown: done
Hope this helps.
Code:
018-01-04 17:24:33 Unable to open file /root/.biblepaycore3/blocks/blk00000.dat
2018-01-04 17:24:33 ERROR: WriteBlockToDisk: OpenBlockFile failed
2018-01-04 17:24:33 *** Failed to write block
2018-01-04 17:24:33 Error: Error: A fatal internal error occurred, see debug.log for details
2018-01-04 17:24:33 ProcessNewBlock : ACCEPTED
2018-01-04 17:24:33 libevent: Error from accept() call: Too many open files
2018-01-04 17:24:33 libevent: Error from accept() call: Too many open files
2018-01-04 17:24:33 libevent: Error from accept() call: Too many open files
2018-01-04 17:24:33 scheduler thread interrupt
2018-01-04 17:24:33 opencon thread interrupt
2018-01-04 17:24:33 mnbcon thread interrupt
2018-01-04 17:24:33 msghand thread interrupt
2018-01-04 17:24:33 addcon thread interrupt
2018-01-04 17:24:33 net thread interrupt
2018-01-04 17:24:33 PrepareShutdown: In progress...
2018-01-04 17:24:33 StopNode()
2018-01-04 17:24:34 Verifying mncache.dat format...
2018-01-04 17:24:34 Loaded info from mncache.dat 0ms
2018-01-04 17:24:34 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2018-01-04 17:24:34 Writting info to mncache.dat...
2018-01-04 17:24:34 Written info to mncache.dat 4ms
2018-01-04 17:24:34 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 23119
2018-01-04 17:24:34 mncache.dat dump finished 4ms
2018-01-04 17:24:34 Verifying mnpayments.dat format...
2018-01-04 17:24:34 Loaded info from mnpayments.dat 0ms
2018-01-04 17:24:34 Votes: 0, Blocks: 0
2018-01-04 17:24:34 Writting info to mnpayments.dat...
2018-01-04 17:24:34 Written info to mnpayments.dat 473ms
2018-01-04 17:24:34 Votes: 25442, Blocks: 2647
2018-01-04 17:24:34 mnpayments.dat dump finished 502ms
2018-01-04 17:24:34 Verifying governance.dat format...
2018-01-04 17:24:34 Loaded info from governance.dat 0ms
2018-01-04 17:24:34 Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2018-01-04 17:24:34 Writting info to governance.dat...
2018-01-04 17:24:34 Written info to governance.dat 3ms
2018-01-04 17:24:34 Governance Objects: 19 (Proposals: 17, Triggers: 1, Watchdogs: 1/1, Other: 0; Seen: 84), Votes: 831
2018-01-04 17:24:34 governance.dat dump finished 3ms
2018-01-04 17:24:34 Verifying netfulfilled.dat format...
2018-01-04 17:24:34 Loaded info from netfulfilled.dat 0ms
2018-01-04 17:24:34 Nodes with fulfilled requests: 0
2018-01-04 17:24:34 Writting info to netfulfilled.dat...
2018-01-04 17:24:34 Written info to netfulfilled.dat 0ms
2018-01-04 17:24:34 Nodes with fulfilled requests: 9
2018-01-04 17:24:34 netfulfilled.dat dump finished 0ms
2018-01-04 17:24:35 Shutdown: done
2018-01-04 17:24:33 ERROR: WriteBlockToDisk: OpenBlockFile failed
2018-01-04 17:24:33 *** Failed to write block
2018-01-04 17:24:33 Error: Error: A fatal internal error occurred, see debug.log for details
2018-01-04 17:24:33 ProcessNewBlock : ACCEPTED
2018-01-04 17:24:33 libevent: Error from accept() call: Too many open files
2018-01-04 17:24:33 libevent: Error from accept() call: Too many open files
2018-01-04 17:24:33 libevent: Error from accept() call: Too many open files
2018-01-04 17:24:33 scheduler thread interrupt
2018-01-04 17:24:33 opencon thread interrupt
2018-01-04 17:24:33 mnbcon thread interrupt
2018-01-04 17:24:33 msghand thread interrupt
2018-01-04 17:24:33 addcon thread interrupt
2018-01-04 17:24:33 net thread interrupt
2018-01-04 17:24:33 PrepareShutdown: In progress...
2018-01-04 17:24:33 StopNode()
2018-01-04 17:24:34 Verifying mncache.dat format...
2018-01-04 17:24:34 Loaded info from mncache.dat 0ms
2018-01-04 17:24:34 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2018-01-04 17:24:34 Writting info to mncache.dat...
2018-01-04 17:24:34 Written info to mncache.dat 4ms
2018-01-04 17:24:34 Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 23119
2018-01-04 17:24:34 mncache.dat dump finished 4ms
2018-01-04 17:24:34 Verifying mnpayments.dat format...
2018-01-04 17:24:34 Loaded info from mnpayments.dat 0ms
2018-01-04 17:24:34 Votes: 0, Blocks: 0
2018-01-04 17:24:34 Writting info to mnpayments.dat...
2018-01-04 17:24:34 Written info to mnpayments.dat 473ms
2018-01-04 17:24:34 Votes: 25442, Blocks: 2647
2018-01-04 17:24:34 mnpayments.dat dump finished 502ms
2018-01-04 17:24:34 Verifying governance.dat format...
2018-01-04 17:24:34 Loaded info from governance.dat 0ms
2018-01-04 17:24:34 Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2018-01-04 17:24:34 Writting info to governance.dat...
2018-01-04 17:24:34 Written info to governance.dat 3ms
2018-01-04 17:24:34 Governance Objects: 19 (Proposals: 17, Triggers: 1, Watchdogs: 1/1, Other: 0; Seen: 84), Votes: 831
2018-01-04 17:24:34 governance.dat dump finished 3ms
2018-01-04 17:24:34 Verifying netfulfilled.dat format...
2018-01-04 17:24:34 Loaded info from netfulfilled.dat 0ms
2018-01-04 17:24:34 Nodes with fulfilled requests: 0
2018-01-04 17:24:34 Writting info to netfulfilled.dat...
2018-01-04 17:24:34 Written info to netfulfilled.dat 0ms
2018-01-04 17:24:34 Nodes with fulfilled requests: 9
2018-01-04 17:24:34 netfulfilled.dat dump finished 0ms
2018-01-04 17:24:35 Shutdown: done
I need to restart some of my miners once/twice per day (reindex fixes them)
The miners that are failing use HTTPS.
The few miners that are running using http seems to be not affected (I haven't needed to restart them, but they are also slower machines)
@Dave, are you using HTTPS or http?
BiblePay - 1.0.7.5
Leisure Upgrade
- Competetive mining feature:
The idea behind competetive mining, is for those with fast processors who mine so fast that they run out of nonces,
this feature automatically adds a tithe for the orphan foundation for a miniscule amount (IE 1 satoshi or .000001 bbp)
IF you run out of mining nonces, and only increments to 2 satoshi again if you run out. However, when the block changes,
the amount is reset to 0 again. Alex and I have tested this and it appears to give a 5% mining edge. Therefore I wanted
to release this as quickly as possible for general consumption. Since it gives a mining edge, I made the feature ON by default.
To turn it off add the key: competetivemining=false to your biblepay.conf file.
- Pool SSL Support (change pool=http:// to pool=https:// and remove poolport=80 in biblepay.conf file to use SSL).
Leisure Upgrade
- Competetive mining feature:
The idea behind competetive mining, is for those with fast processors who mine so fast that they run out of nonces,
this feature automatically adds a tithe for the orphan foundation for a miniscule amount (IE 1 satoshi or .000001 bbp)
IF you run out of mining nonces, and only increments to 2 satoshi again if you run out. However, when the block changes,
the amount is reset to 0 again. Alex and I have tested this and it appears to give a 5% mining edge. Therefore I wanted
to release this as quickly as possible for general consumption. Since it gives a mining edge, I made the feature ON by default.
To turn it off add the key: competetivemining=false to your biblepay.conf file.
- Pool SSL Support (change pool=http:// to pool=https:// and remove poolport=80 in biblepay.conf file to use SSL).
Is it have a problem?I found some upgraded PC can't running bbp process , but old version still running normal....
I tried to reboot or change dns, and changed back to port80 but it seem not work..
quote:
# Error: Error: A fatal internal error occurred, see debug.log for details
Error: Failed to connect best block
I just got the same error. I am reindexing now...
EDIT: Re-indexing seemed to work
1.0.7.5 version seem have problem.
It is the second times occurred , I am re-indexing again.
I worry it will happen again....
Yes, well let's see how it goes over the next 24 hours. See if anyone else has these issues
I have the same problems...
But not on all of the miners, only on a few.
edit: all others are starting to fail now also...
BiblePay - 1.0.7.5
Leisure Upgrade
- Competetive mining feature:
The idea behind competetive mining, is for those with fast processors who mine so fast that they run out of nonces,
this feature automatically adds a tithe for the orphan foundation for a miniscule amount (IE 1 satoshi or .000001 bbp)
IF you run out of mining nonces, and only increments to 2 satoshi again if you run out. However, when the block changes,
the amount is reset to 0 again. Alex and I have tested this and it appears to give a 5% mining edge. Therefore I wanted
to release this as quickly as possible for general consumption. Since it gives a mining edge, I made the feature ON by default.
To turn it off add the key: competetivemining=false to your biblepay.conf file.
- Pool SSL Support (change pool=http:// to pool=https:// and remove poolport=80 in biblepay.conf file to use SSL).
Leisure Upgrade
- Competetive mining feature:
The idea behind competetive mining, is for those with fast processors who mine so fast that they run out of nonces,
this feature automatically adds a tithe for the orphan foundation for a miniscule amount (IE 1 satoshi or .000001 bbp)
IF you run out of mining nonces, and only increments to 2 satoshi again if you run out. However, when the block changes,
the amount is reset to 0 again. Alex and I have tested this and it appears to give a 5% mining edge. Therefore I wanted
to release this as quickly as possible for general consumption. Since it gives a mining edge, I made the feature ON by default.
To turn it off add the key: competetivemining=false to your biblepay.conf file.
- Pool SSL Support (change pool=http:// to pool=https:// and remove poolport=80 in biblepay.conf file to use SSL).
Do we have to change the conf file? Or is it just an option?
it's an option, but I would change it if I where you
So for the realists out there:
20% for our budgets from each block - and 100% of our charity goes to orphans with no overhead
Of the remaining 80%: 50% to miner, 50% to sanctuary if Solo mining
If pool mining: 50% to sanctuary, ~45% to miner over the long term <- this is more realistic, temporarily 50/33 for a couple days
If pool mining @ minersofmen: 50%, 50% (If minersofmen is up?)
And I catch your drift, if you want to work with Gross numbers:
Out of a 14000 BBP block, a miner receives 40% of the block NET counting all possible deductions (budget,pool fees,sanctuary share everything), and today-tempoarily receives 33% of the block counting high pool fees (as of today). Count on that 33% rising over the next 40 days back up to 39% of the block.
[/quote]
Thanks Rob,
Not that I think it's unfair, but it's better to give good amounts of all fees and rewards.
Everywhere u read different value's. Just make one place where u update all information so it's clear for everyone.
Besides that... I think 50% for a masternode is already high. From start it was 10% masternode 80% miner.
If u lower more from the miners they might leave ofcourse.
The pool is good, but with higher fees people just might make a own pool or mine solo. I think that's what we see now.
In the reports from last night I've seen our pool missed even 20 blocks in a row (like 3,3 hour) so someone else got those blocks.
[/quote]
Indeed, 50% feels like a lot but it't only for the lucky mn right, not devided over MN like a pool?
Especially since you can also run a miner on the same machine so there is no need to have a dedicated server.
We have 58 MN.
Every 10(?) minutes a block is mined.
So 144 blocks per day spread over 58 mn: would mean that each MN would get 2 blocks at leasts per day.
Which is 11.000 coins.
which is a lot more then a miner would get even with a lot of servers and has power running....
Or do I misunderstood something?
I understand the pool fee and it's fine for now but it also scares people away and they go mine solo which effectively makes the pool less performing and the payout to pool members is lower.
Which in turn can lead more people into mine solo...
But we get more and more miners on the pool and apparently more solo miners which means the coin is getting better known.
So even with 9 minute block spacing, we should try to figure out if more people are solo mining. The pool is only solving about 22% of the blocks now, vs 45% last week.
So I took a look at the last 20 blocks, and the pools ratio being reported is correct. (Pool solved 5 out of 20). Leading me to believe we have more solo miners.
Alex, can you help us out? Can you verify out of the last 1000 blocks minersformen only solved one?
Im finding it hard to believe solo mining is increasing while our pool miner count is also increasing (now above 2000 miners).
So I took a look at the last 20 blocks, and the pools ratio being reported is correct. (Pool solved 5 out of 20). Leading me to believe we have more solo miners.
Alex, can you help us out? Can you verify out of the last 1000 blocks minersformen only solved one?
Im finding it hard to believe solo mining is increasing while our pool miner count is also increasing (now above 2000 miners).
Me too.
It now looks like we havent found a Block in couple of hours?
Last Height Mined: 23534 (12/30/2017 9:29:25 PM)
(Itsnow around 1 am Right? Not sure because of the Time zone differences.. here ut is 8 am🙂)
Looking at the number if miners and Power we should have found More... Lots More
Can't believe there are a lot of People solo minung.
I have the same problems, it looks like mined not even half of the amount 2 days ago.
Hello,
Indeed that's what I also see.
Looking at the number we have more miners, and it looks like even more power then before.
I had a tab open with the leaderboard of 28 december:
(forgot to close it..)
https://imgur.com/a/mtwWh
And the leaderboard now:
https://imgur.com/a/Cnxqi
So there are more miners and also bigger once.
But we don't really hit any blocks:
Blocks Mined (24 hour period): 43 (21%)
Coins Mined (24 hour period): 233915.32
coins mindes use to be around 500000, so around double.
Avg Time to Solve Block (Over 7 day period): 16
Avg Time to Solve Block (Over 24 hour period): 33
I don't think the difficulty is going up that much?
But correct me if I am wrong
What I see is that the coins mind per hour is very fluctating, sometimes 150 sometimes 300/600.
(probably because of the block hits per hour..)
Efficiency looks quite bad, it was like 100%+
Can someone with more insights explain why it's half of what it was before.
Kind regards,
Wow, got a message from a dentist that wants to accept biblepay. At least one positive thing happened today! Alright.
behind every cloud the sun is shining.