Here is a snipit from a post I made elsewhere:

My experience is with Ubuntu.

Code: [Select]

sudo apt-get install ntp
Add some servers to the config file:

Code: [Select]

sudo nano /etc/npd.confserver ntp.ubuntu.com
server pool.ntp.org

So, I have reached this stage. It would appear from your answer that my keyhotee id is registered. How do I get it to ,show up in my wallet as an account?

help wallet_import_keyhotee

Usage:
wallet_import_keyhotee <firstname> <middlename> <lastname> <brainkey> <keyhoteeid>                    Create the key from keyhotee config and import it to the wallet, creating a new account using this key
Create the key from keyhotee config and import it to the wallet, creating a new account using this key

Parameters:
  firstname (name, required): first name in keyhotee profile config, for salting the seed of private key
  middlename (name, required): middle name in keyhotee profile config, for salting the seed of private key
  lastname (name, required): last name in keyhotee profile config, for salting the seed of private key
  brainkey (brainkey, required): brainkey in keyhotee profile config, for salting the seed of private key
  keyhoteeid (keyhoteeid, required): using keyhotee id as account name

Returns:
  void

wallet_import_keyhotee First Middle Last "Your brain key wrapped in double quotes." yourkeyhoteeid
Result:
  The registered Keyhotee ID will be claimed from the genesis block and placed in your wallet. 

I would recommend increasing the desired number of nodes you are connected to in order to minimize latency.

network_set_advanced_node_parameters { "peer_connection_retry_timeout": 30, "desired_number_of_connections": 50, "maximum_number_of_connections": 100 }
Currently --- there are now 23 active connections to the p2p network

I am interested in the procedure for troubleshooting missed block production and a fork. 

Case in point, block 20559:

blockchain_list_forks
...
20559
     4615a246a6b2e0ea88050c12a1989f914c631ac4                           fox              2       616 2014-07-21T15:10:40         0     YES                  NO
     36e26346e56e443d0beb50dcb44bb7bfd204acc6                          lion              1       390 2014-07-21T15:10:20        22     YES                 YES
...
In this mammalian quadruped battle for block production supremacy, the lion does best the fox even though showing up with a latency of 22 and fewer transactions. 

Is someone willing to enumerate the requisite steps to troubleshoot the blockchain production with me?

wallet_approve_delegate fox


I feel Keyhotee Founders should be granted Delegate status within the genisis block. Founders need to enable block production if they choose to provide this service. Founders still need to be Approved by stakeholders.

I believe the seed node(s) are not functioning properly. 

I have read many reports of stuck at 1034 and 2071.  I too cannot get a fresh client to sync properly with the network.  My latest attempt was to force my client to connect to a single seed node.  Here is the output:
2:~/bitshares_toolkit/programs/client$ ./bitshares_client --p2p-port 8902 --max-connections 1 --clear-peer-database --resync-blockchain --connect-to 107.170.30.182:8903 --disable-default-peers --disable-peer-advertising
Deleting old copy of the blockchain in "/home/XTSAdmin/.BitSharesXTS/chain"
Loading config "/home/XTSAdmin/.BitSharesXTS/config.json"
Initializing genesis state from built-in genesis file
Please be patient, this could take a few minutes.
Successfully re-indexed 0 blocks in 0 seconds.
Not starting RPC server, use --server to enable the RPC interface
Attempting to map P2P port 8902 with UPNP...
Erasing old peer database
Listening for P2P connections on port 8902
Attempting to connect to peer 107.170.30.182:8903
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 2271 blocks left to fetch
--- syncing with p2p network, our last block was created 7 hours ago
--- syncing with p2p network, our last block was created 6 hours ago
--- syncing with p2p network, our last block was created 5 hours ago
I am disconnecting peer 107.170.30.182:8903 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1236 blocks left to fetch
(wallet closed) >>>

Note: the client first tells us there are 2271 blocks to fetch. 
Note: the client is disconnected at block 1034, reconnects and looks for the 1236 blocks to fetch, but fails to do so. 

(wallet closed) >>> about
{
  "bitshares_toolkit_revision": "23cd03536932cfbc081de47586316586c2fb16c4",
  "bitshares_toolkit_revision_age": "5 hours ago",
  "fc_revision": "06fe9e0303b10f8cd6ef6a8da506495e5b113c39",
  "fc_revision_age": "16 hours ago",
  "compile_date": "compiled on Jul 16 2014 at 03:06:57"
}
(wallet closed) >>> config
{
  "blockchain_id": "4b9f25c5e7204fd2af460d7a63fad3ce758e873ade2679c6ac14cfb62d4f05a7"
  ...
}
Does anyone have a peer node IP:PORT properly synced beyond block 2071 that I may connect to?