Author Topic: BitShares 2 Release Coordination Thread  (Read 48125 times)

0 Members and 1 Guest are viewing this topic.

Offline twitter

  • Sr. Member
  • ****
  • Posts: 279
    • View Profile
re-syn  ing  :'(......

DONE!!!


bue need some vote  back for servicing network
« Last Edit: October 15, 2015, 01:19:30 am by twitter »
witness:

Offline dichalcog3nid3

Guys! Top notch witness b33lz338v8 needs your votes! Many thanks!  :D

http://x.makerdao.com you may support my work by voting for WITNESS b33lz38v8

EkremH

  • Guest
No, oct 5 was just an example. I found at the source the genesis.json, but I could not find seed node ?

Offline lafona

  • Sr. Member
  • ****
  • Posts: 231
    • View Profile
  • BitShares: lafona
You said: "Seed nodes and genesis file have been included in the source.". I found the genesis.json, but where to find the seed node? As in pre-releases to run witness_node we have to run ./witness_node -d oct5 --genesis-json oct5-genesis.json -s "104.236.51.238:2005", so we need a seed node. Or it works and if we just run ./witness_node ?

It should work if you just run ./witness_node. You don't have to include the arguments for seed nodes or genesis file. If you already tried running it with the old args, oct5 etc. You may need to run it with --resync-blockchain to get it to remove the files from the old chain.
BTS Witnesses: delegate-1.lafona     Witness Thread: https://bitsharestalk.org/index.php/topic,21569.msg280911/topicseen.html#msg280911
MUSE Witness: lafona

EkremH

  • Guest
You said: "Seed nodes and genesis file have been included in the source.". I found the genesis.json, but where to find the seed node? As in pre-releases to run witness_node we have to run ./witness_node -d oct5 --genesis-json oct5-genesis.json -s "104.236.51.238:2005", so we need a seed node. Or it works and if we just run ./witness_node ?

Offline Riverhead


Back in sync. I was worried about the --replay-blockchain but it replayed it in about 10 seconds. Wow.

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
my witness is up for as long as it is needed. I helped testing on testnet.
I was a little delayed getting it up, was checking and double checking the ubuntu linux builds. Both the light wallet and CLI is working well over there for the past day.

Code: [Select]
get_witness maqifrnswa
{
  "id": "1.6.43",
  "witness_account": "1.2.6004",
  "last_aslot": 0,
  "signing_key": "BTS61sn4chv5XVwEEbkmU3V7atoHcfuRfdwKjaeTNEsaXSLQgNCcm",
  "vote_id": "1:54",
  "total_votes": 0,
  "url": "",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}
« Last Edit: October 14, 2015, 10:02:19 pm by maqifrnswa »
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
looks like my witness in.abit is still in sync, haven't been voted in though, do I need to restart or replay?

you are in now
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline bytemaster

looks like my witness in.abit is still in sync, haven't been voted in though, do I need to restart or replay?

If you are still in sync you should be ok.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
looks like my witness in.abit is still in sync, haven't been voted in though, do I need to restart or replay?
BitShares committee member: abit
BitShares witness: in.abit

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
I was travelling last night and ran out of battery, always happens :)
Witness ready and separate node on 40.127.190.171:1777

Code: [Select]
get_witness betaxtrade
{
  "id": "1.6.39",
  "witness_account": "1.2.6956",
  "last_aslot": 0,
  "signing_key": "BTS6JhLDwYRKSa7FjEmfhy4VHHMn8SZySc8RJrbc5mWyCvERV3coy",
  "vote_id": "1:49",
  "total_votes": 0,
  "url": "",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}

@bytemaster, needs some votes too...
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline bytemaster

All witnesses may need to replay the blockchain to get back in sync.  There seems to be an issue that can cause things to get out of sync.

Done. Deleted folder object_database and config folder, and restarted. Now syncing nicely.

My witness also crashed earlier today (around 14:00 UTC) and I had to do the same thing. Here is a log of the event in case it is useful.

Previously I didn't have to restart my seed node, but this time it was necessary. Please ask for more logs if needed.

witness spectral is synced again and ready (but needs votes! :) )

Voted!
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline Spectral

All witnesses may need to replay the blockchain to get back in sync.  There seems to be an issue that can cause things to get out of sync.

Done. Deleted folder object_database and config folder, and restarted. Now syncing nicely.

My witness also crashed earlier today (around 14:00 UTC) and I had to do the same thing. Here is a log of the event in case it is useful.

Previously I didn't have to restart my seed node, but this time it was necessary. Please ask for more logs if needed.

witness spectral is synced again and ready (but needs votes! :) )
Vote for BTS-2 witness: spectral (1.6.30)
0.9 DVS delegate: dvs1.bitspace
Stay tuned for bitspace-clains worker!

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
All witnesses may need to replay the blockchain to get back in sync.  There seems to be an issue that can cause things to get out of sync.

Is replay enough? or do we need to resync?
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline bytemaster

All witnesses may need to replay the blockchain to get back in sync.  There seems to be an issue that can cause things to get out of sync.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.