Quote from: dave_bbp on March 17, 2019, 07:41:34 AM

Quote from: eyedoctrader1 on March 17, 2019, 02:53:17 AM

Hello fellow miners. I need some help getting my wallet to go into syncing mode. After the past week with all the changes to the wallet I discovered that I could not get my wallet to connect to the network. I heard about adding "minersleep=0" to biblepay.conf file which I added. I also increased my genproclimit up to the number of cores of my Xeon processor (4). I upgraded to wallet version 1.2.0.1. When I run the wallet it opens up showing it's behind by 9 days and then just sits there and says no block source available for hours. It never connects to the network to perform the final syncing. Also, I cannot run my masternode either while my wallet is in this non-operational state. Can anyone tell me what changes I need to make to either biblepay.conf file or deletions to files in the biblepaycore directory that will reinstate the syncing process?

Here's a copy of my current biblepay.conf file:

addnode=node.biblepay.org
addnode=biblepay.inspect.network
#tithe=1
gen=1
genproclimit=4
minersleep=0
poolport=80
pool=https://pool.biblepay.org
workerid=eyedoctrader7_3

Thanks in advance to anyone who can help me get back online!

If you are already on 1.2.0.1 wallets then it should be pretty simple to get you back on track.
Close your wallets and first of all remove the "poolport" line from the config, since this is wrong for connecting via https.

Then on Linux do the following:

Code:

cd ~/.biblepaycore
rm -rf banlist.dat blocks/ chainstate/ database/ *.log fee_estimates.dat governance.dat mncache.dat mnpayments.dat netfulfilled.dat SAN/ peers.dat .lock .cookie

(On Windows simply paste "%appdata%/biblepaycore" in the explorer and delete everything in there except for "backups", "wallet.dat" and both configs (bbp and mn).

Then restart the wallet and let it sync from scratch. As I've written yesterday, this should be pretty fast right now. Check if you are on the correct chain with

Code:

getblockhash 107525
c6622f1ea9417e463925207ff578f1f697ee1209651e3890b23e2d45dfdd7bb7

Good luck!

Dave, thanks for your help. I was finally able to get back online with those tweaks. It did, however, take almost 15 minutes for the program to connect to the blockchain and to start syncing. Initially I thought it was still broken. I found that setting the genproclimit to my number of cores (4) only consumed roughly 50% of my CPU usage so I upped the number to 7 and now it is remaining consistently around 90 to 95%. Is this the correct way to run the wallet and to make the setting? Thanks for your help again!