bible_pay is any problem with Ryzen CPUs? cos tested my Ryzen 1700 8cores/16threads and is worst like my HTPC 2cores/4threads ... thanks for help
Topic: BiblePay - New Coin Launch - Official Thread - page 75. (Read 119854 times)
amen
bible_pay is any problem with Ryzen CPUs? cos tested my Ryzen 1700 8cores/16threads and is worst like my HTPC 2cores/4threads ... thanks for help
bible_pay is any problem with Ryzen CPUs? cos tested my Ryzen 1700 8cores/16threads and is worst like my HTPC 2cores/4threads ... thanks for help
Hahaha, we have some comedians here.
Gave me a good chuckle.It is funny, but Please, please do not abuse the prayer feature.
Right now it is available for very serious prayers, what if someone has cancer or has a serious illness and needs us to pray?
They are not going to be very happy when its littered with trash. This is a serious instrument designed to get our community to pray for others who really need it.
And I think right now in the world with the instability its more of a necessity than ever to have it available and be responsible.
If people do abuse it we will have no choice but to put admin tools around it making it hard for anyone to just send a valid prayer in.
Thanks.
Can i get a guide on "how to install BiblePay-qt on Linux/Ubuntu VPS?
remove "blocks", "chainstate" directory, then remove "banlist.dat" file
add to biblepay.conf these lines:
and then start biblepay
add to biblepay.conf these lines:
Code:
addnode=137.74.0.113
addnode=37.59.14.211
addnode=94.23.196.50
addnode=94.23.12.37
addnode=91.121.83.119
addnode=188.165.193.28
I updated to the new version and it worked(synced successfully).
Thanks anyway. i will add the nodes
My wallet hasnt been able to sync for the past 2 days. what could be the problem?
remove "blocks", "chainstate" directory, then remove "banlist.dat" fileadd to biblepay.conf these lines:
Code:
addnode=137.74.0.113
addnode=37.59.14.211
addnode=94.23.196.50
addnode=94.23.12.37
addnode=91.121.83.119
addnode=188.165.193.28
My wallet hasnt been able to sync for the past 2 days. what could be the problem?
Just catching up on the thread. Installed the new biblepay on my workers, all working now. Great work dev.
Biblepay is probably the most interesting coin I follow. Not a typical clone of another coin, biblehash is genuinely interesting, dev is communicative and actually knows what they're doing. 👍
Wasn't aware of public beta-testing on the main chain. Will definitely volunteer next time you put the call out.
Biblepay is probably the most interesting coin I follow. Not a typical clone of another coin, biblehash is genuinely interesting, dev is communicative and actually knows what they're doing. 👍
Wasn't aware of public beta-testing on the main chain. Will definitely volunteer next time you put the call out.
Hahaha, we have some comedians here.
Gave me a good chuckle.Haha
this is funny, hope liugang saw that message, lol~~ 
Very nice concept... Hope this coin become more valuable when it's hits exchange
Hahaha, we have some comedians here.
Gave me a good chuckle.
I did it before updates and got less HPS with more cores enabled.
Now i made another try and:
genproclimit=6 i got 6235,17HPS and 18649,49HPS2 at less than 60% load for miner.
genproclimit=12 i got 5961,53HPS and 14035,45HPS2 at less than 80% load for miner.
Now i made another try and:
genproclimit=6 i got 6235,17HPS and 18649,49HPS2 at less than 60% load for miner.
genproclimit=12 i got 5961,53HPS and 14035,45HPS2 at less than 80% load for miner.
im tested my Ryzen 1700 every setups with genproclimit from 8 to 24 and still have hashpower 3839.95 6785.13 
Is normal to have all of the cores (CPU X5650 genproclimit=6) at less than 60% load while mining?
X5650 has 6 cores and 12 threads. You need to increase genproclimit to 12 if you want 100%.
Is normal to have all of the cores (CPU X5650 genproclimit=6) at less than 60% load while mining?
Code:
2017-09-14 07:08:46 socket send error An established connection was aborted by the software in your host machine. (10053)
While syncing, this error shows up just after block 7012, and then it stops syncing and has 0 peers. I started with a completely clean directory of course. Then after a while it syncs a few more blocks and then stops with another error:
Code:
2017-09-14 07:11:24 socket recv error An existing connection was forcibly closed by the remote host. (10054)
Edit: spamming this command into the console multiple times syncs it eventually:
Code:
addnode "pool.biblepay.org" "onetry"
Ubuntu miners dropped from pool still happen. Any clue?
I can confirm that I have the same issue running 1.0.3.4 on Debian Linux.
Lots of:
Quote
2017-09-13 23:46:28 socket recv error Connection reset by peer (104)
2017-09-13 23:48:35 socket recv error Connection reset by peer (104)
2017-09-13 23:50:42 socket recv error Connection reset by peer (104)
2017-09-13 23:52:49 socket recv error Connection reset by peer (104)
2017-09-13 23:54:57 socket recv error Connection reset by peer (104)
2017-09-13 23:57:04 socket recv error Connection reset by peer (104)
2017-09-13 23:59:11 socket recv error Connection reset by peer (104)
2017-09-14 00:01:18 socket recv error Connection reset by peer (104)
2017-09-14 00:03:25 socket recv error Connection reset by peer (104)
2017-09-14 00:05:32 socket recv error Connection reset by peer (104)
2017-09-14 00:07:40 socket recv error Connection reset by peer (104)
2017-09-13 23:48:35 socket recv error Connection reset by peer (104)
2017-09-13 23:50:42 socket recv error Connection reset by peer (104)
2017-09-13 23:52:49 socket recv error Connection reset by peer (104)
2017-09-13 23:54:57 socket recv error Connection reset by peer (104)
2017-09-13 23:57:04 socket recv error Connection reset by peer (104)
2017-09-13 23:59:11 socket recv error Connection reset by peer (104)
2017-09-14 00:01:18 socket recv error Connection reset by peer (104)
2017-09-14 00:03:25 socket recv error Connection reset by peer (104)
2017-09-14 00:05:32 socket recv error Connection reset by peer (104)
2017-09-14 00:07:40 socket recv error Connection reset by peer (104)
And still have:
Quote
2017-09-13 23:07:35 ProcessNewBlock : ACCEPTED
2017-09-13 23:07:54 socket recv error Connection reset by peer (104)
2017-09-13 23:08:06 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7361.000000 pindexPrev 271c540a2ff535f1a76095333af4be559dc03344063a8240cbe6c57f2b319383
2017-09-13 23:08:06 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3213187)^M
** ProcessGetData:Cannot load block from disk.^M
2017-09-13 23:08:08 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7335.000000 pindexPrev 7c8ebea50332103b657ffae35b44a568473db479abe1ddda751e856d3101e618
2017-09-13 23:08:08 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3202733)^M
** ProcessGetData:Cannot load block from disk.^M
2017-09-13 23:08:10 UpdateTip: new best=3fa7e67c94be8d98ab261a3e4bd987d9109d5581d7cbdcc8197875e400ac38aa height=7496 log2_work=49.133899 tx=11543 date=2017-09-13 23:08:06 progress=1.000000 cache=0.0MiB(38tx)
2017-09-13 23:08:10 ProcessNewBlock : ACCEPTED
2017-09-13 23:10:01 socket recv error Connection reset by peer (104)
2017-09-13 23:11:48 UpdateTip: new best=88b6821089d7bca250e5319957b5489ba79625d479a6674003a4da980b9a8424 height=7497 log2_work=49.135977 tx=11545 date=2017-09-13 23:11:40 progress=0.999999 cache=0.0MiB(40tx)
2017-09-13 23:11:48 ProcessNewBlock : ACCEPTED
2017-09-13 23:07:54 socket recv error Connection reset by peer (104)
2017-09-13 23:08:06 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7361.000000 pindexPrev 271c540a2ff535f1a76095333af4be559dc03344063a8240cbe6c57f2b319383
2017-09-13 23:08:06 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3213187)^M
** ProcessGetData:Cannot load block from disk.^M
2017-09-13 23:08:08 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7335.000000 pindexPrev 7c8ebea50332103b657ffae35b44a568473db479abe1ddda751e856d3101e618
2017-09-13 23:08:08 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3202733)^M
** ProcessGetData:Cannot load block from disk.^M
2017-09-13 23:08:10 UpdateTip: new best=3fa7e67c94be8d98ab261a3e4bd987d9109d5581d7cbdcc8197875e400ac38aa height=7496 log2_work=49.133899 tx=11543 date=2017-09-13 23:08:06 progress=1.000000 cache=0.0MiB(38tx)
2017-09-13 23:08:10 ProcessNewBlock : ACCEPTED
2017-09-13 23:10:01 socket recv error Connection reset by peer (104)
2017-09-13 23:11:48 UpdateTip: new best=88b6821089d7bca250e5319957b5489ba79625d479a6674003a4da980b9a8424 height=7497 log2_work=49.135977 tx=11545 date=2017-09-13 23:11:40 progress=0.999999 cache=0.0MiB(40tx)
2017-09-13 23:11:48 ProcessNewBlock : ACCEPTED
It still seems to think it is submitting to the pool, but the pool is not showing or counting it (phaseshift.w2):
Quote
$ ../biblepay/bin/biblepay-cli getmininginfo
{
"blocks": 7550,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 441.3595706618963,
"errors": "",
"genproclimit": 8,
"networkhashps": 45819800310.70996,
"hashps": 56562.73997076839,
"minerstarttime": "09-13-2017 22:43:42",
"pooledtx": 0,
"testnet": false,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; ",
"poolinfo2": "RMC_09-14-2017 07:06:21; RMC_09-14-2017 07:12:12; RMC_09-14-2017 07:06:53; ",
"poolinfo3": "CFW 09-14-2017 07:06:20; CFW 09-14-2017 07:12:11; CFW 09-14-2017 07:06:51; ",
"miningpulse": 52683,
"poolmining": true
}
{
"blocks": 7550,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 441.3595706618963,
"errors": "",
"genproclimit": 8,
"networkhashps": 45819800310.70996,
"hashps": 56562.73997076839,
"minerstarttime": "09-13-2017 22:43:42",
"pooledtx": 0,
"testnet": false,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; ",
"poolinfo2": "RMC_09-14-2017 07:06:21; RMC_09-14-2017 07:12:12; RMC_09-14-2017 07:06:53; ",
"poolinfo3": "CFW 09-14-2017 07:06:20; CFW 09-14-2017 07:12:11; CFW 09-14-2017 07:06:51; ",
"miningpulse": 52683,
"poolmining": true
}
On the plus side, the error below seems to not happen any more when stopping biblepay under Linux with 1.0.3.4:
Quote
"terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
terminate called recursively"
what(): std::bad_alloc
terminate called recursively"
Unfortunately I have removed all of my miners. They will mine for an hour or so and then crash with previous posted errors. I have completely installed from scratch, including removing the profile folder with same results. Hope to mine again when these issues are solved.
Thanks dev for the quick attention to the issues today! Its that sort of strength that doesn't get recognized that has the potential to take this coin places.
Yes I agree. Also the community is pretty strong and its growing. The way you guys brought up the issues and suggestions are amazing. I spend all day at work and don't get a time to look at the thread and issues. By the time I come home, the solution or work around has already been delivered. I upgraded to latest wallet and it wasn't syncing someone mentioned to restart the wallet again and that worked.
Reliable investments are done.Any updates on the bounty?
Thanks dev for the quick attention to the issues today! Its that sort of strength that doesn't get recognized that has the potential to take this coin places.
Jump to: