** POOM UPDATE **
Todd from Cameroon did more exhaustive checking on both Chinese and Israeli children (and lost tribes of Israel), and primarily due to incompatibilities with governments (and the cost of living in Israel), both are currently not available for POOM.
I thanked him for the research.
Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 85. (Read 243376 times)
October 14, 2019, 11:33:48 AM
October 14, 2019, 10:22:15 AM
120€/monthly is price for bilboard in our county city
Still better off dressing in a giant rabbit suit and walking down the highway with a BBP sign...
October 14, 2019, 10:17:29 AM
Bitcointalk Thread for CPUMiner
https://bitcointalksearch.org/topic/an-even-more-optimized-version-of-cpuminer-poolers-cpuminer-cpu-only-55038
"cpuminer help – Usage, Flags and Command Examples"
https://rehmann.co/blog/cpuminer-help/
===
I havent been able to help test the miner, b/c my ubuntu machine freezes when it goes over 40-50% CPU,
Its issue Ive been having for many months, too lazy to fix it hahaha, ughh, LOL
I just found this --threads=N flag for cpuminer, so I can try testing again
I have debug=1 in config
===
Should I setup valgrind?
Old notes I found:
"please compile the source code version of biblepay, and run biblepay in valgrind like this:
If you just leave it run til it crashes again, you can then give us the line # and module filename.
Btw, you can't run valgrind on a binary (you can but it is useless to us). It must be run on a compiled source."
Reference: https://github.com/biblepay/biblepay/issues/76
===
QUESTION: Should we run valgrind on the miner and the wallet?
===
Valgrind
https://wiki.ubuntu.com/Valgrind
http://valgrind.org/
http://valgrind.org/docs/manual/quick-start.html
===
Build BBP Miner from Source:
https://github.com/biblepay/cpuminer/blob/master/BuildingBBPMiner.txt
https://bitcointalksearch.org/topic/an-even-more-optimized-version-of-cpuminer-poolers-cpuminer-cpu-only-55038
"cpuminer help – Usage, Flags and Command Examples"
https://rehmann.co/blog/cpuminer-help/
===
I havent been able to help test the miner, b/c my ubuntu machine freezes when it goes over 40-50% CPU,
Its issue Ive been having for many months, too lazy to fix it hahaha, ughh, LOL
I just found this --threads=N flag for cpuminer, so I can try testing again
I have debug=1 in config
===
Should I setup valgrind?
Old notes I found:
"please compile the source code version of biblepay, and run biblepay in valgrind like this:
Code:
sudo apt get install valgrind
cd ~/biblepay-evolution/src/qt
valgrind ./biblepay-qt
cd ~/biblepay-evolution/src/qt
valgrind ./biblepay-qt
If you just leave it run til it crashes again, you can then give us the line # and module filename.
Btw, you can't run valgrind on a binary (you can but it is useless to us). It must be run on a compiled source."
Reference: https://github.com/biblepay/biblepay/issues/76
===
QUESTION: Should we run valgrind on the miner and the wallet?
===
Valgrind
https://wiki.ubuntu.com/Valgrind
http://valgrind.org/
http://valgrind.org/docs/manual/quick-start.html
===
Build BBP Miner from Source:
https://github.com/biblepay/cpuminer/blob/master/BuildingBBPMiner.txt
Thanks for starting to debug; well, valgrind is very useful (for some of the cases), for example, cases where we can reproduce a crash within 30 minutes or so.
But in this case valgrind is not going to help us because one hour of mining in valgrind takes approximately 30 days (due to the overhead).
So it looks like we will need to finish debugging it in GDB (or xcode etc).
So dont worry about valgrind for now as it will just waste your time
.I do have some more traces now (I had them running all night). Im reacting to these next and then Ill make a new release.
One case addresses Orbis' JSON issue (I have that one), and another case addresses the mining crash (I believe).
Orbis as far as rebooting the wallet after a crash, no that should not be necessary. It could be that you found a block and your ABN was out for a while, but I confirm biblepay continues to run properly at that point.
October 14, 2019, 10:13:40 AM
It seems I am stucked mining since 8 of October, as no new transactions arise. However, CPUs are working. I was on 1.4.9 version since it was delivered, and I have updated this morning to 1.5.0, but I am still in the same situation. Getinfo and getmininginfo show correct data. What could be happening?
PS. Traditional wallet/miner, I am not talking about the new miner.
PS. Traditional wallet/miner, I am not talking about the new miner.
Most likely governance data is corrupt, and the wallet then decides to go on the wrong chain; please restart with:
./biblepay-qt -erasechain=1
Let it resync and then see if you are at the same hash/block as one of the block explorers - explorer.biblepay.org or chainz ?
Thanks.
EDIT: Btw, we do have the 'exec reassesschains' option for people with low bandwidth who want to try it first. But erasechain is better if you can walk away from it for a while.
October 14, 2019, 05:37:49 AM
It seems I am stucked mining since 8 of October, as no new transactions arise. However, CPUs are working. I was on 1.4.9 version since it was delivered, and I have updated this morning to 1.5.0, but I am still in the same situation. Getinfo and getmininginfo show correct data. What could be happening?
PS. Traditional wallet/miner, I am not talking about the new miner.
PS. Traditional wallet/miner, I am not talking about the new miner.
October 14, 2019, 02:53:37 AM
120€/monthly is price for bilboard in our county city
October 14, 2019, 02:48:21 AM
We are proud to annouce a big partnership with BIBLEPAY
We listed biblepay on Needyex
https://needyex.com/trade/index/market/bbp_needy/
https://needyex.com/Trade/index/market/bbp_btc
happy trading
We listed biblepay on Needyex
https://needyex.com/trade/index/market/bbp_needy/
https://needyex.com/Trade/index/market/bbp_btc
happy trading
October 13, 2019, 05:29:32 PM
I went ahead and bought the newsletter plugin license
https://forum.biblepay.org/index.php?topic=456.0
and entered in the new license key
Still trying to debug what is wrong with our newsletters not sending
https://www.thenewsletterplugin.com/documentation/email-sending-issues
Test email from Status page works
Latest Newsletter test email did not work again
I created a new default empty basic newsletter as described above, it worked!
Going to re-create the newsletter and try again
https://forum.biblepay.org/index.php?topic=456.0
and entered in the new license key
Still trying to debug what is wrong with our newsletters not sending
https://www.thenewsletterplugin.com/documentation/email-sending-issues
Test email from Status page works
Latest Newsletter test email did not work again
I created a new default empty basic newsletter as described above, it worked!
Going to re-create the newsletter and try again
October 13, 2019, 04:33:17 PM
New type of error after hitted block on my WIN 1003 miner:
Restart of miner didn't help. Only reboot of computer (both WIN and Linux) helps.
On new start of a miner on linux it gives me this:
Code:
Erroring out
[2019-10-13 23:31:59] json_rpc_call failed, retry after 30 seconds
Dying due to unable to convert to bin [2019-10-13 23:32:30] JSON invalid target
It stops working, but didn't quit program. This message is rolling over and over again.[2019-10-13 23:31:59] json_rpc_call failed, retry after 30 seconds
Dying due to unable to convert to bin [2019-10-13 23:32:30] JSON invalid target
Restart of miner didn't help. Only reboot of computer (both WIN and Linux) helps.
On new start of a miner on linux it gives me this:
Code:
*** Error in `/usr/local/bin/bbpminer_linux': malloc(): memory corruption (fast): 0x00007f662400ecc0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f6635a0a7e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x82651)[0x7f6635a15651]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7f6635a17184]
/lib/x86_64-linux-gnu/libc.so.6(__strdup+0x1a)[0x7f6635a1e48a]
/lib/x86_64-linux-gnu/libc.so.6(+0xbdd0b)[0x7f6635a50d0b]
/usr/local/bin/bbpminer_linux(+0x458c3)[0x55c0bc5418c3]
/usr/local/bin/bbpminer_linux(+0x41a0e)[0x55c0bc53da0e]
/usr/local/bin/bbpminer_linux(+0x44e2b)[0x55c0bc540e2b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f6635d646ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f6635a9a41d]
======= Memory map: ========
55c0bc4fc000-55c0bcdbf000 r-xp 00000000 fc:00 4331 /usr/local/bin/bbpminer_linux
55c0bcfbe000-55c0bcfe0000 r--p 008c2000 fc:00 4331 /usr/local/bin/bbpminer_linux
55c0bcfe0000-55c0bcfef000 rw-p 008e4000 fc:00 4331 /usr/local/bin/bbpminer_linux
55c0bcfef000-55c0bd032000 rw-p 00000000 00:00 0
55c0bd2f9000-55c0bd31a000 rw-p 00000000 00:00 0 [heap]
7f6624000000-7f662405c000 rw-p 00000000 00:00 0
7f662405c000-7f6628000000 ---p 00000000 00:00 0
7f6628000000-7f6628021000 rw-p 00000000 00:00 0
7f6628021000-7f662c000000 ---p 00000000 00:00 0
7f662c000000-7f662c021000 rw-p 00000000 00:00 0
7f662c021000-7f6630000000 ---p 00000000 00:00 0
7f6630773000-7f6630789000 r-xp 00000000 fc:00 392981 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f6630789000-7f6630988000 ---p 00016000 fc:00 392981 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f6630988000-7f6630989000 rw-p 00015000 fc:00 392981 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f6630989000-7f663098a000 ---p 00000000 00:00 0
7f663098a000-7f663118a000 rw-p 00000000 00:00 0
7f663118a000-7f663118b000 ---p 00000000 00:00 0
7f663118b000-7f663198b000 rw-p 00000000 00:00 0
7f663198b000-7f663198c000 ---p 00000000 00:00 0
7f663198c000-7f663218c000 rw-p 00000000 00:00 0
7f663218c000-7f663218d000 ---p 00000000 00:00 0
7f663218d000-7f663298d000 rw-p 00000000 00:00 0
7f663298d000-7f663298e000 ---p 00000000 00:00 0
7f663298e000-7f663318e000 rw-p 00000000 00:00 0
7f663318e000-7f663318f000 ---p 00000000 00:00 0
7f663318f000-7f663398f000 rw-p 00000000 00:00 0
7f663398f000-7f6633990000 ---p 00000000 00:00 0
7f6633990000-7f6634190000 rw-p 00000000 00:00 0
7f6634190000-7f6634191000 ---p 00000000 00:00 0
7f6634191000-7f6634991000 rw-p 00000000 00:00 0
7f6634991000-7f6634992000 ---p 00000000 00:00 0
7f6634992000-7f6635192000 rw-p 00000000 00:00 0
7f6635192000-7f6635193000 ---p 00000000 00:00 0
7f6635193000-7f6635993000 rw-p 00000000 00:00 0
7f6635993000-7f6635b53000 r-xp 00000000 fc:00 396529 /lib/x86_64-linux-gnu/libc-2.23.so
7f6635b53000-7f6635d53000 ---p 001c0000 fc:00 396529 /lib/x86_64-linux-gnu/libc-2.23.so
7f6635d53000-7f6635d57000 r--p 001c0000 fc:00 396529 /lib/x86_64-linux-gnu/libc-2.23.so
7f6635d57000-7f6635d59000 rw-p 001c4000 fc:00 396529 /lib/x86_64-linux-gnu/libc-2.23.so
7f6635d59000-7f6635d5d000 rw-p 00000000 00:00 0
7f6635d5d000-7f6635d75000 r-xp 00000000 fc:00 396516 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f6635d75000-7f6635f74000 ---p 00018000 fc:00 396516 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f6635f74000-7f6635f75000 r--p 00017000 fc:00 396516 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f6635f75000-7f6635f76000 rw-p 00018000 fc:00 396516 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f6635f76000-7f6635f7a000 rw-p 00000000 00:00 0
7f6635f7a000-7f6635f7d000 r-xp 00000000 fc:00 396514 /lib/x86_64-linux-gnu/libdl-2.23.so
7f6635f7d000-7f663617c000 ---p 00003000 fc:00 396514 /lib/x86_64-linux-gnu/libdl-2.23.so
7f663617c000-7f663617d000 r--p 00002000 fc:00 396514 /lib/x86_64-linux-gnu/libdl-2.23.so
7f663617d000-7f663617e000 rw-p 00003000 fc:00 396514 /lib/x86_64-linux-gnu/libdl-2.23.so
7f663617e000-7f6636197000 r-xp 00000000 fc:00 441287 /lib/x86_64-linux-gnu/libz.so.1.2.8
7f6636197000-7f6636396000 ---p 00019000 fc:00 441287 /lib/x86_64-linux-gnu/libz.so.1.2.8
7f6636396000-7f6636397000 r--p 00018000 fc:00 441287 /lib/x86_64-linux-gnu/libz.so.1.2.8
7f6636397000-7f6636398000 rw-p 00019000 fc:00 441287 /lib/x86_64-linux-gnu/libz.so.1.2.8
7f6636398000-7f66363be000 r-xp 00000000 fc:00 396515 /lib/x86_64-linux-gnu/ld-2.23.so
7f66365b1000-7f66365b6000 rw-p 00000000 00:00 0
7f66365bc000-7f66365bd000 rw-p 00000000 00:00 0
7f66365bd000-7f66365be000 r--p 00025000 fc:00 396515 /lib/x86_64-linux-gnu/ld-2.23.so
7f66365be000-7f66365bf000 rw-p 00026000 fc:00 396515 /lib/x86_64-linux-gnu/ld-2.23.so
7f66365bf000-7f66365c0000 rw-p 00000000 00:00 0
7ffd7e97d000-7ffd7e99e000 rw-p 00000000 00:00 0 [stack]
7ffd7e9c4000-7ffd7e9c7000 r--p 00000000 00:00 0 [vvar]
7ffd7e9c7000-7ffd7e9c9000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f6635a0a7e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x82651)[0x7f6635a15651]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7f6635a17184]
/lib/x86_64-linux-gnu/libc.so.6(__strdup+0x1a)[0x7f6635a1e48a]
/lib/x86_64-linux-gnu/libc.so.6(+0xbdd0b)[0x7f6635a50d0b]
/usr/local/bin/bbpminer_linux(+0x458c3)[0x55c0bc5418c3]
/usr/local/bin/bbpminer_linux(+0x41a0e)[0x55c0bc53da0e]
/usr/local/bin/bbpminer_linux(+0x44e2b)[0x55c0bc540e2b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f6635d646ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f6635a9a41d]
======= Memory map: ========
55c0bc4fc000-55c0bcdbf000 r-xp 00000000 fc:00 4331 /usr/local/bin/bbpminer_linux
55c0bcfbe000-55c0bcfe0000 r--p 008c2000 fc:00 4331 /usr/local/bin/bbpminer_linux
55c0bcfe0000-55c0bcfef000 rw-p 008e4000 fc:00 4331 /usr/local/bin/bbpminer_linux
55c0bcfef000-55c0bd032000 rw-p 00000000 00:00 0
55c0bd2f9000-55c0bd31a000 rw-p 00000000 00:00 0 [heap]
7f6624000000-7f662405c000 rw-p 00000000 00:00 0
7f662405c000-7f6628000000 ---p 00000000 00:00 0
7f6628000000-7f6628021000 rw-p 00000000 00:00 0
7f6628021000-7f662c000000 ---p 00000000 00:00 0
7f662c000000-7f662c021000 rw-p 00000000 00:00 0
7f662c021000-7f6630000000 ---p 00000000 00:00 0
7f6630773000-7f6630789000 r-xp 00000000 fc:00 392981 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f6630789000-7f6630988000 ---p 00016000 fc:00 392981 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f6630988000-7f6630989000 rw-p 00015000 fc:00 392981 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f6630989000-7f663098a000 ---p 00000000 00:00 0
7f663098a000-7f663118a000 rw-p 00000000 00:00 0
7f663118a000-7f663118b000 ---p 00000000 00:00 0
7f663118b000-7f663198b000 rw-p 00000000 00:00 0
7f663198b000-7f663198c000 ---p 00000000 00:00 0
7f663198c000-7f663218c000 rw-p 00000000 00:00 0
7f663218c000-7f663218d000 ---p 00000000 00:00 0
7f663218d000-7f663298d000 rw-p 00000000 00:00 0
7f663298d000-7f663298e000 ---p 00000000 00:00 0
7f663298e000-7f663318e000 rw-p 00000000 00:00 0
7f663318e000-7f663318f000 ---p 00000000 00:00 0
7f663318f000-7f663398f000 rw-p 00000000 00:00 0
7f663398f000-7f6633990000 ---p 00000000 00:00 0
7f6633990000-7f6634190000 rw-p 00000000 00:00 0
7f6634190000-7f6634191000 ---p 00000000 00:00 0
7f6634191000-7f6634991000 rw-p 00000000 00:00 0
7f6634991000-7f6634992000 ---p 00000000 00:00 0
7f6634992000-7f6635192000 rw-p 00000000 00:00 0
7f6635192000-7f6635193000 ---p 00000000 00:00 0
7f6635193000-7f6635993000 rw-p 00000000 00:00 0
7f6635993000-7f6635b53000 r-xp 00000000 fc:00 396529 /lib/x86_64-linux-gnu/libc-2.23.so
7f6635b53000-7f6635d53000 ---p 001c0000 fc:00 396529 /lib/x86_64-linux-gnu/libc-2.23.so
7f6635d53000-7f6635d57000 r--p 001c0000 fc:00 396529 /lib/x86_64-linux-gnu/libc-2.23.so
7f6635d57000-7f6635d59000 rw-p 001c4000 fc:00 396529 /lib/x86_64-linux-gnu/libc-2.23.so
7f6635d59000-7f6635d5d000 rw-p 00000000 00:00 0
7f6635d5d000-7f6635d75000 r-xp 00000000 fc:00 396516 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f6635d75000-7f6635f74000 ---p 00018000 fc:00 396516 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f6635f74000-7f6635f75000 r--p 00017000 fc:00 396516 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f6635f75000-7f6635f76000 rw-p 00018000 fc:00 396516 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f6635f76000-7f6635f7a000 rw-p 00000000 00:00 0
7f6635f7a000-7f6635f7d000 r-xp 00000000 fc:00 396514 /lib/x86_64-linux-gnu/libdl-2.23.so
7f6635f7d000-7f663617c000 ---p 00003000 fc:00 396514 /lib/x86_64-linux-gnu/libdl-2.23.so
7f663617c000-7f663617d000 r--p 00002000 fc:00 396514 /lib/x86_64-linux-gnu/libdl-2.23.so
7f663617d000-7f663617e000 rw-p 00003000 fc:00 396514 /lib/x86_64-linux-gnu/libdl-2.23.so
7f663617e000-7f6636197000 r-xp 00000000 fc:00 441287 /lib/x86_64-linux-gnu/libz.so.1.2.8
7f6636197000-7f6636396000 ---p 00019000 fc:00 441287 /lib/x86_64-linux-gnu/libz.so.1.2.8
7f6636396000-7f6636397000 r--p 00018000 fc:00 441287 /lib/x86_64-linux-gnu/libz.so.1.2.8
7f6636397000-7f6636398000 rw-p 00019000 fc:00 441287 /lib/x86_64-linux-gnu/libz.so.1.2.8
7f6636398000-7f66363be000 r-xp 00000000 fc:00 396515 /lib/x86_64-linux-gnu/ld-2.23.so
7f66365b1000-7f66365b6000 rw-p 00000000 00:00 0
7f66365bc000-7f66365bd000 rw-p 00000000 00:00 0
7f66365bd000-7f66365be000 r--p 00025000 fc:00 396515 /lib/x86_64-linux-gnu/ld-2.23.so
7f66365be000-7f66365bf000 rw-p 00026000 fc:00 396515 /lib/x86_64-linux-gnu/ld-2.23.so
7f66365bf000-7f66365c0000 rw-p 00000000 00:00 0
7ffd7e97d000-7ffd7e99e000 rw-p 00000000 00:00 0 [stack]
7ffd7e9c4000-7ffd7e9c7000 r--p 00000000 00:00 0 [vvar]
7ffd7e9c7000-7ffd7e9c9000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
October 13, 2019, 03:10:20 PM
Bitcointalk Thread for CPUMiner
https://bitcointalksearch.org/topic/an-even-more-optimized-version-of-cpuminer-poolers-cpuminer-cpu-only-55038
"cpuminer help – Usage, Flags and Command Examples"
https://rehmann.co/blog/cpuminer-help/
===
I havent been able to help test the miner, b/c my ubuntu machine freezes when it goes over 40-50% CPU,
Its issue Ive been having for many months, too lazy to fix it hahaha, ughh, LOL
I just found this --threads=N flag for cpuminer, so I can try testing again
I have debug=1 in config
===
Should I setup valgrind?
Old notes I found:
"please compile the source code version of biblepay, and run biblepay in valgrind like this:
If you just leave it run til it crashes again, you can then give us the line # and module filename.
Btw, you can't run valgrind on a binary (you can but it is useless to us). It must be run on a compiled source."
Reference: https://github.com/biblepay/biblepay/issues/76
===
QUESTION: Should we run valgrind on the miner and the wallet?
===
Valgrind
https://wiki.ubuntu.com/Valgrind
http://valgrind.org/
http://valgrind.org/docs/manual/quick-start.html
===
Build BBP Miner from Source:
https://github.com/biblepay/cpuminer/blob/master/BuildingBBPMiner.txt
https://bitcointalksearch.org/topic/an-even-more-optimized-version-of-cpuminer-poolers-cpuminer-cpu-only-55038
"cpuminer help – Usage, Flags and Command Examples"
https://rehmann.co/blog/cpuminer-help/
===
I havent been able to help test the miner, b/c my ubuntu machine freezes when it goes over 40-50% CPU,
Its issue Ive been having for many months, too lazy to fix it hahaha, ughh, LOL
I just found this --threads=N flag for cpuminer, so I can try testing again
I have debug=1 in config
===
Should I setup valgrind?
Old notes I found:
"please compile the source code version of biblepay, and run biblepay in valgrind like this:
Code:
sudo apt get install valgrind
cd ~/biblepay-evolution/src/qt
valgrind ./biblepay-qt
cd ~/biblepay-evolution/src/qt
valgrind ./biblepay-qt
If you just leave it run til it crashes again, you can then give us the line # and module filename.
Btw, you can't run valgrind on a binary (you can but it is useless to us). It must be run on a compiled source."
Reference: https://github.com/biblepay/biblepay/issues/76
===
QUESTION: Should we run valgrind on the miner and the wallet?
===
Valgrind
https://wiki.ubuntu.com/Valgrind
http://valgrind.org/
http://valgrind.org/docs/manual/quick-start.html
===
Build BBP Miner from Source:
https://github.com/biblepay/cpuminer/blob/master/BuildingBBPMiner.txt
October 13, 2019, 01:53:45 PM
I got email that the explorer server got rebooted
"Our monitoring system indicated an issue with the hardware node hosting the instances listed in this email.
Our engineering team has investigated the issue and initiated a restart of the host node in question."
So explorer is down, Ill jump in and fix it now
=
UPDATE: Explorer is up and syncing, almost caught up now
Everything should auto run b/c of crontab, even after a reboot
BiblePay daemon was running
Mongodb was running
Nodejs was NOT running, not sure what issue is, didnt dig into it
"Our monitoring system indicated an issue with the hardware node hosting the instances listed in this email.
Our engineering team has investigated the issue and initiated a restart of the host node in question."
So explorer is down, Ill jump in and fix it now
=
UPDATE: Explorer is up and syncing, almost caught up now
Everything should auto run b/c of crontab, even after a reboot
BiblePay daemon was running
Mongodb was running
Nodejs was NOT running, not sure what issue is, didnt dig into it
October 13, 2019, 11:32:45 AM
1003 crash with -D with this result:
BTW coinabase address is not working for me. It still came to different address.
And my experience is, that it looks, that after crash, miner is not able to hit block, till I restart BBP wallet. Run bbpminer is not enough.
I don't know if It's true or it's coincidence.
Code:
The instruction at Ox00007FF878D0D62C referenced memory F at OxFFFFFFFFFFFFFFFF. The memory could not be read.
BTW coinabase address is not working for me. It still came to different address.
And my experience is, that it looks, that after crash, miner is not able to hit block, till I restart BBP wallet. Run bbpminer is not enough.
I don't know if It's true or it's coincidence.
October 13, 2019, 10:19:10 AM
crashed too on win 10
October 13, 2019, 10:18:46 AM
Ok 1.0.0.3 didnt last much longer, but now Im running one in debug mode in gdb and another one in valgrind.
Ill keep debugging until we find the cause of the crash.
Ill keep debugging until we find the cause of the crash.
One Windows 10 computer I didn't do all the security updates (it has been off for several months) mined for 12+ hours (on 1.0.0.1 bbpminer version) with no issue.
I want to speculate that crashes seem to occur when a GSC using up all the coinage inputs (ABN starved) or when the contents fo the UTXOs change, the miner gets confused? If ABN is off on testnet, this would be an easy thing to test in TestNet for me.
Ill try that idea of starving the miner, that might be the problem.
I wont have time to release the testnet version til tomorrow but we will release it asap.
That might explain why I never crashed during development - I ran it against testnet with no abn.
October 13, 2019, 10:16:54 AM
I just checked in 1.0.0.3, lets run it with the "-D" switch at the end of the command line, and see if it reveals the problem.
(Or if its fixed now).
Nothing change after upgrade 1.0.0.3 and command line with "-D"
still crashing after a few moment.
When the bbpminer crashed(IE: Abort , Bus error , core dumped etc), I found that this also caused some system structure problems(UBUNTU 16), need to shut down and then restart to access via ssh. Otherwise, you can not enter the system via ssh before shutting down.
Shouldnt be possible in linux - miner cant take down the server.
Please try again.
October 13, 2019, 09:48:37 AM
I just checked in 1.0.0.3, lets run it with the "-D" switch at the end of the command line, and see if it reveals the problem.
(Or if its fixed now).
Nothing change after upgrade 1.0.0.3 and command line with "-D"
still crashing after a few moment.
When the bbpminer crashed(IE: Abort , Bus error , core dumped etc), I found that this also caused some system structure problems(UBUNTU 16), need to shut down and then restart to access via ssh. Otherwise, you can not enter the system via ssh before shutting down.
October 13, 2019, 09:39:25 AM
Ok 1.0.0.3 didnt last much longer, but now Im running one in debug mode in gdb and another one in valgrind.
Ill keep debugging until we find the cause of the crash.
Ill keep debugging until we find the cause of the crash.
One Windows 10 computer I didn't do all the security updates (it has been off for several months) mined for 12+ hours (on 1.0.0.1 bbpminer version) with no issue.
I want to speculate that crashes seem to occur when a GSC using up all the coinage inputs (ABN starved) or when the contents fo the UTXOs change, the miner gets confused? If ABN is off on testnet, this would be an easy thing to test in TestNet for me.
October 13, 2019, 09:26:46 AM
Ok 1.0.0.3 didnt last much longer, but now Im running one in debug mode in gdb and another one in valgrind.
Ill keep debugging until we find the cause of the crash.
Ill keep debugging until we find the cause of the crash.
October 13, 2019, 09:24:36 AM
Youd have to run it in valgrind to get the actual trace info; how many hours at a time did it run with coinbase addr set?
Edit: thats great you mined a block; I assume the reward came to a brand new key.
Edit: thats great you mined a block; I assume the reward came to a brand new key.
valgrind is for Linux isn't? Couldn't find a Windows version. Maybe this? http://www.codersnotes.com/sleepy/
I am not sure if coinbase-addr sends to the address I specify, but I'll have to keep checking. I also put a coinbase sig text. I think something is getting saved into the blockchain (according to chainz), but not the text I specified.
On the coinbase address, I see the issue with that - its preferring the address biblepaycore is sending (as if you started to solo mine) - I can fix that in the next version; but I have a question, when you say you injected a signature to be checked in chainz, what do you mean?
--coinbase-addr=ADDR payout address for solo mining
--coinbase-sig=TEXT data to insert in the coinbase when possible
So, when you specify a --coinbase-addr , you can specify a specific reward address to send to.
For my use case, different receiving would tell me which computer is mining rewards.
--coinbase-sig=TEXT in the raw output of the block, you will see your custom text included with mined block.
This is low priority. It is just a feature supported with minerd for bitcoin back when cpu mining was viable for bitcoin.
Ok, now I know which command you used to embed a coinbase sig. Yeah, we will have to take that option out as we dont support custom coinbase signatures (they must be made from the core wallet, due to chainlocks being implemented soon, which requires binary data to be stored and the signature therefore wont be calculated from the external miner). However we do support custom prayers and messages, but again - the external miner wont have the capability to insert a custom prayer or message from the mining side.
But we will be able to support the custom payout address, somehow - soon as we get closer to a pool.
October 13, 2019, 09:17:27 AM
again miner for 5-6 users
sunk,orbis,rob and etc......
where is so easy way for miners? nonstop hard to setup
WE WANT TO 1 CLICK SW.MINER like on others coins
BIBLEPAY where is that coins from wallet? i tried install new wallet on new machines and replace friends wallet.dat ... see on this I CAN SENT WALLET.DAT to you and check it....
sunk,orbis,rob and etc......
where is so easy way for miners? nonstop hard to setup
WE WANT TO 1 CLICK SW.MINER like on others coins
BIBLEPAY where is that coins from wallet? i tried install new wallet on new machines and replace friends wallet.dat ... see on this I CAN SENT WALLET.DAT to you and check it....
BB5h6ud4znPzFFqb5T6PR9JMidjdDRAwmD
If you have the private key for the above public key, you will have most of the coins.
in tools, debug console:
xx:xx:xx dumpprivkey BB5h6ud4znPzFFqb5T6PR9JMidjdDRAwmD
xx:xx:xx Private key for address BB5h6ud4znPzFFqb5T6PR9JMidjdDRAwmD is not known (code -4)
I don't have the private key so I get this answer. But if you have the private key, wallet will say.
Then once you have this key, copy to safe place (like password manager).
start biblepay brand new with brand new wallet.
then do:
importprivkey privatekey
make sure to keep private key secret.
Jump to: