Author

Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 456. (Read 243386 times)

newbie
Activity: 491
Merit: 0
but wallet on ccex is down... so if it stays offline then all bbp stays there for 3 months...
jr. member
Activity: 490
Merit: 4
almost 10mil dumped on c-cex  Huh



look at the price action

did somebody call it quits with bbp ?

Looks like it.. and/or trying to cash out while they can.

Could be monthly superblock sale as well?  dunno for sure.
full member
Activity: 221
Merit: 100
almost 10mil dumped on c-cex  Huh



look at the price action

did somebody call it quits with bbp ?
full member
Activity: 221
Merit: 100
Code:
2018-05-30 02:02:50 Error reading mncache.dat: Load: File format is unknown or invalid, please fix it manually
2018-05-30 02:02:50 Error: Failed to load masternode cache from mncache.dat
Error: Failed to load masternode cache from mncache.dat
2018-05-30 02:02:50 scheduler thread interrupt
2018-05-30 02:02:50 PrepareShutdown: In progress...
2018-05-30 02:02:50 StopNode()
2018-05-30 02:02:50 Verifying mncache.dat format...
2018-05-30 02:02:50 ERROR: Read: Deserialize or I/O error - CAutoFile::read: end of file: iostream error
2018-05-30 02:02:50 Error reading mncache.dat: Dump: File format is unknown or invalid, please fix it manually
2018-05-30 02:02:50 Verifying mnpayments.dat format...
2018-05-30 02:02:50 ERROR: Read: Deserialize or I/O error - CAutoFile::read: end of file: iostream error
2018-05-30 02:02:50 Error reading mnpayments.dat: Dump: File format is unknown or invalid, please fix it manually
2018-05-30 02:02:50 Verifying governance.dat format...
2018-05-30 02:02:50 ERROR: Read: Deserialize or I/O error - CAutoFile::read: end of file: iostream error
2018-05-30 02:02:50 Error reading governance.dat: Dump: File format is unknown or invalid, please fix it manually
2018-05-30 02:02:50 Verifying netfulfilled.dat format...
2018-05-30 02:02:50 ERROR: Read: Deserialize or I/O error - CAutoFile::read: end of file: iostream error
2018-05-30 02:02:50 Error reading netfulfilled.dat: Dump: File format is unknown or invalid, please fix it manually
2018-05-30 02:02:51 Shutdown: done

