I updated and everything seemed to work properly.
As soon as I published price feeds I started missing blocks.
emski (unlocked) >>> info
{
"blockchain_head_block_num": 227738,
"blockchain_head_block_age": "5 seconds old",
"blockchain_head_block_timestamp": "2014-08-15T07:17:00",
"blockchain_average_delegate_participation": "91.82 %",
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "153,146.14196 BTSX",
"blockchain_delegate_pay_rate": "1.26608 BTSX",
"blockchain_share_supply": "1,999,957,225.95763 BTSX",
"blockchain_blocks_left_in_round": 17,
"blockchain_next_round_time": "3 minutes in the future",
"blockchain_next_round_timestamp": "2014-08-15T07:19:50",
"blockchain_random_seed": "14bfd263fd0987fa90ce853b16c3461e89f4524e",
"client_data_dir": "/home/emski/bitsharesnodeTock/bitsharesx/programs/client/dd4.0",
"network_num_connections": 66,
"network_num_connections_max": 200,
"ntp_time": "2014-08-15T07:17:05",
"ntp_time_error": -0.0043769999999999998,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "37 minutes in the future",
"wallet_unlocked_until_timestamp": "2014-08-15T07:53:41",
"wallet_scan_progress": "? %",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": "at least 3 minutes in the future",
"wallet_next_block_production_timestamp": null
}
emski (unlocked) >>> blockchain_list_blocks
HEIGHT TIMESTAMP SIGNING DELEGATE # TXS SIZE TOTAL FEES LATENCY PROCESSING TIME
===================================================================================================================
227738 2014-08-15T07:17:00 dpos.crazybit 0 166 0.00000 BTSX 0 0.004883
227737 2014-08-15T07:16:50 fox 0 166 0.00000 BTSX 0 0.000117
MISSED 2014-08-15T07:16:40 lotto-delegate N/A N/A N/A N/A N/A
227736 2014-08-15T07:16:30 init34 0 166 0.00000 BTSX 0 0.002168
And where is my console.log ?
Output from 3.1 client:
227736
6b6301bb71de964c1a8f759f304316a3f6417967 lotto-delegate 2 502 2014-08-15T07:16:40 0 NO NO
71f889b8659ff455185586ebedca7e99a21a59bf fox 0 166 2014-08-15T07:16:50 0 YES YES
227744
704bd508f16573c486e8ba828026f257364cc340 delegate.webber 0 166 2014-08-15T07:18:10 0 YES NO
61d53df45eebe57e9f81632dc27eb845ced89d3e delegate.webber 0 166 2014-08-15T07:18:10 0 YES YES
REASONS FOR INVALID BLOCKS
6b6301bb71de964c1a8f759f304316a3f6417967: 10 assert_exception: Assert Exception
converter_itr != _converters.end():
{}
th_a operations.cpp:62 to_variant
{}
th_a operations.cpp:64 to_variant
{"trx_num":0}
th_a chain_database.cpp:1003 apply_transactions
What if the delegate in the round just after me hasn't updated?
When we are required to publish price feeds?
Should we do it for all currencies ?
Not sure if this is related to 0.4.0 delegates vs 0.3.1 but I'm see this. Note that I haven't missed a block because of this. I have not published a feed yet.
Peer 104.131.134.181:51145 disconnected us: You offered us a block that we reject as invalid
Peer 106.185.24.234:39314 disconnected us: You offered us a block that we reject as invalid
hm .. my backup system successfully upgraded and produced blocks .. when switching to the main system with 0.4.0 he missed blocks ... wlthough all seemed fine ..
strange .. looking into ito
//edit: seems I needed to reanble block production
Do not publish price feeds until after hardfork and all clients are upgraded. This is a new operation that is part of the hardfork. All old clients will reject blocks containing publish price feed operation. This is the reason for missed blocks.
Large transaction and block sizes are also part of the hardfork, and could result in missed blocks.
console.log was disabled by default in previous update for security concerns. It can be enabled using --log-commands argument.
Delegates are still free to upgrade but must be aware that there a crashing issue has been identified. Brave delegates can upgrade and run client in a debugger to help us get a stack trace of the crash.
Show Posts
