4021
General Discussion / Re: Test Net for Advanced Users
« on: August 20, 2015, 10:00:36 pm »Let's join to the official testnetI'm in. Witness id 1.6.5247.
https://github.com/cryptonomex/graphene/releases/tag/test1
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Let's join to the official testnetI'm in. Witness id 1.6.5247.
https://github.com/cryptonomex/graphene/releases/tag/test1
Yeah. I just wasnt sure if there was something I had missed in the genesis, or if the minimum was coded into the client.Looks like we need a new genesis file.
This was answered when bm changed it in the client.
commit 2f0065d593dfd06deda970f9a8df59a930c50bff
Author: Daniel Larimer <dan@bitshares.org>
Date: Thu Aug 20 13:23:25 2015 -0400
genesis file specifies 101 min
Bytemaster is the minimum witness count hard coded or in the genesis?I think what he means is: if we vote in more witness (maybe include init witness) then the number of active witnesses will automatically increase.
Failed to push new blocks. What is exact command?Yes it's too late, and I'm re-syncing.
./witness_node -s 114.92.254.159:62015 --genesis-json aug-19-puppies-test-genesis.json
BM please check my comment on Github. https://github.com/cryptonomex/graphene/issues/247#issuecomment-132349244
So the real question is, why were we missing so many blocks? Who got voted in and why did you stop producing?
Actually there is a trick to restarting block production after so much time has passed.
First add a the following checkpoint
[HEADNUM+1, "00000000.....00"]
With that checkpoint you will be able to produce the next block. Once you have produced the block, other nodes can add a checkpoint with that freshly produced block and you will be up and running again.
Every time a checkpoint is reached it resets the required undo history to 0. Adding a checkpoint at HEADNUM will reset it to 0, but the next block you produce will have missed over 1000 blocks so is immediately beyond the reach. Therefore, we need to "checkpoint" the "next block" for which we do not know the ID yet.
So the real question is, why were we missing so many blocks? Who got voted in and why did you stop producing?
./witness_node ...... --checkpoint '[40903,"00009fc7e518d750f653ba0ca25a3067bd304f30"]'
[/s]I think it should be useful if slot < 1000. But we've missed more than 10000 blocks already.Did it get you going again? Seems to be still stuck or maybe you are on your own fork now? Which is your adress to use as seed-node?
I'm sure that I'm not on my own fork. Check this: http://45.55.6.216:8080/#/explorer/blocks or try 'info' command in cliwallet, my result is:Code: [Select]new >>> info
info
{
"head_block_num": 40902,
"head_block_id": "00009fc6d4e24db66e13af461b94063165999bfa",
"head_block_age": "4 hours old",
"next_maintenance_time": "4 hours ago",
"chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb",
...
}
OK, I see. So starting the witness-node with Checkpoint didn't make a difference then?
1117002ms th_a witness.cpp:240 block_production_loo ] slot: 14798 scheduled_witness: 1.6.1 scheduled_time: 2015-08
-20T11:18:37 now: 2015-08-20T11:18:37
1118002ms th_a witness.cpp:240 block_production_loo ] slot: 14799 scheduled_witness: 1.6.5248 scheduled_time: 2015
-08-20T11:18:38 now: 2015-08-20T11:18:38
1119002ms th_a witness.cpp:240 block_production_loo ] slot: 14800 scheduled_witness: 1.6.5247 scheduled_time: 2015-08-20T11:18:39 now: 2015-08-20T11:18:39
1119002ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.5247 production slot has arrived; generating a block now...
1119004ms th_a db_block.cpp:170 _push_block ] Failed to push new block:
3070000 undo_database_exception: undo database exception
General question (since I could not find this elsewhere):I don't know if there is a download link for the blockchain.
Is there a genuine place from where I can download "an up-to-date" BitShares blockchain? Setting up a new client is easy, but syncing it takes long and sometimes does not work such that the whole process needs to be repeated again and again (my slow little pc, c847/8gb, often has problems here and it takes days to re-sync/re-download the chain)... As such, it would be awesome to have an official and always "up-to-date" download link for the BitShares blockchain.
That said, my question is if such a download link is already there (and I could not find it), or would it be a great addition to the BitShare's homepage?
EDIT: Also 8gb ram seem sometimes not enough for a re-sync (using v0.9.2)... is that true? Did some one else make similar experiences?
Did it get you going again? Seems to be still stuck or maybe you are on your own fork now? Which is your adress to use as seed-node?
new >>> info
info
{
"head_block_num": 40902,
"head_block_id": "00009fc6d4e24db66e13af461b94063165999bfa",
"head_block_age": "4 hours old",
"next_maintenance_time": "4 hours ago",
"chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb",
...
}
...
{"recently_missed":47937,"max_undo":1000}
...
{"recently_missed":47981,"max_undo":1000}
...
{"recently_missed":48685,"max_undo":1000}
--checkpoint '[40902,"00009fc6d4e24db66e13af461b94063165999bfa"]' --enable-stale-production
1122000ms th_a witness.cpp:240 block_production_loo ] slot: 11203 scheduled_witness: 1.6.5247 scheduled_[967/1963]
-08-20T10:18:42 now: 2015-08-20T10:18:42
1122000ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.5247 production slot has arrived; generating a b
lock now...
1122001ms th_a db_block.cpp:170 _push_block ] Failed to push new block:
3070000 undo_database_exception: undo database exception
The database does not have enough undo history to support a blockchain with so many missed blocks. Please add a checkpoint if you woul
d like to continue applying blocks beyond this point.
{"recently_missed":44813,"max_undo":1000}
th_a db_update.cpp:72 update_global_dynamic_data
{"next_block.block_num()":40903}
th_a db_block.cpp:439 _apply_block
1122001ms th_a witness.cpp:266 block_production_loo ] Got exception while generating block:
3070000 undo_database_exception: undo database exception
The database does not have enough undo history to support a blockchain with so many missed blocks. Please add a checkpoint if you woul
d like to continue applying blocks beyond this point.
{"recently_missed":44813,"max_undo":1000}
th_a db_update.cpp:72 update_global_dynamic_data
{"next_block.block_num()":40903}
th_a db_block.cpp:439 _apply_block
{"new_block":{"previous":"00009fc6d4e24db66e13af461b94063165999bfa","timestamp":"2015-08-20T10:18:42","witness":"1.6.5247","next_s
ecret_hash":"a151bcbe08eac49feb4eb86a5a68f332b4e7cf9d","previous_secret":"2fa1e05db52f0c421e335648c21bb3707383c1d6","transaction_merkl
e_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"206ea3856d3cf6317f19ab6b5d3af6648409ac092eae9c
c8d943d7357e3ac9c753141733131d2312c4644d44125835afce24190d295c21a6a620920ab660ec5f5c","transactions":[]}}
th_a db_block.cpp:176 _push_block
{"witness_id":"1.6.5247"}
th_a db_block.cpp:315 _generate_block
Good idea. I am going to check how to set checkpoints. If you or anybody know please post here, thanks!I'm stuck at 40902 now. Looks like the testnet is dead again?
Yes, same for me, I was late for the party. If you already are a block producer maybe you can retsart your witness and try checkpointing option just for fun? Maybe you can get it back to life?
Option's obviously it's already there:
https://github.com/cryptonomex/graphene/blob/9c0c588ed62165886a510775d76c8524c50c09c5/libraries/app/application.cpp
Regards
{
"head_block_num": 40902,
"head_block_id": "00009fc6d4e24db66e13af461b94063165999bfa",
"head_block_age": "4 minutes old",
"next_maintenance_time": "31 seconds ago",
"chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb",
"active_witnesses": [
"1.6.0",
"1.6.1",
"1.6.2",
"1.6.1525",
"1.6.1536",
"1.6.4435",
"1.6.5245",
"1.6.5246",
"1.6.5247",
"1.6.5248",
"1.6.5249"
],
"active_committee_members": [
"1.5.0",
"1.5.1",
"1.5.2",
"1.5.3",
"1.5.4",
"1.5.5",
"1.5.6",
"1.5.7",
"1.5.8",
"1.5.9"
],
"entropy": "8927f3f36c4599a6a7af5a3cdfb70a8f57d463ae"
}
2015-08-20T07:11:59 th_a:invoke handle_block handle_block ] Got block #40902 from network application.cp
p:343
2015-08-20T07:12:00 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.4435 scheduled_time: 2015-08-2
0T07:12:00 now: 2015-08-20T07:12:00 witness.cpp:240
2015-08-20T07:12:01 th_a:Witness Block Production block_production_loo ] slot: 2 scheduled_witness: 1.6.5245 scheduled_time: 2015-08-2
0T07:12:01 now: 2015-08-20T07:12:01 witness.cpp:240
2015-08-20T07:12:02 th_a:Witness Block Production block_production_loo ] slot: 3 scheduled_witness: 1.6.1 scheduled_time: 2015-08-20T0
7:12:02 now: 2015-08-20T07:12:02 witness.cpp:240
2015-08-20T07:12:03 th_a:Witness Block Production block_production_loo ] slot: 4 scheduled_witness: 1.6.5247 scheduled_time: 2015-08-2
0T07:12:03 now: 2015-08-20T07:12:03 witness.cpp:240
2015-08-20T07:12:03 th_a:Witness Block Production block_production_loo ] Witness 1.6.5247 production slot has arrived; generating a bl
ock now... witness.cpp:243
2015-08-20T07:12:03 th_a:Witness Block Production _push_block ] Failed to push new block:
3070000 undo_database_exception: undo database exception
The database does not have enough undo history to support a blockchain with so many missed blocks. Please add a checkpoint if you would like to continue applying blocks beyond this point.
{"recently_missed":1006,"max_undo":1000}
th_a db_update.cpp:72 update_global_dynamic_data
{"next_block.block_num()":40903}
th_a db_block.cpp:439 _apply_block db_block.cpp:170