giving up trying to keep the sancs up...
full member
Activity: 1176
Merit: 111
Anyway, I was just going to remark that this is the first time that I've had an orphaned PODC Update transaction.
EDIT: Ah, and that orphaned transaction has made 90,066 BBP 'disappear' from my wallet.  Hrmph. :-(

I hope that can be remedied and re-sent. Good reminder not to send any transactions to other addresses until the blockchain issues, orphans, forks, etc settle down by tomorrow?
full member
Activity: 1176
Merit: 111
I just remember these type of discussion from previous months. So restart fallen miners and wait for block 49405 Smiley

As said by others, there are other problems, too. Some of my system still produce huge debug.logs, I needed to deactivate it to make the system stable again. My Windows Wallet is crashing over and over. At least on my systems, it is much worse then last time.


Yeah, two of my sancs ran out of space due to out-of-control debug.log files. I couldn't even have the shell autocomplete a command. And that was in, what, 12 hours? Something to add to my list - a script to force a max size on the debug.log file.

I thin in Linux, you could manage based on an hourly cronjob I imagine.

https://unix.stackexchange.com/questions/299106/how-keep-last-50-lines-in-logfile
https://unix.stackexchange.com/questions/17209/how-to-limit-log-file-size-using
full member
Activity: 345
Merit: 100
If you rename or delete debug.log after the wallet is closed, and then start the wallet with the "-printtoconsole" parameter, that should prevent the log filling up issue that we all seem to be experiencing.  Those of you on Linux can use the logrotate command to regularly move the logs to keep it low, although I'm not sure if you can do it based on size with a trigger, but you might be able to configure logrotate to rotate the biblepay logs hourly.

Anyway, I was just going to remark that this is the first time that I've had an orphaned PODC Update transaction.
EDIT: Ah, and that orphaned transaction has made 90,776 BBP (number corrected) 'disappear' from my wallet.  Hrmph. :-(

Update:  The transaction is on the Explorer, but with no confirmations: http://explorer.biblepay.org:3001/tx/844bae64cf51506263946201746cc4a6ee3034f1b0b17759607f629ef21f73e7
jr. member
Activity: 235
Merit: 3
Argh. All my sancs crashed again, after filling up the disk with 20GB of debug.log in the space of an hour or two. After removing and restarting, they are hanging now on "activating best chain"

Yeah, I'll just try tomorrow myself, I think. I'm away from home anyway, so can't do the re-activation from the controller wallet until then anyway.
Nox, did you see my PM? Smiley

Yup -I had sent Togo a PM on that just an hour or two before you wrote me. I'll send everything out tomorrow night when I'm back at my home computer.
full member
Activity: 364
Merit: 102
Argh. All my sancs crashed again, after filling up the disk with 20GB of debug.log in the space of an hour or two. After removing and restarting, they are hanging now on "activating best chain"

Yeah, I'll just try tomorrow myself, I think. I'm away from home anyway, so can't do the re-activation from the controller wallet until then anyway.
Nox, did you see my PM? Smiley
jr. member
Activity: 235
Merit: 3
Argh. All my sancs crashed again, after filling up the disk with 20GB of debug.log in the space of an hour or two. After removing and restarting, they are hanging now on "activating best chain"

Yeah, I'll just try tomorrow myself, I think. I'm away from home anyway, so can't do the re-activation from the controller wallet until then anyway.
full member
Activity: 574
Merit: 104
I can't re-open my wallet after crashing but I guess it's that's life: as we say here, what the Lord gives you with one hand, it takes it away with the other lol

In debug.log

Code:
2018-05-29 21:42:38 GUI: Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

2018-05-29 21:42:38

************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_16bad_lexical_castEEEEE       
bad lexical cast: source type value could not be interpreted as target       
C:\Program Files\BiblepayCore\biblepay-qt.exe in Runaway exception       


And I can't restart the windows wallet even if I use -reindex, -rescan, etc.

I had the same error I think. My Sanc wallets have all gone haywire and I've given up for today Sad

MIP
newbie
Activity: 362
Merit: 0
I can't re-open my wallet after crashing but I guess it's that's life: as we say here, what the Lord gives you with one hand, it takes it away with the other lol

In debug.log

Code:
2018-05-29 21:42:38 GUI: Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

2018-05-29 21:42:38

************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_16bad_lexical_castEEEEE       
bad lexical cast: source type value could not be interpreted as target       
C:\Program Files\BiblepayCore\biblepay-qt.exe in Runaway exception       


And I can't restart the windows wallet even if I use -reindex, -rescan, etc.
jr. member
Activity: 235
Merit: 3
Great day to be MIP lol
Of the last 151 blocks:

top 5 winners:
CPID: 96892ec0fc8a2710fa84f26c9c84cd3e 48 Blocks
CPID: 6f10570756afd25e02ca7d0ca6bf1a44 18 Blocks
CPID: 684b644e09134455f34639d65bea3851 10 Blocks
CPID: fa5062d1c29baf2e298b674f40ee59b7 5 Blocks
CPID: 4928c2303e4e4ff44eb031b5a95403b3 4 Blocks

24 blocks to "unknown" / no CPID
lol, I'll never understand how this is possible. I remember last month when we had this issue there was one guy on the main pool who received almost every single block (alone) and he himself had no clue why. Cheesy
That was me! And this time, absolutely nothing, other than a bunch of crashed sancs Sad But hey, that's the way it goes, I guess?
jr. member
Activity: 405
Merit: 3
Great day to be MIP lol
Of the last 151 blocks:

top 5 winners:
CPID: 96892ec0fc8a2710fa84f26c9c84cd3e 48 Blocks
CPID: 6f10570756afd25e02ca7d0ca6bf1a44 18 Blocks
CPID: 684b644e09134455f34639d65bea3851 10 Blocks
CPID: fa5062d1c29baf2e298b674f40ee59b7 5 Blocks
CPID: 4928c2303e4e4ff44eb031b5a95403b3 4 Blocks

24 blocks to "unknown" / no CPID
lol, I'll never understand how this is possible. I remember last month when we had this issue there was one guy on the main pool who received almost every single block (alone) and he himself had no clue why. Cheesy
jr. member
Activity: 490
Merit: 4
Great day to be MIP lol
Of the last 151 blocks:

top 5 winners:
CPID: 96892ec0fc8a2710fa84f26c9c84cd3e 48 Blocks
CPID: 6f10570756afd25e02ca7d0ca6bf1a44 18 Blocks
CPID: 684b644e09134455f34639d65bea3851 10 Blocks
CPID: fa5062d1c29baf2e298b674f40ee59b7 5 Blocks
CPID: 4928c2303e4e4ff44eb031b5a95403b3 4 Blocks

24 blocks to "unknown" / no CPID
jr. member
Activity: 490
Merit: 4
We're experiencing rollbacks....

I've been tallying the "you got a block" alerts.. I had one for 49345, and 49348

my client is showing it JUST reached a height of 49345, again..

it seems like there are many mini-forks going on..
This could explain all the client crashes..
edit:
I get there were issues the last 2 months with this, but I don't recall this level of chaos happening.. is it more people, or is something different this time?
newbie
Activity: 39
Merit: 0
I just remember these type of discussion from previous months. So restart fallen miners and wait for block 49405 Smiley

As said by others, there are other problems, too. Some of my system still produce huge debug.logs, I needed to deactivate it to make the system stable again. My Windows Wallet is crashing over and over. At least on my systems, it is much worse then last time.



So that why I concerned , the monthly superblock must be separate from "normal superblock" to prevent it encounter errors.
jr. member
Activity: 235
Merit: 3
I just remember these type of discussion from previous months. So restart fallen miners and wait for block 49405 Smiley

As said by others, there are other problems, too. Some of my system still produce huge debug.logs, I needed to deactivate it to make the system stable again. My Windows Wallet is crashing over and over. At least on my systems, it is much worse then last time.


Yeah, two of my sancs ran out of space due to out-of-control debug.log files. I couldn't even have the shell autocomplete a command. And that was in, what, 12 hours? Something to add to my list - a script to force a max size on the debug.log file.
newbie
Activity: 164
Merit: 0
Any thoughts on C-CEX going on vacation, on the release of a mandatory upgrade next month? Does this mean C-CEX will be on an unacceptable version? Disallowing transactions on the exchange seems like a wise move in this context.

we are going to be in a mess, since many high rating Crypto android application relay only on CCEX to obtain BBP daily value.
jr. member
Activity: 219
Merit: 3
I just remember these type of discussion from previous months. So restart fallen miners and wait for block 49405 Smiley

As said by others, there are other problems, too. Some of my system still produce huge debug.logs, I needed to deactivate it to make the system stable again. My Windows Wallet is crashing over and over. At least on my systems, it is much worse then last time.

Jump to: