+500%

well (unlocked) >>> info
{
  "blockchain_head_block_num": 0,
  "blockchain_head_block_time": "20140620T015641",
  "blockchain_head_block_time_rel": "0 second old",
  "blockchain_confirmation_requirement": 202,
  "blockchain_average_delegate_participation": 0,
  "network_num_connections": 0,
  "ntp_time": "20140620T015641.483649",
  "ntp_error_seconds": -0.076316999999999996,
  "wallet_unlocked_seconds_remaining": 9999553,
  "wallet_next_block_production_time": "20140620T015800",
  "wallet_seconds_until_next_block_production": 79,
  "wallet_local_time": "20140620T015641",
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "blockchain_shares": 9999999984056,
  "network_num_connections_max": 12,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20141013T193554",
  "wallet_version": 100
}


The same issue occurred on my server.
Can anyone use the network_get_peer_info command , and give me an available node.
I should manually to add the available node.

I manually add a nodes to fixed my problems.

network_add_node "80.240.133.79:55577" "add"

But how can I know the node is correctly on the main chain?

Quote from: welk1n on June 16, 2014, 07:57:34 am

Quote from: xeroc on June 16, 2014, 07:23:03 am

Quote from: welk1n on June 16, 2014, 07:19:33 am

updated the latest codes

but it shows

Code: [Select]

wang (unlocked) >>> info
{
  "blockchain_head_block_num": 0,
  "blockchain_head_block_time": "20140616T071527",
  "blockchain_head_block_time_rel": "0 second old",
  "blockchain_confirmation_requirement": 194,
  "blockchain_average_delegate_participation": 0,
  "network_num_connections": 0,
  "wallet_unlocked_seconds_remaining": 9999891,
  "wallet_next_block_production_time": "20140616T071615",
  "wallet_seconds_until_next_block_production": 48,
  "wallet_local_time": "20140616T071527",
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "blockchain_shares": 9999999983936,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20141010T010018",
  "wallet_version": 100
}
wang (unlocked) >>> about
{
  "bitshares_toolkit_revision": "bb16f2323fe66c31e6b8de8f5c774c7b35c877b5",
  "bitshares_toolkit_revision_age": "10 hours ago",
  "fc_revision": "888a01881aa5aa1313509aa7044455cac02359dc",
  "fc_revision_age": "13 hours ago",
  "compile_date": "compiled on Jun 16 2014 at 15:10:43"
}



You are not yet synced .. I run the same code. All fine here ..

Quote

  "network_num_connections": 0,

[/b]
Seems to be a connection issue at your end

This is very strange.
Yesterday, the node is working good, there are almost 7 connections all the time.
I just compile the latest.

more info:

Code: [Select]

wang (unlocked) >>> network_list_potential_peers
ENDPOINT                 LAST SEEN                LAST CONNECT ATTEMPT     SUCCESSFUL CONNECT ATTEMPTS   FAILED CONNECT ATTEMPTS       LAST CONNECTION DISPOSITION        LAST ERROR                   
114.215.104.153:8764     1970-01-01T00:00:00      2014-06-16T07:52:50      0                             12                            last_connection_failed             0 exception: unspecified
Broken pipe
    {"message":"Broken pipe"}
    asio  asio.cpp:28
84.238.140.192:8764      1970-01-01T00:00:00      2014-06-16T07:52:50      0                             12                            last_connection_failed             0 exception: unspecified
Broken pipe
    {"message":"Broken pipe"}
    asio  asio.cpp:28
107.170.30.182:8764      1970-01-01T00:00:00      2014-06-16T07:52:50      0                             12                            last_connection_failed             9 canceled_exception: Canceled
Operation canceled
    {"message":"Operation canceled"}
    asio  asio.cpp:45
wang (unlocked) >>>
wang (unlocked) >>>
wang (unlocked) >>> network_get_peer_info
[]


delete your peer database

I  delete the .BitSharesXTS absolutely.

updated the latest codes

but it shows
wang (unlocked) >>> info
{
  "blockchain_head_block_num": 0,
  "blockchain_head_block_time": "20140616T071527",
  "blockchain_head_block_time_rel": "0 second old",
  "blockchain_confirmation_requirement": 194,
  "blockchain_average_delegate_participation": 0,
  "network_num_connections": 0,
  "wallet_unlocked_seconds_remaining": 9999891,
  "wallet_next_block_production_time": "20140616T071615",
  "wallet_seconds_until_next_block_production": 48,
  "wallet_local_time": "20140616T071527",
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "blockchain_shares": 9999999983936,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20141010T010018",
  "wallet_version": 100
}
wang (unlocked) >>> about
{
  "bitshares_toolkit_revision": "bb16f2323fe66c31e6b8de8f5c774c7b35c877b5",
  "bitshares_toolkit_revision_age": "10 hours ago",
  "fc_revision": "888a01881aa5aa1313509aa7044455cac02359dc",
  "fc_revision_age": "13 hours ago",
  "compile_date": "compiled on Jun 16 2014 at 15:10:43"
}



