Show Posts
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.
I have another problem, when I restart witness_node, usually it takes a long time to get connected to network, and sometimes won't get connected at all.
I have added a new section Tips on the wiki.
https://github.com/cryptonomex/graphene/wiki/How-to-setup-your-witness-for-test-net-(Ubuntu-14.04)
So if you have any tips, you can add them there if is not general setup. I have just added spartako's from the previous post.
Also I have put some credits to list everyone
Code: [Select]3508896ms th_a application.cpp:265 startup ] Detected unclean shutdown. Replaying blockchain...It takes too much time to replay blockchain.. How to "cleanly" shutdown the witness node?
Question bump.
I have found this error in my witness:Looks like you're on a fork.. Try restart, if it happen again try restart with --resync-blockchain.Code: [Select]1249999ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.4231 production slot has arrived; generating a block now...
1250000ms th_a witness.cpp:266 block_production_loo ] Got exception while generating block:
10 assert_exception: Assert Exception
_consecutive_production_enabled || db.get_dynamic_global_properties().current_witness != scheduled_witness: Last block was generated by the same witness, this node is probably disconnect
ed from the network so block production has been disabled. Disable this check with --allow-consecutive option.
{}
th_a witness.cpp:248 block_production_loop
Is it related to p2p problem?
1249999ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.4231 production slot has arrived; generating a block now...
1250000ms th_a witness.cpp:266 block_production_loo ] Got exception while generating block:
10 assert_exception: Assert Exception
_consecutive_production_enabled || db.get_dynamic_global_properties().current_witness != scheduled_witness: Last block was generated by the same witness, this node is probably disconnect
ed from the network so block production has been disabled. Disable this check with --allow-consecutive option.
{}
th_a witness.cpp:248 block_production_loop
That's odd spartako I seeCode: [Select]ocked >>> get_witness spartako
get_witness spartako
{
"id": "1.6.4231",
"witness_account": "1.2.72727",
"signing_key": "GPH5mgup8evDqMnT86L7scVebRYDC2fwAWmygPEUL43LjstQegYCC",
"next_secret_hash": "7933c3cad5ce7cf05646dd36a4da6882fbd74255",
"previous_secret": "311664bc1ac2a3accdc31761f36835c9c985b1e2",
"pay_vb": "1.13.185",
"vote_id": "1:4231",
"total_votes": "64999598829",
"url": ""
But I don't see you in info. I do see double representations of 1.6.1526 1530 1537 and 1595 so maybe it's a display issue.
In regards to checking witness stats. I don't think there is currently a way to see them directly. You can use the get_witness command to check that the next secret hash and previous secret are changing. Watch your witness node for your witness number or use the gui and go to the block explorer page.
Also great job betax, and thanks for the nodes abit.
get_witness spartako
{
"id": "1.6.4231",
"witness_account": "1.2.72727",
My delegate feeds (spartako,spartako1,spartako2) are updated with xeroc script.Would you please update your script again .. I skrew up big time with the last commit ..
https://github.com/xeroc/bitshares-pytools/commit/58e3dbb8fb1ca8c98eb553da1b1b582326b12e8d#diff-27bb350ac3c5ac68778a08476c884d8eR225
I noticed today that three different prices exist on the blockchain .. namely:
- the old price
- the new price
- 1/the new price
the letter was my mistake (a dumb one)
fixed it in a new commit ..
Also:
Because the price feed is derived from the MEDIAN of all feeds and we just "changed" the rules, we should first make the market stop entirely instead of having highly inconsistent prices that fuck up the MEDIAN!
Hence, I do not publish the index prices untill at least 51 delegate are willing to publish the NEW price!
