What config change do I need if I want to switch over to the testnet?
Start with -testnet or add testnet=1 to the biblepaytest.conf config file, and -conf=biblepaytest.conf.
Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 418. (Read 243386 times)
July 05, 2018, 06:47:16 PM
Start with -testnet or add testnet=1 to the biblepaytest.conf config file, and -conf=biblepaytest.conf.
July 05, 2018, 06:45:59 PM
A friend of mine wanted to start some POW (heat) mining because his RAC is already pretty high. He has Ubuntu 18 running and compiled from the 1.1.3.8 release. The compilation itself worked perfectly, but unfortunately the mining processes still suffer from this strange memory leak. It quite quickly went up to >500 MB per task, at which he stopped it.
Are there any of you who are running BBP on Ubuntu 18? Is the memory leak a known issue? Thanks for your efforts!
Are there any of you who are running BBP on Ubuntu 18? Is the memory leak a known issue? Thanks for your efforts!
When you say "per task" you mean per "setgenerate" thread?
We can give it a drive on a profiler and see who's to blame, but if it's happening on 18 and not in 16 or 17, it sounds like it could be some buggy external library packed in 18 that we are using.
Thanks for checking that out. Unfortunately I currently don't have any means to compile or test it under Ubuntu 18...
Edit: All right. So he had multiple wallets running and this was "per instance". BUT running only 1 instance, but with more threads (setgenerate true 16) had the same effect. He was pretty quickly at >4GB RAM usage.
He compiled from the old install_biblepay.sh script someone posted on reddit quite a while ago (but this should still be ok). The only thing he changed was some openssl library; he isn't sure, but he thinks it was "EVP_CIPHER_CTX".
Hope that helps.
They need to run biblepay with openssl 1.0.1k and not change the source code. Then the wallet takes up 291K of ram on both platforms (windows and linux).
July 05, 2018, 06:05:30 PM
What config change do I need if I want to switch over to the testnet?
July 05, 2018, 06:00:34 PM
When we are after mandatory update what is the situation with cryptobridge listing?
CryptoBridge was notified to move forward with our listing July 3rd,
Today, they asked for some coins to use, so I believe they have the wallet installed and are in testing
July 05, 2018, 01:38:43 PM
When we are after mandatory update what is the situation with cryptobridge listing?
July 05, 2018, 12:05:12 PM
A friend of mine wanted to start some POW (heat) mining because his RAC is already pretty high. He has Ubuntu 18 running and compiled from the 1.1.3.8 release. The compilation itself worked perfectly, but unfortunately the mining processes still suffer from this strange memory leak. It quite quickly went up to >500 MB per task, at which he stopped it.
Are there any of you who are running BBP on Ubuntu 18? Is the memory leak a known issue? Thanks for your efforts!
Are there any of you who are running BBP on Ubuntu 18? Is the memory leak a known issue? Thanks for your efforts!
When you say "per task" you mean per "setgenerate" thread?
We can give it a drive on a profiler and see who's to blame, but if it's happening on 18 and not in 16 or 17, it sounds like it could be some buggy external library packed in 18 that we are using.
Thanks for checking that out. Unfortunately I currently don't have any means to compile or test it under Ubuntu 18...
Edit: All right. So he had multiple wallets running and this was "per instance". BUT running only 1 instance, but with more threads (setgenerate true 16) had the same effect. He was pretty quickly at >4GB RAM usage.
He compiled from the old install_biblepay.sh script someone posted on reddit quite a while ago (but this should still be ok). The only thing he changed was some openssl library; he isn't sure, but he thinks it was "EVP_CIPHER_CTX".
Hope that helps.
July 05, 2018, 11:19:43 AM
A friend of mine wanted to start some POW (heat) mining because his RAC is already pretty high. He has Ubuntu 18 running and compiled from the 1.1.3.8 release. The compilation itself worked perfectly, but unfortunately the mining processes still suffer from this strange memory leak. It quite quickly went up to >500 MB per task, at which he stopped it.
Are there any of you who are running BBP on Ubuntu 18? Is the memory leak a known issue? Thanks for your efforts!
Are there any of you who are running BBP on Ubuntu 18? Is the memory leak a known issue? Thanks for your efforts!
When you say "per task" you mean per "setgenerate" thread?
We can give it a drive on a profiler and see who's to blame, but if it's happening on 18 and not in 16 or 17, it sounds like it could be some buggy external library packed in 18 that we are using.
July 05, 2018, 10:53:14 AM
A friend of mine wanted to start some POW (heat) mining because his RAC is already pretty high. He has Ubuntu 18 running and compiled from the 1.1.3.8 release. The compilation itself worked perfectly, but unfortunately the mining processes still suffer from this strange memory leak. It quite quickly went up to >500 MB per task, at which he stopped it.
Are there any of you who are running BBP on Ubuntu 18? Is the memory leak a known issue? Thanks for your efforts!
Are there any of you who are running BBP on Ubuntu 18? Is the memory leak a known issue? Thanks for your efforts!
July 04, 2018, 04:41:43 PM
Biblepay.org SSL cert has expired (as of today) great timing
expired july 3, 2018
need to renew with godaddy if they are using the same certificate provider.
someone should have gotten an e-mail warning about this weeks ago...?
I hope that it's just an expired certificate and not a coordinated attack on our new website, because I would feel WAY responsible.
Renewed for two more years; we switched hosts and SSL providers thats why the e-mail didn't come in.
We're using rapidssl now.
Thanks for the quick fix. You're working very hard on a USA holiday
July 04, 2018, 01:51:05 PM
Happens often, looks like they just restocked.
I just wish WCG could get their act together. Rosetta@Home is hit/miss with the Android tasks. Hopefully, they have a surplus. With Android mining, I'm between two difficult places with WCG GDPR and R@H with few tasks.
It seems R@H limits to 10k per batch release... Now that we are increasing the burden on them, i'm curious if they are struggling to keep up. Happened with the PC tasks early on as well.
July 04, 2018, 01:10:55 PM
Happens often, looks like they just restocked.
I just wish WCG could get their act together. Rosetta@Home is hit/miss with the Android tasks. Hopefully, they have a surplus. With Android mining, I'm between two difficult places with WCG GDPR and R@H with few tasks.
July 04, 2018, 01:09:15 PM
Thanks but masternode wallet will never restart, it is running 24/7. Any other command to disable debug.log message?
https://en.bitcoin.it/wiki/Running_Bitcoin
I haven't tried myself, but you could try printtoconsole so all output goes to console. If you're not logged in, it won't matter... and if you log in via a different session, it shouldn't show up in your console.
Or you could set up a separate cron job that deletes debug.log once an hour:
https://www.cyberciti.biz/faq/remove-log-files-in-linux-unix-bsd/
Good luck.
July 04, 2018, 12:46:31 PM
Ahh the irony, I had to laugh when this ad came up...
Haha! Google has humor.
PSA: I've set up an official alert service for when a mandatory wallet update gets released. You can sign up for it at:
https://www.biblepay.org/newsletter/
July 04, 2018, 12:24:32 PM
Ahh the irony, I had to laugh when this ad came up...
July 04, 2018, 08:58:03 AM
Argh! Stupid me. Forgot to delete the blocks folder! 
Everything fine!
Thank you.
Everything fine!
Thank you.
July 04, 2018, 08:43:04 AM
I did update to 1.1.3.8c but the wallet never starts. It's been sitting for more than two and a half hours at "Loading block index".
Id did the wallet cleanup process after I installed the latest.
Last line in debug.log is: 2018-07-04 10:58:09 LoadBlockIndexGuts 1530701889.000000 2018-07-04 12:37:26
Should I just revert to 1.1.3.7 for now?
The wallet seems to consume up to about 1,7GB of memory before going back down to about 1GB, and just going in circles with that.
Id did the wallet cleanup process after I installed the latest.
Last line in debug.log is: 2018-07-04 10:58:09 LoadBlockIndexGuts 1530701889.000000 2018-07-04 12:37:26
Should I just revert to 1.1.3.7 for now?
The wallet seems to consume up to about 1,7GB of memory before going back down to about 1GB, and just going in circles with that.
If you had it running during the superblock bug, then the index can be corrupted.
if you delete the chainstate and blocks folders in your data dir, let it re-build them. this will take care of it.
If it's your main wallet, make sure to re-start the client after it has synced so podcupdates work again.
July 04, 2018, 08:09:49 AM
I did update to 1.1.3.8c but the wallet never starts. It's been sitting for more than two and a half hours at "Loading block index".
Id did the wallet cleanup process after I installed the latest.
Last line in debug.log is: 2018-07-04 10:58:09 LoadBlockIndexGuts 1530701889.000000 2018-07-04 12:37:26
Should I just revert to 1.1.3.7 for now?
The wallet seems to consume up to about 1,7GB of memory before going back down to about 1GB, and just going in circles with that.
Id did the wallet cleanup process after I installed the latest.
Last line in debug.log is: 2018-07-04 10:58:09 LoadBlockIndexGuts 1530701889.000000 2018-07-04 12:37:26
Should I just revert to 1.1.3.7 for now?
The wallet seems to consume up to about 1,7GB of memory before going back down to about 1GB, and just going in circles with that.
July 04, 2018, 08:04:58 AM
look that this project is really quite awesome, from the details and concept of this platform is really cool to the team great job looking forward on your success this will be the most great system in digital world..
July 04, 2018, 07:53:08 AM
When will the Android client update?
July 04, 2018, 07:36:23 AM
I know CryptoBridge is waiting, so during the next release we will need to start using the Github releases feature also.
(This allows bots to see that we released a new mandatory upgrade).
(This allows bots to see that we released a new mandatory upgrade).
I see you did this for the latest release, which is great!
Do you think you could also add the .exe files in future releases? I think it's good for accessibility, if the website is inaccessible for any reason (like now), to not have a single point of failure.
So if you cover Windows, then what do you think about the idea to add Licht and/or MIP to the repo so they can supplement every release with Linux and Mac binaries?
https://github.com/biblepay/biblepay/releases/tag/1.1.3.8
Jump to: