He got me back in.  Just make sure he knows you're updated.  In the future we should have the tell us when you're updated thread list all the delegates that have updated in the first post.  I think Dan is busy enough already without having to wade through six pages of a thread to see who is ready.

same here ..

Quote from: puppies on August 28, 2014, 06:15:33 PM
any particular reason that I have been voted out?

(mine too) look like a bunch of inits were brought in

any particular reason that I have been voted out?

Quote from: xeroc on August 28, 2014, 12:20:22 PM

Quote from: Riverhead on August 28, 2014, 12:11:07 PM
Anyone running a node and having it crash after a bit (perhaps due to a lot of connections) I wrote a simple script to keep it going. Now I just need to tail -f node.log in a small window to make sure it restarts itself.

screen start_node.sh
tail -f node.log

Code Select Expand



while [ 1=1 ] ; do
echo "Starting node server" >>node.log
bitshares_client
echo "Balls, crashed" >> node.log
sleep 5
done


in short

Code Select Expand


while true; do ./bitshares_client; done


+5% +5% +5%, this will make life easier for the guys running seed nodes.

www.minebitshares-com
www2.minebitshares-com

Delegates now upgrades to 0.4.9

Node Server: 188.226.195.137:60696 updated to 0.4.9

network_add_node "188.226.195.137:60696" add


{
  "blockchain_head_block_num": 339290,
  "blockchain_head_block_age": "2 seconds old",
  "blockchain_head_block_timestamp": "2014-08-28T15:35:40",
  "blockchain_average_delegate_participation": "90.18 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "155,244.02643 BTSX",
  "blockchain_delegate_pay_rate": "1.28343 BTSX",
  "blockchain_share_supply": "1,999,930,605.40256 BTSX",
  "blockchain_blocks_left_in_round": 70,
  "blockchain_next_round_time": "at least 12 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-28T15:47:20",
  "blockchain_random_seed": "cbed8e07c7e937629f0032a484570a12202ca0ec",
  "client_data_dir": "/home/ihashfury/.BitSharesX",
  "client_version": "0.4.9",
  "network_num_connections": 36,
  "network_num_connections_max": 36,
  "ntp_time": "2014-08-28T15:35:42",
  "ntp_time_error": -0.0016199999999999999,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "3 years 2 months in the future",
  "wallet_unlocked_until_timestamp": "2017-10-28T20:08:40",
  "wallet_last_scanned_block_timestamp": "2014-08-27T15:52:40",
  "wallet_scan_progress": "? %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

Quote from: vikram on August 28, 2014, 02:27:58 PM

Quote from: Riverhead on August 28, 2014, 11:10:05 AM
I have created a node and chain server:


Node Server: 104.131.35.149:1776

Will you be keeping this up so that we can add to the list of default seed nodes?

Yes. I have rented another Droplet as a dedicated node and chain server. It will be funded from my delegate.


Updated max connections to 200 to help get us passed this initial sync frenzy.

Quote from: Riverhead on August 28, 2014, 11:10:05 AM
I have created a node and chain server:


Node Server: 104.131.35.149:1776

Will you be keeping this up so that we can add to the list of default seed nodes?

maqifrnswa and delegate1.maqifrnswa are now on 0.4.9

Quote from: Riverhead on August 28, 2014, 11:38:03 AM
I wonder if it would be smoother with a staggered release:

1) node/chain servers upgrade and fully snyc.

2) delegates upgrade and fully sync

3) release to masses now that infrastructure is up to date.


I know we can't wait for everyone but perhaps wait until 10 - 20 of each type to check in before updating the version on the DACSun website.

+5%

doxymoron-delegate updated.

delegate1.y8 have finished updated

Quote from: Riverhead on August 28, 2014, 11:38:03 AM
I wonder if it would be smoother with a staggered release:

1) node/chain servers upgrade and fully snyc.

2) delegates upgrade and fully sync

3) release to masses now that infrastructure is up to date.


I know we can't wait for everyone but perhaps wait until 10 - 20 of each type to check in before updating the version on the DACSun website.

I agree this is how it should be done.    I am attempting to gain my bearings on what is going on now that I am in the office.

1) Looks like my 0.4.8 OS X GUI still has 8 connections and 97% delegate participation!   Good work guys.
2) My 0.4.9 command line client (OSX) fully synced from last night, attempting a fresh sync (so far so good, 8 connections from scratch)
3) About to test out 0.4.9 OS X GUI to see where we get....

Update:  fully connected from a fresh start with 7 connections.   Now for the GUI.

Quote from: xeroc on August 28, 2014, 12:20:22 PM
in short

Code Select Expand


while true; do ./bitshares_client; done


That works well too but I wanted something to watch :).