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

while true; do ./bitshares_client; done


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



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


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.

As I said before - sync with 0.4.8 and then use the same data-dir for 0.4.9.

Quote from: testz on August 28, 2014, 11:13:11 AM

Can't connect.  :(

Looks like my node is still syncing. Might explain a lot of issues we're seeing if most of the seeds are either pre-fork or still syncing.


  "blockchain_head_block_num": 135386,
  "blockchain_head_block_age": "24 days old",
  "blockchain_head_block_timestamp": "2014-08-04T10:04:30",
  "blockchain_average_delegate_participation": "0.05 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "131,570.66965 BTSX",
  "blockchain_delegate_pay_rate": "1.08772 BTSX",
  "blockchain_share_supply": "1,999,970,644.53254 BTSX",
  "blockchain_blocks_left_in_round": 55,
  "blockchain_next_round_time": "at least 9 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-28T11:28:10",
  "blockchain_random_seed": "e9576da879344a18b126333ab971f57a47d4aad0",
  "client_data_dir": "/home/riverhead/.BitSharesX",
  "client_version": "0.4.9",
  "network_num_connections": 28,
  "network_num_connections_max": 100,
  "ntp_time": "2014-08-28T11:19:05",
  "ntp_time_error": -0.028185999999999999,


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


Chain Server: 104.131.35.149:1775

Can't connect.  :(

I have created a node and chain server:


Node Server: 104.131.35.149:1776


Chain Server: 104.131.35.149:1775

updated to 0.4.9 and running smoothly

liondani
liondani-delegate-1

please vote for
delegate.liondani
so I can remove my 2 current active delegates

Updated to 0.4.9

updated to 0.4.9

wackou-delegate on 0.4.9 too, up and running

upgraded to 0.49

delegate ID : chinese

done.

bts.coin
e.coin
bimin.coin

Delegate ID:d.e
Delegate ID:delegate.eureka

but why not connected ？

Delegate ID:dnsdac
upgraded  to 0.4.9  and running smoothly
vote me in  :D