October 5 Test Network

[cube]

It is appraching midnight (and bedtime) here in asia.  I hope I am not going to miss any update.

[bytemaster]

The most recent master has a fix for failure to switch to the proper fork.   We are resolving a few other issues so there may be additional updates.

My apologies for the rapid fixes.

[iHashFury]

wintness 'delegate.ihashfury' and nodes - updated to latest master

[roadscape]

roadscape updated to master

[cube]

bitcube is updated to master.

[jtme]

jtm1 updated

[wackou]

wackou updated to latest master

[theoretical]

1. Is it normal that serving up block is repeated so many times, and is that the output indicating that my witness is producing a block?

Yes, and sort of.  "Serving up block" just means you are telling other p2p nodes about a block.  You should get one for every node you're connected to when you produce a block (because none of them know about your shiny new block until you tell them), so you'll see a bunch of them when you produce.  But you'll also get a few of them for every block you see -- all that means is you heard about some block before some of your peers, so you get to be the one to tell those peers about the block.  You might even see a large number of consecutively numbered "serving up block" messages for a bunch of blocks in the past, if a peer is syncing from you.

None of this matters if you build from 8e96d9c89cd24a733d4838901f781af0315ec667 or later, as the "serving up block" message is removed (it is sort of spammy and not all that informative).

2. How can I check if my feeds are transacted correctly?

For now, use your account history at https://graphene.bitshares.org/#/account/spectral/overview

If you are using the CLI wallet, you can do

Code: [Select]

get_account_history spectral 10


[puppies]

Everyone else, please update your witness to the latest master before block 58500  (about 4 hours).

Can someone please tell me how to update the witness without stop it?

Can I copy the current "graphene" folder, rename it to "current-graphene", update the copied "graphene", restart the witness in this new folder?
Do I have to use update_witness when launching the updated one? How does it works?

Thanks xD

I've used a few different strategies.  Most often what I have done is
1) build a fresh build on a different box.
2) get it set up and running with a secondary public private key pair (more on this below)
3) switch block production to this second key pair
4) build on my main box and restart witness node
5) switch block production back.
This time I am trying something new.  I have created a secondary build directory on my main box and have launched a second witness_node running with a secondary key pair.  Once the build is complete on the local box that has all of my balances I will switch over production, shut down the first build, and rebuild it.

In order to switch between witnesses you will need at least two sets of public private key pairs.  You can generate these key pairs with the wallet command

Code: [Select]

suggest_brain_keyI recommend saving the output of that command to a file so you can reference it later.  On your secondary box you will replace the current active public private key pair, with this new public private key pair.  I suggest doing this in the config.ini, but you can also do it all in command line.  Once both boxes are up and running with different key pairs, you can switch between them with the wallet command

Code: [Select]

update_witness <witness_account> <url> <public key> true
you should be able to use "" if you want an empty url. 

Hope this cleared things up and didn't just confuse you further.

[spartako]

It seems init* are down

[wuyanren]

How so many witnesses are not online。That seems not to be good.

[Fox]

[...]

Everyone else, please update your witness to the latest master before block 58500  (about 4 hours).

Update complete:

Code: [Select]

cd ~/graphene
git checkout master
git pull
git submodule update --init --recursive --force
#cmake -DCMAKE_BUILD_TYPE=Debug .
cmake -D CMAKE_BUILD_TYPE=Release .
make -j4


[twitter]

bue is updating

[mindphlux]

Witness mindphlux.witness has been updated to latest master.

[Spectral]

spectral updated to latest master

Code: [Select]

366235ms th_a       application.cpp:388           handle_block         ] Got block #54845 with time 2015-10-07T14:06:06 from network with latency of 236 ms from init1
369000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
369181ms th_a       application.cpp:388           handle_block         ] Got block #54846 with time 2015-10-07T14:06:09 from network with latency of 182 ms from init10
375000ms th_a       witness.cpp:176               block_production_loo ] Generated block #54848 with timestamp 2015-10-07T14:06:15 at time 2015-10-07T14:06:15
375031ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375034ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375037ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375039ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375040ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375042ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375043ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375044ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375045ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375047ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375049ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375086ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375109ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375110ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375127ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375141ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375141ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375143ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375147ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375192ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375209ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375214ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375220ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375248ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375289ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375290ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375350ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375600ms th_a       application.cpp:518           get_item             ] Serving up block #54848
375840ms th_a       application.cpp:518           get_item             ] Serving up block #54848
378000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
378179ms th_a       application.cpp:388           handle_block         ] Got block #54849 with time 2015-10-07T14:06:18 from network with latency of 180 ms from init5
381000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn

And I have a few of questions concerning this output:

1. Is it normal that serving up block is repeated so many times, and is that the output indicating that my witness is producing a block?

2. How can I check if my feeds are transacted correctly?

3. Can somebody check how my latency is doing compared to other witnesses?