I'am on good chain ?
all my nodes now running on block 7476 with hash b902dbafd8b12647a990354877a27ba2e8a2d7b35fc572eff2d18edf9584f32a
Topic: BiblePay - New Coin Launch - Official Thread - page 79. (Read 119833 times)
Alright, lets rewind the whole day back to about 7 AM and try this again.
Version 1.0.3.4 (the future mandatory) is now checked in for linux only. This new version includes a 'protocol' upgrade meaning it wont communicate with prior versions. If anyone on linux wants to upgrade now and start pre-testing go for it.
Win is compiling and will be ready in two hours.
In the mean time I need to run some errands, Ill be back in two hours and we can release Windows and I will make a POST so everyone can be ready at approx the same time to try the mandatory upgrade again.
Version 1.0.3.4 (the future mandatory) is now checked in for linux only. This new version includes a 'protocol' upgrade meaning it wont communicate with prior versions. If anyone on linux wants to upgrade now and start pre-testing go for it.
Win is compiling and will be ready in two hours.
In the mean time I need to run some errands, Ill be back in two hours and we can release Windows and I will make a POST so everyone can be ready at approx the same time to try the mandatory upgrade again.
does it mean we have to flush blocks and chainstate directories ?
I did that on 1 upgraded box .
it's now on 7188 and doing nothing:
blocks": 7188,
"blocks": 7188,
"currentblocksize": 0,
"currentblocktx": 0,
"difficulty": 40.48123000304026,
"errors": "",
"genproclimit": 32,
"networkhashps": 2275758480.220703,
"hashps": 0,
"minerstarttime": "09-13-2017 19:49:22",
"pooledtx": 0,
"testnet": false,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"miningpulse": 0,
"poolmining": false
other upgraded boxes are at diff levels :
blocks": 7460,
"blocks": 7475,
"blocks": 7447,
showing activity but again not hitting the pool :
smthing like this :
Code:
"poolinfo2": "Submitting Solution 09-13-2017 20:11:26; Submitting Solution 09-13-2017 20:12:21; RMC_09-13-2017 20
:12:31; Submitting Solution 09-13-2017 20:12:23; Submitting Solution 09-13-2017 20:12:26; Submitting Solution 09-13
-2017 20:12:29; Submitting Solution 09-13-2017 20:11:28; RM_09-13-2017 20:12:30; Submitting Solution 09-13-2017 20:
12:16; Submitting Solution 09-13-2017 20:12:15; Submitting Solution 09-13-2017 20:12:20; Submitting Solution 09-13-
2017 20:12:26; Submitting Solution 09-13-2017 20:12:09; Submitting Solution 09-13-2017 20:12:29; Submitting Solutio
n 09-13-2017 20:12:18; Submitting Solution 09-13-2017 20:12:22; ",
"poolinfo3": "HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_D
OWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; ",
:12:31; Submitting Solution 09-13-2017 20:12:23; Submitting Solution 09-13-2017 20:12:26; Submitting Solution 09-13
-2017 20:12:29; Submitting Solution 09-13-2017 20:11:28; RM_09-13-2017 20:12:30; Submitting Solution 09-13-2017 20:
12:16; Submitting Solution 09-13-2017 20:12:15; Submitting Solution 09-13-2017 20:12:20; Submitting Solution 09-13-
2017 20:12:26; Submitting Solution 09-13-2017 20:12:09; Submitting Solution 09-13-2017 20:12:29; Submitting Solutio
n 09-13-2017 20:12:18; Submitting Solution 09-13-2017 20:12:22; ",
"poolinfo3": "HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_D
OWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; ",
Thank you for the hard work. I couldn't do what you do so it is much appreciated.
Thank you for your hard work bible_pay!!
So basically, 1.0.3.1-1.0.3.3 was a failure.
This version contains a bad LogPrint message, that causes the entire wallet to die.
The new version is almost ready. I just tested it and it works on Debian and raises the subsidy back up to normal at block 7500.
This version contains a bad LogPrint message, that causes the entire wallet to die.
The new version is almost ready. I just tested it and it works on Debian and raises the subsidy back up to normal at block 7500.
I was just looking into why 1.0.3.3 didn't work. Thanks for sorting it so quickly.
Not really a priority, but hopefully can be fixed for a later version, whenever I issue the stop command to the server I get an error:
"terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
terminate called recursively"
https://github.com/biblepay/biblepay/issues/5
Thanks
Alright, lets rewind the whole day back to about 7 AM and try this again.
Version 1.0.3.4 (the future mandatory) is now checked in for linux only. This new version includes a 'protocol' upgrade meaning it wont communicate with prior versions. If anyone on linux wants to upgrade now and start pre-testing go for it.
Win is compiling and will be ready in two hours.
In the mean time I need to run some errands, Ill be back in two hours and we can release Windows and I will make a POST so everyone can be ready at approx the same time to try the mandatory upgrade again.
Version 1.0.3.4 (the future mandatory) is now checked in for linux only. This new version includes a 'protocol' upgrade meaning it wont communicate with prior versions. If anyone on linux wants to upgrade now and start pre-testing go for it.
Win is compiling and will be ready in two hours.
In the mean time I need to run some errands, Ill be back in two hours and we can release Windows and I will make a POST so everyone can be ready at approx the same time to try the mandatory upgrade again.
Nice a new version :-D
But wat about the mining and transaction from today ...
I understand that a role back will take this away?
I made my first transaction today lol
(Just a minor miner on a old laptop )
bible_pay can you post here how can we upgrade our wallet? pls dont waste our real time ... and can you write on main web http://biblepay.org/ what version we downloading?
Alright, lets rewind the whole day back to about 7 AM and try this again.
Version 1.0.3.4 (the future mandatory) is now checked in for linux only. This new version includes a 'protocol' upgrade meaning it wont communicate with prior versions. If anyone on linux wants to upgrade now and start pre-testing go for it.
Win is compiling and will be ready in two hours.
In the mean time I need to run some errands, Ill be back in two hours and we can release Windows and I will make a POST so everyone can be ready at approx the same time to try the mandatory upgrade again.
Version 1.0.3.4 (the future mandatory) is now checked in for linux only. This new version includes a 'protocol' upgrade meaning it wont communicate with prior versions. If anyone on linux wants to upgrade now and start pre-testing go for it.
Win is compiling and will be ready in two hours.
In the mean time I need to run some errands, Ill be back in two hours and we can release Windows and I will make a POST so everyone can be ready at approx the same time to try the mandatory upgrade again.
Any computers that I upgraded to 1.0.3.2 do not connect to nodes. No matter how many addnodes I have in the conf.
All of the computers running 1.0.3.1 do connect to nodes even after restarting them.
None are showing up on the pool.
All of the computers running 1.0.3.1 do connect to nodes even after restarting them.
None are showing up on the pool.
JUST WAIT
So basically, 1.0.3.1-1.0.3.3 was a failure.
This version contains a bad LogPrint message, that causes the entire wallet to die.
The new version is almost ready. I just tested it and it works on debian and raises the subsidy back up to normal at block 7500.
buddies how you upgrade your wallet?
tried install newest wallet on new machine and same problem like you Windows 64bit file. "A fatal error occurred. Biblepay Core can no longer safely continue and will quit."
tried install newest wallet on new machine and same problem like you Windows 64bit file. "A fatal error occurred. Biblepay Core can no longer safely continue and will quit."
Any computers that I upgraded to 1.0.3.2 do not connect to nodes. No matter how many addnodes I have in the conf.
All of the computers running 1.0.3.1 do connect to nodes even after restarting them.
None are showing up on the pool.
All of the computers running 1.0.3.1 do connect to nodes even after restarting them.
None are showing up on the pool.
JUST WAIT
Any computers that I upgraded to 1.0.3.2 do not connect to nodes. No matter how many addnodes I have in the conf.
All of the computers running 1.0.3.1 do connect to nodes even after restarting them.
None are showing up on the pool.
All of the computers running 1.0.3.1 do connect to nodes even after restarting them.
None are showing up on the pool.
To date, the synchronization was working, today after restarting the wallet sync has stopped working
problems with the blockchain . we'll have to wait for a resolution
To date, the synchronization was working, today after restarting the wallet sync has stopped working
Hello. solo minig cannot synchronize with the network for 11 hours. What to do? purse Biblepay v1.0.3.2 version
start with adding this in your biblepay.conf and restarting the wallet :
addnode=node.biblepay.org
addnode=biblepay.inspect.network
gen=1
Yes, it is spelled out in the config. No synchronization. after the restart, says the source blocks are not available. Although there are 5 active connections
1.3.2 working
but I tried on one node upgrade to 1.3.3
make clean
./configure
make
and on 1.3.3
gentoo Linux 4.7.10-hardened
gcc (Gentoo Hardened 4.9.3 p1.5, pie-0.6.4) 4.9.3
but I tried on one node upgrade to 1.3.3
make clean
./configure
make
and on 1.3.3
Code:
2017-09-13 17:46:42 init message: Activating best chain...
2017-09-13 17:46:42
************************
EXCEPTION: St13runtime_error
tinyformat: Not enough conversion specifiers in format string
biblepay in AppInit()
2017-09-13 17:46:42 PrepareShutdown: In progress...
gentoo Linux 4.7.10-hardened
gcc (Gentoo Hardened 4.9.3 p1.5, pie-0.6.4) 4.9.3
Hello. solo minig cannot synchronize with the network for 11 hours. What to do? purse Biblepay v1.0.3.2 version
start with adding this in your biblepay.conf and restarting the wallet :
addnode=node.biblepay.org
addnode=biblepay.inspect.network
gen=1
I just upgraded 5 min ago to 1.0.3.2 ..... no block souce available. ...
Hello. solo minig cannot synchronize with the network for 11 hours. What to do? purse Biblepay v1.0.3.2 version
Sorry, been gone debugging the problem with the new version. Kind of hard to find the root cause.
You'll never believe how dumb the problem is- the issue is with changing the DGW parameter, in mid stream, a certain block header between 7100-7250 causes an unprintable log error, and that actually takes down the whole wallet.
The key is to set a future block number for the subsidy increase. I obviously would have done that, but I was viewing this as Hey we need a mandatory lets just change it now.
Let me go back and set up the change and Ill get back in about 30 minutes.
You'll never believe how dumb the problem is- the issue is with changing the DGW parameter, in mid stream, a certain block header between 7100-7250 causes an unprintable log error, and that actually takes down the whole wallet.
The key is to set a future block number for the subsidy increase. I obviously would have done that, but I was viewing this as Hey we need a mandatory lets just change it now.
Let me go back and set up the change and Ill get back in about 30 minutes.
Jump to: