This seems to have been the same problem as reported here: https://bitsharestalk.org/index.php?topic=13469.msg176001#msg176001

Quote from: liondani on January 31, 2015, 06:05:36 PM
when the active connections drop we get an output on the cli client that informs us...
can we get something identical for the participation rate? For example when it drops to 90%,80%,70%etc  we should have an output...
so on occasions  like this, we could check easily if our client also lost significant participation rate as mentioned on this thread ...  I can't know for sure if that was the case with mine... (or can I check it somehow?)

There is a warning in the client if the delegate participation drops below a reasonable threshold. It's even color coded for different "levels" as I recall. Oh, sorry, just saw the cli part of that... Sounds like a good idea.

when the active connections drop we get an output on the cli client that informs us...
can we get something identical for the participation rate? For example when it drops to 90%,80%,70%etc  we should have an output...
so on occasions  like this, we could check easily if our client also lost significant participation rate as mentioned on this thread ...  I can't know for sure if that was the case with mine... (or can I check it somehow?)

We're looking into the cause now for the duplicate transaction error that caused the loss of delegate participation. We worked around the problem for now by temporarily configuring some delegates to one transaction per block, and now the duplicate transactions appear to have expired.

We are back:

default (unlocked) >>> getinfo
{
  "blockchain_head_block_num": 1668905,
  "blockchain_head_block_age": "3 seconds old",
  "blockchain_head_block_timestamp": "2015-01-31T17:18:50",
  "blockchain_average_delegate_participation": "98.06 %",
  "blockchain_confirmation_requirement": 201,
  "blockchain_share_supply": "2,499,305,921.71248 BTS",
  "blockchain_blocks_left_in_round": 19,
  "blockchain_next_round_time": "at least 3 minutes in the future",
  "blockchain_next_round_timestamp": "2015-01-31T17:22:00",
  "blockchain_random_seed": "22afd0ccc3dd0885b95c2b8fe9e5f04dd942ce96",
  "client_data_dir": "/home/fabiux/.BitShares",
  "client_version": "v0.5.3",
  "network_num_connections": 20,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2015-01-31T17:18:53",
  "ntp_time_error": 0.000386,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "31 years  in the future",
  "wallet_unlocked_until_timestamp": "1910-09-03T12:23:58",
  "wallet_last_scanned_block_timestamp": "2014-07-24T09:23:30",
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "2 minutes in the future",
  "wallet_next_block_production_timestamp": "2015-01-31T17:21:00"
}



It seems recovery now...

default (unlocked) >>> getinfo
{
  "blockchain_head_block_num": 1668892,
  "blockchain_head_block_age": "6 seconds old",
  "blockchain_head_block_timestamp": "2015-01-31T17:16:40",
  "blockchain_average_delegate_participation": "78.29 %",
  "blockchain_confirmation_requirement": 214,
  "blockchain_share_supply": "2,499,305,711.11248 BTS",
  "blockchain_blocks_left_in_round": 32,
  "blockchain_next_round_time": "at least 5 minutes in the future",
  "blockchain_next_round_timestamp": "2015-01-31T17:22:00",
  "blockchain_random_seed": "b9d0c9d5a41b8daf2eea383439fee47bc5cb3a64",
  "client_data_dir": "/home/fabiux/.BitShares",
  "client_version": "v0.5.3",
  "network_num_connections": 8,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2015-01-31T17:16:46",
  "ntp_time_error": 0.00038699999999999997,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "31 years  in the future",
  "wallet_unlocked_until_timestamp": "1910-09-03T12:23:58",
  "wallet_last_scanned_block_timestamp": "2014-07-24T09:23:30",
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "4 minutes in the future",
  "wallet_next_block_production_timestamp": "2015-01-31T17:21:00"
}



Nothing to worry about.
It is OK now.
Devs should explain what happened exactly soon.

{
  "alert_level": "red",
  "estimated_confirmation_seconds": 2570,
  "participation_rate": 33.892617449664428
}

lots of delegates dropped off the network?

wtf is going on????


>> security_state

{
  "alert_level": "red",
  "estimated_confirmation_seconds": 2600,
  "participation_rate": 34.121621621621621
}

Me too I have problem:


default (unlocked) >>> getinfo
{
  "blockchain_head_block_num": 1668809,
  "blockchain_head_block_age": "10 seconds old",
  "blockchain_head_block_timestamp": "2015-01-31T17:02:30",
  "blockchain_average_delegate_participation": "34.12 %",
  "blockchain_confirmation_requirement": 293,
  "blockchain_share_supply": "2,499,304,553.71248 BTS",
  "blockchain_blocks_left_in_round": 14,
  "blockchain_next_round_time": "at least 2 minutes in the future",
  "blockchain_next_round_timestamp": "2015-01-31T17:05:00",
  "blockchain_random_seed": "8075a4cb127f2c30fbda349d24566de34667a95a",
  "client_data_dir": "/home/fabiux/.BitShares",
  "client_version": "v0.5.3",
  "network_num_connections": 19,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2015-01-31T17:02:40",
  "ntp_time_error": -0.005666,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "31 years  in the future",
  "wallet_unlocked_until_timestamp": "1910-08-25T18:24:59",
  "wallet_last_scanned_block_timestamp": "2014-07-24T09:23:30",
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "at least 2 minutes in the future",
  "wallet_next_block_production_timestamp": "2015-01-31T17:07:50"
}



on bitsharesblocks and my delegates

was showing 21 minutes old for block 1668785

flush peers and restarted now showing 5 secs old block 1668786

anyone else?