Main > Stakeholder Proposals
--> All Delegates: Please upgrade to 0.4.27.1 ASAP <--
iHashFury:
Delegate updated to v0.4.27.1
I had some issues with sending funds to publish feeds but all is well again 8)
Riverhead:
--- Quote from: emski on December 18, 2014, 06:41:51 am ---
--- Quote from: Riverhead on December 18, 2014, 02:23:42 am ---
--- Quote from: bytemaster on December 17, 2014, 09:52:51 pm ---
--- Quote from: emski on December 17, 2014, 08:16:33 pm ---Isn't the multiple chains block signing a security issue ?
How can one be sure that his client is on the right chain with 60% delegate participation if 40% of these delegates sign in two chains ?
--- End quote ---
That is a delegate issue based upon their use of their custom software. It should be a fireable offense to produce on more than one chain.
--- End quote ---
Currently we need to develop all our support scripts in production environments. DevShares will be a nice change of stress.
--- End quote ---
.
Why don't you just try to theoretically explain the delegate backup system first?
--- End quote ---
Sorry Emski, I didn't see this question until now. What happened with my delegate wasn't an automated backup system. Currently I have no scripts in place that detect one node missing blocks to enable another. I have ideas about that but have been too afraid of signing on two chains (ya, I know :P ). What happened the other night was a setup designed to survive a reboot kicked in when the instance rebooted. The scripts didn't have a check to see if the node was active before reboot. I have since moved the wallet directory to wallet.standby so that the node can still stay in sync without risk of it becoming unlocked.
It was a stupid oversight and I've paid for it; both literally and figuratively.
emski:
--- Quote from: Riverhead on December 18, 2014, 02:23:42 am ---
--- Quote from: bytemaster on December 17, 2014, 09:52:51 pm ---
--- Quote from: emski on December 17, 2014, 08:16:33 pm ---Isn't the multiple chains block signing a security issue ?
How can one be sure that his client is on the right chain with 60% delegate participation if 40% of these delegates sign in two chains ?
--- End quote ---
That is a delegate issue based upon their use of their custom software. It should be a fireable offense to produce on more than one chain.
--- End quote ---
Currently we need to develop all our support scripts in production environments. DevShares will be a nice change of stress.
--- End quote ---
Why don't you just try to theoretically explain the delegate backup system first?
Riverhead:
--- Quote from: bytemaster on December 17, 2014, 09:52:51 pm ---
--- Quote from: emski on December 17, 2014, 08:16:33 pm ---Isn't the multiple chains block signing a security issue ?
How can one be sure that his client is on the right chain with 60% delegate participation if 40% of these delegates sign in two chains ?
--- End quote ---
That is a delegate issue based upon their use of their custom software. It should be a fireable offense to produce on more than one chain.
--- End quote ---
Currently we need to develop all our support scripts in production environments. DevShares will be a nice change of stress.
alt:
I have update to 0.4.27.1, but offen stop sync. here is some information
stop at block 1288364
--- Code: --- "blockchain_head_block_num": 1288364,
"blockchain_head_block_age": "12 minutes old",
"blockchain_head_block_timestamp": "2014-12-18T01:54:20",
"blockchain_average_delegate_participation": "52.33 %",
--- End code ---
there is a fork at here
--- Code: --- 1288363
1e52304898b7e133a3c5f70e28fc2e98642d98b4 bitsharesx-delegate 4 4042 2014-12-18T01:54:20 0 YES NO
44bd8acf6b7d9f6a11158c8a87652b1e2a29f739 black-widow 3 3798 2014-12-18T01:54:30 0 N/A NO
--- End code ---
and from the log file, it can't find block 1288364 at database
--- Code: ---2014-12-18T01:54:40 th_a:invoke handle_message switch_to_fork ] pop 1e52304898b7e133a3c5f70e28fc2e98642d98b4 chain_database.cpp:693
2014-12-18T01:54:40 th_a:invoke handle_message push_block ] fork permanently rejected as it has permanently invalid block chain_database.cpp:1745
2014-12-18T01:54:40 p2p:message read_loop process_block_during ] Successfully pushed block 1288365 (id:75bda8624c5b6d389683a549701cccd55762ea2a) node.cpp:3050
2014-12-18T01:54:41 p2p:message read_loop read_loop ] message transmission failed 6 key_not_found_exception: Key Not Found
unable to find key 1288364
{"key":1288364}
th_a level_map.hpp:102 fetch
error fetching key 1288364
{"key":1288364}
th_a level_map.hpp:112 fetch
{"block_num":1288364}
th_a chain_database.cpp:1647 get_block message_oriented_connection.cpp:165
2014-12-18T01:54:41 p2p:message read_loop read_loop ] disconnected 6 key_not_found_exception: Key Not Found
--- End code ---
I have to restart client, then it can sync again.
Navigation
[0] Message Index
[#] Next page
Go to full version