These could be intermittent issues as well, but if I knew the worker I could dig into it further
Hi, I reworked it, now it is grouped by worker, so you know which system might be the problem. But you can ignore very small percentages of CPID errors (like 1 error in 2000 solutions). They might simply be a problem in the answer of the biblepay client of the pool itself. Perfect! I don't know if the list has a limit, but the count went way down and it was 1 per machine basically, or the count is incorrect? a different one I looked at with only 1 worker went from 4 errors to 1 as well |
|
|
|
Hi leetlezee, I just added the new error view 2 hours ago, and it seems that it is already working  The error is based on a check of your CPID with with the biblepay client. It looks if it a known CPID and if it has a payment from Rosetta@home tasks in the last 24h. If not, an error is shown and the work/solution rejected (reason: The same rules as above are required to solve a block, and if you can't solve blocks, you wouldn't help the pool -> no payment  ). Could you send us the output of "exec getboincinfo" from the commandline (linux) or debug console (windows)? Nice feature, it would be helpful to show which worker generated the error as well I have seen both Illegal_CPID Invalid_CPID But all my clients appear to be functioning ok from what I can tell. and the cpid was in last nights superblock, and I currently have RAC. These could be intermittent issues as well, but if I knew the worker I could dig into it further thanks! EDIT: A more detailed description may be helpful as well if possible |
|
|
|
Awesome, what command do the linux guys type to pull down the launchpad binary for ubuntu for example?
once they add the PPA, it should be just sudo apt-get update
sudo apt-get upgrade
|
|
|
|
Installed Windows 64 wallet v1122, after running several hours it crashed.  Ive got a log from my machine and from MIPs, so Im good with examples now; regarding the actual root cause: It appears we are OK as a network to stay on 1.1.2.2 as we had a block in the chain that was not accepted by the supermajority and as they reorganized, the chain recovered, but there is a bug in our reorg code that *may* crash the node when it hits the "AcceptBlockHeader: prev block not found". I'm working on a patch for the future, but most likely we wont hit this crash again for weeks. In the mean time, anyone who crashed, just delete your blocks and chainstate and restart. That's good news, nice find! |
|
|
|
Anyone else getting "Runaway Exceptions" ? This was after the re-build index. "A fatal error occurred. Biblepay Core can no longer continue safely and will quit." Windows / 1.1.2.2 / 64-bit debuglog: 2018-04-20 11:03:32 UpdateTip: new best=000001790a3009771fac55c14e4adfb5e14a444014d1bd29c32f3af9c6218600 height=2972 log2_work=32.761858 tx=3550 date=2017-08-13 17:32:14 progress=0.022648 cache=0.5MiB(2147tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=00000218bba44361705e8ff92f24cdc90349700565c4bf1669644c5d20d3aa70 height=2973 log2_work=32.763139 tx=3551 date=2017-08-13 17:41:12 progress=0.022654 cache=0.5MiB(2148tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=00000096d09b68783f67ba96a993275e150546ff468e7513073e54aeb0cdd33a height=2974 log2_work=32.764177 tx=3553 date=2017-08-13 17:44:40 progress=0.022667 cache=0.5MiB(2145tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=000000797b79b0e1d408f6ad1fb253388b0fce2a88709c008e30b8fc44798949 height=2975 log2_work=32.765234 tx=3554 date=2017-08-13 17:45:18 progress=0.022673 cache=0.5MiB(2146tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=000000b945e8bb6cc9ae20fe0f06f09fe5431ca866be8b0224a84383c6243539 height=2976 log2_work=32.767639 tx=3555 date=2017-08-13 17:59:52 progress=0.022680 cache=0.5MiB(2147tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=000000ec9d190481026326e671ffcb2f585c43a0e47aeade6faa54c7f7f8a973 height=2977 log2_work=32.769762 tx=3556 date=2017-08-13 18:36:49 progress=0.022686 cache=0.5MiB(2148tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=000002f011d4bee9845c5e519344dc92f738b9ba5e177d236f48e6d37a425fc8 height=2978 log2_work=32.770581 tx=3557 date=2017-08-13 18:33:08 progress=0.022692 cache=0.5MiB(2149tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=00000347e7ce9ee399c0bdbbada6c3c98704a90dd040e833718f62a418a8845e height=2979 log2_work=32.771264 tx=3560 date=2017-08-13 18:37:50 progress=0.022712 cache=0.5MiB(2150tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=00000096aa8662b2646d1521341b40fa3da5c35a0b1f86ca3f4046744fde243a height=2980 log2_work=32.771996 tx=3561 date=2017-08-13 18:37:53 progress=0.022718 cache=0.5MiB(2151tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=00000102a979d60b1232a0728321ebce152a304672c71ac8fb7db4f62c945634 height=2981 log2_work=32.773692 tx=3563 date=2017-08-13 18:51:24 progress=0.022731 cache=0.5MiB(2152tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=0000006a51f0e1e0572bdfa5ebdb8566ea70f03c6795b2b6c2d18a1e74735f4a height=2982 log2_work=32.775154 tx=3564 date=2017-08-13 19:00:37 progress=0.022737 cache=0.5MiB(2153tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=000000a2d487204db3b41121960c00cd9ecc9c9e9dfc80fb650be0c282c00a1a height=2983 log2_work=32.776435 tx=3565 date=2017-08-13 19:01:44 progress=0.022743 cache=0.5MiB(2154tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=0000007e75777a48d9d87f4917e3f78edda220ceb5f70b56b494bc09646b7531 height=2984 log2_work=32.777829 tx=3566 date=2017-08-13 19:10:50 progress=0.022750 cache=0.5MiB(2155tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=000000625b650796cd96b35630282cce16dbb2f0e9f5b4d888adc932d97c0214 height=2985 log2_work=32.779889 tx=3567 date=2017-08-13 19:36:50 progress=0.022756 cache=0.5MiB(2156tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=0000028bcd0a90bb76316acd6ac1609df92b1dc0cad19d3da48e16c707127738 height=2986 log2_work=32.781111 tx=3568 date=2017-08-13 19:38:57 progress=0.022763 cache=0.5MiB(2157tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 UpdateTip: new best=000000eb316bde69093291f6e7b6980f4c05d39d9b057da6b6f556ecf9718940 height=2987 log2_work=32.782148 tx=3570 date=2017-08-13 19:48:33 progress=0.022775 cache=0.5MiB(2158tx)
2018-04-20 11:03:32 ProcessNewBlock : ACCEPTED
2018-04-20 11:03:32 socket select error The operation completed successfully. (0)
2018-04-20 11:03:32
************************
EXCEPTION: St8bad_cast
std::bad_cast
C:\Program Files\BiblepayCore\biblepay-qt.exe in ProcessMessages()
|
|
|
|
Strangely, after updating both of my sancs oh, 13 hours ago, I've run into a problem.
They both ran ok for quite a while, but now both have stopped getting new blocks and a getinfo call shows 41632 as the block index (my Windows, and other block explorers, show 41638).
Anybody else running into any problems? Masternode sync status is 999, nothing is throwing errors...I'm not sure what's going on.
I have 2 clients reporting "no block source available" edit: the addnode to the config fixed them.. wonder if some main node is down? |
|
|
|
|
Upgrading now..
There is an issue with the in-wallet alert.. A machine I already had the wallet open on doesn't report an upgrade requirement but any new opens it does.
Perhaps a periodic check routine is in order?
|
|
|
|
DONE! I added the narrative hint to that page.
Perhaps you can add a "Back Button", or option to vote from the detail view? I like the full view of the letter better, but its a bit of a pain to go back to the list to actually vote. either solution would be helpful. |
|
|
|
Could I have a favor please - we send out the orphan outbound letters in 3 days and there are a lot in the pool that are not upvoted - could we have 5-10 people please go into pool.biblepay.org and upvote some good letters?
Thanks!
Rob
PS I'll be borrowing the 250K for letter writing fees later today in order to implement phase 1 rewards for letter-writing.
EDIT: I'll make the list filtered by unsent to make this a little easier!
What are the requirements to upvote? If I click on an outbound letter it acts like I can edit, but I see no buttons. |
|
|
|
|
Is it just me or are the wallet download links missing from the main site?
|
|
|
|
|
I think there may be an issue...
Ran exec testvote earlier, and it came back an error "Invalid object type 0Governanceobject is not valid - "
Tried again a few mins ago, and it crashed the wallet.
wallet ver 1.1.1.9
|
|
|
|
|
I would like to see a calculator..
Enter RAC + WCG, enter stake value let it calculate what your payment % would be.
It seems my RAC keeps climbing despite my attempts to stabilize it.. my uxto is dropping and my payments are dropping further.
Also, RAC as seen on the biblepay pool doesn't match what the client says, and that doesn't match what I see in my control panel for the R@H page.
how is RAC determined for purposes of calculation?
|
|
|
|
The Individuals Share of RAC formula is: ModifiedRAC/TotalRAC * 1000 (Your Modified RAC = UTXO depressed RAC for RAH + WCG). Both of these columns above are exposed in the superblock view report in the pool. [/quote] Thanks, I appreciate it |
|
|
|
You just need to solve a few tasks and have magnitude > 0, and be in the superblock.
Then the error message will go away.
Basically, up until the patch was applied to the pool, CPIDS with no magnitude were not actually pulling any weight for the pool.
How is MAG determined? I seem to have 2.5, but the number is meaningless to me  |
|
|
|
|
Feature request:
Wallet MAX RAC ...
I would like a way to limit myself to the rac I can 100% stake, can we add this to the wallet? It's stressful watching my payment decline as my rac keeps climbing (and trying to adjust RAC accordingly)
Edit: perhaps this is bigger than I initially thought..
|
|
|
|
I see that, but what is the calc that determines payout from the available masterblock pool? |
|
|
|
|
will ask again.
Can we get the exact calc the contract is using to calculate payments?
had some bbp loaned to me to help with earning... RAC keeps climbing unfortunately so went to 90% then 80%
Losing a chunk of my earnings despite the climbing RAC .. It would be beneficial to know how the calculations work to try and avoid this.
|
|
|
|
|
I'm trying to find the DR stages/calcs... can we re-post them? Perhaps they should be added to the main post?
It would also be good to report out what the current DR status is..
Also, the full calc used by the sancs would be awesome ..
|
|
|
|
|
Has there been some slippage in the block times? looks like todays PODC block is 2hrs later than yesterdays
|
|
|
|
The Network hash exploded, too. Wow. And my pool now has 500 active miners. One week ago it had 100 miners. These numbers are looking a bit strange, I don't see such a huge grows in the forums or anywhere else. What might be the reason for this "silent" grows? I suspect people who cannot earn w/ PODC are trying to mine POBH to get started? |
|
|
|
|
Show Posts