Quote from: Troglodactyl on June 15, 2014, 01:59:11 pm

FWIW: Last night I updated, which put me at 3-4 connections after launch instead of 1.  I manually added nodes until I was up to about 9, and left it for the night.  This morning I was down to 5, and apparently on a fork quite a few blocks behind on the chain.  My suspicion is that the cause is too many leaf nodes all on the old version so they only have one connection.

I am running with old version (built more than 30 hours ago) and now has 12 connections.

Suggestion: Is it possible to have a command that allows us to list the blocks produced by a given delegate account name?
like blocks_produced_by_delegate <delegate_account_name>

Maybe you can use the  wallet_get_account commands


welk1n (unlocked) >>> wallet_get_account init-delegate-33
{
  "index": 10,
  "id": 33,
  "name": "init-delegate-33",
  "public_data": null,
  "owner_key": "XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA",
  "active_key_history": [[
      "20140615T021914",
      "XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA"
    ]
  ],
  "delegate_info": {
    "votes_for": 99732150532,
    "votes_against": 0,
    "blocks_produced": 137,
    "blocks_missed": 18,
    "pay_balance": 5988191,
    "next_secret_hash": "419c0a4c97a2ea0847778747fdb7c5470ac6a1e6",
    "last_block_num_produced": 6140
  },
  "registration_date": "20140601T000000",
  "last_update": "20140601T000000",
  "meta_data": null,
  "account_address": "XTSG6FH3Q32yVgoafyJLnPS5JTo9juK5rWY4",
  "trust_level": 0,
  "private_data": null
}

Quote from: welk1n on June 15, 2014, 03:23:50 am

It is working well now ?

Code: [Select]

--- there are now 4 active connections to the p2p network
welk1n (unlocked) >>> info
{
  "blockchain_head_block_num": 5654,
  "blockchain_head_block_time": "20140615T032230",
  "blockchain_head_block_time_rel": "32 seconds ago",
  "blockchain_confirmation_requirement": 285,
  "blockchain_average_delegate_participation": 61.237373737373737,
  "network_num_connections": 4,
  "wallet_unlocked_seconds_remaining": 9996219,
  "wallet_next_block_production_time": "20140615T032915",
  "wallet_seconds_until_next_block_production": 373,
  "wallet_local_time": "20140615T032302",
  "blockchain_random_seed": "ca281b06e58c7f9f52d211baf7911bf38691525d",
  "blockchain_shares": 10000092853224,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20141008T200641",
  "wallet_version": 100
}


Lookin' good!

 ,Thanks!
The four delegates of mine (30,31,32,33)
I use the blockchain_list_delegates commands .
It seems that  they produced blocks well.
Please vote them , thank you !

Am I on the main chain?

welk1n (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            TRUST LEVEL   
welk1n-d-5                         XTS6z7aMnBmXi7qL9uHfgWS6d1wedEpvQNTrwgeGb8h1MH9WVXtRC           NO                    0             
init-delegate-33 *                 XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA           2014-06-01T00:00:00   0             
init-delegate-32 *                 XTS7p56UNQLyWc3NB2yeT4VVtYhanf6wFC356c6vbfpvQ9CHUmg6X           2014-06-01T00:00:00   0             
init-delegate-31 *                 XTS5urryfpdjZgwavKwufJ9A1d816LFaPbSQLu5eP2G76B7hbtuxj           2014-06-01T00:00:00   0             
init-delegate-30 *                 XTS6f8fzmUDQp63nTYgsA2GQtvFoPvKrmTmuhkCvQUCnKUJwxTxtx           2014-06-01T00:00:00   0             
"OK"
welk1n (unlocked) >>> info
{
  "blockchain_head_block_num": 452,
  "blockchain_head_block_time": "20140613T060600",
  "blockchain_confirmation_requirement": 290,
  "blockchain_average_delegate_participation": 27.713059472716125,
  "network_num_connections": 7,
  "wallet_unlocked_seconds_remaining": 997346,
  "wallet_next_block_production_time": "20140613T060700",
  "wallet_seconds_until_next_block_production": 52,
  "wallet_local_time": "20140613T060608",
  "blockchain_random_seed": "32fa7e7088b6984898073462f227a7e24c9e5630",
  "blockchain_shares": 9999980679465,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20140624T190834",
  "wallet_version": 100
}