Dry Run 8: Need for Speed

[betax]

I pasted my PTS private key (the one used for snapshot) and it says imported, but no extra balance yet.

Does it allow only AGS balance? I badly want to be a delegate.

wallet_rescan_blockchain

[betax]

The issues I have experienced:

1. My number of connections got reduced to 4.
2. Blockchain was not updated for 2 hours, I assumed fork.
3. Stop, delete chain and peers and start again.
4. Connection number 1.
5. Stop, delete chain, peers and code and rebuilt.
6. Just now I got 5 connections.

Number of desired connections : 30 now 50.

[sumantso]

I pasted my PTS private key (the one used for snapshot) and it says imported, but no extra balance yet.

Does it allow only AGS balance? I badly want to be a delegate.

[xeroc]

  "blockchain_head_block_num": 4440,
  "blockchain_head_block_age": "1 second in the future",

as a result:

Code: [Select]

default (unlocked) >>> blockchain_list_blocks
HEIGHT  TIMESTAMP           SIGNING DELEGATE                # TXS   SIZE    TOTAL FEES      LATENCY PROCESSING TIME
-------------------------------------------------------------------------------------------------------------------
4441    2014-07-09T12:36:50 fox                             0       182     0.00000 XTS     0       0.002238       
MISSED  2014-07-09T12:36:40 delegate-baozi                  N/A     N/A     N/A             N/A     N/A           
4440    2014-07-09T12:36:30 crabbypattie-1                  0       182     0.00000 XTS     42949672910.002172    <<< ------------------------------


[emski]

  "blockchain_head_block_num": 4440,
  "blockchain_head_block_age": "1 second in the future",

Code: [Select]

emski2 (unlocked) >>> info
{
  "blockchain_head_block_num": 4440,
  "blockchain_head_block_age": "1 second in the future",
  "blockchain_head_block_timestamp": "20140709T123630",
  "blockchain_average_delegate_participation": 77.099236641221367,
  "blockchain_delegate_pay_rate": 36672310,
  "blockchain_blocks_left_in_round": 4,
  "blockchain_confirmation_requirement": 218,
  "blockchain_share_supply": 199682021837085,
  "blockchain_random_seed": "b3ab94ad9fb735e1f90d673acfb66918d77ac37d",
  "blockchain_database_version": 112,
  "blockchain_version": 105,
  "network_num_connections": 29,
  "network_num_connections_max": 500,
  "network_protocol_version": 104,
  "ntp_time": "20140709T123629",
  "ntp_error": 0.095741000000000007,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "17 weeks in the future",
  "wallet_unlocked_until_timestamp": "20141102T023531",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 101
}
emski2 (unlocked) >>> info
{
  "blockchain_head_block_num": 4440,
  "blockchain_head_block_age": "17 seconds old",
  "blockchain_head_block_timestamp": "20140709T123630",
  "blockchain_average_delegate_participation": 75.939849624060145,
  "blockchain_delegate_pay_rate": 36672310,
  "blockchain_blocks_left_in_round": 4,
  "blockchain_confirmation_requirement": 218,
  "blockchain_share_supply": 199682021837085,
  "blockchain_random_seed": "b3ab94ad9fb735e1f90d673acfb66918d77ac37d",
  "blockchain_database_version": 112,
  "blockchain_version": 105,
  "network_num_connections": 29,
  "network_num_connections_max": 500,
  "network_protocol_version": 104,
  "ntp_time": "20140709T123647",
  "ntp_error": 0.095741000000000007,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "17 weeks in the future",
  "wallet_unlocked_until_timestamp": "20141102T023531",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 101
}


[bitmeat]

I will have Eric work on making UPnP more robust.   Right now it considers you firewalled if you report a different IP than the server sees.

Are we using UDP or TCP? My point is, being able to receive a connection is also important since most are behind firewall.

Also - are all Windows clients behind firewall having the same problem?

[xeroc]

So I relaunched the seed node last night and forgot to unlock the wallet so that is why delegate participation was in the dumps. 

We have some kind of latent bug that only appears to show up after hours of operation where all of a sudden the connection count just starts falling off.  Our seed node dropped from 45 connections to 12 over time (no new connections).... I then relaunch it and it quickly climbed back up to 12.  I then increased the desired connection count and got up to 25. 

If other delegates are seeing similar behavior I would like to know.

.. same thing here

[xeroc]

For you delegates out there: 

Code: [Select]

network_set_advanced_node_parameters {"desired_number_of_connections":50,  "maximum_number_of_connections": 100}

This will maximize your connectivity.

That's what I run it with .. usually:

Code: [Select]

{
  "peer_connection_retry_timeout": 30,
  "desired_number_of_connections": 25,
  "maximum_number_of_connections": 64
}
Anyway .. I am again producing blocks .. no idea what happend that morning (GMT+1)

[bytemaster]

Running on Windows by the way...

Tried the param --min-delegate-connection-count 3 (added it to target in the shortcut)
Also did the desired connections set to 50. Still not producing blocks.

Still have only 4 connections. Should I forward a specific port from the firewall to my PC? Or is the client using UPnP?

I will have Eric work on making UPnP more robust.   Right now it considers you firewalled if you report a different IP than the server sees.

[bitmeat]

Running on Windows by the way...

Tried the param --min-delegate-connection-count 3 (added it to target in the shortcut)
Also did the desired connections set to 50. Still not producing blocks.

Still have only 4 connections. Should I forward a specific port from the firewall to my PC? Or is the client using UPnP?

[bytemaster]

So I relaunched the seed node last night and forgot to unlock the wallet so that is why delegate participation was in the dumps. 

We have some kind of latent bug that only appears to show up after hours of operation where all of a sudden the connection count just starts falling off.  Our seed node dropped from 45 connections to 12 over time (no new connections).... I then relaunch it and it quickly climbed back up to 12.  I then increased the desired connection count and got up to 25. 

If other delegates are seeing similar behavior I would like to know.

[bytemaster]

My delegates got disconnected .. had to resync the whole chain to be able to produce more blocks

For you delegates out there: 

Code: [Select]

network_set_advanced_node_parameters {"desired_number_of_connections":50,  "maximum_number_of_connections": 100}

This will maximize your connectivity.

[xeroc]

My delegates got disconnected .. had to resync the whole chain to be able to produce more blocks

[bitmeat]

You can override the required connection count until we figure out what is happening to connections:

--min-delegate-connection-count 3

Thank you, bytemaster! I'm off to bed...

Instructions didn't mention, but I would like to setup linux nodes that run constantly - is there a specific branch I should get the source code from for this Dry Run?

[bytemaster]

You can override the required connection count until we figure out what is happening to connections:

--min-delegate-connection-count 3