Quote from: xeroc on September 28, 2014, 01:49:01 PM
Interestingly, during compile .. the code takes the last git tag ... which seems to be the RC tag currently :)

If you ask me it doesn't picked up the last git tag... but it was a "random" selection....
for me it compiled v0.4.18 as you can see... (I updated today)

It's exactly the same tag for the 2 versions if you look closely! That's wired...

I am talking about this:

delegate (locked) >>>
delegate (locked) >>> info
{
  "blockchain_head_block_num": 603692,
  "blockchain_head_block_age": "0 second old",
  "blockchain_head_block_timestamp": "2014-09-28T13:47:30",
  "blockchain_average_delegate_participation": "98.06 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_delegate_pay_rate": "1.48840 BTSX",
  "blockchain_share_supply": "1,999,986,122.90940 BTSX",
  "blockchain_blocks_left_in_round": 86,
  "blockchain_next_round_time": "at least 14 minutes in the future",
  "blockchain_next_round_timestamp": "2014-09-28T14:01:50",
  "blockchain_random_seed": "4e8de10d66f38d1c58ef7ae1d73a83f78277f674",
  "client_data_dir": "/home/coin/.BitSharesX",
  "client_version": "v0.4.18-RC1",    <<<< ------------------------------------------------------
  "network_num_connections": 73,
  "network_num_connections_max": 200,
  "ntp_time": null,
  "ntp_time_error": null,
  "wallet_open": true,
  "wallet_unlocked": false,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

although I run the last code .. that tag seems to not be updated from the RC update ..

Interestingly, during compile .. the code takes the last git tag ... which seems to be the RC tag currently :)

I am on git-master and not on a particular tag .. that might be the cause

Quote from: xeroc on September 28, 2014, 01:15:37 PM
I updated to .. but my version field still states -RC .. how is yours?

Same problem, my states still v0.4.17 ...
I guess it's an issue for bitsharesblocks...
Before 20 minutes it stated it was 2000 blocks in past!!!
Could it be that his server are getting versions data every 30 minutes or something like that and not in "real time", just to let their server not taking to much resources ?

Quote
liondani (unlocked) >>> info
{
  "blockchain_head_block_num": 603657,
  "blockchain_head_block_age": "5 seconds old",
  "blockchain_head_block_timestamp": "2014-09-28T13:41:30",
  "blockchain_average_delegate_participation": "99.02 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_delegate_pay_rate": "1.48882 BTSX",
  "blockchain_share_supply": "1,999,986,130.65043 BTSX",
  "blockchain_blocks_left_in_round": 20,
  "blockchain_next_round_time": "at least 3 minutes in the future",
  "blockchain_next_round_timestamp": "2014-09-28T13:44:50",
  "blockchain_random_seed": "5502d9902df40bcb41263b703fb9c38c9c1d3ee0",
  "client_data_dir": "/home/liondani/.BitSharesX",
  "client_version": "v0.4.18",
  "network_num_connections": 16,
  "network_num_connections_max": 200,
  "ntp_time": "2014-09-28T13:41:35",
  "ntp_time_error": -0.016098999999999999,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "2 years 10 months in the future",
  "wallet_unlocked_until_timestamp": "2017-07-23T08:45:18",
  "wallet_last_scanned_block_timestamp": "2014-09-28T13:25:50",
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "at least 3 minutes in the future",
  "wallet_next_block_production_timestamp": "2014-09-28T13:56:40"
}

I updated to .. but my version field still states -RC .. how is yours?

delegate.liondani
Updated to v.0.4.18  ;)

Updated to v.0.4.17  ;)

delegate.liondani
Updated to v.0.4.17-RC2  ;)

Quote from: liondani on September 22, 2014, 08:04:03 PM
Managed to upgrade to to the final version v0.4.16 just 30 minutes before block 554800 appeared!!! (before  1-3 minutes)  :P

Hah just in time, nice.

Managed to upgrade to to the final version v0.4.16 just 30 minutes before block 554800 appeared!!! (before  1-3 minutes)  :P

Posted some hours ago about this issue (watch out for forks):

https://bitsharestalk.org/index.php?topic=9159.msg118786#msg118786

Missing blocks "out of the blue" - especially holidays can be a tough job for delegates....  8)

Both my 2 delegates www.minebitshares-com and www2.minebitshares-com have also missed blocks recently without explanation for the first time.

They both run on Amazon AWS instances and nothing has changed apart from upgrading to 0.4.16   :'(

I am missing blocks right now but I can't check my server for the next 7 hours....
The participation is right now at 89% so I assume it doesn't necessary mean my server is off-line!

I don't want to run the delegate from the VPS right now before I am sure about what is happening, so I want to be sure that I don't' will be  the reason of fork a creation.

So the question:
Is anybody else missing blocks right now for no apparent reason?
What is happening right now? Why so many delegates are missing blocks right now?
Coincidence or something else?


PS after I missed the first block it produced some and then I lost 4 consecutive blocks. So that means my server is not off-line and the client is working.
      But why am I missing blocks every now and then?

Quote from: AJ on September 14, 2014, 03:00:26 AM
Great work so far. Liondani, do you have any tips for up and coming delegates? Your advice is surely looked upon with experience.

Thanks for your kind works  ;)
I will post some tips soon... for now I will try to entertain you all !

http://youtu.be/pUjE9H8QlA4

http://youtu.be/pUjE9H8QlA4

Great work so far. Liondani, do you have any tips for up and coming delegates? Your advice is surely looked upon with experience.