BitShares Forum

Main => General Discussion => Topic started by: bytemaster on August 14, 2015, 10:39:33 pm

Title: Test Net for Advanced Users
Post by: bytemaster on August 14, 2015, 10:39:33 pm: Download this Aug-14 snapshot of BitShares:

https://drive.google.com/open?id=0B_GVo0GoC_v_S3lPOWlUbFJFWTQ

If you have a mac, download the draft version of BitShares 0.9.2 which has a new api call
https://github.com/bitshares/bitshares/releases/tag/untagged-4166986045ff28284dc4

Console>> wallet_export_keys /tmp/bitshares.json

That file will contain all of your public/private key pairs sorted by account. You can use that data to import into graphene. Note: GUI import is still somewhat broken.

You can connect to the test network as:

Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-14-test-genesis.json -d test_net -s 104.200.28.117:61705 ./cli_wallet -w wallet_name --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6
For some help with the CLI wallet:
https://github.com/cryptonomex/graphene/wiki/CLI-Wallet-Cookbook

How to become an active witness:
https://github.com/cryptonomex/graphene/wiki/Howto-become-an-active-witness-in-BitShares-2.0

Next week we will provide information for GUI users.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 14, 2015, 10:48:18 pm: awesomesauce

For those of us not running OSX would you suggest we pull and build that version, or is there a reasonable way of pulling those keys manually?

Now that I am looking at it it looks like both import_account_keys and import_accounts require importing from json. Is that right? if so building that version of 0.9.2 seems like a good idea.
Title: Re: Test Net for Advanced Users
Post by: CLains on August 14, 2015, 11:22:13 pm: +5%
Title: Re: Test Net for Advanced Users
Post by: abit on August 15, 2015, 12:27:01 am: Quote from: bytemaster on August 14, 2015, 10:39:33 pm
If you have a mac, download the draft version of BitShares 0.9.2 which has a new api call
https://github.com/bitshares/bitshares/releases/tag/untagged-4166986045ff28284dc4

This download is broken.. showing a 404 page.
Is there a way to build from source? Best if for Ubuntu.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 15, 2015, 12:41:32 am: Quote from: abit on August 15, 2015, 12:27:01 am
Quote from: bytemaster on August 14, 2015, 10:39:33 pm
If you have a mac, download the draft version of BitShares 0.9.2 which has a new api call
https://github.com/bitshares/bitshares/releases/tag/untagged-4166986045ff28284dc4

This download is broken.. showing a 404 page.
Is there a way to build from source? Best if for Ubuntu.

Mines still building. Ill post instructions in a couple minutes if it works.

edit

On Ubuntu 14.04 this worked to update the client. This is assuming that you already have the build directory set up. checking out bitshares breaks the submodules so you have to pull a couple manually. Works and exports keys into a nice encrypted json.
Code: [Select]
git pull git checkout bitshares cd libraries rm -r fc git clone https://github.com/cryptonomex/fc.git cd fc/vendor rm -r secp256k1-zkp git clone https://github.com/cryptonomex/secp256k1-zkp.git cd ../../.. git submodule update --init --recursive cmake . make bitshares_client
Title: Re: Test Net for Advanced Users
Post by: ebit on August 15, 2015, 12:57:32 am: +5%
Title: Re: Test Net for Advanced Users
Post by: abit on August 15, 2015, 01:27:45 am: Quote from: puppies on August 15, 2015, 12:41:32 am

On Ubuntu 14.04 this worked to update the client. This is assuming that you already have the build directory set up. checking out bitshares breaks the submodules so you have to pull a couple manually. Works and exports keys into a nice encrypted json.

Thanks! Trying.. slow network :(
Title: Re: Test Net for Advanced Users
Post by: puppies on August 15, 2015, 03:16:46 am: There needs to be an easier way to import balances. Perhaps some way to import all private keys held in the wallet.

I manually imported at least a hundred keys and got a total of 6 hits for 3600 CORE. Unfortunately not even enough to upgrade account.
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 05:27:04 am: +5% lets try ubuntu
Title: Re: Test Net for Advanced Users
Post by: reyreyrey on August 15, 2015, 06:22:36 am: +5% +5% +5% +5%
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 15, 2015, 06:53:39 am: +5% .. gonna join the network tomorrow .. i am out for today
Title: Re: Test Net for Advanced Users
Post by: clayop on August 15, 2015, 06:56:10 am: Setting up another VPN (as same as my current VPS) now. Hopefully I can successfully settle my testnet delegate there :)
Title: Re: Test Net for Advanced Users
Post by: VoR0220 on August 15, 2015, 07:27:14 am: Beautifully done.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 15, 2015, 07:50:38 am: @xeroc
I'm stuck in importing my balance keys. The error is
Code: [Select]
7 bad_cast_exception: Bad Cast Invalid cast from string_type to Array {"type":"string_type"} th_a variant.cpp:530 get_array
Can you help me?

Edit: I found it. [balance wif key]
Title: Re: Test Net for Advanced Users
Post by: clayop on August 15, 2015, 08:31:29 am: I finally set up the first testnet delegate :D Server location is Asia, using google computing service.
Title: Re: Test Net for Advanced Users
Post by: Musewhale on August 15, 2015, 08:38:50 am: i am in +5% +5% +5%
Title: Re: Test Net for Advanced Users
Post by: cass on August 15, 2015, 08:42:38 am: Quote
If you have a mac, download the draft version of BitShares 0.9.2 which has a new api call
https://github.com/bitshares/bitshares/releases/tag/untagged-4166986045ff28284dc4

link doesn't work for me ...
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 15, 2015, 03:05:43 pm: The import process described in the how-to is a stop-gap measure. We have already done significant work to make that easier.

At the end of the day it will be as easy as:

1. export BTS 1 wallet
2. import into BTS 2
Title: Re: Test Net for Advanced Users
Post by: puppies on August 15, 2015, 03:19:36 pm: Quote from: bytemaster on August 15, 2015, 03:05:43 pm
The import process described in the how-to is a stop-gap measure. We have already done significant work to make that easier.

At the end of the day it will be as easy as:

1. export BTS 1 wallet
2. import into BTS 2
+5%
Title: Re: Test Net for Advanced Users
Post by: spartako on August 15, 2015, 04:59:39 pm: Great! I'm in! +5%
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 05:00:56 pm: I have to be very silly but I am also stuck on the :

Code: [Select]
7 bad_cast_exception: Bad Cast Invalid cast from string_type to Array {"type":"string_type"} th_a variant.cpp:530 get_array
I am using the wif of the balance, using the output documented in the wiki:

Code: [Select]
Each of these balances can be investigated via: BitShares0.9: >>> blockchain_get_balance BTSAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA .... "asset_id": 0, <- asset_id (0: BTS) "data": { "owner": "BTSOOOOOOOOOOOOOOOOOOOOOOOOOOOOOWNER", <- address ... "balance": 0, <- balance ... The required part (the owner of the balance) is denoted as owner. Pick one or more address for BTS balances and dump the corresponding private key(s) with: BitShares0.9: >>> wallet_dump_private_key BTSOOOOOOOOOOOOOOOOOOOOOOOOOOOOOWNER "5......." # the <balance wif key>

edit: english code -> english
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 05:07:04 pm: And I also solved it :

The syntax is

Code: [Select]
import_balance betax [5....] true
It is expecting an array as it says in the error doh!
Title: Re: Test Net for Advanced Users
Post by: clayop on August 15, 2015, 05:13:56 pm: Quote from: betax on August 15, 2015, 05:07:04 pm
And I also solved it :

The syntax is

Code: [Select]
import_balance betax [5....] true
It is expecting an array as it says in the error doh!

That's the problem what I experienced.
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 15, 2015, 06:11:57 pm: Oh .. thanks for pointing this out. I will fix the wiki as soon as I get back to my computer .. sorry for the trouble
Title: Re: Test Net for Advanced Users
Post by: clayop on August 15, 2015, 06:42:34 pm: Quote from: xeroc on August 15, 2015, 06:11:57 pm
Oh .. thanks for pointing this out. I will fix the wiki as soon as I get back to my computer .. sorry for the trouble

Don't worry xeroc. I did.
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 08:57:29 pm: Thanks clayop.. your brackets on the other post hinted the answer. Xeroc don't worry your instructions are really good.

Another problem, now when I try to start the witness, I get a decimal parse error for --witness-id "1.6.5155"

Code: [Select]
parse_error_exception: Parse Error Can't parse a number with two decimal places {} th_a json.cpp:277 number_from_stream {"str":"1.6.5155"} th_a json.cpp:478 from_string rethrow {} th_a witness.cpp:88 plugin_initialize
I have tried to configure the witness-id in the config.ini but I get this warning:

Code: [Select]
3312033ms th_a witness.cpp:70 plugin_initialize ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","wif key"] 3312121ms th_a thread.cpp:95 thread ] name:ntp tid:139624819738368 3312121ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 3312121ms th_a thread.cpp:95 thread ] name:p2p tid:139624800855808 3312289ms ntp ntp.cpp:81 request_now ] sending request to 172.82.134.52:123 3312289ms th_a application.cpp:116 reset_p2p_node ] Adding seed node 104.200.28.117:61705 3312290ms th_a application.cpp:128 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:53031 3312292ms th_a application.cpp:178 reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090 [b]3312292ms th_a witness.cpp:143 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration.[/b] 3312292ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks. 3312292ms th_a main.cpp:166 main ] Chain ID is cefacd8adb8bee2bf3b757e882d2828297ceb67b1882982cbde882688ecb46a8 3312395ms ntp ntp.cpp:147 read_loop ] received ntp reply from 172.82.134.52:123 3312395ms ntp ntp.cpp:161 read_loop ] ntp offset: 1679989, round_trip_delay 106243 3312395ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 1679989
Any thoughts ?

Note: I am doing this in between family time, hence the delay on the postings
Title: Re: Test Net for Advanced Users
Post by: clayop on August 15, 2015, 09:06:43 pm: Quote from: betax on August 15, 2015, 08:57:29 pm
Thanks clayop.. your brackets on the other post hinted the answer. Xeroc don't worry your instructions are really good.

Another problem, now when I try to start the witness, I get a decimal parse error for --witness-id "1.6.5155"

Code: [Select]
parse_error_exception: Parse Error Can't parse a number with two decimal places {} th_a json.cpp:277 number_from_stream {"str":"1.6.5155"} th_a json.cpp:478 from_string rethrow {} th_a witness.cpp:88 plugin_initialize
I have tried to configure the witness-id in the config.ini but I get this warning:

Code: [Select]
3312033ms th_a witness.cpp:70 plugin_initialize ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","wif key"] 3312121ms th_a thread.cpp:95 thread ] name:ntp tid:139624819738368 3312121ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 3312121ms th_a thread.cpp:95 thread ] name:p2p tid:139624800855808 3312289ms ntp ntp.cpp:81 request_now ] sending request to 172.82.134.52:123 3312289ms th_a application.cpp:116 reset_p2p_node ] Adding seed node 104.200.28.117:61705 3312290ms th_a application.cpp:128 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:53031 3312292ms th_a application.cpp:178 reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090 [b]3312292ms th_a witness.cpp:143 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration.[/b] 3312292ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks. 3312292ms th_a main.cpp:166 main ] Chain ID is cefacd8adb8bee2bf3b757e882d2828297ceb67b1882982cbde882688ecb46a8 3312395ms ntp ntp.cpp:147 read_loop ] received ntp reply from 172.82.134.52:123 3312395ms ntp ntp.cpp:161 read_loop ] ntp offset: 1679989, round_trip_delay 106243 3312395ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 1679989
Any thoughts ?

Note: I am doing this in between family time, hence the delay on the postings

Maybe a minor bug. I resolved the same problem by using cookbook

Code: [Select]
--witness-id \""1.6.xxxx"\
If it does not work, change quote marks in the private key section together.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 15, 2015, 09:09:59 pm: Quote from: betax on August 15, 2015, 08:57:29 pm
Thanks clayop.. your brackets on the other post hinted the answer. Xeroc don't worry your instructions are really good.

Another problem, now when I try to start the witness, I get a decimal parse error for --witness-id "1.6.5155"

Code: [Select]
parse_error_exception: Parse Error Can't parse a number with two decimal places {} th_a json.cpp:277 number_from_stream {"str":"1.6.5155"} th_a json.cpp:478 from_string rethrow {} th_a witness.cpp:88 plugin_initialize
I have tried to configure the witness-id in the config.ini but I get this warning:

Code: [Select]
3312033ms th_a witness.cpp:70 plugin_initialize ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","wif key"] 3312121ms th_a thread.cpp:95 thread ] name:ntp tid:139624819738368 3312121ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 3312121ms th_a thread.cpp:95 thread ] name:p2p tid:139624800855808 3312289ms ntp ntp.cpp:81 request_now ] sending request to 172.82.134.52:123 3312289ms th_a application.cpp:116 reset_p2p_node ] Adding seed node 104.200.28.117:61705 3312290ms th_a application.cpp:128 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:53031 3312292ms th_a application.cpp:178 reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090 [b]3312292ms th_a witness.cpp:143 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration.[/b] 3312292ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks. 3312292ms th_a main.cpp:166 main ] Chain ID is cefacd8adb8bee2bf3b757e882d2828297ceb67b1882982cbde882688ecb46a8 3312395ms ntp ntp.cpp:147 read_loop ] received ntp reply from 172.82.134.52:123 3312395ms ntp ntp.cpp:161 read_loop ] ntp offset: 1679989, round_trip_delay 106243 3312395ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 1679989
Any thoughts ?

Note: I am doing this in between family time, hence the delay on the postings

I had the same errors. I ended up fixing it by changing test_net/config.in I to
Code: [Select]
# ID of witness controlled by this node (e.g. "1.6.0", quotes are required, may specify multiple times) witness-id = "1.6.1435" # Tuple of [PublicKey, WIF private key] (may specify multiple times) private-key = ["GPHxxxxxxxxxx", "privatexxxxxxx"]
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 09:16:45 pm: I have found the issue, you both were right. It needs to be changed on the wiki too.

From the github main page, this is the right format.
Code: [Select]
./witness_node --rpc-endpoint 127.0.0.1:8090 --enable-stale-production -w '"1.6.0"' '"1.6.1"' '"1.6.2"' '"1.6.3"' '"1.6.4"' '"1.6.5"' '"1.6.6"' '"1.6.7"' '"1.6.8"' '"1.6.9"'
It needs to be wrapped in single quotes and double quotes, so when parsing is not treated as a number.
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 09:18:10 pm: I guess that array parameters have been a new addition and xeroc has not been able to catch up on his document.
Title: Re: Test Net for Advanced Users
Post by: abit on August 15, 2015, 09:19:37 pm: //EDIT: solved. my fault again. copy & paste but lost one character..

I met a problem while importing balance (the real keys replaced by *** ):

Code: [Select]
import_balance in.abit [5K58****dGSz,5KSE****EHJd,5HuJ****uzj7,5KPR****zmq8,5KUn****kzno,5Jtc****D4R4,5Jus****EpCH,5JNv****KfWz] true 10 assert_exception: Assert Exception priv_key: Invalid Private Key {"key":"5Jtc****D4R4"} th_a wallet.cpp:2710 import_balance {"name_or_id":"in.abit"} th_a wallet.cpp:2757 import_balanceIt works if I remove that key from the array. It also work if I import that key alone.
Any thoughts?
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 09:22:15 pm: It might be a recent transaction that wasn't on the snapshot.

Edit: Just noticed you said all the 5Js so it is a pattern... Ill check when my witness finish synching loading, and see if I have a 5j to test.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 15, 2015, 09:27:58 pm: Quote from: betax on August 15, 2015, 09:18:10 pm
I guess that array parameters have been a new addition and xeroc has not been able to catch up on his document.

Great! Can you write down an example (EXCEPT your private key) for dummies like me?
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 09:32:32 pm: Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-14-test-genesis.json -d test_net -s 104.200.28.117:61705 --enable-stale-production -w '"1.6.5155"' I have my key, private key in the config.ini
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 09:42:41 pm: Well next issue my key / private are not loading, they are different ones from the config, and getting a parsing error as parameters
Title: Re: Test Net for Advanced Users
Post by: puppies on August 15, 2015, 09:54:02 pm: Quote from: betax on August 15, 2015, 09:42:41 pm
Well next issue my key / private are not loading, they are different ones from the config, and getting a parsing error as parameters

It took me awhile to realize that the -d test_net I'm bytemasters instructions was the data directory. I was modifying the wrong config.ini. that might be your issue.
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 10:01:15 pm: Thanks, I was wondering what was that parameter.. and why it was not loading from config.

This is my final version, which parses correctly the private key, I have removed the -d test-net as per puppies recommendation.
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-14-test-genesis.json -s 104.200.28.117:61705 --witness-id '"1.6.5155"' --private-key '["GP...................................oy", "5KW.......................P8a"]'
Edit:
I edited the wiki, to fix the parameter issues. Mainly you need to wrap strings that required double quotes, with single quotes.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 15, 2015, 10:09:38 pm: Is there a way to withdraw witness pay yet?

Also I know it's not a big deal but I was going that our bts id's would transfer over to 2.0. For example I'm kinda proud of the fact that dele-puppy is account number 1193 in bts. Just as a status symbol that it's an old account.
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 10:14:13 pm: How long does it take to sync ? Just in case I am still doing something wrong
Title: Re: Test Net for Advanced Users
Post by: puppies on August 15, 2015, 10:15:29 pm: After I finally got it right it hung for five to ten minutes.
Title: Re: Test Net for Advanced Users
Post by: abit on August 15, 2015, 10:16:41 pm: //EDIT: got it, it's due to wrong starting parameters.

Another "5J" problem.. Can't start my witness even though it's voted in :(
Code: [Select]
726136ms th_a witness.cpp:88 plugin_initialize ] 10 assert_exception: Assert Exception base58str.substr( 0, prefix_len ) == prefix: {"base58str":"5J9YY***********************************wVCN"} th_a types.cpp:54 public_key_type 726144ms th_a main.cpp:173 main ] Exiting with error: 10 assert_exception: Assert Exception base58str.substr( 0, prefix_len ) == prefix: {"base58str":"5J9YY***********************************wVCN"} th_a types.cpp:54 public_key_type rethrow {} th_a witness.cpp:88 plugin_initialize
Before restart:
Code: [Select]
unlocked >>> get_witness in.abit { "id": "1.6.5156", "witness_account": "1.2.38793", "signing_key": "GPH65XNUxWdYGqGyW9NtXdRpNntumLYT1cJ7CNE7F78Pwxrnx6cbV", "next_secret_hash": "d210b0644edfcee411f00058dd862279402c61b4", "previous_secret": "0000000000000000000000000000000000000000", "vote_id": "1:5284", "total_votes": 2389598829, "url": "url-to-proposal" }
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 10:17:58 pm: Quote from: puppies on August 15, 2015, 10:15:29 pm
After I finally got it right it hung for five to ten minutes.

Thanks, I think Ill give it another 5 / 10 minutes then.
Title: Re: Test Net for Advanced Users
Post by: abit on August 15, 2015, 10:47:59 pm: Quote from: betax on August 15, 2015, 09:22:15 pm
It might be a recent transaction that wasn't on the snapshot.

Edit: Just noticed you said all the 5Js so it is a pattern... Ill check when my witness finish synching loading, and see if I have a 5j to test.
solved. stupid me.. :-[
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 11:33:38 pm: Finally I am producing blocks.

My node after all attempts would not start, it was stuck. I thought it was an issue with ntp, (new build) so I installed and configure sources.
Finally I deleted the object_data directory to start fresh, and rebooted the server.

And its working... :)
Title: Re: Test Net for Advanced Users
Post by: abit on August 15, 2015, 11:35:52 pm: Strange error with witness:
Code: [Select]
1748966ms th_a application.cpp:342 handle_block ] Got block #104467 from network 1749534ms th_a application.cpp:342 handle_block ] Got block #104468 from network 1757502ms th_a application.cpp:342 handle_block ] Got block #104469 from network 1759976ms th_a application.cpp:342 handle_block ] Got block #104475 from network 1759977ms th_a application.cpp:364 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:51 push_block {"new_block":{"previous":"0001981a644a3dddd4e2c7db84bb49f6fec77355","timestamp":"2015-08-15T23:29:16","witness":"1.6.5","next_secr et_hash":"b3a177eb67d1e7b782e54e1ad216b87b79dc440d","previous_secret":"933e421c25e571c2fc9bf5fab56f5140cfb5f753","transaction_merkle_r oot":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f3e0a2d9b6d6ee76e3d90c77eb1680380c4cf3fe87646089 e83bd7f8446a8c79878c2a81e98329ceb3c753b958bdde66ef4f147c8f7d254bc8774825810dedda5","transactions":[]}} th_a db_block.cpp:173 _push_blockWhy 104470~104474 missed?
It stopped syncing after this error, unable to push block again and again.
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 11:40:26 pm: I am currently on #105026, so you should be on the same.
Title: Re: Test Net for Advanced Users
Post by: betax on August 15, 2015, 11:42:11 pm: Well time for bed.. forgot to mention, my test witness is in a Azure VPS - North Europe. (2 cores, 3 gigs of ram).
Title: Re: Test Net for Advanced Users
Post by: liondani on August 16, 2015, 01:48:54 am: I will be in at Monday with my VPS from Greece!
It sucks that I must wait until then :'(
Title: Re: Test Net for Advanced Users
Post by: abit on August 16, 2015, 07:55:39 am: I'm still not in sync :(
Every time ctrl+c kill witness and restart, it wipes everything, then resync slowly, then stuck somewhere.
Code: [Select]
2088883ms th_a application.cpp:264 startup ] Detected unclean shutdown. Replaying blockchain... 2088883ms th_a application.cpp:227 operator() ] Initializing database... 2099945ms th_a db_management.cpp:67 wipe ] Wiping database 2099968ms th_a object_database.cpp:82 wipe ] Wiping object_database.
100% CPU while wiping. Is it quicker to just remove the object_database directory and the witness_data directory before restart?
Title: Re: Test Net for Advanced Users
Post by: abit on August 16, 2015, 08:24:41 am: Quote from: betax on August 15, 2015, 11:40:26 pm
I am currently on #105026, so you should be on the same.
Can you post your node's IP/port so that others can add it to peers list?
Title: Re: Test Net for Advanced Users
Post by: puppies on August 16, 2015, 08:54:09 am: Quote from: abit on August 16, 2015, 08:24:41 am
Quote from: betax on August 15, 2015, 11:40:26 pm
I am currently on #105026, so you should be on the same.
Can you post your node's IP/port so that others can add it to peers list?
45.55.6.216:42317 is one of my nodes.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 16, 2015, 08:58:30 am: Whats going on here?
Code: [Select]
3299997ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.1 scheduled_time: 2015-08-16T08:55:00 now: 2015-08-16T08:55:00 3300134ms th_a application.cpp:342 handle_block ] Got block #134274 from network 3300436ms th_a application.cpp:342 handle_block ] Got block #134274 from network 3300538ms th_a application.cpp:437 get_item ] Request for item {"item_type":1001,"item_hash":"84dc9853e4ddd3941281f6260886aef9713829f0"} 3300997ms th_a witness.cpp:239 block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-16T08:55:01 3300998ms th_a witness.cpp:207 operator() ] Not producing block because head block time is in the future (is the system clock set correctly?). 3301997ms th_a witness.cpp:239 block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-16T08:55:02 3301998ms th_a witness.cpp:207 operator() ] Not producing block because head block time is in the future (is the system clock set correctly?). 3302997ms th_a witness.cpp:239 block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-16T08:55:03 3302998ms th_a witness.cpp:207 operator() ] Not producing block because head block time is in the future (is the system clock set correctly?). 3303997ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.1439 scheduled_time: 2015-08-16T08:55:04 now: 2015-08-16T08:55:04
Title: Re: Test Net for Advanced Users
Post by: betax on August 16, 2015, 11:20:35 am: Quote from: abit on August 16, 2015, 07:55:39 am
I'm still not in sync :(
Every time ctrl+c kill witness and restart, it wipes everything, then resync slowly, then stuck somewhere.
Code: [Select]
2088883ms th_a application.cpp:264 startup ] Detected unclean shutdown. Replaying blockchain... 2088883ms th_a application.cpp:227 operator() ] Initializing database... 2099945ms th_a db_management.cpp:67 wipe ] Wiping database 2099968ms th_a object_database.cpp:82 wipe ] Wiping object_database.
100% CPU while wiping. Is it quicker to just remove the object_database directory and the witness_data directory before restart?

I stopped the witness, delete the database, restarted server. Then launch the witness.

Ill post the node IP later on.
Title: Re: Test Net for Advanced Users
Post by: betax on August 16, 2015, 11:21:34 am: Quote from: puppies on August 16, 2015, 08:58:30 am
Whats going on here?
Code: [Select]
3299997ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.1 scheduled_time: 2015-08-16T08:55:00 now: 2015-08-16T08:55:00 3300134ms th_a application.cpp:342 handle_block ] Got block #134274 from network 3300436ms th_a application.cpp:342 handle_block ] Got block #134274 from network 3300538ms th_a application.cpp:437 get_item ] Request for item {"item_type":1001,"item_hash":"84dc9853e4ddd3941281f6260886aef9713829f0"} 3300997ms th_a witness.cpp:239 block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-16T08:55:01 3300998ms th_a witness.cpp:207 operator() ] Not producing block because head block time is in the future (is the system clock set correctly?). 3301997ms th_a witness.cpp:239 block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-16T08:55:02 3301998ms th_a witness.cpp:207 operator() ] Not producing block because head block time is in the future (is the system clock set correctly?). 3302997ms th_a witness.cpp:239 block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-16T08:55:03 3302998ms th_a witness.cpp:207 operator() ] Not producing block because head block time is in the future (is the system clock set correctly?). 3303997ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.1439 scheduled_time: 2015-08-16T08:55:04 now: 2015-08-16T08:55:04

I have the same issues every so often, and I have ntp running
Title: Re: Test Net for Advanced Users
Post by: lafona on August 16, 2015, 12:52:44 pm: Quote from: betax on August 16, 2015, 11:21:34 am
Quote from: puppies on August 16, 2015, 08:58:30 am
Whats going on here?
Code: [Select]
3299997ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.1 scheduled_time: 2015-08-16T08:55:00 now: 2015-08-16T08:55:00 3300134ms th_a application.cpp:342 handle_block ] Got block #134274 from network 3300436ms th_a application.cpp:342 handle_block ] Got block #134274 from network 3300538ms th_a application.cpp:437 get_item ] Request for item {"item_type":1001,"item_hash":"84dc9853e4ddd3941281f6260886aef9713829f0"} 3300997ms th_a witness.cpp:239 block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-16T08:55:01 3300998ms th_a witness.cpp:207 operator() ] Not producing block because head block time is in the future (is the system clock set correctly?). 3301997ms th_a witness.cpp:239 block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-16T08:55:02 3301998ms th_a witness.cpp:207 operator() ] Not producing block because head block time is in the future (is the system clock set correctly?). 3302997ms th_a witness.cpp:239 block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-16T08:55:03 3302998ms th_a witness.cpp:207 operator() ] Not producing block because head block time is in the future (is the system clock set correctly?). 3303997ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.1439 scheduled_time: 2015-08-16T08:55:04 now: 2015-08-16T08:55:04

I have the same issues every so often, and I have ntp running
I was seeing the same thing. Restarting the witness seemed to fix it though.
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 16, 2015, 02:18:48 pm: I am seeing these:
Code: [Select]
708971ms th_a application.cpp:486 get_blockchain_synop ] reference_point: 0000000000000000000000000000000000000000 number_of_blocks_after_reference_point: 0 result: ["00003f86b4220fb29e16036f5d696bb5243f9a07","00013f8685820e64a33f3b87f8cf6474b0e7e5c7","0001bf8635d391238db9e93931aae721abd53bab","0001ff868e9aec5f1f14cfb66e5f49fb0280329e","00021f86654dc5d0c4b92583d55fda1c9f7dd82f","00022f869f1a17f045c6952b2e0f449024df7742","0002378624f2f684ed05d697aea7aff3d0b3513a","00023b8665b1af0e5fd6785b618446d70b7b7c16","00023d8649c554e0c149ee44b4ea746d1ace0d85","00023e86432bacf440402bfc0cc09ef1918400f4","00023f0670f542d7bb358bc620100fd3120d87c2","00023f464af6c15db54edeb71b84fb9ced19a473","00023f66bd846878966710660b72c7f1ddfe0412","00023f762feec6a58f31a1fbf74f2f6722cd1235","00023f7e66d776c07eb3ef892981761da11c5dbb","00023f8250a4aa2c2143a226b50074a05d66a788","00023f8477a53510d63dca1dd1de05a67d251d2d","00023f853fe584f1891a6f246f2ed7238a6bcabd","00023f868da02c32c1d8c6faef53b4a0c51ade92"]Then the syncing progress stopped with no more blocks

I also frequently see this:
Code: [Select]
1130033ms p2p tcp_socket.cpp:162 bind ] Exception binding outgoing connection to desired local endpoint: bind: Address already in usewith no ports besides NTP and SSH in use .. no idea what port the client wants to bind ..
Title: Re: Test Net for Advanced Users
Post by: abit on August 16, 2015, 03:22:06 pm: Quote from: puppies on August 16, 2015, 08:54:09 am
Quote from: abit on August 16, 2015, 08:24:41 am
Quote from: betax on August 15, 2015, 11:40:26 pm
I am currently on #105026, so you should be on the same.
Can you post your node's IP/port so that others can add it to peers list?
45.55.6.216:42317 is one of my nodes.
Thanks. It seems my node connected to 45.55.6.216:59189.
Title: Re: Test Net for Advanced Users
Post by: maqifrnswa on August 16, 2015, 03:50:32 pm: ~~On ARM something ist up with genesis.json~~

my fault for not using the genesis file provided! I can generate genesis using witness_node fine, and it reads fine
Title: Re: Test Net for Advanced Users
Post by: abit on August 16, 2015, 04:00:40 pm: My current node is 114.92.254.159:62015, but it may change since it's dynamic IP address. Still not in sync though.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 16, 2015, 04:31:00 pm: I got this error on my non-witness node

Code: [Select]
3315889ms th_a application.cpp:330 handle_block ] Got block #147334 from network 862723ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 862729ms ntp ntp.cpp:81 request_now ] sending request to 129.6.15.30:123 1162730ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 1162736ms ntp ntp.cpp:81 request_now ] sending request to 69.50.219.51:123 1162765ms ntp ntp.cpp:147 read_loop ] received ntp reply from 69.50.219.51:123 1162765ms ntp ntp.cpp:161 read_loop ] ntp offset: 1256929, round_trip_delay 28530 1162765ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 1256929

And in my another node (with active witness) I got the same error messages

Code: [Select]
1568000ms th_a witness.cpp:239 block_production_loo ] slot: 26417 schedu led_witness: 1.6.1446 scheduled_time: 2015-08-16T16:26:08 now: 2015-08-16T16:26:08 1568001ms th_a witness.cpp:242 block_production_loo ] Witness 1.6.1446 p roduction slot has arrived; generating a block now... 1568003ms th_a db_block.cpp:167 _push_block ] Failed to push new block: 3070000 undo_database_exception: undo database exception The database does not have enough undo history to support a blockchain with so many missed b locks. Please add a checkpoint if you would like to continue applying blocks beyond this poi nt. {"recently_missed":53819,"max_undo":1000} th_a db_update.cpp:68 update_global_dynamic_data {"next_block.block_num()":134420} th_a db_block.cpp:448 _apply_block 1568003ms th_a witness.cpp:265 block_production_loo ] Got exception whil e generating block: ...
Title: Re: Test Net for Advanced Users
Post by: puppies on August 16, 2015, 04:32:31 pm: Quote from: clayop on August 16, 2015, 04:31:00 pm
I got this error on my non-witness node

Code: [Select]
3315889ms th_a application.cpp:330 handle_block ] Got block #147334 from network 862723ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 862729ms ntp ntp.cpp:81 request_now ] sending request to 129.6.15.30:123 1162730ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 1162736ms ntp ntp.cpp:81 request_now ] sending request to 69.50.219.51:123 1162765ms ntp ntp.cpp:147 read_loop ] received ntp reply from 69.50.219.51:123 1162765ms ntp ntp.cpp:161 read_loop ] ntp offset: 1256929, round_trip_delay 28530 1162765ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 1256929

And in my another node (with active witness) I got the same error messages

Code: [Select]
1568000ms th_a witness.cpp:239 block_production_loo ] slot: 26417 schedu led_witness: 1.6.1446 scheduled_time: 2015-08-16T16:26:08 now: 2015-08-16T16:26:08 1568001ms th_a witness.cpp:242 block_production_loo ] Witness 1.6.1446 p roduction slot has arrived; generating a block now... 1568003ms th_a db_block.cpp:167 _push_block ] Failed to push new block: 3070000 undo_database_exception: undo database exception The database does not have enough undo history to support a blockchain with so many missed b locks. Please add a checkpoint if you would like to continue applying blocks beyond this poi nt. {"recently_missed":53819,"max_undo":1000} th_a db_update.cpp:68 update_global_dynamic_data {"next_block.block_num()":134420} th_a db_block.cpp:448 _apply_block 1568003ms th_a witness.cpp:265 block_production_loo ] Got exception whil e generating block: ...
I'm getting the same error on my delegate node.
Title: Re: Test Net for Advanced Users
Post by: betax on August 16, 2015, 05:11:04 pm: Same here... ill restart

edit: that does not do anything.

Code: [Select]
74002ms th_a witness.cpp:191 operator() ] Not producing block because production is disabled. 775002ms th_a witness.cpp:239 block_production_loo ] slot: 11858 scheduled_witness: 1.6.0 scheduled_time: 2015-08-16T17:12:55 now: 2015-08-16T17:12:55 775002ms th_a witness.cpp:191 operator() ] Not producing block because production is disabled. 776002ms th_a witness.cpp:239 block_production_loo ] slot: 11859 scheduled_witness: 1.6.2 scheduled_time: 2015-08-16T17:12:56 now: 2015-08-16T17:12:56 776002ms th_a witness.cpp:191 operator() ] Not producing block because production is disabled. 777002ms th_a witness.cpp:239 block_production_loo ] slot: 11860 scheduled_witness: 1.6.1435 scheduled_time: 2015-08-16T17:12:57 now: 2015-08-16T17:12:57 777002ms th_a witness.cpp:191 operator() ] Not producing block because production is disabled.
Title: Re: Test Net for Advanced Users
Post by: abit on August 16, 2015, 05:21:10 pm: My node is stuck at 134419 as well.. is it on the right fork?
I'm not running with --enable-stale-production though..
Code: [Select]
info { "head_block_num": 134419, "head_block_id": "00020d137298dab08e3147893e61dfed75ad7d0e", "head_block_age": "8 hours old", "next_maintenance_time": "8 hours ago", "chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.1435", "1.6.1439", "1.6.1446", "1.6.5155", "1.6.5156" ], "active_committee_members": [ "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8", "1.5.9" ], "entropy": "e8f56f18210fc56faa891342f94cbade418c834f" }
Edit: I'll try to restart with BM's seed node only
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 16, 2015, 05:44:45 pm: Node up -

Code: [Select]
204.44.115.139:61705
with witness

Code: [Select]
get_witness delegate.ihashfury { "id": "1.6.1504",

I think it ready to produce blocks but not voted in yet
Title: Re: Test Net for Advanced Users
Post by: puppies on August 16, 2015, 05:49:15 pm: Im stuck after a --resync-blockchain as well.
Code: [Select]
{ "head_block_num": 147334, "head_block_id": "00023f868da02c32c1d8c6faef53b4a0c51ade92", "head_block_age": "4 hours old", "next_maintenance_time": "4 hours ago", "chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6]
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 16, 2015, 05:55:02 pm: Code: [Select]
get_dynamic_global_properties { "id": "2.1.0", "random": "cac65461d8694c0c44c9c0909041bb8d15121e79", "head_block_number": 147334, "head_block_id": "00023f868da02c32c1d8c6faef53b4a0c51ade92", "time": "2015-08-16T13:55:17", "current_witness": "1.6.1", "next_maintenance_time": "2015-08-16T14:00:00", "witness_budget": 112918612, "accounts_registered_this_interval": 0, "recently_missed_count": 998, "dynamic_flags": 0 }
Title: Re: Test Net for Advanced Users
Post by: abit on August 16, 2015, 06:11:26 pm: Quote from: iHashFury on August 16, 2015, 05:44:45 pm
Node up -

Code: [Select]
204.44.115.139:61705
with witness

Code: [Select]
get_witness delegate.ihashfury { "id": "1.6.1504",

I think it ready to produce blocks but not voted in yet
You can vote it in.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 16, 2015, 06:27:28 pm: Yep - I have voted but only had a small balance

Lots of cut, paste and import balance keys :P
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 16, 2015, 06:30:46 pm: withess print screen

Code: [Select]
1784002ms th_a witness.cpp:191 operator() ] Not producing block because production is disabled. 1785002ms th_a witness.cpp:239 block_production_loo ] slot: 16468 scheduled_witness: 1.6.0 scheduled_time: 2015-08-16T18:29:45 now: 2015-08-16T18:29:45 1785002ms th_a witness.cpp:191 operator() ] Not producing block because production is disabled. 1786001ms th_a witness.cpp:239 block_production_loo ] slot: 16469 scheduled_witness: 1.6.2 scheduled_time: 2015-08-16T18:29:46 now: 2015-08-16T18:29:46 1786002ms th_a witness.cpp:191 operator() ] Not producing block because production is disabled. 1787002ms th_a witness.cpp:239 block_production_loo ] slot: 16470 scheduled_witness: 1.6.1435 scheduled_time: 2015-08-16T18:29:47 now: 2015-08-16T18:29:47 1787002ms th_a witness.cpp:191 operator() ] Not producing block because production is disabled. 1788001ms th_a witness.cpp:239 block_production_loo ] slot: 16471 scheduled_witness: 1.6.5155 scheduled_time: 2015-08-16T18:29:48 now: 2015-08-16T18:29:48 1788002ms th_a witness.cpp:191 operator() ] Not producing block because production is disabled.
Title: Re: Test Net for Advanced Users
Post by: abit on August 16, 2015, 06:38:35 pm: Quote from: abit on August 16, 2015, 05:21:10 pm
My node is stuck at 134419 as well.. is it on the right fork?
I'm not running with --enable-stale-production though..
Code: [Select]
info { "head_block_num": 134419, "head_block_id": "00020d137298dab08e3147893e61dfed75ad7d0e", "head_block_age": "8 hours old", "next_maintenance_time": "8 hours ago", "chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.1435", "1.6.1439", "1.6.1446", "1.6.5155", "1.6.5156" ], "active_committee_members": [ "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8", "1.5.9" ], "entropy": "e8f56f18210fc56faa891342f94cbade418c834f" }
Edit: I'll try to restart with BM's seed node only

Here is log.
Code: [Select]
2015-08-16T18:06:34 p2p:message read_loop process_block_during ] received a sync block from peer 104.200.28.117:61705 node.cpp:3073 2015-08-16T18:06:34 p2p:process_backlog_of_sync_blocks process_backlog_of_s ] in process_backlog_of_sync_blocks node.c pp:2959 2015-08-16T18:06:34 p2p:process_backlog_of_sync_blocks process_backlog_of_s ] currently 1 blocks in the process of being handled node.cpp:2965 2015-08-16T18:06:34 p2p:process_backlog_of_sync_blocks process_backlog_of_s ] currently 1 sync items to consider node.cpp:2995 2015-08-16T18:06:34 p2p:process_backlog_of_sync_blocks process_backlog_of_s ] currently 0 sync items to consider node.cpp:2995 2015-08-16T18:06:34 p2p:process_backlog_of_sync_blocks process_backlog_of_s ] leaving process_backlog_of_sync_blocks, 1 processed node.cpp:3056 2015-08-16T18:06:34 p2p:process_backlog_of_sync_blocks trigger_fetch_sync_i ] Triggering fetch sync items loop now node.cpp:1081 2015-08-16T18:06:34 p2p:fetch_sync_items_loop fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:1020 2015-08-16T18:06:34 p2p:fetch_sync_items_loop fetch_sync_items_loo ] no sync items to fetch right now, going to sleep node.cpp:1070 2015-08-16T18:06:34 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] in send_sync_block_to_node_delegate() node.cpp:2777 2015-08-16T18:06:34 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] Failed to push sync block 134318 (id:00020cae30db6d247c1b3e356a55e93808e1290d): client rejected sync block sent by peer: {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"fork_database.cpp","line":51,"method":"push_block","hostname":"","thread_name":"th_a","timestamp":"2015-08-16T18:06:34"},"format":"itr != _index.get<block_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":173,"method":"_push_block","hostname":"","thread_name":"th_a","timestamp":"2015-08-16T18:06:34"},"format":"","data":{"new_block":{"previous":"00020cade4b2e23a805d33e5585cd501b327efd5","timestamp":"2015-08-16T08:55:51","witness":"1.6.1435","next_secret_hash":"852c62c5a7e927cfff752276b543b1731a58b42f","previous_secret":"ed9b9f8a4624bbb6eb2dba63336b2643a5b5561b","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f06bab5ea47138f12a31f15fb82962c87d5679b3e176002b78422f6143301870676208b51eb11bf4320a05282171e95f5c33992e3e4034e63eaf1b57f087a8827","transactions":[]}}},{"context":{"level":"warn","file":"application.cpp","line":373,"method":"handle_block","hostname":"","thread_name":"th_a","timestamp":"2015-08-16T18:06:34"},"format":"","data":{"blk_msg":{"block":{"previous":"00020cade4b2e23a805d33e5585cd501b327efd5","timestamp":"2015-08-16T08:55:51","witness":"1.6.1435","next_secret_hash":"852c62c5a7e927cfff752276b543b1731a58b42f","previous_secret":"ed9b9f8a4624bbb6eb2dba63336b2643a5b5561b","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f06bab5ea47138f12a31f15fb82962c87d5679b3e176002b78422f6143301870676208b51eb11bf4320a05282171e95f5c33992e3e4034e63eaf1b57f087a8827","transactions":[]},"block_id":"00020cae30db6d247c1b3e356a55e93808e1290d"},"sync_mode":true}}]} node.cpp:2813 2015-08-16T18:06:34 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] disconnecting client 104.200.28.117:61705 because it offered us the rejected block node.cpp:2928 2015-08-16T18:06:34 p2p:send_sync_block_to_node_delegate send_message ] peer_connection::send_message() enqueueing message of type 5011 for peer 104.200.28.117:61705 peer_connection.cpp:365 2015-08-16T18:06:34 p2p:send_sync_block_to_node_delegate send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-16T18:06:34 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-16T18:06:34 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5011 for peer 104.200.28.117:61705 peer_connection.cpp:291
Does it mean that BM's node are on a wrong fork?
Code: [Select]
... received a sync block from peer 104.200.28.117:61705 ... ... block 134318 (id:00020cae30db6d247c1b3e356a55e93808e1290d) ... ... "timestamp":"2015-08-16T18:06:34" ... {"previous":"00020cade4b2e23a805d33e5585cd501b327efd5","timestamp":"2015-08-16T08:55:51" ...
Title: Re: Test Net for Advanced Users
Post by: puppies on August 16, 2015, 06:51:59 pm: Quote from: iHashFury on August 16, 2015, 06:27:28 pm
Yep - I have voted but only had a small balance

Lots of cut, paste and import balance keys :P

Xerocs python script really helps.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 16, 2015, 08:28:17 pm: I still can't get past 147334. Anyone have a higher blockhead?
Title: Re: Test Net for Advanced Users
Post by: clayop on August 16, 2015, 11:03:24 pm: I'm still having the same problem. Waiting for Devs back
Title: Re: Test Net for Advanced Users
Post by: roadscape on August 17, 2015, 01:34:41 am: Quote from: puppies on August 16, 2015, 08:28:17 pm
I still can't get past 147334. Anyone have a higher blockhead?

I'm stuck at 147,334 as well.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 17, 2015, 02:03:36 am: if anyone wants to keep testing, I have started a new chain. Just change the seed node to 45.55.6.216:1776

You can use the same wallet, but I am assuming you will need to import_balance again.

oh. and delete the chain folder or launch with --resync-blockchain
Title: Re: Test Net for Advanced Users
Post by: abit on August 17, 2015, 09:21:06 am: Quote from: puppies on August 17, 2015, 02:03:36 am
if anyone wants to keep testing, I have started a new chain. Just change the seed node to 45.55.6.216:1776

You can use the same wallet, but I am assuming you will need to import_balance again.

oh. and delete the chain folder or launch with --resync-blockchain
Or set a different data directory. Re-syncing.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 17, 2015, 12:20:19 pm: Well this testnet died a firey death. We are looking into the cause and will report back later.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 17, 2015, 12:28:02 pm: Code: [Select]
locked >>> info info { "head_block_num": 147334, "head_block_id": "00023f868da02c32c1d8c6faef53b4a0c51ade92", "head_block_age": "23 hours old", "next_maintenance_time": "22 hours ago", "chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.1435", "1.6.1439", "1.6.1446", "1.6.5155", "1.6.5156" ], "active_committee_members": [ "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8", "1.5.9" ], "entropy": "cac65461d8694c0c44c9c0909041bb8d15121e79" }
I had a node that was a mere passive observer on the network and this was its final state.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 17, 2015, 12:54:59 pm: I have looked into why this test network died and it was due to low witness participation... test witnesses joined, got elected, and failed to produce blocks! >:( bad, bad test witnesses! :P

Under Graphene we have some "safety" features that may be overly strict in the context of a test network.

The idea is that the nodes will increase the amount of undo history they track by 2 every time a block is missed and decrease it by 1 every time a block is produced. The nodes are configured to maintain a maximum undo history and once that history has been reached no new blocks may be pushed without a checkpoint to clear the history. Since no one was around to produce a checkpoint block production simply stopped.

In a production environment we would expect that witness participation rate shouldn't fall below 66% for very long and if it did then all of the witnesses would be actively monitoring and repairing the network by setting a checkpoint.

With 1 second blocks it probably didn't take much wall-clock time for hit the limit.

Note: the reason for this limit is to make sure that no blockchain can exist where a new node could get "stuck" on a dead branch and unable to automatically rejoin the main network.
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 17, 2015, 01:08:19 pm: Quote from: bytemaster on August 17, 2015, 12:54:59 pm
I have looked into why this test network died and it was due to low witness participation... test witnesses joined, got elected, and failed to produce blocks! >:( bad, bad test witnesses! :P

Under Graphene we have some "safety" features that may be overly strict in the context of a test network.

The idea is that the nodes will increase the amount of undo history they track by 2 every time a block is missed and decrease it by 1 every time a block is produced. The nodes are configured to maintain a maximum undo history and once that history has been reached no new blocks may be pushed without a checkpoint to clear the history. Since no one was around to produce a checkpoint block production simply stopped.

In a production environment we would expect that witness participation rate shouldn't fall below 66% for very long and if it did then all of the witnesses would be actively monitoring and repairing the network by setting a checkpoint.

With 1 second blocks it probably didn't take much wall-clock time for hit the limit.

Note: the reason for this limit is to make sure that no blockchain can exist where a new node could get "stuck" on a dead branch and unable to automatically rejoin the main network.
Can we have the next blockchain start with N=101 witnesses? that way, we can gradually remove the initial delegates that are supposed to be more reliable, aren't they?
Title: Re: Test Net for Advanced Users
Post by: emski on August 17, 2015, 01:08:47 pm: Is it possible for a pre-anounce of the next test network ?
For example X days before it is started so the witnesses can prepare.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 17, 2015, 01:11:11 pm: For those asking the obvious question:

The undo history is currently set at 1000 blocks. Every 10 blocks the undo buffer grew by 2 which means it took the network 83 minutes to "hang" given that 50% of the witnesses were not producing blocks.
Title: Re: Test Net for Advanced Users
Post by: betax on August 17, 2015, 01:44:57 pm: Quote from: betax on August 16, 2015, 11:21:34 am
Quote from: puppies on August 16, 2015, 08:58:30 am
Whats going on here?
Code: [Select]
3299997ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.1 scheduled_time: 2015-08-16T08:55:00 now: 2015-08-16T08:55:00 3300134ms th_a application.cpp:342 handle_block ] Got block #134274 from network 3300436ms th_a application.cpp:342 handle_block ] Got block #134274 from network 3300538ms th_a application.cpp:437 get_item ] Request for item {"item_type":1001,"item_hash":"84dc9853e4ddd3941281f6260886aef9713829f0"} 3300997ms th_a witness.cpp:239 block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-16T08:55:01 3300998ms th_a witness.cpp:207 operator() ] Not producing block because head block time is in the future (is the system clock set correctly?). 3301997ms th_a witness.cpp:239 block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-16T08:55:02 3301998ms th_a witness.cpp:207 operator() ] Not producing block because head block time is in the future (is the system clock set correctly?). 3302997ms th_a witness.cpp:239 block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-16T08:55:03 3302998ms th_a witness.cpp:207 operator() ] Not producing block because head block time is in the future (is the system clock set correctly?). 3303997ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.1439 scheduled_time: 2015-08-16T08:55:04 now: 2015-08-16T08:55:04

I have the same issues every so often, and I have ntp running

@Bytemaster any ideas about this issue?

my witness was producing blocks, but every so often we have this issue.
Title: Re: Test Net for Advanced Users
Post by: lafona on August 17, 2015, 02:19:27 pm: Is setting a checkpoint something any witness could do? Would that have been enough keep the testnet going (at least temporarily)?
Also sorry for the massive amount of missed blocks, tried switching my witness to a rasberrypi and never managed to get it working on the vps after that. Guess I got too excited. It did seem to work fine on the micro AWS instance though.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 17, 2015, 02:29:20 pm: It's there currently a way to check witness performance? I couldn't find one outside of watching my witness node or manually looking at blocks.
Title: Re: Test Net for Advanced Users
Post by: Krills on August 17, 2015, 02:51:18 pm: For now, the dev team can't even publish a testnet for general users,how low quality they are,no wonder the price act like shit.
Title: Re: Test Net for Advanced Users
Post by: betax on August 17, 2015, 02:59:10 pm: Quote from: Krills on August 17, 2015, 02:51:18 pm
For now, the dev team can't even publish a testnet for general users,how low quality they are,no wonder the price act like shit.

This is an advanced users test net, which it was actually really good, but all of us were experimenting, getting first hands experience, setting up servers etc. So is not going to smoothly.
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 17, 2015, 03:05:55 pm: Who of you can recall bts testnets 1 through 12?
[emoji14]
Title: Re: Test Net for Advanced Users
Post by: maqifrnswa on August 17, 2015, 03:11:31 pm: Quote from: xeroc on August 17, 2015, 03:05:55 pm
Who of you can recall bts testnets 1 through 12?
[emoji14]

That was fun - especially the "do everything you can to break the network" days! It also was cool seeing the API develop and features being added and evolving.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 17, 2015, 03:14:41 pm: @bytemaster So you meant all of five test witnesses were missing blocks?
Title: Re: Test Net for Advanced Users
Post by: betax on August 17, 2015, 03:17:15 pm: Quote from: xeroc on August 17, 2015, 03:05:55 pm
Who of you can recall bts testnets 1 through 12?
[emoji14]

I do !!
Title: Re: Test Net for Advanced Users
Post by: puppies on August 17, 2015, 03:21:13 pm: Quote from: clayop on August 17, 2015, 03:14:41 pm
@bytemaster So you meant all of five test witnesses were missing blocks?

He said we lost a count of 2 every ten seconds. That would be 4 witnesses missing blocks.
Title: Re: Test Net for Advanced Users
Post by: betax on August 17, 2015, 04:14:25 pm: I was producing blocks, but every so often I had the ntp error.
Title: Re: Test Net for Advanced Users
Post by: maqifrnswa on August 17, 2015, 04:20:27 pm: side note, ARM bitshares works fine - sorry for the noise earlier -- stupid mistake on my part! next testnet I can through an RPI2 on it
Title: Re: Test Net for Advanced Users
Post by: abit on August 17, 2015, 04:35:12 pm: My test witness missed all blocks since I haven't enabled block production.. ;)
Title: Re: Test Net for Advanced Users
Post by: clayop on August 17, 2015, 04:38:41 pm: Quote from: abit on August 17, 2015, 04:35:12 pm
My test witness missed all blocks since I haven't enabled block production.. ;)

Hey! >:( :P

I believe that my witness was producing blocks. But didn't check about the ntp error.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 17, 2015, 04:59:36 pm: Quote from: abit on August 17, 2015, 04:35:12 pm
My test witness missed all blocks since I haven't enabled block production.. ;)

I may have done the same but I don't think I was voted in.

How do you enable block production?
Title: Re: Test Net for Advanced Users
Post by: betax on August 17, 2015, 05:02:21 pm: Quote from: abit on August 17, 2015, 04:35:12 pm
My test witness missed all blocks since I haven't enabled block production.. ;)

I did not enable block production, I just vote myself in.
Title: Re: Test Net for Advanced Users
Post by: betax on August 17, 2015, 05:13:21 pm: Are we going to test up to 1000 witnesses? If I am correct that is the new number...

And can we spin some test vps like the D14 in Azure with
16 cores 112 GB ram? Just to get an idea of performance, it could be same zone, etc.

Or amazon r3.8xlarge, 32, 104, 244, 2 x 320 SSD

Obviously for a short period of time ;)

Edit.. amazon option has more ram
Title: Re: Test Net for Advanced Users
Post by: puppies on August 17, 2015, 05:24:37 pm: Quote from: iHashFury on August 17, 2015, 04:59:36 pm
Quote from: abit on August 17, 2015, 04:35:12 pm
My test witness missed all blocks since I haven't enabled block production.. ;)

I may have done the same but I don't think I was voted in.

How do you enable block production?

Nothing is needed beyond launching the witness_node with the witness ID and public private key pair. You can also add them to the config.ini if you prefer.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 17, 2015, 05:37:47 pm: Quote from: puppies on August 17, 2015, 05:24:37 pm
Quote from: iHashFury on August 17, 2015, 04:59:36 pm
Quote from: abit on August 17, 2015, 04:35:12 pm
My test witness missed all blocks since I haven't enabled block production.. ;)

I may have done the same but I don't think I was voted in.

How do you enable block production?

Nothing is needed beyond launching the witness_node with the witness ID and public private key pair. You can also add them to the config.ini if you prefer.

Cool - thanks - so I did set my witness correctly :)
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 17, 2015, 06:10:38 pm: Quote from: betax on August 17, 2015, 04:14:25 pm
I was producing blocks, but every so often I had the ntp error.

I have seen that NTP error from time to time myself. We will look into it.

Vikram and I have reviewed the testnet and have identified a patch that would allow us to revive the existing test net by specifying a checkpoint. Once we are sure we can revive the testnet we will start a new network with at least 100 witness slots so that it is less likely for a few bad apples to result in this issue.

It could be that you produced blocks on a fork. If any of you have evidence that you were on a fork (have a block that wasn't included in the main chain) then that is something I am very interested in.
Title: Re: Test Net for Advanced Users
Post by: Fox on August 17, 2015, 07:51:55 pm: Quote from: betax on August 17, 2015, 05:13:21 pm
Edit.. amazon option has more ram
FWIW -Looking at my Azure VPS for Graphine, I have the G5 machine size option: 32 cores, 448GB RAM [1]
No, I'm not currently running this size during testing.

[1] http://azure.microsoft.com/en-us/pricing/details/virtual-machines/#Linux
Not all locations have the G series instances available.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 17, 2015, 08:16:52 pm: So what is the state of things at this point? I'm 90% finished rebuilding fresh from src (I presume there have been many changes since 8/9) on 2 systems.

Are you guys using the procedure in the readme for "Running private testnet", or xeroc's process for importing balances from 0.9.2?
Title: Re: Test Net for Advanced Users
Post by: betax on August 17, 2015, 08:23:05 pm: Quote from: Fox on August 17, 2015, 07:51:55 pm
Quote from: betax on August 17, 2015, 05:13:21 pm
Edit.. amazon option has more ram
FWIW -Looking at my Azure VPS for Graphine, I have the G5 machine size option: 32 cores, 448GB RAM [1]
No, I'm not currently running this size during testing.

[1] http://azure.microsoft.com/en-us/pricing/details/virtual-machines/#Linux
Not all locations have the G series instances available.

+5% G for Guthrie ? ;)
Title: Re: Test Net for Advanced Users
Post by: betax on August 17, 2015, 08:24:39 pm: Quote from: Thom on August 17, 2015, 08:16:52 pm
So what is the state of things at this point? I'm 90% finished rebuilding fresh from src (I presume there have been many changes since 8/9) on 2 systems.

Are you guys using the procedure in the readme for "Running private testnet", or xeroc's process for importing balances from 0.9.2?

Xeroc's with the bytemaster's start up parameters, see my post.
Title: Re: Test Net for Advanced Users
Post by: betax on August 17, 2015, 08:26:47 pm: Quote from: bytemaster on August 17, 2015, 06:10:38 pm
Quote from: betax on August 17, 2015, 04:14:25 pm
I was producing blocks, but every so often I had the ntp error.

I have seen that NTP error from time to time myself. We will look into it.

Vikram and I have reviewed the testnet and have identified a patch that would allow us to revive the existing test net by specifying a checkpoint. Once we are sure we can revive the testnet we will start a new network with at least 100 witness slots so that it is less likely for a few bad apples to result in this issue.

It could be that you produced blocks on a fork. If any of you have evidence that you were on a fork (have a block that wasn't included in the main chain) then that is something I am very interested in.

From the comments with logs, the blocks I could see were ~ matching my current blocks so I don't think we forked.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 17, 2015, 08:44:25 pm: Quote from: betax on August 17, 2015, 08:24:39 pm
Quote from: Thom on August 17, 2015, 08:16:52 pm
So what is the state of things at this point? I'm 90% finished rebuilding fresh from src (I presume there have been many changes since 8/9) on 2 systems.

Are you guys using the procedure in the readme for "Running private testnet", or xeroc's process for importing balances from 0.9.2?

Xeroc's with the bytemaster's start up parameters, see my post.

I've been monitoring this thread all day, but I'm not sure which of your posts you're referring to, or what you mean "bytemaster's parameters" .

When I tried this on the 9th I was unable to import a balance or register a witness. I am starting to try that now. According to xeroc's instructions under git/graphene/docs, he says to start the witness with a downloaded genesis block (https://drive.google.com/open?id=0B_GVo0GoC_v_S3lPOWlUbFJFWTQ):

Code: [Select]
programs/witness_node/witness_node -s 104.200.28.117:61705 --rpc-endpoint 127.0.0.1:8090 --genesis-json aug-14-test-genesis.json
Is this still the correct IP:port for the seed node and genesis block to use?
Title: Re: Test Net for Advanced Users
Post by: puppies on August 17, 2015, 08:52:38 pm: Quote from: Thom on August 17, 2015, 08:44:25 pm
Quote from: betax on August 17, 2015, 08:24:39 pm
Quote from: Thom on August 17, 2015, 08:16:52 pm
So what is the state of things at this point? I'm 90% finished rebuilding fresh from src (I presume there have been many changes since 8/9) on 2 systems.

Are you guys using the procedure in the readme for "Running private testnet", or xeroc's process for importing balances from 0.9.2?

Xeroc's with the bytemaster's start up parameters, see my post.

I've been monitoring this thread all day, but I'm not sure which of your posts you're referring to, or what you mean "bytemaster's parameters" .

When I tried this on the 9th I was unable to import a balance or register a witness. I am starting to try that now. According to xeroc's instructions under git/graphene/docs, he says to start the witness with a downloaded genesis block (https://drive.google.com/open?id=0B_GVo0GoC_v_S3lPOWlUbFJFWTQ):

Code: [Select]
programs/witness_node/witness_node -s 104.200.28.117:61705 --rpc-endpoint 127.0.0.1:8090 --genesis-json aug-14-test-genesis.json
Is this still the correct IP:port for the seed node and genesis block to use?
Download the genesis Json in the op, and follow the commands to launch witness node and cli wallet. To import your delegate I would suggest following the link about becoming a delegate. His python script is especially useful.

The test net died, but I started another one, so if you want to test until another official one comes up replace the url in bytemasters command with 45.55.6.216:1776
Title: Re: Test Net for Advanced Users
Post by: puppies on August 17, 2015, 09:01:55 pm: Quote from: bytemaster on August 17, 2015, 06:10:38 pm
Quote from: betax on August 17, 2015, 04:14:25 pm
I was producing blocks, but every so often I had the ntp error.

I have seen that NTP error from time to time myself. We will look into it.

Vikram and I have reviewed the testnet and have identified a patch that would allow us to revive the existing test net by specifying a checkpoint. Once we are sure we can revive the testnet we will start a new network with at least 100 witness slots so that it is less likely for a few bad apples to result in this issue.

It could be that you produced blocks on a fork. If any of you have evidence that you were on a fork (have a block that wasn't included in the main chain) then that is something I am very interested in.

If we all added a checkpoint = to our config.ini or will it require a different build?
Title: Re: Test Net for Advanced Users
Post by: Thom on August 17, 2015, 09:02:26 pm: Thanks puppies.

I'll go back to the OP here, thought was was really old & outdated by now, but I guess not.

I'll use the 45.55.6.216:1776 seed node you mentioned.

I started the witness on the unedited config.ini file with the seed from xeroc's write up. It runs, but the cli crashes:

Code: [Select]
deletech@Jessie:~/bts2.0$ ./cli_wallet -s ws://127.0.0.1:8090 Logging RPC to file: logs/rpc/rpc.log 3273995ms th_a main.cpp:111 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W 3273995ms th_a main.cpp:115 main ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV 3273995ms th_a main.cpp:116 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3 Starting a new wallet with chain ID 3fda83797955b6d7c3916a08bab36f9a86169c23298a5f519e48dff1d4e6475a (from egenesis) 3273995ms th_a main.cpp:163 main ] wdata.ws_server: ws://127.0.0.1:8090 3273997ms th_a main.cpp:168 main ] wdata.ws_user: wdata.ws_password: 0 exception: unspecified Remote server gave us an unexpected chain_id {"remote_chain_id":"a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c","chain_id":"3fda83797955b6d7c3916a08bab36f9a86169c23298a5f519e48dff1d4e6475a"} th_a wallet.cpp:375 wallet_api_impl
That's probably expected. I review the OP and see if I can get up to speed...
Title: Re: Test Net for Advanced Users
Post by: puppies on August 17, 2015, 09:19:54 pm: Quote from: Thom on August 17, 2015, 09:02:26 pm
Thanks puppies.

I'll go back to the OP here, thought was was really old & outdated by now, but I guess not.

I'll use the 45.55.6.216:1776 seed node you mentioned.

I started the witness on the unedited config.ini file with the seed from xeroc's write up. It runs, but the cli crashes:

Code: [Select]
deletech@Jessie:~/bts2.0$ ./cli_wallet -s ws://127.0.0.1:8090 Logging RPC to file: logs/rpc/rpc.log 3273995ms th_a main.cpp:111 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W 3273995ms th_a main.cpp:115 main ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV 3273995ms th_a main.cpp:116 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3 Starting a new wallet with chain ID 3fda83797955b6d7c3916a08bab36f9a86169c23298a5f519e48dff1d4e6475a (from egenesis) 3273995ms th_a main.cpp:163 main ] wdata.ws_server: ws://127.0.0.1:8090 3273997ms th_a main.cpp:168 main ] wdata.ws_user: wdata.ws_password: 0 exception: unspecified Remote server gave us an unexpected chain_id {"remote_chain_id":"a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c","chain_id":"3fda83797955b6d7c3916a08bab36f9a86169c23298a5f519e48dff1d4e6475a"} th_a wallet.cpp:375 wallet_api_impl
That's probably expected. I review the OP and see if I can get up to speed...

Yeah you're on the wrong chain. You will need to launch with --genesis-json and --resync-blockchain.

Alternately you can add the genesis to your config.ini and delete the chain folder, or change the data directory with -d
Title: Re: Test Net for Advanced Users
Post by: Thom on August 17, 2015, 09:26:18 pm: Using this to launch the witness node, wiped the _data_dir (there doesn't seem to be a wallet yet, probably b/c it is crashing):

Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json ../Downloads/aug-14-test-genesis.json -d test_net -s 45.55.6.216:1776 --enable-stale-production -w \""1.6.0"\" \""1.6.1"\" \""1.6.2"\" \""1.6.3"\" \""1.6.4"\"
Is that correct? I'm have a little difficulty following the permutations between the instructions in the OP of this thread and xeroc's instructions for importing balances from 0.9.2. The OP doesn't appear to address importing from 0.9.2, which xeroc's instructions do. I'm just a bit confused by the mixture of accounts in this predefined genesis block and using balances imported from 0.9.2.

Not even sure if I should be trying to import a balance from 0.9.2. Is that what most of you testing now are doing or just using the balance from nathan's account mentioned in the OP?
Title: Re: Test Net for Advanced Users
Post by: Thom on August 17, 2015, 09:30:29 pm: With the witness ran as I indicated in my last post I still can't get the cli to run using the info in the OP:

Code: [Select]
./cli_wallet -w wallet_name --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6 Logging RPC to file: logs/rpc/rpc.log 1677766ms th_a main.cpp:111 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W 1677766ms th_a main.cpp:115 main ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV 1677766ms th_a main.cpp:116 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3 Starting a new wallet with chain ID 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6 (from CLI) 1677766ms th_a main.cpp:163 main ] wdata.ws_server: ws://localhost:8090 1677769ms th_a main.cpp:168 main ] wdata.ws_user: wdata.ws_password: 0 exception: unspecified Remote server gave us an unexpected chain_id {"remote_chain_id":"a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c","chain_id":"081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6"} th_a wallet.cpp:375 wallet_api_impl
Does the chain-id in the OP still correct against your seed?
Title: Re: Test Net for Advanced Users
Post by: puppies on August 17, 2015, 09:37:59 pm: Quote from: Thom on August 17, 2015, 09:30:29 pm
With the witness ran as I indicated in my last post I still can't get the cli to run using the info in the OP:

Code: [Select]
./cli_wallet -w wallet_name --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6 Logging RPC to file: logs/rpc/rpc.log 1677766ms th_a main.cpp:111 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W 1677766ms th_a main.cpp:115 main ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV 1677766ms th_a main.cpp:116 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3 Starting a new wallet with chain ID 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6 (from CLI) 1677766ms th_a main.cpp:163 main ] wdata.ws_server: ws://localhost:8090 1677769ms th_a main.cpp:168 main ] wdata.ws_user: wdata.ws_password: 0 exception: unspecified Remote server gave us an unexpected chain_id {"remote_chain_id":"a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c","chain_id":"081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6"} th_a wallet.cpp:375 wallet_api_impl
Does the chain-id in the OP still correct against your seed?

Yeah. I've still got.
[Codeunlocked >>> info
info
{
"head_block_num": 58249,
"head_block_id": "0000e389b37fdc0d2a5879c7b32f5154893bdf0b",
"head_block_age": "1 second old",
"next_maintenance_time": "4 minutes in the future",
"chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6",
"active_witnesses": [
"1.6.0",
"1.6.1",
"1.6.2",
"1.6.3",
"1.6.4",
"1.6.5",
"1.6.6",
"1.6.1435",
"1.6.1439",
"1.6.5155"
],
"active_committee_members": [
"1.5.0",
"1.5.1",
"1.5.2",
"1.5.3",
"1.5.4",
"1.5.5",
"1.5.6",
"1.5.7",
"1.5.8",
"1.5.9"
],
"entropy": "0673bf1ccd60a996958985b9e956657c6c9edc3e"
}
unlocked >>>[/code]]
Title: Re: Test Net for Advanced Users
Post by: clayop on August 17, 2015, 09:43:39 pm: Aug 17 testnet is coming
Title: Re: Test Net for Advanced Users
Post by: puppies on August 17, 2015, 09:45:31 pm: Quote from: Thom on August 17, 2015, 09:26:18 pm
Using this to launch the witness node, wiped the _data_dir (there doesn't seem to be a wallet yet, probably b/c it is crashing):

Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json ../Downloads/aug-14-test-genesis.json -d test_net -s 45.55.6.216:1776 --enable-stale-production -w \""1.6.0"\" \""1.6.1"\" \""1.6.2"\" \""1.6.3"\" \""1.6.4"\"
Is that correct? I'm have a little difficulty following the permutations between the instructions in the OP of this thread and xeroc's instructions for importing balances from 0.9.2. The OP doesn't appear to address importing from 0.9.2, which xeroc's instructions do. I'm just a bit confused by the mixture of accounts in this predefined genesis block and using balances imported from 0.9.2.

Not even sure if I should be trying to import a balance from 0.9.2. Is that what most of you testing now are doing or just using the balance from nathan's account mentioned in the OP?

Get rid of the --enable-stale-production -w \""1.6.0"\" \""1.6.1"\" \""1.6.2"\" \""1.6.3"\" \""1.6.4"\"
You will add your witness node later.

Make sure that you are modifying the test_net/config.ini the -d is the data directory. It is not the witness_node_data_dir/config.ini

I launch with ./witness_node -d test_net and everything else is in my config.ini I am at work, and only have access to my vps. I will add the first half of my config.ini in a minute.

This is the first part of my config.ini it should have all the modifications you need to change from default.
Code: [Select]
#Endpoint for P2P node to listen on p2p-endpoint = 0.0.0.0:1776 # P2P nodes to connect to on startup (may specify multiple times) # seed-node = # Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints. # checkpoint = # Endpoint for websocket RPC to listen on rpc-endpoint = 127.0.0.1:8090 # Endpoint for TLS websocket RPC to listen on # rpc-tls-endpoint = # The TLS certificate file for this server # server-pem = # Password for this certificate # server-pem-password = # File to read Genesis State from genesis-json = aug-14-test-genesis.json]

My guess from your error is that it isn't loading the genesis.json. Perhaps try moving it to your witness_node directory. Thats where mine is, hence the config.ini
Title: Re: Test Net for Advanced Users
Post by: Thom on August 17, 2015, 09:51:48 pm: Quote from: Thom on August 17, 2015, 09:26:18 pm
Using this to launch the witness node, wiped the _data_dir (there doesn't seem to be a wallet yet, probably b/c it is crashing):

Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json ../Downloads/aug-14-test-genesis.json -d test_net -s 45.55.6.216:1776 --enable-stale-production -w \""1.6.0"\" \""1.6.1"\" \""1.6.2"\" \""1.6.3"\" \""1.6.4"\"

My node is still running with those params. Getting lots of output. I started the node with no _data_dir, so I presume there's no need for the resync param. Always start with the --genesis-json param using aug json.

My IP is 72.161.53.59.

~~BTW, are you on skype | BitShares General group? Might be faster than forum posts.~~

OK I see you posted as I was. Thanks for the config, that helps.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 17, 2015, 09:59:55 pm: I moved the genesis json into same folder as witness binary and removed the _data_dir folder and the other cmd line params. Not using your config yet.

Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-14-test-genesis.json -d test_net -s 45.55.6.216:1776
I'll try that next. cli wallet still will not run with above witness params. I'll see if the config you posted will help that.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 17, 2015, 10:07:05 pm: This is a pain. Using these and now witness won't start:

cmd:
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" -d test_net -s 45.55.6.216:1776
test_net/config.ini:
Code: [Select]
#Endpoint for P2P node to listen on p2p-endpoint = 0.0.0.0:1776 # P2P nodes to connect to on startup (may specify multiple times) # seed-node = # Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints. # checkpoint = # Endpoint for websocket RPC to listen on rpc-endpoint = 127.0.0.1:8090 # Endpoint for TLS websocket RPC to listen on # rpc-tls-endpoint = # The TLS certificate file for this server # server-pem = # Password for this certificate # server-pem-password = # File to read Genesis State from genesis-json = aug-14-test-genesis.json # JSON file specifying API permissions # api-access = # Enable block production, even if the chain is stale. enable-stale-production = false # Percent of witnesses (0-99) that must be participating in order to produce blocks required-participation = false # Allow block production, even if the last block was produced by the same witness. allow-consecutive = false # ID of witness controlled by this node (e.g. "1.6.0", quotes are required, may specify multiple times) # witness-id = # Tuple of [PublicKey, WIF private key] (may specify multiple times) private-key = ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"] # Account ID to track history for (may specify multiple times) # track-account = # Track market history by grouping orders into buckets of equal size measured in seconds specified as a JSON array of numbers bucket-size = [15,60,300,3600,86400] # How far back in time to track history for each bucket size, measured in the number of buckets (default: 1000) history-per-size = 1000 # declare an appender named "stderr" that writes messages to the console [log.console_appender.stderr] stream=std_error # declare an appender named "p2p" that writes messages to p2p.log [log.file_appender.p2p] filename=logs/p2p/p2p.log # filename can be absolute or relative to this config file # route any messages logged to the default logger to the "stderr" logger we # declared above, if they are info level are higher [logger.default] level=info appenders=stderr # route messages sent to the "p2p" logger to the p2p appender declared above [logger.p2p] level=debug appenders=p2p
Some file is expected that is missing. I added the genesis cmd line param back in but same issue:
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" -d test_net -s 45.55.6.216:1776 558187ms th_a witness.cpp:70 plugin_initialize ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"] 558188ms th_a application.cpp:228 operator() ] Initializing database... 558191ms th_a main.cpp:173 main ] Exiting with error: 11 eof_exception: End Of File unexpected end of file {} th_a json.cpp:430 variant_from_stream {"data_dir":"/home/deletech/bts2.0/test_net/blockchain"} th_a db_management.cpp:94 open {} th_a application.cpp:301 startup
Title: Re: Test Net for Advanced Users
Post by: puppies on August 17, 2015, 10:12:21 pm: What error is it throwing? And sorry no Skype account. I probably should make one though.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 17, 2015, 10:23:30 pm: I've never seen that error. Do you have data in your blockchain directory? Maybe add a --resync-blockchain to your command
Title: Re: Test Net for Advanced Users
Post by: Thom on August 17, 2015, 10:30:19 pm: I have no fucking idea what is going on. No matter what I've tried I can't get the witness to start now.

I have tried adding the config.ini you posted to the top of mine. I've tried using ONLY what you posted as the config.ini. I've removed the -d test_net and reverted to the old seed, no matter what I get this same error. No log file is generated. There is a bug with the cmd line processing is my guess, but if so it doesn't explain why using the same args as before produces this error.

Thought the genesis file might have become corrupted, but refreshing it did nothing. Here is where I am. Using ONLY the config.ini lines you posted, no others:

Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --resync-blockchain -s 45.55.6.216:1776 -d test_net 2205326ms th_a witness.cpp:70 plugin_initialize ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"] 2205327ms th_a db_management.cpp:67 wipe ] Wiping database 2205329ms th_a object_database.cpp:82 wipe ] Wiping object_database. 2205336ms th_a application.cpp:228 operator() ] Initializing database... 2205343ms th_a main.cpp:173 main ] Exiting with error: 11 eof_exception: End Of File unexpected end of file {} th_a json.cpp:430 variant_from_stream {"data_dir":"/home/deletech/bts2.0/test_net/blockchain"} th_a db_management.cpp:94 open {} th_a application.cpp:301 startup
I'll switch over and try this on one of my VPS systems and see if I can get anywhere.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 17, 2015, 10:56:40 pm: perhaps try
Code: [Select]
./witness_node -d new-data-dirlet it start up and then CTRL C to kill it. Then do
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-14-test-genesis.json -d new-data-dir -s 45.55.6.216:1776If that doesn't work then I am completely out of ideas.
Title: Re: Test Net for Advanced Users
Post by: abit on August 17, 2015, 11:18:13 pm: Quote from: puppies on August 17, 2015, 05:24:37 pm
Quote from: iHashFury on August 17, 2015, 04:59:36 pm
Quote from: abit on August 17, 2015, 04:35:12 pm
My test witness missed all blocks since I haven't enabled block production.. ;)

I may have done the same but I don't think I was voted in.

How do you enable block production?

Nothing is needed beyond launching the witness_node with the witness ID and public private key pair. You can also add them to the config.ini if you prefer.
Doesn't it need the parameter '--enable-stale-production'?
Title: Re: Test Net for Advanced Users
Post by: puppies on August 17, 2015, 11:34:41 pm: Quote from: abit on August 17, 2015, 11:18:13 pm
Quote from: puppies on August 17, 2015, 05:24:37 pm
Quote from: iHashFury on August 17, 2015, 04:59:36 pm
Quote from: abit on August 17, 2015, 04:35:12 pm
My test witness missed all blocks since I haven't enabled block production.. ;)

I may have done the same but I don't think I was voted in.

How do you enable block production?

Nothing is needed beyond launching the witness_node with the witness ID and public private key pair. You can also add them to the config.ini if you prefer.
Doesn't it need the parameter '--enable-stale-production'?
only if you are the initial node starting a stale chain. If you are joining a live chain it's not needed.
Title: Re: Test Net for Advanced Users
Post by: abit on August 17, 2015, 11:41:29 pm: Quote from: puppies on August 17, 2015, 08:52:38 pm
The test net died, but I started another one, so if you want to test until another official one comes up replace the url in bytemasters command with 45.55.6.216:1776
I'm in and producing blocks, witness 1.6.5155.
Current IP/port of my observing/seed node is 114.92.254.159:62016.

Command of witness node for observing:
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8170" --genesis-json "aug-14-test-genesis.json" --data-dir="testnet_puppies_ob" -s "45.55.6.216:1776" --p2p-endpoint "0.0.0.0:62016"
Command of CLI wallet for observing:
Code: [Select]
./cli_wallet -w wallet-testnet-puppies-ob.json --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6 -s ws://127.0.0.1:8170
Command of witness node for block producing:
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8190" --genesis-json "aug-14-test-genesis.json" --data-dir="testnet_puppies_prod" -s "45.55.6.216:1776" --witness-id '"1.6.5155"' --private-key '["MY_SIGNING_KEY","PRIVATE_KEY_OF_MY_SIGNING_KEY"]'
Command of CLI wallet for block producing:
Code: [Select]
./cli_wallet -w wallet-testnet-puppies-prod.json --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6 -s ws://127.0.0.1:8190
//Edit: removed the '--enable-stale-production' parameter.
Title: Re: Test Net for Advanced Users
Post by: abit on August 17, 2015, 11:44:33 pm: Quote from: puppies on August 17, 2015, 11:34:41 pm
Quote from: abit on August 17, 2015, 11:18:13 pm
Quote from: puppies on August 17, 2015, 05:24:37 pm
Quote from: iHashFury on August 17, 2015, 04:59:36 pm
Quote from: abit on August 17, 2015, 04:35:12 pm
My test witness missed all blocks since I haven't enabled block production.. ;)

I may have done the same but I don't think I was voted in.

How do you enable block production?

Nothing is needed beyond launching the witness_node with the witness ID and public private key pair. You can also add them to the config.ini if you prefer.
Doesn't it need the parameter '--enable-stale-production'?
only if you are the initial node starting a stale chain. If you are joining a live chain it's not needed.
I don't think so.. Without '--enable-stale-production' my witness doesn't produce blocks.
It's really confusing. Maybe it's better to have 2 parameters: '--enable-block-production' and '--enable-stale-production'.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 17, 2015, 11:48:35 pm: Quote from: abit on August 17, 2015, 11:44:33 pm
Quote from: puppies on August 17, 2015, 11:34:41 pm
Quote from: abit on August 17, 2015, 11:18:13 pm
Quote from: puppies on August 17, 2015, 05:24:37 pm
Quote from: iHashFury on August 17, 2015, 04:59:36 pm
Quote from: abit on August 17, 2015, 04:35:12 pm
My test witness missed all blocks since I haven't enabled block production.. ;)

I may have done the same but I don't think I was voted in.

How do you enable block production?

Nothing is needed beyond launching the witness_node with the witness ID and public private key pair. You can also add them to the config.ini if you prefer.
Doesn't it need the parameter '--enable-stale-production'?
only if you are the initial node starting a stale chain. If you are joining a live chain it's not needed.
I don't think so.. Without '--enable-stale-production' my witness doesn't produce blocks.
It's really confusing. Maybe it's better to have 2 parameters: '--enable-block-production' and '--enable-stale-production'.

There are two arguments: -w "1.6.X" means produce for that witness, enable-stale means produce alone.
Title: Re: Test Net for Advanced Users
Post by: lafona on August 17, 2015, 11:51:34 pm: Quote from: abit on August 17, 2015, 11:44:33 pm
Quote from: puppies on August 17, 2015, 11:34:41 pm
Quote from: abit on August 17, 2015, 11:18:13 pm
Quote from: puppies on August 17, 2015, 05:24:37 pm
Quote from: iHashFury on August 17, 2015, 04:59:36 pm
Quote from: abit on August 17, 2015, 04:35:12 pm
My test witness missed all blocks since I haven't enabled block production.. ;)

I may have done the same but I don't think I was voted in.

How do you enable block production?

Nothing is needed beyond launching the witness_node with the witness ID and public private key pair. You can also add them to the config.ini if you prefer.
Doesn't it need the parameter '--enable-stale-production'?
only if you are the initial node starting a stale chain. If you are joining a live chain it's not needed.
I don't think so.. Without '--enable-stale-production' my witness doesn't produce blocks.
It's really confusing. Maybe it's better to have 2 parameters: '--enable-block-production' and '--enable-stale-production'.
I thought the same last night, but I just set up my node earlier without the stale production and it was producing blocks when I left.
Title: Re: Test Net for Advanced Users
Post by: abit on August 18, 2015, 12:23:03 am: Quote from: bytemaster on August 17, 2015, 11:48:35 pm
There are two arguments: -w "1.6.X" means produce for that witness, enable-stale means produce alone.
Thanks. Just restarted my witness without enable-stale parameter and it works!

By the way how to "cleanly" exit the witness node? It takes much time to replay while restarting.

Quote from: lafona on August 17, 2015, 11:51:34 pm
Quote from: abit on August 17, 2015, 11:44:33 pm
Without '--enable-stale-production' my witness doesn't produce blocks.
It's really confusing. Maybe it's better to have 2 parameters: '--enable-block-production' and '--enable-stale-production'.
I thought the same last night, but I just set up my node earlier without the stale production and it was producing blocks when I left.

Maybe because the "Generated block" lines in the console log are in white color, so I didn't notice them.
Code: [Select]
540991ms th_a witness.cpp:242 block_production_loo ] Witness 1.6.5155 production slot has arrived; generating a bl ock now... 540992ms th_a witness.cpp:255 block_production_loo ] Generated block #66220 with timestamp 2015-08-18T00:09:01 at time 2015-08-18T00:09:01
And this line of log is in blue:
Code: [Select]
884991ms th_a witness.cpp:191 operator() ] Not producing block because production is disabled. 8But the real reason of 'production disabled' is "not enabled stale production && it's stale now "? I would not get confused if the log says "... because stale production is disabled".
Title: Re: Test Net for Advanced Users
Post by: abit on August 18, 2015, 02:22:05 am: Quote from: bytemaster on August 17, 2015, 06:10:38 pm
Quote from: betax on August 17, 2015, 04:14:25 pm
I was producing blocks, but every so often I had the ntp error.

I have seen that NTP error from time to time myself. We will look into it.

Vikram and I have reviewed the testnet and have identified a patch that would allow us to revive the existing test net by specifying a checkpoint. Once we are sure we can revive the testnet we will start a new network with at least 100 witness slots so that it is less likely for a few bad apples to result in this issue.

It could be that you produced blocks on a fork. If any of you have evidence that you were on a fork (have a block that wasn't included in the main chain) then that is something I am very interested in.

Looks like I'm on a fork right now, stopped syncing and stopped producing blocks. Logs of production witness are here. It perhaps caused by slow network connection to other peers.

Code: [Select]
2015-08-18T02:04:12 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.6 scheduled_time: 2015-08-18T0 2:04:13 now: 2015-08-18T02:04:13 witness.cpp:239 2015-08-18T02:04:13 th_a:invoke handle_block handle_block ] Got block #71842 from network application.cp p:342 2015-08-18T02:04:13 th_a:invoke get_item get_item ] Request for item {"item_type":1001,"item_hash":"000118a2245ede2df39a1 f4ae6da4e12f62f8232"} application.cpp:437 2015-08-18T02:04:13 th_a:invoke get_item get_item ] Serving up block #71842 application.cpp:445 2015-08-18T02:04:13 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.5155 scheduled_time: 2015-08-1 8T02:04:14 now: 2015-08-18T02:04:14 witness.cpp:239 2015-08-18T02:04:13 th_a:Witness Block Production block_production_loo ] Witness 1.6.5155 production slot has arrived; generating a bl ock now... witness.cpp:242 2015-08-18T02:04:13 th_a:Witness Block Production block_production_loo ] Generated block #71843 with timestamp 2015-08-18T02:04:14 at time 2015-08-18T02:04:14 witness.cpp:255 2015-08-18T02:04:13 th_a:invoke get_item get_item ] Request for item {"item_type":1001,"item_hash":"000118a30cd6a49579d36 ad1217b098a544a798a"} application.cpp:437 2015-08-18T02:04:13 th_a:invoke get_item get_item ] Serving up block #71843 application.cpp:445 2015-08-18T02:04:14 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.1439 scheduled_time: 2015-08-1 8T02:04:15 now: 2015-08-18T02:04:15 witness.cpp:239 2015-08-18T02:04:15 th_a:Witness Block Production block_production_loo ] slot: 2 scheduled_witness: 1.6.1 scheduled_time: 2015-08-18T0 2:04:16 now: 2015-08-18T02:04:16 witness.cpp:239 2015-08-18T02:04:16 th_a:Witness Block Production block_production_loo ] slot: 3 scheduled_witness: 1.6.0 scheduled_time: 2015-08-18T0 2:04:17 now: 2015-08-18T02:04:17 witness.cpp:239 2015-08-18T02:04:17 th_a:Witness Block Production block_production_loo ] slot: 4 scheduled_witness: 1.6.5 scheduled_time: 2015-08-18T0 2:04:18 now: 2015-08-18T02:04:18 witness.cpp:239 2015-08-18T02:04:18 th_a:Witness Block Production block_production_loo ] slot: 5 scheduled_witness: 1.6.4 scheduled_time: 2015-08-18T0 2:04:19 now: 2015-08-18T02:04:19 witness.cpp:239 2015-08-18T02:04:19 th_a:Witness Block Production block_production_loo ] slot: 6 scheduled_witness: 1.6.1435 scheduled_time: 2015-08-1 8T02:04:20 now: 2015-08-18T02:04:20 witness.cpp:239 2015-08-18T02:04:20 th_a:invoke get_item get_item ] Request for item {"item_type":1001,"item_hash":"000118a30cd6a49579d36 ad1217b098a544a798a"} application.cpp:437 2015-08-18T02:04:20 th_a:invoke get_item get_item ] Serving up block #71843 application.cpp:445 2015-08-18T02:04:20 th_a:invoke handle_block handle_block ] Got block #71844 from network application.cp p:342 2015-08-18T02:04:20 th_a:invoke handle_block handle_block ] Error when pushing block: 10 assert_exception: Assert Exception itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:51 push_block {"new_block":{"previous":"000118a3ca0d1e6e5737f248ddb53836aa6212e4","timestamp":"2015-08-18T02:04:16","witness":"1.6.1","next_secret_hash":"6449e9c56a67b58d886f2064e929f17f94fe78f1","previous_secret":"68c24af208df75b7b3d6570206492ef3bee5c5b9","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f4becadfa61a394b550ce6d086fb5d9eb3da8c883ac703048c7baee139414089f6777d1c03787d982160d23ecef7df3df3ea8713c15441247c30c4ef5568e22ac","transactions":[]}} th_a db_block.cpp:173 _push_block application.cpp:364 2015-08-18T02:04:20 th_a:Witness Block Production block_production_loo ] slot: 7 scheduled_witness: 1.6.2 scheduled_time: 2015-08-18T02:04:21 now: 2015-08-18T02:04:21 witness.cpp:239 2015-08-18T02:04:21 th_a:invoke handle_block handle_block ] Got block #71845 from network application.cpp:342 2015-08-18T02:04:21 th_a:invoke handle_block handle_block ] Error when pushing block: 10 assert_exception: Assert Exception itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:51 push_block {"new_block":{"previous":"000118a4b95f7448500f912995feeffe47e61773","timestamp":"2015-08-18T02:04:17","witness":"1.6.0","next_secret_hash":"6449e9c56a67b58d886f2064e929f17f94fe78f1","previous_secret":"68c24af208df75b7b3d6570206492ef3bee5c5b9","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"2041523e0275f0ce506c797145c86f2b5ed5fb7d9eb9cff0f1cb9364e5a06c327e535dfd76846d56824d41ad69e502d2b88679b7060b33200128991dacf92f97ae","transactions":[]}} th_a db_block.cpp:173 _push_block application.cpp:364
The observer witness node is stuck as well, haven't find related log yet.

//EDIT: console log of observer node is here.
Code: [Select]
251230ms th_a application.cpp:342 handle_block ] Got block #71840 from network 252602ms th_a application.cpp:342 handle_block ] Got block #71841 from network 253600ms th_a application.cpp:342 handle_block ] Got block #71842 from network 253998ms th_a application.cpp:342 handle_block ] Got block #71843 from network 440984ms th_a application.cpp:486 get_blockchain_synop ] reference_point: 0000000000000000000000000000000000000000 num ber_of_blocks_after_reference_point: 0 result: ["000018a317c85eac7ed13615354fcef049951d86","000098a3e1624c807fd57d019d0dcf58844905ac", "0000d8a3f2164ee15e1d2404cf5815daaf024091","0000f8a34a36120b0ccf1ed468f1e5c1a0b81239","000108a338ff000b4ea31a71938f19d6668a330e","0001 10a3079a6cdffeb63507c7c4a44406221c1b","000114a31f31315fe4d4f9a3c18923029b506111","000116a318c63b35c2dbdd46e674b4c49dcf0673","000117a3c 2bdf2658c7d67a5f9040e65ac98a02d","00011823272051adb5851eb6617b11145a03979e","0001186341115fddf7f06780b5164e5254324f96","000118833ab2b2 fc44045ebb63376313df4cf712","0001189332e4dc39800f335bbd4cf10135617a33","0001189b4b78dec8eb8efebeb5b9fab06e6647ad","0001189fcd7f19f8469 b604041fd14a225ce5bae","000118a1ac5579df7e3f7952bf3889e7f6cc8413","000118a2245ede2df39a1f4ae6da4e12f62f8232","000118a30cd6a49579d36ad1 217b098a544a798a"] 466784ms th_a application.cpp:486 get_blockchain_synop ] reference_point: 0000000000000000000000000000000000000000 num ber_of_blocks_after_reference_point: 0 result: ["000018a317c85eac7ed13615354fcef049951d86","000098a3e1624c807fd57d019d0dcf58844905ac", "0000d8a3f2164ee15e1d2404cf5815daaf024091","0000f8a34a36120b0ccf1ed468f1e5c1a0b81239","000108a338ff000b4ea31a71938f19d6668a330e","0001 10a3079a6cdffeb63507c7c4a44406221c1b","000114a31f31315fe4d4f9a3c18923029b506111","000116a318c63b35c2dbdd46e674b4c49dcf0673","000117a3c 2bdf2658c7d67a5f9040e65ac98a02d","00011823272051adb5851eb6617b11145a03979e","0001186341115fddf7f06780b5164e5254324f96","000118833ab2b2 fc44045ebb63376313df4cf712","0001189332e4dc39800f335bbd4cf10135617a33","0001189b4b78dec8eb8efebeb5b9fab06e6647ad","0001189fcd7f19f8469 b604041fd14a225ce5bae","000118a1ac5579df7e3f7952bf3889e7f6cc8413","000118a2245ede2df39a1f4ae6da4e12f62f8232","000118a30cd6a49579d36ad1 217b098a544a798a"]
Title: Re: Test Net for Advanced Users
Post by: Thom on August 18, 2015, 02:44:37 am: I finally managed to get it working on puppie's test net. I'm embarassed to say what was causing all of my difficulties, so I won't! :-[

Tomorrow is another day, and I will have much better luck I'm sure.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 18, 2015, 04:01:44 am: Quote from: Thom on August 18, 2015, 02:44:37 am
I finally managed to get it working on puppie's test net. I'm embarassed to say what was causing all of my difficulties, so I won't! :-[

Tomorrow is another day, and I will have much better luck I'm sure.

We've all been there. Don't beat yourself up :).
Title: Re: Test Net for Advanced Users
Post by: betax on August 18, 2015, 01:20:15 pm: Quote from: Thom on August 18, 2015, 02:44:37 am
I finally managed to get it working on puppie's test net. I'm embarassed to say what was causing all of my difficulties, so I won't! :-[

Tomorrow is another day, and I will have much better luck I'm sure.

Don't worry, as you have seen we all have struggled. Apologies I could not point you directly to my post as I was sneaking a few responses before travelling ;)
Title: Re: Test Net for Advanced Users
Post by: abit on August 18, 2015, 02:51:03 pm: Got stuck in puppies' chain yesterday:
Code: [Select]
"head_block_num": 72042.
Unable to sync today:
Code: [Select]
2015-08-18T14:46:05 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Disconnecting peer 45.55.6.216:1776 because they didn't respond to my request for sync item 00000064848aa88b1476bf797ad9560c08b4b239 node.cpp:1307
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 18, 2015, 03:14:22 pm: For those getting error messages about your "clock" being out of sync, the issue was a bad error message. Once every maintenance interval the blockchain skips some slots (currently configured to be 3) so that nodes can perform computational tasks that may take longer than a fraction of the normal block interval to complete. These tasks include tallying votes among other things. I have revised the error message to be a status message indicating that it is probably just a maintenance interval.

https://github.com/cryptonomex/graphene/issues/244
Title: Re: Test Net for Advanced Users
Post by: puppies on August 18, 2015, 03:18:25 pm: The network is still up and generating blocks on at least three different systems.
Code: [Select]
"head_block_num": 113869, "head_block_id": "0001bccd0acdf8b05c58b6cc5e6e36d717de523c", "head_block_age": "2 seconds old", "next_maintenance_time": "4 minutes in the future", "chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6",It seems like your node did fork and now wont accept the proper chain.
Code: [Select]
get_block 72042 { "previous": "000119696d1d31776e6431586e14fd2e4c0b4f58", "timestamp": "2015-08-18T02:07:59", "witness": "1.6.1435", "next_secret_hash": "72dcf0475fa5d0c145a235f590b5be3597c17753", "previous_secret": "2813946aacd0bfda5541bf243f5bc47aee51e314", "transaction_merkle_root": "0000000000000000000000000000000000000000", "extensions": [], "witness_signature": "201506e5034d1df8627196bc97b5293eed3efbb6391a256789ca4a6912f169b45b51045f55f9be468a2db485bfcc4952996e10d1f4be0cc1c0eef2764470649035", "transactions": [] } locked >>> get_block 72043 get_block 72043 { "previous": "0001196a1eb9d0e2021fd4f6ac9fe452ea46d4b3", "timestamp": "2015-08-18T02:08:00", "witness": "1.6.0", "next_secret_hash": "031a792684e0d99dab315ce6aea4fa92c85c6707", "previous_secret": "cd722b49f39a4b7160e081ae2c26cdf71f8e9194", "transaction_merkle_root": "0000000000000000000000000000000000000000", "extensions": [], "witness_signature": "1f64cf6d9e48683ed2259772c5006c0a1ec195dc280c59b5941250fa1581e8b86c0d32ed49d47d9d57cc87b3088e2f52bc15c7dc500955fa334864a3ed7b08be63", "transactions": [] } locked >>> get_block 72044 get_block 72044 { "previous": "0001196bf9cf506fb01511e20c8566694b952a7d", "timestamp": "2015-08-18T02:08:01", "witness": "1.6.4", "next_secret_hash": "42899548ec99624cb2102330c429562510ef09a0", "previous_secret": "2777b474efe4774a69d716f61b5cf156deb3a232", "transaction_merkle_root": "0000000000000000000000000000000000000000", "extensions": [], "witness_signature": "1f02312f66e1dcf78335d1c5ee999181cd3a0191d927d48376fa5702a493d418514d01eb530328c2dee956d5824103b8576e7974049e0d414eab142fd3ddbbe991", "transactions": [] } locked >>>im curious is your block 72042 matches mine.
Title: Re: Test Net for Advanced Users
Post by: betax on August 18, 2015, 03:26:14 pm: Quote from: bytemaster on August 18, 2015, 03:14:22 pm
For those getting error messages about your "clock" being out of sync, the issue was a bad error message. Once every maintenance interval the blockchain skips some slots (currently configured to be 3) so that nodes can perform computational tasks that may take longer than a fraction of the normal block interval to complete. These tasks include tallying votes among other things. I have revised the error message to be a status message indicating that it is probably just a maintenance interval.

https://github.com/cryptonomex/graphene/issues/244

+5%
Title: Re: Test Net for Advanced Users
Post by: betax on August 18, 2015, 03:36:13 pm: @Bytemaster are you going to launch a new test net or shall we all stick with puppies ?
Title: Re: Test Net for Advanced Users
Post by: abit on August 18, 2015, 03:46:28 pm: Quote from: puppies on August 18, 2015, 03:18:25 pm
The network is still up and generating blocks on at least three different systems.
Code: [Select]
"head_block_num": 113869, "head_block_id": "0001bccd0acdf8b05c58b6cc5e6e36d717de523c", "head_block_age": "2 seconds old", "next_maintenance_time": "4 minutes in the future", "chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6",It seems like your node did fork and now wont accept the proper chain.
Code: [Select]
get_block 72042 { "previous": "000119696d1d31776e6431586e14fd2e4c0b4f58", "timestamp": "2015-08-18T02:07:59", "witness": "1.6.1435", "next_secret_hash": "72dcf0475fa5d0c145a235f590b5be3597c17753", "previous_secret": "2813946aacd0bfda5541bf243f5bc47aee51e314", "transaction_merkle_root": "0000000000000000000000000000000000000000", "extensions": [], "witness_signature": "201506e5034d1df8627196bc97b5293eed3efbb6391a256789ca4a6912f169b45b51045f55f9be468a2db485bfcc4952996e10d1f4be0cc1c0eef2764470649035", "transactions": [] } locked >>> get_block 72043 get_block 72043 { "previous": "0001196a1eb9d0e2021fd4f6ac9fe452ea46d4b3", "timestamp": "2015-08-18T02:08:00", "witness": "1.6.0", "next_secret_hash": "031a792684e0d99dab315ce6aea4fa92c85c6707", "previous_secret": "cd722b49f39a4b7160e081ae2c26cdf71f8e9194", "transaction_merkle_root": "0000000000000000000000000000000000000000", "extensions": [], "witness_signature": "1f64cf6d9e48683ed2259772c5006c0a1ec195dc280c59b5941250fa1581e8b86c0d32ed49d47d9d57cc87b3088e2f52bc15c7dc500955fa334864a3ed7b08be63", "transactions": [] } locked >>> get_block 72044 get_block 72044 { "previous": "0001196bf9cf506fb01511e20c8566694b952a7d", "timestamp": "2015-08-18T02:08:01", "witness": "1.6.4", "next_secret_hash": "42899548ec99624cb2102330c429562510ef09a0", "previous_secret": "2777b474efe4774a69d716f61b5cf156deb3a232", "transaction_merkle_root": "0000000000000000000000000000000000000000", "extensions": [], "witness_signature": "1f02312f66e1dcf78335d1c5ee999181cd3a0191d927d48376fa5702a493d418514d01eb530328c2dee956d5824103b8576e7974049e0d414eab142fd3ddbbe991", "transactions": [] } locked >>>im curious is your block 72042 matches mine.
Looks like my node produced a #72042 block but failed to broadcast it in time (networking issue) then got stuck. It got #72043 and following blocks but failed to push them into chain database, because those blocks are linked to another #72042, but it didn't request for that #72042.
There could be an issue in code. Maybe current code just throw out an exception in this case. Maybe it's better to temporarily save the new block and request for it's previous block if it's not same as the one in current fork.

Just restarted my node and catching up.

The node is in China, network condition will be OK in next 8 hours or so (mid-night), and may go bad again after that.

//update: my node should have produced a #72042 block but not #72043.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 18, 2015, 04:15:10 pm: Last night when I was able to successfully start the witness node and connect the cli wallet to it I had to change the chain-id to what the witness reported rather than the value in the OP. In looking at the puppies post today (quoted by abit) the chain-id is back to original in OP.

The 2 values I've seen follow. Would someone explain what is the chain-id and why does it keep changing? Are we running separate tests on each chain or is it simply a test of stamina to make sure "advanced" people can keep up with changes here :)

1) 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6
2) a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c

I suspect the chain-id I connected with last night was some temporary chain puppies ran for a time. I'll use the value in the OP if that's where we're all converging. I now need to create an account, migrate a balance so it can be upgraded to lifetime membership and then register it as a witness. Is all that covered by xeroc's doc linked in the OP? Has anything changed in that process?

For example, should I use puppies seed IP or the one in the OP? Does that even matter? My mind is buzzing with all these details :o
Title: Re: Test Net for Advanced Users
Post by: puppies on August 18, 2015, 04:25:58 pm: Quote from: Thom on August 18, 2015, 04:15:10 pm
Last night when I was able to successfully start the witness node and connect the cli wallet to it I had to change the chain-id to what the witness reported rather than the value in the OP. In looking at the puppies post today (quoted by abit) the chain-id is back to original in OP.

The 2 values I've seen follow. Would someone explain what is the chain-id and why does it keep changing? Are we running separate tests on each chain or is it simply a test of stamina to make sure "advanced" people can keep up with changes here :)

1) 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6
2) a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c

I suspect the chain-id I connected with last night was some temporary chain puppies ran for a time. I'll use the value in the OP if that's where we're all converging. I now need to create an account, migrate a balance so it can be upgraded to lifetime membership and then register it as a witness. Is all that covered by xeroc's doc linked in the OP? Has anything changed in that process?

For example, should I use puppies seed IP or the one in the OP? Does that even matter? My mind is buzzing with all these details :o

Your current delegate is already set up as a witness
Code: [Select]
get_witness delegate.verbaltech { "id": "1.6.1530", "witness_account": "1.2.22307", "signing_key": "GPH52ms1dYJko2v5vS3rCdVLzQBogjeDRc1CpkaZ4seC4J4H7Uc71", "next_secret_hash": "5c00bd4aca04a9057c09b20b05f723f2e23deb65", "previous_secret": "0000000000000000000000000000000000000000", "vote_id": "1:1530", "total_votes": 0, "url": "" }You need to launch the witness node with your id 1.6.1530. your public signing key, and the corresponding private key. Init delegates have 0 votes so you can be voted in with limited funds. let me know when you're up and running and I can vote you in.

Xeroc's instructions on becoming a delegate explain how to find your private key and launch, but some of syntax appears to be incorrect.(not sure if the wiki has been updated yet) I would re read the first 4 pages of this thread, as there are numerous examples of how to launch the witness node correctly.

EDIT
in regards to the chain id. I thought I would have to change it when I relaunched the test net, but when I launched with the correct genesis it used the same chain id. I am guessing that the chain id is derived from the genesis block. Hopefully BM can explain.

In regards to the -s node, I do not know if BMs node is connected to my test net, as I havent found a way to check peers within the wallet, and I havent dug through the logs to see all connected nodes. I would suggest that you use 45.55.6.216:1776 until BM posts a new test net (which will probably require a rebuild of the executables)
Title: Re: Test Net for Advanced Users
Post by: Thom on August 18, 2015, 05:02:41 pm: Thanks puppies. I will review those posts.

I just now started a witness node using:

Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --resync-blockchain -d test_net -s 45.55.6.216:1776 ./cli_wallet -w test_wallet --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6
and the chain-id reported by the cli_wallet in the info api call is "a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c", not what was provided on the cmd line. Is that b/c I'm connecting to your seed?

Again, just trying to be on the same page as everyone testing here, but I'm not sure I am, which is why I am asking all these questions.

Also, is it necessary to do the set_password every time you start the wallet? Where is the wallet folder stored? It doesn't seem to be in the same folder as cli_wallet. I have reviewed the "cli wallet cookbook" but it didn't answer that. Every time I start the cli_wallet I have to set the password, why?

Witness questions

I am surprised to hear delegate.verbaltech is already registered as a witness. When did that happen? I was under the distinct impression from reading xeroc's doc that getting to that stage took a number of steps, like migrating balances, upgrading to lifetime member status etc.

I found the info on how to I specify the witness id, there may be a problem on using the signing keys for delegate.verbaltech. I'm sending you a PM about that issue, which may be the last huddle to jump over.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 18, 2015, 05:04:26 pm: and now my node with my personal delegate seems to have forked. This should be the relevant log
Code: [Select]
h_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104 2015-08-18T16:27:33 p2p:message read_loop on_message ] handling message block_message_type 1a3a73d360660de01a4b1f9dfcc5add8d5ee3aa4 size 173 from peer 114.92.254.159:62016 node.cpp:1651 2015-08-18T16:27:33 p2p:message read_loop process_block_during ] received a block from peer 114.92.254.159:62016, passing it to client node.cpp:3087 2015-08-18T16:27:33 p2p:message read_loop process_block_during ] Successfully pushed block 118179 (id:0001cda313b6a140c0f384624e632c95fbed9804) node.cpp:3109 2015-08-18T16:27:33 p2p:message read_loop process_block_during ] client validated the block, advertising it to other peers node.cpp:3133 2015-08-18T16:27:33 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (82 left) peer_connection.cpp:479 2015-08-18T16:27:33 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 0 advertised to us (108 left) peer_connection.cpp:479 2015-08-18T16:27:33 p2p:advertise_inventory_loop advertise_inventory_ ] beginning an iteration of advertise inventory node.cpp:1175 2015-08-18T16:27:33 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: true node.cpp:1188 2015-08-18T16:27:33 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (82 left) peer_connection.cpp:479 2015-08-18T16:27:33 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: false node.cpp:1188 2015-08-18T16:27:33 p2p:advertise_inventory_loop advertise_inventory_ ] inventory_to_advertise: [{"item_type":1001,"item_hash":"1a3a73d360660de01a4b1f9dfcc5add8d5ee3aa4"}] node.cpp:1196 2015-08-18T16:27:33 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_advertised_to_peer.find(item_to_advertise): {"item":{"item_type":1476398304,"item_hash":"847f0000000000000000000078a30558847f0000"},"timestamp":"2016-10-13T22:37:12"} node.cpp:1200 2015-08-18T16:27:33 p2p:advertise_inventory_loop advertise_inventory_ ] advertising 0 new item(s) of 0 type(s) to peer 45.55.6.216:1776 node.cpp:1218 2015-08-18T16:27:33 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 0 advertised to us (108 left) peer_connection.cpp:479 2015-08-18T16:27:33 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104 2015-08-18T16:27:33 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type e8c9515d4e56d73cbb49ed5d56eedf4d6901b073 size 25 from peer 114.92.254.159:62016 node.cpp:1651 2015-08-18T16:27:33 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (82 left) peer_connection.cpp:479 2015-08-18T16:27:33 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 114.92.254.159:62016 node.cpp:2613 2015-08-18T16:27:33 p2p:message read_loop on_item_ids_inventor ] adding item ac3580aa78a43aa6cab5e0599c05aa65a0818117 from inventory message to our list of items to fetch node.cpp:2647 2015-08-18T16:27:33 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:1104 2015-08-18T16:27:33 p2p:fetch_items_loop fetch_items_loop ] requesting item ac3580aa78a43aa6cab5e0599c05aa65a0818117 from peer 114.92.254.159:62016 node.cpp:1123 2015-08-18T16:27:33 p2p:fetch_items_loop send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 114.92.254.159:62016 peer_connection.cpp:365 2015-08-18T16:27:33 p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-18T16:27:33 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-18T16:27:33 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 114.92.254.159:62016 peer_connection.cpp:291 2015-08-18T16:27:33 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 114.92.254.159:62016 peer_connection.cpp:294 2015-08-18T16:27:33 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-18T16:27:33 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-18T16:27:34 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 273c1c45d465267877955f6a74879444f50acb87 size 25 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-18T16:27:34 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 1 advertised to us (107 left) peer_connection.cpp:479 2015-08-18T16:27:34 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-18T16:27:34 p2p:message read_loop on_item_ids_inventor ] adding item 68653fd811768cb6bb2ef6a63d73bdf9298beb95 from inventory message to our list of items to fetch node.cpp:2647 2015-08-18T16:27:34 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:1104 2015-08-18T16:27:34 p2p:fetch_items_loop fetch_items_loop ] requesting item 68653fd811768cb6bb2ef6a63d73bdf9298beb95 from peer 45.55.6.216:1776 node.cpp:1123 2015-08-18T16:27:34 p2p:fetch_items_loop send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:365 2015-08-18T16:27:34 p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-18T16:27:34 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-18T16:27:34 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:291 2015-08-18T16:27:34 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 45.55.6.216:1776 peer_connection.cpp:294 2015-08-18T16:27:34 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-18T16:27:34 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-18T16:27:34 p2p:message read_loop on_message ] handling message block_message_type 68653fd811768cb6bb2ef6a63d73bdf9298beb95 size 173 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-18T16:27:34 p2p:message read_loop process_block_during ] received a block from peer 45.55.6.216:1776, passing it to client node.cpp:3087 2015-08-18T16:27:34 p2p:message read_loop process_block_during ] Failed to push block 118181 (id:0001cda58068604136998b1998eb09a3b8b3fa56), client rejected block sent by peer node.cpp:3198 2015-08-18T16:27:34 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104 2015-08-18T16:27:34 p2p:message read_loop on_message ] handling message block_message_type ac3580aa78a43aa6cab5e0599c05aa65a0818117 size 172 from peer 114.92.254.159:62016 node.cpp:1651 2015-08-18T16:27:34 p2p:message read_loop process_block_during ] received a block from peer 114.92.254.159:62016, passing it to client node.cpp:3087 2015-08-18T16:27:34 p2p:message read_loop process_block_during ] Successfully pushed block 118180 (id:0001cda4fff8b59d6242e9cfbb706492a6b250ea) node.cpp:3109 2015-08-18T16:27:34 p2p:message read_loop process_block_during ] client validated the block, advertising it to other peers node.cpp:3133 2015-08-18T16:27:34 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (83 left) peer_connection.cpp:479 2015-08-18T16:27:34 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 0 advertised to us (108 left) peer_connection.cpp:479 2015-08-18T16:27:34 p2p:advertise_inventory_loop advertise_inventory_ ] beginning an iteration of advertise inventory node.cpp:1175 2015-08-18T16:27:34 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: true node.cpp:1188 2015-08-18T16:27:34 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (83 left) peer_connection.cpp:479 2015-08-18T16:27:34 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: false node.cpp:1188 2015-08-18T16:27:34 p2p:advertise_inventory_loop advertise_inventory_ ] inventory_to_advertise: [{"item_type":1001,"item_hash":"ac3580aa78a43aa6cab5e0599c05aa65a0818117"}] node.cpp:1196 2015-08-18T16:27:34 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_advertised_to_peer.find(item_to_advertise): {"item":{"item_type":1476398304,"item_hash":"847f0000000000000000000078a30558847f0000"},"timestamp":"2016-10-13T22:37:12"} node.cpp:1200 2015-08-18T16:27:34 p2p:advertise_inventory_loop advertise_inventory_ ] advertising 0 new item(s) of 0 type(s) to peer 45.55.6.216:1776 node.cpp:1218 2015-08-18T16:27:34 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 0 advertised to us (108 left) peer_connection.cpp:479 2015-08-18T16:27:34 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104 2015-08-18T16:27:35 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 7961814825b2c7f2b262b8e14426da647ff4b137 size 25 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-18T16:27:35 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 1 advertised to us (107 left) peer_connection.cpp:479 2015-08-18T16:27:35 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-18T16:27:35 p2p:message read_loop on_item_ids_inventor ] adding item f2420b4d7371ddf4aa1cb07d5561a0b65e6f1014 from inventory message to our list of items to fetch node.cpp:2647 2015-08-18T16:27:35 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:1104 2015-08-18T16:27:35 p2p:fetch_items_loop fetch_items_loop ] requesting item f2420b4d7371ddf4aa1cb07d5561a0b65e6f1014 from peer 45.55.6.216:1776 node.cpp:1123 2015-08-18T16:27:35 p2p:fetch_items_loop send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:365 2015-08-18T16:27:35 p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-18T16:27:35 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-18T16:27:35 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:291 2015-08-18T16:27:35 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 45.55.6.216:1776 peer_connection.cpp:294 2015-08-18T16:27:35 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-18T16:27:35 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-18T16:27:35 p2p:message read_loop on_message ] handling message block_message_type f2420b4d7371ddf4aa1cb07d5561a0b65e6f1014 size 172 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-18T16:27:35 p2p:message read_loop process_block_during ] received a block from peer 45.55.6.216:1776, passing it to client node.cpp:3087 2015-08-18T16:27:35 p2p:message read_loop process_block_during ] Failed to push block 118182 (id:0001cda68df8d489ac600fa93f814b7cf7a18a94), client rejected block sent by peer node.cpp:3198 2015-08-18T16:27:35 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104 2015-08-18T16:27:35 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 273c1c45d465267877955f6a74879444f50acb87 size 25 from peer 114.92.254.159:62016 node.cpp:1651 2015-08-18T16:27:35 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (83 left) peer_connection.cpp:479 2015-08-18T16:27:35 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 114.92.254.159:62016 node.cpp:2613 2015-08-18T16:27:35 p2p:message read_loop on_item_ids_inventor ] adding item 68653fd811768cb6bb2ef6a63d73bdf9298beb95 from inventory message to our list of items to fetch node.cpp:2647 2015-08-18T16:27:35 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:1104 2015-08-18T16:27:35 p2p:fetch_items_loop fetch_items_loop ] requesting item 68653fd811768cb6bb2ef6a63d73bdf9298beb95 from peer 114.92.254.159:62016 node.cpp:1123 2015-08-18T16:27:35 p2p:fetch_items_loop send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 114.92.254.159:62016 peer_connection.cpp:365 2015-08-18T16:27:35 p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-18T16:27:35 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-18T16:27:35 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 114.92.254.159:62016 peer_connection.cpp:291 2015-08-18T16:27:35 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 114.92.254.159:62016 peer_connection.cpp:294 2015-08-18T16:27:35 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-18T16:27:35 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-18T16:27:35 p2p:message read_loop on_message ] handling message block_message_type 68653fd811768cb6bb2ef6a63d73bdf9298beb95 size 173 from peer 114.92.254.159:62016 node.cpp:1651 2015-08-18T16:27:35 p2p:message read_loop process_block_during ] received a block from peer 114.92.254.159:62016, passing it to client node.cpp:3087 2015-08-18T16:27:35 p2p:message read_loop process_block_during ] Successfully pushed block 118181 (id:0001cda58068604136998b1998eb09a3b8b3fa56) node.cpp:3109 2015-08-18T16:27:35 p2p:message read_loop process_block_during ] client validated the block, advertising it to other peers node.cpp:3133 2015-08-18T16:27:35 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (84 left) peer_connection.cpp:479 2015-08-18T16:27:35 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 0 advertised to us (108 left) peer_connection.cpp:479 2015-08-18T16:27:35 p2p:advertise_inventory_loop advertise_inventory_ ] beginning an iteration of advertise inventory node.cpp:1175 2015-08-18T16:27:35 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: true node.cpp:1188 2015-08-18T16:27:35 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (84 left) peer_connection.cpp:479 2015-08-18T16:27:35 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: false node.cpp:1188 2015-08-18T16:27:35 p2p:advertise_inventory_loop advertise_inventory_ ] inventory_to_advertise: [{"item_type":1001,"item_hash":"68653fd811768cb6bb2ef6a63d73bdf9298beb95"}] node.cpp:1196 2015-08-18T16:27:35 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_advertised_to_peer.find(item_to_advertise): {"item":{"item_type":1476398304,"item_hash":"847f0000000000000000000078a30558847f0000"},"timestamp":"2016-10-13T22:37:12"} node.cpp:1200 2015-08-18T16:27:35 p2p:advertise_inventory_loop advertise_inventory_ ] advertising 0 new item(s) of 0 type(s) to peer 45.55.6.216:1776 node.cpp:1218 2015-08-18T16:27:35 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 0 advertised to us (108 left) peer_connection.cpp:479 2015-08-18T16:27:35 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104
Title: Re: Test Net for Advanced Users
Post by: puppies on August 18, 2015, 05:07:53 pm: Quote from: Thom on August 18, 2015, 05:02:41 pm
Thanks puppies. I will review those posts.

I just now started a witness node using:

Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --resync-blockchain -d test_net -s 45.55.6.216:1776 ./cli_wallet -w test_wallet --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6
and the chain-id reported by the cli_wallet in the info api call is "a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c", not what was provided on the cmd line. Is that b/c I'm connecting to your seed?

Again, just trying to be on the same page as everyone testing here, but I'm not sure I am, which is why I am asking all these questions.

Also, is it necessary to do the set_password every time you start the wallet? Where is the wallet folder stored? It doesn't seem to be in the same folder as cli_wallet. I have reviewed the "cli wallet cookbook" but it didn't answer that. Every time I start the cli_wallet I have to set the password, why?

Witness questions

I am surprised to hear delegate.verbaltech is already registered as a witness. When did that happen? I was under the distinct impression from reading xeroc's doc that getting to that stage took a number of steps, like migrating balances, upgrading to lifetime member status etc.

I found the info on how to I specify the witness id, there may be a problem on using the signing keys for delegate.verbaltech. I'm sending you a PM about that issue, which may be the last huddle to jump over.

Youre getting the wrong chain id because you're not launching with the --genesis-json aug-14-test-genesis.json (typed from memory so double check syntax)

as far as the wallet goes the -w is the name of your wallet. If you change it you will need to create a new pw. I am pretty sure its saved as a file in the cli_wallet dir.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 18, 2015, 05:32:03 pm: I use -w test_wallet (see below), but there is no such folder created in the same folder as the cli_wallet binary. It doesn't seem to create one. Do I need to do that manually before launching the cli_wallet?

About the aug-genesis file, I downloaded it twice, checked it with md5 / sha256 and all copies are identical. The hashes I have for the file are:

md5: 743fef728e800f82bf381f10fb7f4b04
sha256: 83a757d971cfd7f6fe6793f98ff97e22f5637f077a8a2ffbeaaef0d48faac3ea

So this issue is probably where the file lives. If you recall I started with it in some arbitrary Downloads folder. I then moved it into the programs/witness_nodes folder. I use the -d test_net which also lives in the same folder as the binary executable, and uses has your config.ini that specifies the genesis file in it. Got any other ideas?

It seems folder / invocation issues have been common in this thread, that's what bit me yesterday in fact. Sounds like there are a few more to expose.

I start the witness and cli_wallet with shell scripts so it is the same every time. They are brain-dead simple, but it allows for consistency.

Code: [Select]
#!/bin/bash cd ~/bts2.0/graphene/programs/witness_node; ./witness_node --rpc-endpoint "127.0.0.1:8090" --resync-blockchain --witness-id '"1.6.1530"' --private-key '["MY_SIGNING_KEY","PRIVATE_KEY_OF_MY_SIGNING_KEY"]' -d test_net -s 45.55.6.216:1776
Code: [Select]
#!/bin/bash cd ~/bts2.0/graphene/programs/cli_wallet; ./cli_wallet -w test_wallet --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 18, 2015, 05:36:14 pm: Those who are reporting that they are stuck on a fork I am very interested in hearing more details.

If my understanding is correct it will fork if the block you produced doesn't get included in the final chain. I will try to replicate this behavior in a test.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 18, 2015, 05:38:31 pm: I've got to step out briefly, but I hope someone will have addressed these questions when I get back. Puppies check out the PM I sent you as well.

Thanks.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 18, 2015, 05:39:33 pm: Quote from: Thom on August 18, 2015, 05:32:03 pm

Code: [Select]
#!/bin/bash cd ~/bts2.0/graphene/programs/witness_node; ./witness_node --rpc-endpoint "127.0.0.1:8090" --resync-blockchain --witness-id '"1.6.1530"' --private-key '["MY_SIGNING_KEY","PRIVATE_KEY_OF_MY_SIGNING_KEY"]' -d test_net -s 45.55.6.216:1776

try adding
Code: [Select]
--genesis-json aug-14-test-genesis.jsonso the final line in you script will be
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --resync-blockchain --witness-id '"1.6.1530"' --private-key '["MY_SIGNING_KEY","PRIVATE_KEY_OF_MY_SIGNING_KEY"]' -d test_net -s 45.55.6.216:1776 --genesis-json aug-14-test-genesis.json
Title: Re: Test Net for Advanced Users
Post by: betax on August 18, 2015, 05:42:19 pm: and put it in the same folder as the ./witness_node
Title: Re: Test Net for Advanced Users
Post by: puppies on August 18, 2015, 05:47:07 pm: Quote from: bytemaster on August 18, 2015, 05:36:14 pm
Those who are reporting that they are stuck on a fork I am very interested in hearing more details.

If my understanding is correct it will fork if the block you produced doesn't get included in the final chain. I will try to replicate this behavior in a test.
If I am reading the logs correctly in my case it was not a generation issue, but a propogation issues. It looks like my node received block 118181 before it got 118180. It tried to push 118181 failed, then got 118180 pushed it successfully, but never went back and tried to push 118181 again so when 118182 came along it also failed to push.

Does that make sense?

Edit. NM it did go back and push 118181. I will dig in the logs more. I can upload the entire log if it will help

Edit #
Just for the record it did push 118181 then 118182, but by that time it had already recieved 118183 and 118184. It failed pushing 118184, and I don't think it ever went back and tried 118183 again. Seems the problem was from being two blocks behind
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 18, 2015, 05:54:25 pm: Quote from: abit on August 18, 2015, 03:46:28 pm
Quote from: puppies on August 18, 2015, 03:18:25 pm
The network is still up and generating blocks on at least three different systems.
Code: [Select]
"head_block_num": 113869, "head_block_id": "0001bccd0acdf8b05c58b6cc5e6e36d717de523c", "head_block_age": "2 seconds old", "next_maintenance_time": "4 minutes in the future", "chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6",It seems like your node did fork and now wont accept the proper chain.
Code: [Select]
get_block 72042 { "previous": "000119696d1d31776e6431586e14fd2e4c0b4f58", "timestamp": "2015-08-18T02:07:59", "witness": "1.6.1435", "next_secret_hash": "72dcf0475fa5d0c145a235f590b5be3597c17753", "previous_secret": "2813946aacd0bfda5541bf243f5bc47aee51e314", "transaction_merkle_root": "0000000000000000000000000000000000000000", "extensions": [], "witness_signature": "201506e5034d1df8627196bc97b5293eed3efbb6391a256789ca4a6912f169b45b51045f55f9be468a2db485bfcc4952996e10d1f4be0cc1c0eef2764470649035", "transactions": [] } locked >>> get_block 72043 get_block 72043 { "previous": "0001196a1eb9d0e2021fd4f6ac9fe452ea46d4b3", "timestamp": "2015-08-18T02:08:00", "witness": "1.6.0", "next_secret_hash": "031a792684e0d99dab315ce6aea4fa92c85c6707", "previous_secret": "cd722b49f39a4b7160e081ae2c26cdf71f8e9194", "transaction_merkle_root": "0000000000000000000000000000000000000000", "extensions": [], "witness_signature": "1f64cf6d9e48683ed2259772c5006c0a1ec195dc280c59b5941250fa1581e8b86c0d32ed49d47d9d57cc87b3088e2f52bc15c7dc500955fa334864a3ed7b08be63", "transactions": [] } locked >>> get_block 72044 get_block 72044 { "previous": "0001196bf9cf506fb01511e20c8566694b952a7d", "timestamp": "2015-08-18T02:08:01", "witness": "1.6.4", "next_secret_hash": "42899548ec99624cb2102330c429562510ef09a0", "previous_secret": "2777b474efe4774a69d716f61b5cf156deb3a232", "transaction_merkle_root": "0000000000000000000000000000000000000000", "extensions": [], "witness_signature": "1f02312f66e1dcf78335d1c5ee999181cd3a0191d927d48376fa5702a493d418514d01eb530328c2dee956d5824103b8576e7974049e0d414eab142fd3ddbbe991", "transactions": [] } locked >>>im curious is your block 72042 matches mine.
Looks like my node produced a #72042 block but failed to broadcast it in time (networking issue) then got stuck. It got #72043 and following blocks but failed to push them into chain database, because those blocks are linked to another #72042, but it didn't request for that #72042.
There could be an issue in code. Maybe current code just throw out an exception in this case. Maybe it's better to temporarily save the new block and request for it's previous block if it's not same as the one in current fork.

Just restarted my node and catching up.

The node is in China, network condition will be OK in next 8 hours or so (mid-night), and may go bad again after that.

//update: my node should have produced a #72042 block but not #72043.

Do you have the p2p logs for this?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 18, 2015, 05:55:08 pm: Quote from: puppies on August 18, 2015, 05:47:07 pm
Quote from: bytemaster on August 18, 2015, 05:36:14 pm
Those who are reporting that they are stuck on a fork I am very interested in hearing more details.

If my understanding is correct it will fork if the block you produced doesn't get included in the final chain. I will try to replicate this behavior in a test.
If I am reading the logs correctly in my case it was not a generation issue, but a propogation issues. It looks like my node received block 118181 before it got 118180. It tried to push 118181 failed, then got 118180 pushed it successfully, but never went back and tried to push 118181 again so when 118182 came along it also failed to push.

Does that make sense?

That sounds very helpful! Logs would be great.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 18, 2015, 06:01:38 pm: There are no private keys or anything like that in the p2p.log is there? I just want to double check before I post.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 18, 2015, 06:05:47 pm: Quote from: puppies on August 18, 2015, 06:01:38 pm
There are no private keys or anything like that in the p2p.log is there? I just want to double check before I post.

There shouldn't be.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 18, 2015, 06:11:23 pm: https://www.dropbox.com/s/q4abwrm8c96wxtg/p2p.log.fork.8.18.15?dl=0 (https://www.dropbox.com/s/q4abwrm8c96wxtg/p2p.log.fork.8.18.15?dl=0)

The trouble seems to start around 16:27:33
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 18, 2015, 06:27:10 pm: Quote from: puppies on August 18, 2015, 06:11:23 pm
https://www.dropbox.com/s/q4abwrm8c96wxtg/p2p.log.fork.8.18.15?dl=0 (https://www.dropbox.com/s/q4abwrm8c96wxtg/p2p.log.fork.8.18.15?dl=0)

The trouble seems to start around 16:27:33

https://github.com/cryptonomex/graphene/issues/247
Title: Re: Test Net for Advanced Users
Post by: puppies on August 18, 2015, 06:33:50 pm: slightly off topic, but is there a good resource on proper protocol to post these issues directly to github? I could post directly to github, but I'm such a github noob that I'm not sure I wouldn't be making things worse than just posting here.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 18, 2015, 07:14:35 pm: I'm getting a whole lot of this on my node running all of the init witnesses
Code: [Select]
599260ms th_a application.cpp:364 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:51 push_block {"new_block":{"previous":"0001d2f41d0e19149625d60d536830b59d41311e","timestamp":"2015-08-18T16:53:10","witness":"1.6.1439","next_secret_hash":"f94d192447e 29642fd594b22a727c5633b23229e","previous_secret":"76f3d6853731d668c0ca1444c69ee2c4105466a8","transaction_merkle_root":"000000000000000000000000000000000000000 0","extensions":[],"witness_signature":"206adacd5a039ab07d1fd430edb4217c87f0ef29cb85ebe9abf597b264cc961a670c0fd4ddff450fc1bd8b0f1123c147e9bc4af9d4d3738fac8017 8ca543747ef1","transactions":[]}} th_a db_block.cpp:173 _push_block 599263ms th_a application.cpp:364 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:51 push_block {"new_block":{"previous":"0001d2f5f40d076e7ed6a39cfd843cf6a239f1c9","timestamp":"2015-08-18T16:53:20","witness":"1.6.1439","next_secret_hash":"8c6ed73e105 dfaad5f6334962c4c0438e0990f2b","previous_secret":"57abab205a18e20ecede92a78aaa06565447d370","transaction_merkle_root":"000000000000000000000000000000000000000 0","extensions":[],"witness_signature":"1f3a5728cc46e0e9d418ace7e1647a28c4a8f346a93d513c23934f87c6e367f5fc778c8d9b8b8a3d790a390d9b47ea9a7ec874b604f1809c619a5f d9dda3fcc70b","transactions":[]}} th_a db_block.cpp:173 _push_block 599265ms th_a application.cpp:364 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception itr != _index.get<block_id>().end(): {}All of it seems to be related to lafonas witness. I can pull logs, or if it would help I can just PM bytemaster with the login credentials of the machine.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 18, 2015, 07:24:09 pm: Quote from: puppies on August 18, 2015, 07:14:35 pm
I'm getting a whole lot of this on my node running all of the init witnesses
Code: [Select]
599260ms th_a application.cpp:364 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:51 push_block {"new_block":{"previous":"0001d2f41d0e19149625d60d536830b59d41311e","timestamp":"2015-08-18T16:53:10","witness":"1.6.1439","next_secret_hash":"f94d192447e 29642fd594b22a727c5633b23229e","previous_secret":"76f3d6853731d668c0ca1444c69ee2c4105466a8","transaction_merkle_root":"000000000000000000000000000000000000000 0","extensions":[],"witness_signature":"206adacd5a039ab07d1fd430edb4217c87f0ef29cb85ebe9abf597b264cc961a670c0fd4ddff450fc1bd8b0f1123c147e9bc4af9d4d3738fac8017 8ca543747ef1","transactions":[]}} th_a db_block.cpp:173 _push_block 599263ms th_a application.cpp:364 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:51 push_block {"new_block":{"previous":"0001d2f5f40d076e7ed6a39cfd843cf6a239f1c9","timestamp":"2015-08-18T16:53:20","witness":"1.6.1439","next_secret_hash":"8c6ed73e105 dfaad5f6334962c4c0438e0990f2b","previous_secret":"57abab205a18e20ecede92a78aaa06565447d370","transaction_merkle_root":"000000000000000000000000000000000000000 0","extensions":[],"witness_signature":"1f3a5728cc46e0e9d418ace7e1647a28c4a8f346a93d513c23934f87c6e367f5fc778c8d9b8b8a3d790a390d9b47ea9a7ec874b604f1809c619a5f d9dda3fcc70b","transactions":[]}} th_a db_block.cpp:173 _push_block 599265ms th_a application.cpp:364 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception itr != _index.get<block_id>().end(): {}All of it seems to be related to lafonas witness. I can pull logs, or if it would help I can just PM bytemaster with the login credentials of the machine.

Yes, that is the line I expected would get triggered for "out-of-order" pushing of blocks. That is very helpful.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 18, 2015, 07:25:13 pm: Quote from: puppies on August 18, 2015, 06:33:50 pm
slightly off topic, but is there a good resource on proper protocol to post these issues directly to github? I could post directly to github, but I'm such a github noob that I'm not sure I wouldn't be making things worse than just posting here.

No real protocol. I suppose you should confirm that it is an actual issue before posting to github.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 18, 2015, 07:26:31 pm: Well done puppies. I think we are not that bad bad test witnesses :P
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 18, 2015, 07:27:59 pm: Everyone who has participated in one of these test network and successfully registered a witness, please post your witness ID and BTS account to this thread and I'll send you 1000 brownie pts.

This testing has been very helpful. I am actively working on a potential fix for the issues found.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 18, 2015, 07:29:05 pm: Quote from: clayop on August 18, 2015, 07:26:31 pm
Well done puppies. I think we are not that bad bad test witnesses :P

+1 You guys have done a great job. If we could find a way to reliably reproduce this with just a few nodes that would be very helpful.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 18, 2015, 07:31:53 pm: Quote from: bytemaster on August 18, 2015, 07:27:59 pm
Everyone who has participated in one of these test network and successfully registered a witness, please post your witness ID and BTS account to this thread and I'll send you 1000 brownie pts.

This testing has been very helpful. I am actively working on a potential fix for the issues found.
+5% 1.6.1435 puppies
Title: Re: Test Net for Advanced Users
Post by: betax on August 18, 2015, 07:39:19 pm: "1.6.5155" betaxtrade :D thanks
Title: Re: Test Net for Advanced Users
Post by: clayop on August 18, 2015, 07:41:46 pm: Sweet.

Witness ID: "1.6.1446"
BTS ID: clayop
Title: Re: Test Net for Advanced Users
Post by: abit on August 18, 2015, 07:45:33 pm: Quote from: bytemaster on August 18, 2015, 07:27:59 pm
Everyone who has participated in one of these test network and successfully registered a witness, please post your witness ID and BTS account to this thread and I'll send you 1000 brownie pts.

This testing has been very helpful. I am actively working on a potential fix for the issues found.
witness ID in OP's chain: "1.6.5156"
witness ID in puppies' chain: "1.6.5155"
bts account: abit
Thanks!
Title: Re: Test Net for Advanced Users
Post by: abit on August 18, 2015, 07:49:39 pm: Quote from: bytemaster on August 18, 2015, 07:29:05 pm
Quote from: clayop on August 18, 2015, 07:26:31 pm
Well done puppies. I think we are not that bad bad test witnesses :P

+1 You guys have done a great job. If we could find a way to reliably reproduce this with just a few nodes that would be very helpful.
Try run a node in a unstable network? With limited bandwidth, or heavy networking load, high latency etc.
Title: Re: Test Net for Advanced Users
Post by: betax on August 18, 2015, 08:40:48 pm: Another attempt for end to end instructions if anybody is interested.

1. Follow instructions for ubuntu build here https://github.com/cryptonomex/graphene/wiki/build-ubuntu
2. Go to the witness directory:
Code: [Select]
cd ~/graphene/programs/witness_node
3. Download genesis
Code: [Select]
wget https://www.dropbox.com/s/zxp2qg0rc9sk1kc/aug-14-test-genesis.json
4.Start a new terminal screen
Code: [Select]
screen5. Run the witness
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-14-test-genesis.json -d test_net_puppies -s 45.55.6.216:1776
Note:
-d parameter is for the directory you want the witness data to be stored
-s is the node you want to connect
6. Detach from screen
Code: [Select]
Ctrl A Ctrl D7. Extract your wif keys for user and balances as per xeroc's instructions https://github.com/cryptonomex/graphene/wiki/Howto-become-an-active-witness-in-BitShares-2.0
8. Navigate to cli_wallet
Code: [Select]
cd ~/graphene/programs/cli_wallet9. Run cli
Code: [Select]
./cli_wallet -w test_wallet_puppies --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6Note:
-w is your directory wallet
10. Setup witness as per xerocs instructions https://github.com/cryptonomex/graphene/wiki/Howto-become-an-active-witness-in-BitShares-2.0
(If you don't see any balances after import remember to list accounts) and copy your keys, witness id
11. Exit
12. Go back to your witness terminal
Code: [Select]
screen -r 13. Exit your witness ctrl c
14. Restart with parameters to start block producing (block producing needs your witness id and private keys)
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-14-test-genesis.json -d test_net_puppies -s 45.55.6.216:1776 --witness-id '"1.6.5156"' --private-key '["GPH6JhL..your.signing.key..bc5mWyCvERV3coy","5K..your.secret..a"]'15. See your witness producing blocks and
you can Ctrl A Ctrl D to detach from screen.
Title: Re: Test Net for Advanced Users
Post by: betax on August 18, 2015, 08:48:48 pm: I don't know if this is an issue, but my balances were not imported / showing until I listed accounts.
Title: Re: Test Net for Advanced Users
Post by: maqifrnswa on August 18, 2015, 09:00:52 pm: betax awesome write up! Thank you

First RPi tests: the old 256 MB pi runs out of memory and ends up using lots of swap (no surprise there...) I have a new quad core rpi2 with 1 GB ram to try next, I just need a microsd card.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 18, 2015, 09:01:42 pm: great compilation of what we learned betax
Title: Re: Test Net for Advanced Users
Post by: abit on August 18, 2015, 09:03:21 pm: Quote from: bytemaster on August 18, 2015, 05:54:25 pm

Do you have the p2p logs for this?
See comment in github: https://github.com/cryptonomex/graphene/issues/247#issuecomment-132349244.
Title: Re: Test Net for Advanced Users
Post by: betax on August 18, 2015, 09:17:07 pm: Thanks..
I have send some CORE around for testing.

I am trying to create an asset (as per our first testnets which was more fun), any idea on how to create the common options parameters in the cli?
From unit tests https://github.com/cryptonomex/graphene/blob/0295f103876afe199a5639c1a12b494f2cb59c98/tests/tests/uia_tests.cpp
Code: [Select]
asset_id_type test_asset_id = db.get_index<asset_object>().get_next_id(); 40 asset_create_operation creator; 41 creator.issuer = account_id_type(); 42 creator.fee = asset(); 43 creator.symbol = "ADVANCED"; 44 creator.common_options.max_supply = 100000000; 45 creator.precision = 2; 46 creator.common_options.market_fee_percent = GRAPHENE_MAX_MARKET_FEE_PERCENT/100; /*1%*/ 47 creator.common_options.issuer_permissions = ASSET_ISSUER_PERMISSION_MASK & ~(disable_force_settle|global_settle); 48 creator.common_options.flags = ASSET_ISSUER_PERMISSION_MASK & ~(disable_force_settle|global_settle|transfer_restricted); 49 creator.common_options.core_exchange_rate = price({asset(2),asset(1,1)}); 50 creator.common_options.whitelist_authorities = creator.common_options.blacklist_authorities = {account_id_type()};
Title: Re: Test Net for Advanced Users
Post by: puppies on August 18, 2015, 09:26:25 pm: Quote from: bytemaster on August 18, 2015, 07:29:05 pm
Quote from: clayop on August 18, 2015, 07:26:31 pm
Well done puppies. I think we are not that bad bad test witnesses :P

+1 You guys have done a great job. If we could find a way to reliably reproduce this with just a few nodes that would be very helpful.
sudo tc qdisc add dev eth0 root netem delay 1000ms
followed by
sudo tc qdisc del dev eth0 root
ten or so seconds later pretty reliably causes a fork, but not sure if its the same type. I think if you had three block producing nodes connected together this could cause the out of order problem.
Title: Re: Test Net for Advanced Users
Post by: betax on August 18, 2015, 09:26:34 pm: Quote from: maqifrnswa on August 18, 2015, 09:00:52 pm
betax awesome write up! Thank you

First RPi tests: the old 256 MB pi runs out of memory and ends up using lots of swap (no surprise there...) I have a new quad core rpi2 with 1 GB ram to try next, I just need a microsd card.

So I guess will need at least the rpi2 to start.
Title: Re: Test Net for Advanced Users
Post by: lafona on August 18, 2015, 10:03:55 pm: I had it producing blocks on the Raspberry pi B (512) earlier with maqifrnswa's build , although it may have been having problems as suggested by puppies diagnosis. I will check when I get home in a few hours. When I looked earlier it was only using 50 MB or so of swap space.

Witness ID: "1.6.1439"
BTS ID: lafona
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 18, 2015, 10:04:13 pm: Quote from: bytemaster on August 18, 2015, 07:27:59 pm
Everyone who has participated in one of these test network and successfully registered a witness, please post your witness ID and BTS account to this thread and I'll send you 1000 brownie pts.

This testing has been very helpful. I am actively working on a potential fix for the issues found.

Registered but not sure if it got voted in with the funds I had :) .

1.6.5155
Title: Re: Test Net for Advanced Users
Post by: abit on August 18, 2015, 11:15:03 pm: Quote from: Riverhead on August 18, 2015, 10:04:13 pm

Registered but not sure if it got voted in with the funds I had :) .

1.6.5155
I think this number is me.. Which chain are you in?
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 19, 2015, 12:09:36 am: Quote from: abit on August 18, 2015, 11:15:03 pm
Quote from: Riverhead on August 18, 2015, 10:04:13 pm

Registered but not sure if it got voted in with the funds I had :) .

1.6.5155
I think this number is me.. Which chain are you in?

Given the level of testing you have done I am going to guess you are in the correct chain and I'm off in left field somewhere. I was on chain: a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c

However I was never able to get the cli_wallet to report that it was syncing.
Title: Re: Test Net for Advanced Users
Post by: alt on August 19, 2015, 12:46:13 am: sorry, but which branch of graphene are you use?
I checkout branch aug-17-testnet, but can't connect to the network
Code: [Select]
2015-08-19T00:46:34 p2p:message read_loop on_closing_connectio ] Peer 104.200.28.117:61705 is disconnecting us because: You are on a different chain from me n ode.cpp:2681 2015-08-19T00:46:34 p2p:message read_loop read_loop ] disconnected 0 exception: unspecified
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 02:17:54 am: Quote from: alt on August 19, 2015, 12:46:13 am
sorry, but which branch of graphene are you use?
I checkout branch aug-17-testnet, but can't connect to the network
Code: [Select]
2015-08-19T00:46:34 p2p:message read_loop on_closing_connectio ] Peer 104.200.28.117:61705 is disconnecting us because: You are on a different chain from me n ode.cpp:2681 2015-08-19T00:46:34 p2p:message read_loop read_loop ] disconnected 0 exception: unspecified
Im still running the aug 14th test.

I have just built the aug 17th test net and when I try to launch I get a different chain id. I'm not sure how the chain id is set. I thought it was from the genesis, but I am launching with the same genesis and getting a different result.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 19, 2015, 02:33:42 am: Quote from: puppies on August 19, 2015, 02:17:54 am
Quote from: alt on August 19, 2015, 12:46:13 am
sorry, but which branch of graphene are you use?
I checkout branch aug-17-testnet, but can't connect to the network
Code: [Select]
2015-08-19T00:46:34 p2p:message read_loop on_closing_connectio ] Peer 104.200.28.117:61705 is disconnecting us because: You are on a different chain from me n ode.cpp:2681 2015-08-19T00:46:34 p2p:message read_loop read_loop ] disconnected 0 exception: unspecified
Im still running the aug 14th test.

I have just built the aug 17th test net and when I try to launch I get a different chain id. I'm not sure how the chain id is set. I thought it was from the genesis, but I am launching with the same genesis and getting a different result.

OMG, I just deleted my aug-17 branch and started building aug-14 branch (based on my guess). Will you maintain aug-14 testnet?
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 02:38:25 am: Quote from: clayop on August 19, 2015, 02:33:42 am
Quote from: puppies on August 19, 2015, 02:17:54 am
Quote from: alt on August 19, 2015, 12:46:13 am
sorry, but which branch of graphene are you use?
I checkout branch aug-17-testnet, but can't connect to the network
Code: [Select]
2015-08-19T00:46:34 p2p:message read_loop on_closing_connectio ] Peer 104.200.28.117:61705 is disconnecting us because: You are on a different chain from me n ode.cpp:2681 2015-08-19T00:46:34 p2p:message read_loop read_loop ] disconnected 0 exception: unspecified
Im still running the aug 14th test.

I have just built the aug 17th test net and when I try to launch I get a different chain id. I'm not sure how the chain id is set. I thought it was from the genesis, but I am launching with the same genesis and getting a different result.

OMG, I just deleted my aug-17 branch and started building aug-14 branch (based on my guess). Will you maintain aug-14 testnet?
yeah. I'll keep it going until bm posts a new one.

Can you post what commit works so that if anyone else wants to join in the mean time they can?

bf47a1610c4aef7e25592aa42ecd4d4ae83a2b5f works for sure.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 19, 2015, 03:30:18 am: I think that I'm in aug-14 testnet. witness id 1.6.1446

Machine type
n1-standard-1 (1 vCPU, 3.75 GB memory)
CPU platform
Intel Ivy Bridge
Zone
asia-east1-c
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 03:36:31 am: Quote from: clayop on August 19, 2015, 03:30:18 am
I think that I'm in aug-14 testnet. witness id 1.6.1446

Machine type
n1-standard-1 (1 vCPU, 3.75 GB memory)
CPU platform
Intel Ivy Bridge
Zone
asia-east1-c
yup I see you.

generating blocks and all.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 19, 2015, 03:41:44 am: I have this message (now solved but I think I should report)

Code: [Select]
2071000ms th_a witness.cpp:242 block_production_loo ] Witness 1.6.1446 p roduction slot has arrived; generating a block now... 2071002ms th_a db_block.cpp:167 _push_block ] Failed to push new block: 3070000 undo_database_exception: undo database exception The database does not have enough undo history to support a blockchain with so many missed b locks. Please add a checkpoint if you would like to continue applying blocks beyond this poi nt. {"recently_missed":1431,"max_undo":1000} th_a db_update.cpp:68 update_global_dynamic_data {"next_block.block_num()":150301} th_a db_block.cpp:448 _apply_block 2071003ms th_a witness.cpp:265 block_production_loo ] Got exception whil e generating block: 3070000 undo_database_exception: undo database exception The database does not have enough undo history to support a blockchain with so many missed b locks. Please add a checkpoint if you would like to continue applying blocks beyond this poi nt. {"recently_missed":1431,"max_undo":1000} th_a db_update.cpp:68 update_global_dynamic_data {"next_block.block_num()":150301} th_a db_block.cpp:448 _apply_block {"new_block":{"previous":"00024b1c3d09ca1f5830e3e5afa94ad35ef5bd8e","timestamp":"2015-08 -19T03:34:31","witness":"1.6.1446","next_secret_hash":"2618a50760983d98ab43df78cd9a007d2e7ea ed7","previous_secret":"e93b540ed63a628df6ef29be551fd9354dac7bed","transaction_merkle_root": "0000000000000000000000000000000000000000","extensions":[],"witness_signature":"20767d9f7cf2 cf5c83d2540b22943e052a5b0d0bb22af5485462a72d330efe82703a5fe6cef4276f0b5b3f76ea419d87901cefef 89c5878ec99add42aa24ab7071","transactions":[]}} th_a db_block.cpp:173 _push_block {"witness_id":"1.6.1446"} th_a db_block.cpp:312 _generate_block

The following is what I have done
- Start witness_node and sync blockchain
- Vote for 1.6.1446, close cli_wallet
- Unclean shutdown (Ctrl+C, Ctrl+C)
- Delete object_id(?) and witness_node dir
- Start witness_node
- After syncing, this problem begins to happen
Title: Re: Test Net for Advanced Users
Post by: clayop on August 19, 2015, 03:57:51 am: Quote from: puppies on August 19, 2015, 02:38:25 am
Quote from: clayop on August 19, 2015, 02:33:42 am
Quote from: puppies on August 19, 2015, 02:17:54 am
Quote from: alt on August 19, 2015, 12:46:13 am
sorry, but which branch of graphene are you use?
I checkout branch aug-17-testnet, but can't connect to the network
Code: [Select]
2015-08-19T00:46:34 p2p:message read_loop on_closing_connectio ] Peer 104.200.28.117:61705 is disconnecting us because: You are on a different chain from me n ode.cpp:2681 2015-08-19T00:46:34 p2p:message read_loop read_loop ] disconnected 0 exception: unspecified
Im still running the aug 14th test.

I have just built the aug 17th test net and when I try to launch I get a different chain id. I'm not sure how the chain id is set. I thought it was from the genesis, but I am launching with the same genesis and getting a different result.

OMG, I just deleted my aug-17 branch and started building aug-14 branch (based on my guess). Will you maintain aug-14 testnet?
yeah. I'll keep it going until bm posts a new one.

Can you post what commit works so that if anyone else wants to join in the mean time they can?

bf47a1610c4aef7e25592aa42ecd4d4ae83a2b5f works for sure.

Yes this commit works with aug-14 testnet
Title: Re: Test Net for Advanced Users
Post by: clayop on August 19, 2015, 04:33:44 am: Quote from: alt on August 19, 2015, 12:46:13 am
sorry, but which branch of graphene are you use?
I checkout branch aug-17-testnet, but can't connect to the network
Code: [Select]
2015-08-19T00:46:34 p2p:message read_loop on_closing_connectio ][b] Peer 104.200.28.117:61705[/b] is disconnecting us because: You are on a different chain from me n ode.cpp:2681 2015-08-19T00:46:34 p2p:message read_loop read_loop ] disconnected 0 exception: unspecified

I think you entered wrong seed address
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 05:08:51 am: Just woke up to this, witness crashed
Code: [Select]
{"new_block":{"previous":"000220b6aba8787154761a665409382bbdfd0e8e","timestamp":"2015-08-18T23:31:05","witness":"1.6.1","next_secret_hash":"51d77f1f4ae0f634c379b4c2ebe86281e4e6bbba","previous_secret":"302b516fb1585c52d55e4160217cc87bcdea1839","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f5f10bb3728f3b4e39bc173d01481859299544c25e66d5784e8197909aa42739f262f20c474c2c377e9ed60a32dfeafedcb4137b7079395cb544d6ab4b71bf8db","transactions":[]}} th_a db_block.cpp:173 _push_block 1866237ms th_a application.cpp:342 handle_block ] Got block #139448 from network 1866238ms th_a application.cpp:364 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:51 push_block {"new_block":{"previous":"000220b7468dcfdf65df858c2752c938f0bfb1e1","timestamp":"2015-08-18T23:31:06","witness":"1.6.5","next_secret_hash":"51d77f1f4ae0f634c379b4c2ebe86281e4e6bbba","previous_secret":"302b516fb1585c52d55e4160217cc87bcdea1839","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f571ecd28616e8de828c48647a217bfb52bd28a4c4fc4ab9b5c6ba7277d5d12fc30313342729b0abfc1e3ced296f51539e31c240fb57a39cdbbb0be19956bfee7","transactions":[]}} th_a db_block.cpp:173 _push_block 1867002ms th_a witness.cpp:239 block_production_loo ] slot: 1667 scheduled_witness: 1.6.5155 scheduled_time: 2015-08-18T23:31:07 now: 2015-08-18T23:31:07 1867007ms th_a application.cpp:342 handle_block ] Got block #139448 from network 1867007ms th_a application.cpp:364 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:51 push_block {"new_block":{"previous":"000220b7468dcfdf65df858c2752c938f0bfb1e1","timestamp":"2015-08-18T23:31:06","witness":"1.6.5","next_secret_hash":"51d77f1f4ae0f634c379b4c2ebe86281e4e6bbba","previous_secret":"302b516fb1585c52d55e4160217cc87bcdea1839","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f571ecd28616e8de828c48647a217bfb52bd28a4c4fc4ab9b5c6ba7277d5d12fc30313342729b0abfc1e3ced296f51539e31c240fb57a39cdbbb0be19956bfee7","transactions":[]}} th_a db_block.cpp:173 _push_block witness_node: /home/azureuser/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Aborted (core dumped)
Title: Re: Test Net for Advanced Users
Post by: abit on August 19, 2015, 06:58:49 am: Quote from: betax on August 19, 2015, 05:08:51 am
Just woke up to this, witness crashed
Code: [Select]
{"new_block":{"previous":"000220b6aba8787154761a665409382bbdfd0e8e","timestamp":"2015-08-18T23:31:05","witness":"1.6.1","next_secret_hash":"51d77f1f4ae0f634c379b4c2ebe86281e4e6bbba","previous_secret":"302b516fb1585c52d55e4160217cc87bcdea1839","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f5f10bb3728f3b4e39bc173d01481859299544c25e66d5784e8197909aa42739f262f20c474c2c377e9ed60a32dfeafedcb4137b7079395cb544d6ab4b71bf8db","transactions":[]}} th_a db_block.cpp:173 _push_block 1866237ms th_a application.cpp:342 handle_block ] Got block #139448 from network 1866238ms th_a application.cpp:364 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:51 push_block {"new_block":{"previous":"000220b7468dcfdf65df858c2752c938f0bfb1e1","timestamp":"2015-08-18T23:31:06","witness":"1.6.5","next_secret_hash":"51d77f1f4ae0f634c379b4c2ebe86281e4e6bbba","previous_secret":"302b516fb1585c52d55e4160217cc87bcdea1839","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f571ecd28616e8de828c48647a217bfb52bd28a4c4fc4ab9b5c6ba7277d5d12fc30313342729b0abfc1e3ced296f51539e31c240fb57a39cdbbb0be19956bfee7","transactions":[]}} th_a db_block.cpp:173 _push_block 1867002ms th_a witness.cpp:239 block_production_loo ] slot: 1667 scheduled_witness: 1.6.5155 scheduled_time: 2015-08-18T23:31:07 now: 2015-08-18T23:31:07 1867007ms th_a application.cpp:342 handle_block ] Got block #139448 from network 1867007ms th_a application.cpp:364 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:51 push_block {"new_block":{"previous":"000220b7468dcfdf65df858c2752c938f0bfb1e1","timestamp":"2015-08-18T23:31:06","witness":"1.6.5","next_secret_hash":"51d77f1f4ae0f634c379b4c2ebe86281e4e6bbba","previous_secret":"302b516fb1585c52d55e4160217cc87bcdea1839","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f571ecd28616e8de828c48647a217bfb52bd28a4c4fc4ab9b5c6ba7277d5d12fc30313342729b0abfc1e3ced296f51539e31c240fb57a39cdbbb0be19956bfee7","transactions":[]}} th_a db_block.cpp:173 _push_block witness_node: /home/azureuser/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Aborted (core dumped)
Me too. Stuck at 160044.
Title: Re: Test Net for Advanced Users
Post by: abit on August 19, 2015, 07:02:15 am: Quote from: clayop on August 19, 2015, 03:41:44 am
I have this message (now solved but I think I should report)

Code: [Select]
2071000ms th_a witness.cpp:242 block_production_loo ] Witness 1.6.1446 p roduction slot has arrived; generating a block now... 2071002ms th_a db_block.cpp:167 _push_block ] Failed to push new block: 3070000 undo_database_exception: undo database exception The database does not have enough undo history to support a blockchain with so many missed b locks. Please add a checkpoint if you would like to continue applying blocks beyond this poi nt. {"recently_missed":1431,"max_undo":1000} th_a db_update.cpp:68 update_global_dynamic_data {"next_block.block_num()":150301} th_a db_block.cpp:448 _apply_block 2071003ms th_a witness.cpp:265 block_production_loo ] Got exception whil e generating block: 3070000 undo_database_exception: undo database exception The database does not have enough undo history to support a blockchain with so many missed b locks. Please add a checkpoint if you would like to continue applying blocks beyond this poi nt. {"recently_missed":1431,"max_undo":1000} th_a db_update.cpp:68 update_global_dynamic_data {"next_block.block_num()":150301} th_a db_block.cpp:448 _apply_block {"new_block":{"previous":"00024b1c3d09ca1f5830e3e5afa94ad35ef5bd8e","timestamp":"2015-08 -19T03:34:31","witness":"1.6.1446","next_secret_hash":"2618a50760983d98ab43df78cd9a007d2e7ea ed7","previous_secret":"e93b540ed63a628df6ef29be551fd9354dac7bed","transaction_merkle_root": "0000000000000000000000000000000000000000","extensions":[],"witness_signature":"20767d9f7cf2 cf5c83d2540b22943e052a5b0d0bb22af5485462a72d330efe82703a5fe6cef4276f0b5b3f76ea419d87901cefef 89c5878ec99add42aa24ab7071","transactions":[]}} th_a db_block.cpp:173 _push_block {"witness_id":"1.6.1446"} th_a db_block.cpp:312 _generate_block

The following is what I have done
- Start witness_node and sync blockchain
- Vote for 1.6.1446, close cli_wallet
- Unclean shutdown (Ctrl+C, Ctrl+C)
- Delete object_id(?) and witness_node dir
- Start witness_node
- After syncing, this problem begins to happen
Looks like you're on a fork. Try resync. Don't add parameter '--enable-stale-production'.

//Edit: Ah, just saw you've solved.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 07:12:25 am: network is still up, but we are running at 70%.
Code: [Select]
unlocked >>> info info { "head_block_num": 161438, "head_block_id": "0002769e3c40d48424a73da31340397dcb3ca150", "head_block_age": "2 seconds old", "next_maintenance_time": "4 minutes in the future", "chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.1435", "1.6.1439", "1.6.1446", "1.6.5155", "1.6.5156" ], "active_committee_members": [ "1.5.10", "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8" ], "entropy": "64d465fa11e74ebc2148dbe6911f6c6f0d3b79ad" }
Title: Re: Test Net for Advanced Users
Post by: abit on August 19, 2015, 07:28:53 am: Quote from: puppies on August 19, 2015, 07:12:25 am
network is still up, but we are running at 70%.
Code: [Select]
unlocked >>> info info { "head_block_num": 161438, "head_block_id": "0002769e3c40d48424a73da31340397dcb3ca150", "head_block_age": "2 seconds old", "next_maintenance_time": "4 minutes in the future", "chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.1435", "1.6.1439", "1.6.1446", "1.6.5155", "1.6.5156" ], "active_committee_members": [ "1.5.10", "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8" ], "entropy": "64d465fa11e74ebc2148dbe6911f6c6f0d3b79ad" }
I restarted and caught up. How to see that 70%?
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 07:53:21 am: Quote from: abit on August 19, 2015, 07:28:53 am
Quote from: puppies on August 19, 2015, 07:12:25 am
network is still up, but we are running at 70%.
Code: [Select]
unlocked >>> info info { "head_block_num": 161438, "head_block_id": "0002769e3c40d48424a73da31340397dcb3ca150", "head_block_age": "2 seconds old", "next_maintenance_time": "4 minutes in the future", "chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.1435", "1.6.1439", "1.6.1446", "1.6.5155", "1.6.5156" ], "active_committee_members": [ "1.5.10", "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8" ], "entropy": "64d465fa11e74ebc2148dbe6911f6c6f0d3b79ad" }
I restarted and caught up. How to see that 70%?
I just watch my witness node and count.

Theres a whole lot of this
Code: [Select]
3312060ms th_a application.cpp:342 handle_block ] Got block #163304 from network 3313000ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.0 scheduled_time: 2015-08-19T07:55:13 now: 2015-08-19T07:55:13 3313060ms th_a application.cpp:342 handle_block ] Got block #163305 from network 3314000ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.4 scheduled_time: 2015-08-19T07:55:14 now: 2015-08-19T07:55:14 3314061ms th_a application.cpp:342 handle_block ] Got block #163306 from network 3315000ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.5156 scheduled_time: 2015-08-19T07:55:15 now: 2015-08-19T07:55:15 3316000ms th_a witness.cpp:239 block_production_loo ] slot: 2 scheduled_witness: 1.6.1439 scheduled_time: 2015-08-19T07:55:16 now: 2015-08-19T07:55:16 3316267ms th_a application.cpp:342 handle_block ] Got block #163307 from network 3317000ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.1435 scheduled_time: 2015-08-19T07:55:17 now: 2015-08-19T07:55:17 3317001ms th_a witness.cpp:242 block_production_loo ] Witness 1.6.1435 production slot has arrived; generating a block now... 3317002ms th_a witness.cpp:255 block_production_loo ] Generated block #163308 with timestamp 2015-08-19T07:55:17 at time 2015-08-19T07:55:17 3317041ms th_a application.cpp:437 get_item ] Request for item {"item_type":1001,"item_hash":"00027decc0281ab06abb0033a6e8863aa5464674"} 3317041ms th_a application.cpp:445 get_item ] Serving up block #163308 3318000ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.2 scheduled_time: 2015-08-19T07:55:18 now: 2015-08-19T07:55:18 3318057ms th_a application.cpp:342 handle_block ] Got block #163309 from network 3319000ms th_a witness.cpp:239 block_production_loo ] slot: 1 scheduled_witness: 1.6.1446 scheduled_time: 2015-08-19T07:55:19 now: 2015-08-19T07:55:19 3320000ms th_a witness.cpp:239 block_production_loo ] slot: 2 scheduled_witness: 1.6.5155 scheduled_time: 2015-08-19T07:55:20 now: 2015-08-19T07:55:20 3321000ms th_a witness.cpp:239 block_production_loo ] slot: 3 scheduled_witness: 1.6.0 scheduled_time: 2015-08-19T07:55:21 now: 2015-08-19T07:55:21 and I watch for the while lines in between the orange ones.
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 07:55:51 am: That should be me, I am syncing now..
Edit:
Starting again...
Title: Re: Test Net for Advanced Users
Post by: clayop on August 19, 2015, 07:59:38 am: My witness was forked after conducting massive transactions. I'm resyncing now and will try this experiment again tomorrow.

Edit: Ok my witness is back
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 19, 2015, 09:15:28 am: Quote from: bytemaster on August 18, 2015, 07:27:59 pm
Everyone who has participated in one of these test network and successfully registered a witness, please post your witness ID and BTS account to this thread and I'll send you 1000 brownie pts.

This testing has been very helpful. I am actively working on a potential fix for the issues found.

The firey death of the test net stopped me getting voted in :P

Code: [Select]
get_witness delegate.ihashfury { "id": "1.6.1504", "witness_account": "1.2.22277",
Is there an eta for a new offical test net?
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 19, 2015, 09:41:40 am: Hello Testneters!

Despite having a genesis-block id and lurking for years now I never got my hands dirty with bitshares-cli or setting up delegates/witnesses which is about to change right now.

I got my node running on sunday but didn't manage to create my witness-id in time. Now I'm on puppies testnet and several steps further but stuck now at "becoming a witness". I get an exception when doing "create_witness XXX":

xxx information cut away xxx
{"error":"10 assert_exception: Assert Exception\ndb().get(op.witness_account).is_lifetime_member():
xxx information cut away xxx

Is this, because the account is a lifetime member because being in the founder block? What is to be done about this? How much is the fee to create a witness or is creation free and only the voting then needs funding? A little confused about all this right now...

Several other questions arise around running the node which maybe are common ground for the experienced delegates. Is there a place to ask them (don't want to spam this thread) - should I start a new one or is there someone that can answer via PM?

Thanks and Regards,

MD
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 19, 2015, 09:48:09 am: @mudshark79
you need to upgrade to a lifetime member first

Code: [Select]
upgrade_account <accountname> true
Quote from: mudshark79 on August 19, 2015, 09:41:40 am
Is this, because the account is a lifetime member because being in the founder
block?
Lifetime member is different from being a founder!

Quote
How much is the fee to create a witness or
is creation free and only the voting then needs funding? A little confused about
all this right now...
you need funds (worthless CORE in a testnet) because you need to
* upgrade to lifetime member
* register a witness
* vote for the witness

Quote
Several other questions arise around running the node which maybe are common
ground for the experienced delegates. Is there a place to ask them (don't want
to spam this thread) - should I start a new one or is there someone that can
answer via PM?
Questions belong in the forum. Just post them here .. or maybe better start a
new thread!
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 19, 2015, 09:52:23 am: Quote from: xeroc on August 19, 2015, 09:48:09 am
@mudshark79
you need to upgrade to a lifetime member first

Code: [Select]
upgrade_account <accountname> true

Oh yes, I really just started reading the "How to become ..." again and I must have overseen this step yesterday. I just managed to create the witness. Will try to get him voted in now...

Thanks 8)

Edit: After that it was done real quick. Got it "blocking"...
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 10:16:30 am: Quote from: iHashFury on August 19, 2015, 09:15:28 am
Quote from: bytemaster on August 18, 2015, 07:27:59 pm
Everyone who has participated in one of these test network and successfully registered a witness, please post your witness ID and BTS account to this thread and I'll send you 1000 brownie pts.

This testing has been very helpful. I am actively working on a potential fix for the issues found.

The firey death of the test net stopped me getting voted in :P

Code: [Select]
get_witness delegate.ihashfury { "id": "1.6.1504", "witness_account": "1.2.22277",
Is there an eta for a new offical test net?

Join us at puppies :)
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 19, 2015, 10:34:55 am: Can't get puppie-testnet resynced. Went on a fork shortly after having produced some blocks. Did Resync without my witness-id and block production but "error when pushing block..." came back shortly after.

When i look at the nodes I'm connected to there are too few to really call it a net. Seems to be only puppies, one more and me? Or should there be someone else?
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 10:44:46 am: I'm there and producing.
Try deleting your witness data directory (i called mine something like testnet_puppies), and restart, that might help.

You are correct, there are not many people at the moment, consider this as the trial and error setting yourself up before the big testnet.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 19, 2015, 10:46:01 am: My witness_node seems to be enamored with chain-id: a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c
Code: [Select]
2295235ms th_a main.cpp:117 main ] Writing new config file at /home/james/data/github/graphene/programs/witness_node/.graphene/config.ini 2295236ms th_a witness.cpp:70 plugin_initialize ] key_id_to_wif_pair: ["GPH6MRyAjQqweee","5KwrPbwdL6PhXuwoho"] 2295237ms th_a application.cpp:228 operator() ] Initializing database... 2321896ms th_a thread.cpp:95 thread ] name:ntp tid:139671886788352 2321900ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 2321902ms th_a thread.cpp:95 thread ] name:p2p tid:139671857415936 2321909ms th_a application.cpp:129 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:33569 2321910ms th_a witness.cpp:143 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration. 2321910ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks. 2321910ms th_a main.cpp:166 main ] Chain ID is a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c 2321926ms ntp ntp.cpp:81 request_now ] sending request to 96.44.142.5:123 2321971ms ntp ntp.cpp:147 read_loop ] received ntp reply from 96.44.142.5:123 2321971ms ntp ntp.cpp:161 read_loop ] ntp offset: -7788, round_trip_delay 45567
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 19, 2015, 11:11:19 am: Quote from: betax on August 19, 2015, 10:44:46 am
I'm there and producing.
Try deleting your witness data directory (i called mine something like testnet_puppies), and restart, that might help.

You are correct, there are not many people at the moment, consider this as the trial and error setting yourself up before the big testnet.

Got it resynced an am producing blocks again. One of my remaining questions is:
Does a NAT-Situation hinder smooth operation? I can set P2P-Bind in config, is there such thing as a public address? (It's clear that running a node "at home" is not for production use but this was my first try - will prepare a VPS for next version) As I see nodes being connected on my p2p-incoming port I assume it somehow works anyway but I would like to get a better understanding...

Is there a wallet-command for listing Nodes in detail? I did netstat to get an overall status...
Title: Re: Test Net for Advanced Users
Post by: twitter on August 19, 2015, 11:15:54 am: OK. I am rebuilding it from source and give itvanother try
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 19, 2015, 11:16:50 am: Quote from: bytemaster on August 18, 2015, 07:27:59 pm
Everyone who has participated in one of these test network and successfully registered a witness, please post your witness ID and BTS account to this thread and I'll send you 1000 brownie pts.

This testing has been very helpful. I am actively working on a potential fix for the issues found.

get_witness mudshark79
{
"id": "1.6.5157",
"witness_account": "1.2.52558",
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 19, 2015, 12:01:17 pm: Having trouble get on the puppies chain

Code: [Select]
witness_node --rpc-endpoint "127.0.0.1:8090" --p2p-endpoint "127.0.0.1:61705" --genesis-json aug-14-test-genesis.json -d test_net_puppies -s 45.55.6.216:1776
I only get this chain after several retries
Code: [Select]
rm test_net_puppies/ -fr
Code: [Select]
Chain ID is a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c
cli_wallet will not load as its a different chain
Title: Re: Test Net for Advanced Users
Post by: abit on August 19, 2015, 12:14:01 pm: Quote from: mudshark79 on August 19, 2015, 11:11:19 am
Quote from: betax on August 19, 2015, 10:44:46 am
I'm there and producing.
Try deleting your witness data directory (i called mine something like testnet_puppies), and restart, that might help.

You are correct, there are not many people at the moment, consider this as the trial and error setting yourself up before the big testnet.

Got it resynced an am producing blocks again. One of my remaining questions is:
Does a NAT-Situation hinder smooth operation? I can set P2P-Bind in config, is there such thing as a public address? (It's clear that running a node "at home" is not for production use but this was my first try - will prepare a VPS for next version) As I see nodes being connected on my p2p-incoming port I assume it somehow works anyway but I would like to get a better understanding...

Is there a wallet-command for listing Nodes in detail? I did netstat to get an overall status...
Another way to specify incoming port is adding parameter --rpc-endpoint 0.0.0.0:your_port.
Doesn't like bitshares_client, the witness node doesn't enable UPNP by default. I'm currently running at home as well, I have to manually configure NAT port forwarding in my router and it works, I can see incoming connection in p2p.log.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 19, 2015, 12:15:15 pm: Quote from: iHashFury on August 19, 2015, 12:01:17 pm
Code: [Select]
Chain ID is a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89ccli_wallet will not load as its a different chain

Right there with you. I've deleted/changed the data directory, recompiled the latest pull, updated the config.ini file, and tried different seed IP's. I cannot get it to join any other chain than 9c. This was not an issue yesterday so there must be some bit left that I haven't reset.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 19, 2015, 12:19:44 pm: Glad I'm not alone :)

Will try again with a home computer this time.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 19, 2015, 12:51:38 pm: Just fired up my cubox and it on puppies chain straight away

Chain ID is 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6
Title: Re: Test Net for Advanced Users
Post by: abit on August 19, 2015, 12:53:53 pm: Is this command useful? @Riverhead
Code: [Select]
rm -rf object_database*
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 19, 2015, 01:02:16 pm: Quote from: abit on August 19, 2015, 12:53:53 pm
Is this command useful? @Riverhead
Code: [Select]
rm -rf object_database*

A good suggestion but it did not take me off 9c. It did however widen my scope outside of the data directory for my reset script so thanks for that :).
Title: Re: Test Net for Advanced Users
Post by: abit on August 19, 2015, 01:14:35 pm: Quote from: Riverhead on August 19, 2015, 01:02:16 pm
Quote from: abit on August 19, 2015, 12:53:53 pm
Is this command useful? @Riverhead
Code: [Select]
rm -rf object_database*

A good suggestion but it did not take me off 9c. It did however widen my scope outside of the data directory for my reset script so thanks for that :).

Is your wallet launched with this command?
Code: [Select]
./cli_wallet -w wallet-testnet-puppies.json --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 19, 2015, 01:39:29 pm: Quote from: abit on August 19, 2015, 01:14:35 pm
Quote from: Riverhead on August 19, 2015, 01:02:16 pm
Quote from: abit on August 19, 2015, 12:53:53 pm
Is this command useful? @Riverhead
Code: [Select]
rm -rf object_database*

A good suggestion but it did not take me off 9c. It did however widen my scope outside of the data directory for my reset script so thanks for that :) .

Is your wallet launched with this command?
Code: [Select]
./cli_wallet -w wallet-testnet-puppies.json --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6

I'm not running the wallet currently - just the witness_node.

Code: [Select]
./witness_node -d .graphene --genesis-json '"aug-14-test-genesis.json"' 2125632ms th_a witness.cpp:70 plugin_initialize ] key_id_to_wif_pair: ["GPH7kNZtp64ZR1R4yC2w9.","5J.Qw8pmqgsK"] 2131814ms th_a thread.cpp:95 thread ] name:ntp tid:140335251613440 2131815ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 2131815ms th_a thread.cpp:95 thread ] name:p2p tid:140335228999424 2131860ms ntp ntp.cpp:81 request_now ] sending request to 50.116.36.122:123 2131860ms th_a application.cpp:117 reset_p2p_node ] Adding seed node 45.55.6.216:1776 2131862ms th_a application.cpp:129 reset_p2p_node ] Configured p2p node to listen on 127.0.0.1:8090 2131863ms th_a application.cpp:179 reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8091 2131863ms th_a witness.cpp:143 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration. 2131863ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks. 2131863ms th_a main.cpp:166 main ] Chain ID is a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c 2131885ms ntp ntp.cpp:147 read_loop ] received ntp reply from 50.116.36.122:123 2131885ms ntp ntp.cpp:161 read_loop ] ntp offset: -2120353, round_trip_delay 25204 2131886ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to -2120353
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 01:49:29 pm: Quote from: Riverhead on August 19, 2015, 01:39:29 pm
Quote from: abit on August 19, 2015, 01:14:35 pm
Quote from: Riverhead on August 19, 2015, 01:02:16 pm
Quote from: abit on August 19, 2015, 12:53:53 pm
Is this command useful? @Riverhead
Code: [Select]
rm -rf object_database*

A good suggestion but it did not take me off 9c. It did however widen my scope outside of the data directory for my reset script so thanks for that :) .

Is your wallet launched with this command?
Code: [Select]
./cli_wallet -w wallet-testnet-puppies.json --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6

I'm not running the wallet currently - just the witness_node.

Code: [Select]
./witness_node -d .graphene --genesis-json '"aug-14-test-genesis.json"' 2125632ms th_a witness.cpp:70 plugin_initialize ] key_id_to_wif_pair: ["GPH7kNZtp64ZR1R4yC2w9.","5J.Qw8pmqgsK"] 2131814ms th_a thread.cpp:95 thread ] name:ntp tid:140335251613440 2131815ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 2131815ms th_a thread.cpp:95 thread ] name:p2p tid:140335228999424 2131860ms ntp ntp.cpp:81 request_now ] sending request to 50.116.36.122:123 2131860ms th_a application.cpp:117 reset_p2p_node ] Adding seed node 45.55.6.216:1776 2131862ms th_a application.cpp:129 reset_p2p_node ] Configured p2p node to listen on 127.0.0.1:8090 2131863ms th_a application.cpp:179 reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8091 2131863ms th_a witness.cpp:143 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration. 2131863ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks. 2131863ms th_a main.cpp:166 main ] Chain ID is a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c 2131885ms ntp ntp.cpp:147 read_loop ] received ntp reply from 50.116.36.122:123 2131885ms ntp ntp.cpp:161 read_loop ] ntp offset: -2120353, round_trip_delay 25204 2131886ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to -2120353
I was building on another computer yesterday, and had to switch back to a git head from the 14th in order to get it to connect with the correct chain-id. Checking out and building bf47a1610c4aef7e25592aa42ecd4d4ae83a2b5f worked, but I still don't know how the chain-id is derived https://github.com/cryptonomex/graphene/wiki/chain-locked-tx (https://github.com/cryptonomex/graphene/wiki/chain-locked-tx) explains why they are important, but not sure how they are generated.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 19, 2015, 02:10:04 pm: So do I need to checkout aug-17-testnet on git

Code: [Select]
git checkout origin/aug-17-testnet
building now
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 02:13:05 pm: Quote from: iHashFury on August 19, 2015, 02:10:04 pm
Code: [Select]
So do I need to checkout aug-17-testnet on git [codegit checkout origin/aug-17-testnet
building now
aug-17-testnet will give you chain id a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c (at least it did for me)
git checkout bf47a1610c4aef7e25592aa42ecd4d4ae83a2b5f
is what worked for me.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 19, 2015, 02:17:04 pm: Quote from: puppies on August 19, 2015, 02:13:05 pm
Quote from: iHashFury on August 19, 2015, 02:10:04 pm
Code: [Select]
So do I need to checkout aug-17-testnet on git [codegit checkout origin/aug-17-testnet
building now
aug-17-testnet will give you chain id a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c (at least it did for me)
git checkout bf47a1610c4aef7e25592aa42ecd4d4ae83a2b5f
is what worked for me.

Thanks puppies. Building 2b5f now.
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 19, 2015, 02:29:17 pm: aug-17-testnet has 100 witnesses and will hopefull be more resistant to whatever caused the death of aug-14-testnet
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 02:34:47 pm: Quote from: xeroc on August 19, 2015, 02:29:17 pm
aug-17-testnet has 100 witnesses and will hopefull be more resistant to whatever caused the death of aug-14-testnet
I am down to switch whenever everyone else is. Please don't keep this alive on my account. I just wanted to continue testing till we got another official test net.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 19, 2015, 02:42:41 pm: Quote from: xeroc on August 19, 2015, 02:29:17 pm
aug-17-testnet has 100 witnesses and will hopefull be more resistant to whatever caused the death of aug-14-testnet

So is 9c the correct chain then? I wasn't able to sync - but that could be a network issue on my VM.

Update: Aug-14 is syncing now. However, I should probably get Aug-17 working instead.
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 19, 2015, 02:47:55 pm: Try connect to graphene.bitshares.org:8090 with the cli wallet .. i think there is a witness runnig which will tell you the chain id on connect .. not sure

Cant give you any more info as I am currently mobile
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 02:49:57 pm: Quote from: Riverhead on August 19, 2015, 02:42:41 pm
Quote from: xeroc on August 19, 2015, 02:29:17 pm
aug-17-testnet has 100 witnesses and will hopefull be more resistant to whatever caused the death of aug-14-testnet

So is 9c the correct chain then? I wasn't able to sync - but that could be a network issue on my VM.

Update: Aug-14 is syncing now. However, I should probably get Aug-17 working instead.
there's no server node for the August 17th test_net. I can try to start one, if everyone is interested.
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 02:50:11 pm: Quote from: xeroc on August 19, 2015, 02:29:17 pm
aug-17-testnet has 100 witnesses and will hopefull be more resistant to whatever caused the death of aug-14-testnet

So are we all going here now? or still on the 14th.. mine has just crashed.
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 02:51:33 pm: Puppies can you keep it up for a while until xeroc is back.
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 19, 2015, 02:52:16 pm: The seed node published in the op should have a websocket open at port 9080
If you connect your cli wallet to that ip directly it will tell you the chainid ..

Edit: afaik devs are working on that network already
I told them yesterday that nobody knows about that network yet .. no idea why they are holding it back .. maybe not on purpose

Anyway I will have to leave for now and will be back tomorrow ..
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 19, 2015, 02:52:37 pm: It would make sense to test on the latest release of both clients and chain. I'm building aug-17 (18ed468c6f0b19bb1e322548d8be64d7faafe4e5) now which will put me back in 9c unless I get something different from the graphene.bitshares.org node.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 19, 2015, 02:57:22 pm: I have pushed an update that will hopefully resolve the out-of-order syncing issues.

Those of you who have gotten good at these test networks can probably test it out for me and let me know if you still have problems.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 02:58:27 pm: I am getting
Code: [Select]
user@user-desktop:~/src/graphene/programs/cli_wallet$ ./cli_wallet -w wallet -s 104.200.28.117:61705Logging RPC to file: logs/rpc/rpc.log 3362460ms th_a main.cpp:111 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W 3362460ms th_a main.cpp:115 main ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV 3362460ms th_a main.cpp:116 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3 3362564ms th_a main.cpp:163 main ] wdata.ws_server: 104.200.28.117:61705 10 assert_exception: Assert Exception uri.substr(0,3) == "ws:": {} th_a websocket.cpp:585 connect {"uri":"104.200.28.117:61705"} th_a websocket.cpp:606 connect user@user-desktop:~/src/graphene/programs/cli_wallet$ ./cli_wallet -w wallet -s 104.200.28.117:8090 Logging RPC to file: logs/rpc/rpc.log 3372945ms th_a main.cpp:111 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W 3372946ms th_a main.cpp:115 main ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV 3372946ms th_a main.cpp:116 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3 3373048ms th_a main.cpp:163 main ] wdata.ws_server: 104.200.28.117:8090 10 assert_exception: Assert Exception uri.substr(0,3) == "ws:": {} th_a websocket.cpp:585 connect {"uri":"104.200.28.117:8090"} th_a websocket.cpp:606 connectI will start working on getting an aug 17th seed node up, unless someone else wants to volunteer
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 02:59:02 pm: Quote from: bytemaster on August 19, 2015, 02:57:22 pm
I have pushed an update that will hopefully resolve the out-of-order syncing issues.

Those of you who have gotten good at these test networks can probably test it out for me and let me know if you still have problems.
Is there a seed node or should I just build from master and make one?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 19, 2015, 02:59:33 pm: No reason to hold back on aug-17 network. Those who know about it, please provide instructions for others to join it.

Note that the aug 17 network does not currently have the fixes I introduced today for the out-of-order block pushing. I will ask Vikram to update his node when he comes in this afternoon.
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 03:02:45 pm: K so we get the latest from github and join what node?
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 19, 2015, 03:05:42 pm: Quote from: bytemaster on August 19, 2015, 02:59:33 pm
No reason to hold back on aug-17 network. Those who know about it, please provide instructions for others to join it.

Note that the aug 17 network does not currently have the fixes I introduced today for the out-of-order block pushing. I will ask Vikram to update his node when he comes in this afternoon.

Cool. I'll just rebuild and launch the latest and greatest. Now that I have the other environmental kinks worked out should be up and running shortly.
Title: Re: Test Net for Advanced Users
Post by: roadscape on August 19, 2015, 03:06:34 pm: I was having the same problems as Riverhead, stuck on a6 chain. Now building aug-17...
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 19, 2015, 03:06:43 pm: You need the genesis block for aug17 .. could someone not mobile please provide a download link @bytemaster

Then you can do prety much what is stated in the op with the aug17 snapshot
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 19, 2015, 03:40:34 pm: Quote from: xeroc on August 19, 2015, 03:06:43 pm
You need the genesis block for aug17 .. could someone not mobile please provide a download link @bytemaster

Then you can do prety much what is stated in the op with the aug17 snapshot

I was hoping it'd be on github - may be a good place for it for testing.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 05:48:56 pm: Well...

Until we get something official, I have a new version up and running with 100 init witnessess. I manually edited the genesis, and everything seems to be working, but I really had no idea what I was doing. https://www.dropbox.com/s/xzlnoyn4tdpdede/aug-19-puppies-test-genesis.json?dl=0 (https://www.dropbox.com/s/xzlnoyn4tdpdede/aug-19-puppies-test-genesis.json?dl=0)

The specific tag I built was 15c99bd65b0c90854d430126582fee49ec645fe6, so if you are having a hard time getting on the same chain-id I would suggest a
Code: [Select]
git checkout 15c99bd65b0c90854d430126582fee49ec645fe6 git submodule update --init --recursive cmake -DBOOST_ROOT="$BOOST_ROOT" -DCMAKE_BUILD_TYPE=Debug . make
I was also having a hard time getting the genesis.json to load. Using the entire path in the command seems to work so for example
Code: [Select]
./witness_node -d test_net --genesis-json /home/user/src/8.19/graphene/programs/witness_node/aug-19-puppies-test-genesis.json
my server is still 45.55.6.216:1776

As always I am running on Ubuntu 14.04. I also have exactly 0 formal computer science training, so if I am doing something wrong please let me know. I am a learn by doing type of guy, and that includes making lots of mistakes.

and the chain id is 5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb but its kinda a pain to get the genesis.json to load and give you that chain-id
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 06:18:02 pm: +5% Thanks ill have a go after.
Title: Re: Test Net for Advanced Users
Post by: maqifrnswa on August 19, 2015, 06:27:55 pm: to help testing, I set up an ubuntu daily build of graphene master
https://bitsharestalk.org/index.php/topic,18039.new.htm

maybe will help a couple more people get involved in testing
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 07:07:47 pm: Quote from: maqifrnswa on August 19, 2015, 06:27:55 pm
to help testing, I set up an ubuntu daily build of graphene master
https://bitsharestalk.org/index.php/topic,18039.new.htm

maybe will help a couple more people get involved in testing

You should go to the play forum, there is a bounty waiting for you. :)
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 07:13:18 pm: Quote from: betax on August 19, 2015, 07:07:47 pm
Quote from: maqifrnswa on August 19, 2015, 06:27:55 pm
to help testing, I set up an ubuntu daily build of graphene master
https://bitsharestalk.org/index.php/topic,18039.new.htm

maybe will help a couple more people get involved in testing

You should go to the play forum, there is a bounty waiting for you. :)
Yeah. I tried to make a play ppa that would contain both cli and gui files, for a couple of days and couldn't get it to work. I even used your bitshares ppa as a template and couldn't get it right. If you can whip one up so easily theres a million pls in it for you (I think)
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 07:57:16 pm: well im up and running
Title: Re: Test Net for Advanced Users
Post by: testz on August 19, 2015, 08:08:03 pm: Quote from: puppies on August 19, 2015, 05:48:56 pm
Well...

Uhhhhh, Probably first Windows witness up and running :)
Witness id: 1.6.4435 or simple testz
Please vote this witness in.

PS: Tomorrow I will try to summarize what I done and maybe will come with small instruction how to build and run witness under Windows
Title: Re: Test Net for Advanced Users
Post by: cryptosile on August 19, 2015, 08:17:00 pm: Also, to help with testing I'm pushing Docker containers for witness and cli in an automated fashion. I will post instructions on how to join using docker later tonight.

https://bitsharestalk.org/index.php/topic,17935.0.html
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 08:17:55 pm: Quote from: testz on August 19, 2015, 08:08:03 pm
Quote from: puppies on August 19, 2015, 05:48:56 pm
Well...

Uhhhhh, Probably first Windows witness up and running :)
Witness id: 1.6.4435 or simple testz
Please vote this witness in.

PS: Tomorrow I will try to summarize what I done and maybe will come with small instruction how to build and run witness under Windows
+5% voted
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 08:20:56 pm: Quote from: cryptosile on August 19, 2015, 08:17:00 pm
Also, to help with testing I'm pushing Docker containers for witness and cli in an automated fashion. I will post instructions on how to join using docker later tonight.

https://bitsharestalk.org/index.php/topic,17935.0.html

+5% Excellent, it will be nice to have the instructions too on how to create the containers
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 08:24:02 pm: Here we are...

(http://picpaste.com/pics/witnesses-rUdOJvqP.1440015806.PNG)

http://picpaste.com/pics/witnesses-rUdOJvqP.1440015806.PNG
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 08:26:31 pm: Quote from: betax on August 19, 2015, 08:24:02 pm
Here we are...

(http://picpaste.com/pics/witnesses-rUdOJvqP.1440015806.PNG)
Awesome, how did you build?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 19, 2015, 08:27:48 pm: Quote from: testz on August 19, 2015, 08:08:03 pm
Quote from: puppies on August 19, 2015, 05:48:56 pm
Well...

Uhhhhh, Probably first Windows witness up and running :)
Witness id: 1.6.4435 or simple testz
Please vote this witness in.

PS: Tomorrow I will try to summarize what I done and maybe will come with small instruction how to build and run witness under Windows

Nice work!
Title: Re: Test Net for Advanced Users
Post by: abit on August 19, 2015, 08:34:10 pm: Quote from: puppies on August 19, 2015, 05:48:56 pm
Well...

Until we get something official, I have a new version up and running with 100 init witnessess. I manually edited the genesis, and everything seems to be working, but I really had no idea what I was doing. https://www.dropbox.com/s/xzlnoyn4tdpdede/aug-19-puppies-test-genesis.json?dl=0 (https://www.dropbox.com/s/xzlnoyn4tdpdede/aug-19-puppies-test-genesis.json?dl=0)

The specific tag I built was 15c99bd65b0c90854d430126582fee49ec645fe6, so if you are having a hard time getting on the same chain-id I would suggest a
Code: [Select]
git checkout 15c99bd65b0c90854d430126582fee49ec645fe6 git submodule update --init --recursive cmake -DBOOST_ROOT="$BOOST_ROOT" -DCMAKE_BUILD_TYPE=Debug . make
I was also having a hard time getting the genesis.json to load. Using the entire path in the command seems to work so for example
Code: [Select]
./witness_node -d test_net --genesis-json /home/user/src/8.19/graphene/programs/witness_node/aug-19-puppies-test-genesis.json
my server is still 45.55.6.216:1776

As always I am running on Ubuntu 14.04. I also have exactly 0 formal computer science training, so if I am doing something wrong please let me know. I am a learn by doing type of guy, and that includes making lots of mistakes.

and the chain id is 5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb but its kinda a pain to get the genesis.json to load and give you that chain-id
Great thanks. +5% Building..
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 08:39:58 pm: Quote from: puppies on August 19, 2015, 08:26:31 pm
Quote from: betax on August 19, 2015, 08:24:02 pm
Here we are...

(http://picpaste.com/pics/witnesses-rUdOJvqP.1440015806.PNG)
Awesome, how did you build?

Using the graphene-ui build instructions :) in github.
As I am using ubuntu in a vps I changed server.js to use 0.0.0.0, also to use prod.
My witnesses uses for rpc 0.0.0.0 instead localhost / 127.0.0.1
Title: Re: Test Net for Advanced Users
Post by: betax on August 19, 2015, 08:47:59 pm: Quote from: testz on August 19, 2015, 08:08:03 pm
Quote from: puppies on August 19, 2015, 05:48:56 pm
Well...

Uhhhhh, Probably first Windows witness up and running :)
Witness id: 1.6.4435 or simple testz
Please vote this witness in.

PS: Tomorrow I will try to summarize what I done and maybe will come with small instruction how to build and run witness under Windows

Voted and looking forward those instructions
Title: Re: Test Net for Advanced Users
Post by: clayop on August 19, 2015, 08:48:05 pm: Great works all you guys. I will be in later tonight.
Title: Re: Test Net for Advanced Users
Post by: abit on August 19, 2015, 09:10:43 pm: My node is online now. Witness id 1.6.5247.
But number of active witnesses is still 11?
Code: [Select]
{ "head_block_num": 11773, "head_block_id": "00002dfdab35043defebc42a6ae9d5a96767fd97", "head_block_age": "1 second old", "next_maintenance_time": "82 seconds in the future", "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.5", "1.6.6", "1.6.1525", "1.6.4435", "1.6.5246", "1.6.5247" ], "active_committee_members": [ "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8", "1.5.9" ], "entropy": "73f47170212775453a20de79b10d927e9d3b761d" }
//Edit: it's 11, not 10
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 09:23:43 pm: Quote from: abit on August 19, 2015, 09:10:43 pm
My node is online now. Witness id 1.6.5247.
But number of active witnesses is still 10?
Code: [Select]
{ "head_block_num": 11773, "head_block_id": "00002dfdab35043defebc42a6ae9d5a96767fd97", "head_block_age": "1 second old", "next_maintenance_time": "82 seconds in the future", "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.5", "1.6.6", "1.6.1525", "1.6.4435", "1.6.5246", "1.6.5247" ], "active_committee_members": [ "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8", "1.5.9" ], "entropy": "73f47170212775453a20de79b10d927e9d3b761d" }
for some reason the info and get_global_properties screen dont show all witnesses. There may have been something I should have changed in the genesis. There are 101 delegate slots though.
Title: Re: Test Net for Advanced Users
Post by: abit on August 19, 2015, 09:27:37 pm: Quote from: puppies on August 19, 2015, 09:23:43 pm
Quote from: abit on August 19, 2015, 09:10:43 pm
My node is online now. Witness id 1.6.5247.
But number of active witnesses is still 10?
Code: [Select]
{ "head_block_num": 11773, "head_block_id": "00002dfdab35043defebc42a6ae9d5a96767fd97", "head_block_age": "1 second old", "next_maintenance_time": "82 seconds in the future", "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.5", "1.6.6", "1.6.1525", "1.6.4435", "1.6.5246", "1.6.5247" ], "active_committee_members": [ "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8", "1.5.9" ], "entropy": "73f47170212775453a20de79b10d927e9d3b761d" }
for some reason the info and get_global_properties screen dont show all witnesses. There may have been something I should have changed in the genesis. There are 101 delegate slots though.
By looking at the screen of witness_node, it's true that only the 11 witnesses are producing blocks.

//Edit: it's 11, not 10
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 09:28:17 pm: Quote from: betax on August 19, 2015, 08:39:58 pm
Quote from: puppies on August 19, 2015, 08:26:31 pm
Quote from: betax on August 19, 2015, 08:24:02 pm
Here we are...

(http://picpaste.com/pics/witnesses-rUdOJvqP.1440015806.PNG)
Awesome, how did you build?

Using the graphene-ui build instructions :) in github.
As I am using ubuntu in a vps I changed server.js to use 0.0.0.0, also to use prod.
My witnesses uses for rpc 0.0.0.0 instead localhost / 127.0.0.1
I had no idea it was so easy. I have been messing around with the light wallet instructions on the build ubuntu page with no real luck.

CNX, you guys have really outdone yourselves with this wallet. Its beautiful. Key import is awesome.

One bug. When I import my keys for puppies there are so many that the confirm button is not visible. Even when I zoom all the way out that middle window goes way below the bottom of the page. I was able to do it by pressing tab, and watching the JS description in the bottom left hand corner of my screen.

This is all in firefox on Xubuntu 14.04
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 09:31:55 pm: Quote from: abit on August 19, 2015, 09:27:37 pm
Quote from: puppies on August 19, 2015, 09:23:43 pm
Quote from: abit on August 19, 2015, 09:10:43 pm
My node is online now. Witness id 1.6.5247.
But number of active witnesses is still 10?
Code: [Select]
{ "head_block_num": 11773, "head_block_id": "00002dfdab35043defebc42a6ae9d5a96767fd97", "head_block_age": "1 second old", "next_maintenance_time": "82 seconds in the future", "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.5", "1.6.6", "1.6.1525", "1.6.4435", "1.6.5246", "1.6.5247" ], "active_committee_members": [ "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8", "1.5.9" ], "entropy": "73f47170212775453a20de79b10d927e9d3b761d" }
for some reason the info and get_global_properties screen dont show all witnesses. There may have been something I should have changed in the genesis. There are 101 delegate slots though.
By looking at the screen of witness_node, it's true that only the 11 witnesses are producing blocks.

//Edit: it's 11, not 10

Yeah. You're right.

Thats funny because I had 100 going earlier. I could tell because I set the genesis to 101, but set my server witness node to 100, and so 1.6.100 was missing blocks every single rotation.
Title: Re: Test Net for Advanced Users
Post by: abit on August 19, 2015, 09:33:16 pm: Quote from: betax on August 19, 2015, 08:39:58 pm
Quote from: puppies on August 19, 2015, 08:26:31 pm
Quote from: betax on August 19, 2015, 08:24:02 pm
Here we are...

(http://picpaste.com/pics/witnesses-rUdOJvqP.1440015806.PNG)
Awesome, how did you build?

Using the graphene-ui build instructions :) in github.
As I am using ubuntu in a vps I changed server.js to use 0.0.0.0, also to use prod.
My witnesses uses for rpc 0.0.0.0 instead localhost / 127.0.0.1
Do you have a URL so others could access the GUI/webwallet?
Title: Re: Test Net for Advanced Users
Post by: abit on August 19, 2015, 09:52:52 pm: Quote from: puppies on August 19, 2015, 09:31:55 pm
Thats funny because I had 100 going earlier. I could tell because I set the genesis to 101, but set my server witness node to 100, and so 1.6.100 was missing blocks every single rotation.

There is a command in help():
Code: [Select]
graphene::chain::signed_transaction set_desired_witness_and_committee_member_count(string, uint16_t, uint16_t, bool)Don't know what it will do though.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 10:04:18 pm: Quote from: abit on August 19, 2015, 09:52:52 pm
Quote from: puppies on August 19, 2015, 09:31:55 pm
Thats funny because I had 100 going earlier. I could tell because I set the genesis to 101, but set my server witness node to 100, and so 1.6.100 was missing blocks every single rotation.

There is a command in help():
Code: [Select]
graphene::chain::signed_transaction set_desired_witness_and_committee_member_count(string, uint16_t, uint16_t, bool)Don't know what it will do though.
I have played around with that command a little bit. It throws an error if you set the desired number to more than what that account is currently voting for.

I would love some clarity on how the number of active witnesses is decided. If you get_witness init92 you can see that its previous secret key is not all zeros. It was producing blocks at some point.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 19, 2015, 10:09:55 pm: Witness created. 1.6.5248 :)
Title: Re: Test Net for Advanced Users
Post by: puppies on August 19, 2015, 10:53:22 pm: I've set up the web wallet at 45.55.6.216:8080 same node as the init witnesses so don't crash it.

Edit. Looks like it needs more work. Giving me an error on account create.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 19, 2015, 11:30:27 pm: Quote from: puppies on August 19, 2015, 10:53:22 pm
I've set up the web wallet at 45.55.6.216:8080 same node as the init witnesses so don't crash it.

Nice :) +5%
Title: Re: Test Net for Advanced Users
Post by: cryptosile on August 20, 2015, 12:51:20 am: Witness everydaycrypto is producing blocks
Title: Re: Test Net for Advanced Users
Post by: puppies on August 20, 2015, 01:42:09 am: so the web wallet at 45.55.6.216:8080 is now functional, but is not allowing new account registrations. I think that is because it doesn't have an account set up to pay for the registration. If anyone knows how to set that up I would greatly appreciate it.

If not then you can still import balances from the 0.9.2 wallet_export_keys command (requires an updated build. read the first two pages of this thread)

Or you can just not create an account and still look at a large chunk of the wallet
Title: Re: Test Net for Advanced Users
Post by: clayop on August 20, 2015, 03:52:49 am: I'm in.
Now going to test massive transactions with witness account.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 20, 2015, 04:06:12 am: Witness node fails to produce blocks after massive transactions from witness account (i.e. 1 CORE transfer * 300 txs)
@bytemaster and @vikram can you look at this?

If anyone can reproduce this bug, it would be nice.
Title: Re: Test Net for Advanced Users
Post by: cryptosile on August 20, 2015, 04:50:24 am: my witness node stopped producing blocks as well.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 20, 2015, 04:54:33 am: Quote from: cryptosile on August 20, 2015, 04:50:24 am
my witness node stopped producing blocks as well.

What did you do?
Title: Re: Test Net for Advanced Users
Post by: testz on August 20, 2015, 05:37:27 am: Quote from: cryptosile on August 20, 2015, 04:50:24 am
my witness node stopped producing blocks as well.

I get:
2162093ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.4435 production slot has arrived; generating a block now...
2162093ms th_a witness.cpp:266 block_production_loo ] Got exception while generating block:
10 assert_exception: Assert Exception
_consecutive_production_enabled || db.get_dynamic_global_properties().current_witness != scheduled_witness: Last block was generated by the same witness, this node is probably disconnected from the network so block production has been disabled. Disable this check with --allow-consecutive option.
{}
th_a witness.cpp:248 graphene::witness_plugin::witness_plugin::block_production_loop
2163091ms th_a witness.cpp:240 block_production_loo ] slot: 6063 scheduled_witness: 1.6.5246 schedul...
Title: Re: Test Net for Advanced Users
Post by: betax on August 20, 2015, 05:44:24 am: Just woke up, Im not producing blocks either.
Code: [Select]
866714cfbbf","000066e44370fae9a1b02625480966b57cc3458a","0000672466da61511d9ef8a386217b1e7235f519","00006744a726781b14726dd82437cd3dff493a50","0000675411988d1632d109b69917632bae5dc68c","0000675c7c19cb50b481a1522b14212368228847","0000676053c543bdb9e0cea06d48328634701b33","000067625f90d27d73ee18d5c3192b123524a87a","00006763c44fd2d25cd3b9966657e194abb6c36c","000067642e6bb2e49584d494b243f7aebb8d3d2b"] 2586746ms th_a application.cpp:492 get_blockchain_synop ] reference_point: 000067642e6bb2e49584d494b243f7aebb8d3d2b number_of_blocks_after_reference_point: 7996 result: ["00002764769c3f0b69e953b5feb889a81247f3b8","00004764b53d527f3af9ef82b5a6f8a98812cfff","0000576494e36a391539acb34b2912a2003a7271","00005f64142465bf62f511966b0064e10e53cad0","00006364751fdb8467125d8603c8847d3b0082c4","00006564f0cfc6e21490e40e368a5f833ab4c9dc","000066640e3d1b4bce1cdc389291a866714cfbbf","000066e44370fae9a1b02625480966b57cc3458a","0000672466da61511d9ef8a386217b1e7235f519","00006744a726781b14726dd82437cd3dff493a50","0000675411988d1632d109b69917632bae5dc68c","0000675c7c19cb50b481a1522b14212368228847","0000676053c543bdb9e0cea06d48328634701b33","000067625f90d27d73ee18d5c3192b123524a87a","00006763c44fd2d25cd3b9966657e194abb6c36c","000067642e6bb2e49584d494b243f7aebb8d3d2b"] 2586995ms th_a application.cpp:492 get_blockchain_synop ] reference_point: 000067642e6bb2e49584d494b243f7aebb8d3d2b number_of_blocks_after_reference_point: 9995 result: ["00002764769c3f0b69e953b5feb889a81247f3b8","00004764b53d527f3af9ef82b5a6f8a98812cfff","0000576494e36a391539acb34b2912a2003a7271","00005f64142465bf62f511966b0064e10e53cad0","00006364751fdb8467125d8603c8847d3b0082c4","00006564f0cfc6e21490e40e368a5f833ab4c9dc","000066640e3d1b4bce1cdc389291a866714cfbbf","000066e44370fae9a1b02625480966b57cc3458a","0000672466da61511d9ef8a386217b1e7235f519","00006744a726781b14726dd82437cd3dff493a50","0000675411988d1632d109b69917632bae5dc68c","0000675c7c19cb50b481a1522b14212368228847","0000676053c543bdb9e0cea06d48328634701b33","000067625f90d27d73ee18d5c3192b123524a87a","00006763c44fd2d25cd3b9966657e194abb6c36c","000067642e6bb2e49584d494b243f7aebb8d3d2b"] 2587004ms th_a witness.cpp:240 block_production_loo ] slot: 13978 scheduled_witness: 1.6.0 scheduled_time: 2015-08-20T05:43:07 now: 2015-08-20T05:43:07 2588007ms th_a witness.cpp:240 block_production_loo ] slot: 13979 scheduled_witness: 1.6.52 scheduled_time: 2015-08-20T05:43:08 now: 2015-08-20T05:43:08 2589008ms th_a witness.cpp:240 block_production_loo ] slot: 13980 scheduled_witness: 1.6.5249 scheduled_time: 2015-08-20T05:43:09 now: 2015-08-20T05:43:09 2590005ms th_a witness.cpp:240 block_production_loo ] slot: 13981 scheduled_witness: 1.6.5248 scheduled_time: 2015-08-20T05:43:10 now: 2015-08-20T05:43:10 2590157ms th_a application.cpp:370 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): {} th_a fork_database.cpp:67 _push_block {"new_block":{"previous":"000067642e6bb2e49584d494b243f7aebb8d3d2b","timestamp":"2015-08-20T01:50:10","witness":"1.6.5249","next_secret_hash":"f4f468fd3e4fb366dd2d972a915db1b3d5345c71","previous_secret":"2bca37cf125efd56697843c3cba65bc9f7075a20","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"2056ea809a37ebb3f8963eedc965e57d640719b787d13583eab4b0c8215c7f13e470eb42c2ac842951201f86b165eca75180a161dfb8fbb981b490e3bdd467b19f","transactions":[]}} th_a db_block.cpp:176 _push_block
Title: Re: Test Net for Advanced Users
Post by: clayop on August 20, 2015, 05:47:45 am: Probably my spam transactions caused the problem.
Title: Re: Test Net for Advanced Users
Post by: testz on August 20, 2015, 05:53:35 am: Quote from: clayop on August 20, 2015, 05:47:45 am
Probably my spam transactions caused the problem.

Yes, and I can't resync to the network, witness_node crashes, so if devs will look to our test net they will found something interesting. :)
Title: Re: Test Net for Advanced Users
Post by: betax on August 20, 2015, 05:59:06 am: Quote from: abit on August 19, 2015, 09:33:16 pm
Quote from: betax on August 19, 2015, 08:39:58 pm
Quote from: puppies on August 19, 2015, 08:26:31 pm
Quote from: betax on August 19, 2015, 08:24:02 pm
Here we are...

(http://picpaste.com/pics/witnesses-rUdOJvqP.1440015806.PNG)
Awesome, how did you build?

Using the graphene-ui build instructions :) in github.
As I am using ubuntu in a vps I changed server.js to use 0.0.0.0, also to use prod.
My witnesses uses for rpc 0.0.0.0 instead localhost / 127.0.0.1
Do you have a URL so others could access the GUI/webwallet?

If you havent seen puppies already http://bitshares2.cloudapp.net:8080/ same warnings, wallet cannot create account (I bet I have missed something), but nice to get a good feel.
Title: Re: Test Net for Advanced Users
Post by: cryptosile on August 20, 2015, 06:40:49 am: I was able to delete my files and resync the witness, then I turned block production back on and it seems to be working now.

Here are some examples of how to use docker to run the witness:

Start a witness, all logs and data will be dumped right after execution stops:
docker run -it --rm sile16/graphene-witness:aug19test --genesis-json /aug-19-puppies-test-genesis.json -s 45.55.6.216:1776
(this docker image i included the genesis json in)

Start a witness with persistent data dir:
docker run -it --rm -v <local data dir>:/witness_node_data_dir sile16/graphene-witness:aug19test --genesis-json /aug-19-puppies-test-genesis.json -s 45.55.6.216:1776

to make it easier to expose ports you can also include --net=host
docker run -it --rm --net=host -v /witness_node/test_net2:/witness_node_data_dir sile16/graphene-witness:aug19test --genesis-json /aug-19-puppies-test-genesis.json -s 45.55.6.216:1776 --rpc-endpoint 127.0.0.1:8090

the docker image is pushed so these commands should work for anyone.
Title: Re: Test Net for Advanced Users
Post by: betax on August 20, 2015, 06:44:12 am: Quote from: testz on August 20, 2015, 05:53:35 am
Quote from: clayop on August 20, 2015, 05:47:45 am
Probably my spam transactions caused the problem.

Yes, and I can't resync to the network, witness_node crashes, so if devs will look to our test net they will found something interesting. :)

I launched with --resync and everything was ok afterwards.
Title: Re: Test Net for Advanced Users
Post by: betax on August 20, 2015, 06:44:30 am: Quote from: cryptosile on August 20, 2015, 06:40:49 am
I was able to delete my files and resync the witness, then I turned block production back on and it seems to be working now.

Here are some examples of how to use docker to run the witness:

Start a witness, all logs and data will be dumped right after execution stops:
docker run -it --rm sile16/graphene-witness:aug19test --genesis-json /aug-19-puppies-test-genesis.json -s 45.55.6.216:1776
(this docker image i included the genesis json in)

Start a witness with persistent data dir:
docker run -it --rm -v <local data dir>:/witness_node_data_dir sile16/graphene-witness:aug19test --genesis-json /aug-19-puppies-test-genesis.json -s 45.55.6.216:1776

to make it easier to expose ports you can also include --net=host
docker run -it --rm --net=host -v /witness_node/test_net2:/witness_node_data_dir sile16/graphene-witness:aug19test --genesis-json /aug-19-puppies-test-genesis.json -s 45.55.6.216:1776 --rpc-endpoint 127.0.0.1:8090

the docker image is pushed so these commands should work for anyone.

+5%
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 06:48:04 am: Happy forking :D
After forked, if restart without --resync-blockchain, then my node won't sync.
If restart with --resync-blockchain, it won't produce block after in sync.

So it's best remove the data directory before start.

I'm online again now.
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 07:14:07 am: I added a default.log by editing config.ini so that screen output could be logged into file. I'm curious why it doesn't be enabled by default.
Code: [Select]
# declare an appender named "default" that writes messages to default.log [log.file_appender.default] filename=logs/default/default.log # filename can be absolute or relative to this config file # route any messages logged to the default logger to the "stderr" logger # and "default" logger we # declared above, if they are info level are higher [logger.default] level=info appenders=stderr,default
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 07:20:38 am: I'm stuck at 40902 now. Looks like the testnet is dead again?

Code: [Select]
{ "head_block_num": 40902, "head_block_id": "00009fc6d4e24db66e13af461b94063165999bfa", "head_block_age": "4 minutes old", "next_maintenance_time": "31 seconds ago", "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.1525", "1.6.1536", "1.6.4435", "1.6.5245", "1.6.5246", "1.6.5247", "1.6.5248", "1.6.5249" ], "active_committee_members": [ "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8", "1.5.9" ], "entropy": "8927f3f36c4599a6a7af5a3cdfb70a8f57d463ae" }
Code: [Select]
2015-08-20T07:11:59 th_a:invoke handle_block handle_block ] Got block #40902 from network application.cp p:343 2015-08-20T07:12:00 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.4435 scheduled_time: 2015-08-2 0T07:12:00 now: 2015-08-20T07:12:00 witness.cpp:240 2015-08-20T07:12:01 th_a:Witness Block Production block_production_loo ] slot: 2 scheduled_witness: 1.6.5245 scheduled_time: 2015-08-2 0T07:12:01 now: 2015-08-20T07:12:01 witness.cpp:240 2015-08-20T07:12:02 th_a:Witness Block Production block_production_loo ] slot: 3 scheduled_witness: 1.6.1 scheduled_time: 2015-08-20T0 7:12:02 now: 2015-08-20T07:12:02 witness.cpp:240 2015-08-20T07:12:03 th_a:Witness Block Production block_production_loo ] slot: 4 scheduled_witness: 1.6.5247 scheduled_time: 2015-08-2 0T07:12:03 now: 2015-08-20T07:12:03 witness.cpp:240 2015-08-20T07:12:03 th_a:Witness Block Production block_production_loo ] Witness 1.6.5247 production slot has arrived; generating a bl ock now... witness.cpp:243 2015-08-20T07:12:03 th_a:Witness Block Production _push_block ] Failed to push new block: 3070000 undo_database_exception: undo database exception The database does not have enough undo history to support a blockchain with so many missed blocks. Please add a checkpoint if you would like to continue applying blocks beyond this point. {"recently_missed":1006,"max_undo":1000} th_a db_update.cpp:72 update_global_dynamic_data {"next_block.block_num()":40903} th_a db_block.cpp:439 _apply_block db_block.cpp:170
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 20, 2015, 08:02:02 am: For those eagerly waiting .. here is another howto
https://github.com/cryptonomex/graphene/wiki/Howto-import-an-existing-delegate-as-witness-in-BitShares-2.0
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 20, 2015, 08:42:27 am: Quote from: abit on August 20, 2015, 07:20:38 am
I'm stuck at 40902 now. Looks like the testnet is dead again?

Code: [Select]
{ "head_block_num": 40902, "head_block_id": "00009fc6d4e24db66e13af461b94063165999bfa", "head_block_age": "4 minutes old", "next_maintenance_time": "31 seconds ago", "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.1525", "1.6.1536", "1.6.4435", "1.6.5245", "1.6.5246", "1.6.5247", "1.6.5248", "1.6.5249" ], "active_committee_members": [ "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8", "1.5.9" ], "entropy": "8927f3f36c4599a6a7af5a3cdfb70a8f57d463ae" }
Code: [Select]
2015-08-20T07:11:59 th_a:invoke handle_block handle_block ] Got block #40902 from network application.cp p:343 2015-08-20T07:12:00 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.4435 scheduled_time: 2015-08-2 0T07:12:00 now: 2015-08-20T07:12:00 witness.cpp:240 2015-08-20T07:12:01 th_a:Witness Block Production block_production_loo ] slot: 2 scheduled_witness: 1.6.5245 scheduled_time: 2015-08-2 0T07:12:01 now: 2015-08-20T07:12:01 witness.cpp:240 2015-08-20T07:12:02 th_a:Witness Block Production block_production_loo ] slot: 3 scheduled_witness: 1.6.1 scheduled_time: 2015-08-20T0 7:12:02 now: 2015-08-20T07:12:02 witness.cpp:240 2015-08-20T07:12:03 th_a:Witness Block Production block_production_loo ] slot: 4 scheduled_witness: 1.6.5247 scheduled_time: 2015-08-2 0T07:12:03 now: 2015-08-20T07:12:03 witness.cpp:240 2015-08-20T07:12:03 th_a:Witness Block Production block_production_loo ] Witness 1.6.5247 production slot has arrived; generating a bl ock now... witness.cpp:243 2015-08-20T07:12:03 th_a:Witness Block Production _push_block ] Failed to push new block: 3070000 undo_database_exception: undo database exception The database does not have enough undo history to support a blockchain with so many missed blocks. Please add a checkpoint if you would like to continue applying blocks beyond this point. {"recently_missed":1006,"max_undo":1000} th_a db_update.cpp:72 update_global_dynamic_data {"next_block.block_num()":40903} th_a db_block.cpp:439 _apply_block db_block.cpp:170

Yes, same for me, I was late for the party. If you already are a block producer maybe you can retsart your witness and try checkpointing option just for fun? Maybe you can get it back to life?
Option's obviously it's already there:
https://github.com/cryptonomex/graphene/blob/9c0c588ed62165886a510775d76c8524c50c09c5/libraries/app/application.cpp

Regards
Title: Re: Test Net for Advanced Users
Post by: betax on August 20, 2015, 08:46:18 am: Quote from: abit on August 20, 2015, 06:48:04 am
Happy forking :D
After forked, if restart without --resync-blockchain, then my node won't sync.
If restart with --resync-blockchain, it won't produce block after in sync.

So it's best remove the data directory before start.

I'm online again now.

If restarted with --resync, needs to restarted again after sync. I have to do it also if I deleted the data directory.
Title: Re: Test Net for Advanced Users
Post by: betax on August 20, 2015, 09:07:04 am: Quote from: xeroc on August 20, 2015, 08:02:02 am
For those eagerly waiting .. here is another howto
https://github.com/cryptonomex/graphene/wiki/Howto-import-an-existing-delegate-as-witness-in-BitShares-2.0

Nice! I have just done a small correction on
Code: [Select]
--witness-id '"<witnessid>"'
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 10:01:05 am: Quote from: mudshark79 on August 20, 2015, 08:42:27 am
Quote from: abit on August 20, 2015, 07:20:38 am
I'm stuck at 40902 now. Looks like the testnet is dead again?

Yes, same for me, I was late for the party. If you already are a block producer maybe you can retsart your witness and try checkpointing option just for fun? Maybe you can get it back to life?
Option's obviously it's already there:
https://github.com/cryptonomex/graphene/blob/9c0c588ed62165886a510775d76c8524c50c09c5/libraries/app/application.cpp

Regards
Good idea. I am going to check how to set checkpoints. If you or anybody know please post here, thanks!
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 20, 2015, 10:26:50 am: Quote from: abit on August 20, 2015, 10:01:05 am
Quote from: mudshark79 on August 20, 2015, 08:42:27 am
Quote from: abit on August 20, 2015, 07:20:38 am
I'm stuck at 40902 now. Looks like the testnet is dead again?

Yes, same for me, I was late for the party. If you already are a block producer maybe you can retsart your witness and try checkpointing option just for fun? Maybe you can get it back to life?
Option's obviously it's already there:
https://github.com/cryptonomex/graphene/blob/9c0c588ed62165886a510775d76c8524c50c09c5/libraries/app/application.cpp

Regards
Good idea. I am going to check how to set checkpoints. If you or anybody know please post here, thanks!

Line 594 of application.ccp says:
("checkpoint,c", bpo::value<vector<string>>()->composing(), "Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints.")

so adding "--checkpoint [BLOCK_NUM,BLOCK_ID]" or '-c [BLOCK_NUM,BLOCK_ID]' for the witness startup should do it....
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 10:28:17 am: It's as easy as adding this to the witness_node command:
Code: [Select]
--checkpoint '[40902,"00009fc6d4e24db66e13af461b94063165999bfa"]' --enable-stale-production
But it seems too late to rescue the network, I still get this error:
Code: [Select]
1122000ms th_a witness.cpp:240 block_production_loo ] slot: 11203 scheduled_witness: 1.6.5247 scheduled_[967/1963] -08-20T10:18:42 now: 2015-08-20T10:18:42 1122000ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.5247 production slot has arrived; generating a b lock now... 1122001ms th_a db_block.cpp:170 _push_block ] Failed to push new block: 3070000 undo_database_exception: undo database exception The database does not have enough undo history to support a blockchain with so many missed blocks. Please add a checkpoint if you woul d like to continue applying blocks beyond this point. {"recently_missed":44813,"max_undo":1000} th_a db_update.cpp:72 update_global_dynamic_data {"next_block.block_num()":40903} th_a db_block.cpp:439 _apply_block 1122001ms th_a witness.cpp:266 block_production_loo ] Got exception while generating block: 3070000 undo_database_exception: undo database exception The database does not have enough undo history to support a blockchain with so many missed blocks. Please add a checkpoint if you woul d like to continue applying blocks beyond this point. {"recently_missed":44813,"max_undo":1000} th_a db_update.cpp:72 update_global_dynamic_data {"next_block.block_num()":40903} th_a db_block.cpp:439 _apply_block {"new_block":{"previous":"00009fc6d4e24db66e13af461b94063165999bfa","timestamp":"2015-08-20T10:18:42","witness":"1.6.5247","next_s ecret_hash":"a151bcbe08eac49feb4eb86a5a68f332b4e7cf9d","previous_secret":"2fa1e05db52f0c421e335648c21bb3707383c1d6","transaction_merkl e_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"206ea3856d3cf6317f19ab6b5d3af6648409ac092eae9c c8d943d7357e3ac9c753141733131d2312c4644d44125835afce24190d295c21a6a620920ab660ec5f5c","transactions":[]}} th_a db_block.cpp:176 _push_block {"witness_id":"1.6.5247"} th_a db_block.cpp:315 _generate_block
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 20, 2015, 10:28:50 am: Checkpoints are supposed to be part of config.ini .. it may be the same syntax as checkpoints.json from bitshares0.9
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 20, 2015, 10:32:25 am: Quote from: abit on August 20, 2015, 10:28:17 am
It's as easy as adding this to the witness_node command:
Code: [Select]
--checkpoint '[40902,"00009fc6d4e24db66e13af461b94063165999bfa"]' --enable-stale-production
But it seems too late to rescue the network, I still get this error:
Code: [Select]
1122000ms th_a witness.cpp:240 block_production_loo ] slot: 11203 scheduled_witness: 1.6.5247 scheduled_[967/1963] -08-20T10:18:42 now: 2015-08-20T10:18:42 1122000ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.5247 production slot has arrived; generating a b lock now... 1122001ms th_a db_block.cpp:170 _push_block ] Failed to push new block: 3070000 undo_database_exception: undo database exception The database does not have enough undo history to support a blockchain with so many missed blocks. Please add a checkpoint if you woul d like to continue applying blocks beyond this point. {"recently_missed":44813,"max_undo":1000} th_a db_update.cpp:72 update_global_dynamic_data {"next_block.block_num()":40903} th_a db_block.cpp:439 _apply_block 1122001ms th_a witness.cpp:266 block_production_loo ] Got exception while generating block: 3070000 undo_database_exception: undo database exception The database does not have enough undo history to support a blockchain with so many missed blocks. Please add a checkpoint if you woul d like to continue applying blocks beyond this point. {"recently_missed":44813,"max_undo":1000} th_a db_update.cpp:72 update_global_dynamic_data {"next_block.block_num()":40903} th_a db_block.cpp:439 _apply_block {"new_block":{"previous":"00009fc6d4e24db66e13af461b94063165999bfa","timestamp":"2015-08-20T10:18:42","witness":"1.6.5247","next_s ecret_hash":"a151bcbe08eac49feb4eb86a5a68f332b4e7cf9d","previous_secret":"2fa1e05db52f0c421e335648c21bb3707383c1d6","transaction_merkl e_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"206ea3856d3cf6317f19ab6b5d3af6648409ac092eae9c c8d943d7357e3ac9c753141733131d2312c4644d44125835afce24190d295c21a6a620920ab660ec5f5c","transactions":[]}} th_a db_block.cpp:176 _push_block {"witness_id":"1.6.5247"} th_a db_block.cpp:315 _generate_block

Did it get you going again? Seems to be still stuck or maybe you are on your own fork now? Which is your adress to use as seed-node?
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 10:35:25 am: Maybe we still have chance? According to the log, the 'recently_missed' number is increasing.

Code: [Select]
... {"recently_missed":47937,"max_undo":1000} ... {"recently_missed":47981,"max_undo":1000} ... {"recently_missed":48685,"max_undo":1000}
Retrying..
Title: Re: Test Net for Advanced Users
Post by: brainbug on August 20, 2015, 11:03:42 am: General question (since I could not find this elsewhere):

Is there a genuine place from where I can download "an up-to-date" BitShares blockchain? Setting up a new client is easy, but syncing it takes long and sometimes does not work such that the whole process needs to be repeated again and again (my slow little pc, c847/8gb, often has problems here and it takes days to re-sync/re-download the chain)... As such, it would be awesome to have an official and always "up-to-date" download link for the BitShares blockchain.

That said, my question is if such a download link is already there (and I could not find it), or would it be a great addition to the BitShare's homepage?

EDIT: Also 8gb ram seem sometimes not enough for a re-sync (using v0.9.2)... is that true? Did some one else make similar experiences?
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 11:08:45 am: Quote from: mudshark79 on August 20, 2015, 10:32:25 am
Did it get you going again? Seems to be still stuck or maybe you are on your own fork now? Which is your adress to use as seed-node?

I'm sure that I'm not on my own fork. Check this: http://45.55.6.216:8080/#/explorer/blocks or try 'info' command in cliwallet, my result is:
Code: [Select]
new >>> info info { "head_block_num": 40902, "head_block_id": "00009fc6d4e24db66e13af461b94063165999bfa", "head_block_age": "4 hours old", "next_maintenance_time": "4 hours ago", "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb", ... }
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 20, 2015, 11:12:22 am: Quote from: abit on August 20, 2015, 11:08:45 am
Quote from: mudshark79 on August 20, 2015, 10:32:25 am
Did it get you going again? Seems to be still stuck or maybe you are on your own fork now? Which is your adress to use as seed-node?

I'm sure that I'm not on my own fork. Check this: http://45.55.6.216:8080/#/explorer/blocks or try 'info' command in cliwallet, my result is:
Code: [Select]
new >>> info info { "head_block_num": 40902, "head_block_id": "00009fc6d4e24db66e13af461b94063165999bfa", "head_block_age": "4 hours old", "next_maintenance_time": "4 hours ago", "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb", ... }

OK, I see. So starting the witness-node with Checkpoint didn't make a difference then?
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 11:15:58 am: Quote from: brainbug on August 20, 2015, 11:03:42 am
General question (since I could not find this elsewhere):

Is there a genuine place from where I can download "an up-to-date" BitShares blockchain? Setting up a new client is easy, but syncing it takes long and sometimes does not work such that the whole process needs to be repeated again and again (my slow little pc, c847/8gb, often has problems here and it takes days to re-sync/re-download the chain)... As such, it would be awesome to have an official and always "up-to-date" download link for the BitShares blockchain.

That said, my question is if such a download link is already there (and I could not find it), or would it be a great addition to the BitShare's homepage?

EDIT: Also 8gb ram seem sometimes not enough for a re-sync (using v0.9.2)... is that true? Did some one else make similar experiences?
I don't know if there is a download link for the blockchain.
8GB RAM is more than enough. If you're using Windows or Linux, try run 'bitshares_client' rather than GUI for initial syncing. After in-sync you can press ctrl+d to close it then open GUI.
Wish you good luck.
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 11:20:00 am: Quote from: mudshark79 on August 20, 2015, 11:12:22 am
Quote from: abit on August 20, 2015, 11:08:45 am
Quote from: mudshark79 on August 20, 2015, 10:32:25 am
Did it get you going again? Seems to be still stuck or maybe you are on your own fork now? Which is your adress to use as seed-node?

I'm sure that I'm not on my own fork. Check this: http://45.55.6.216:8080/#/explorer/blocks or try 'info' command in cliwallet, my result is:
Code: [Select]
new >>> info info { "head_block_num": 40902, "head_block_id": "00009fc6d4e24db66e13af461b94063165999bfa", "head_block_age": "4 hours old", "next_maintenance_time": "4 hours ago", "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb", ... }

OK, I see. So starting the witness-node with Checkpoint didn't make a difference then?
I think it should be useful if slot < 1000. But we've missed more than 10000 blocks already.
Code: [Select]
1117002ms th_a witness.cpp:240 block_production_loo ] slot: 14798 scheduled_witness: 1.6.1 scheduled_time: 2015-08 -20T11:18:37 now: 2015-08-20T11:18:37 1118002ms th_a witness.cpp:240 block_production_loo ] slot: 14799 scheduled_witness: 1.6.5248 scheduled_time: 2015 -08-20T11:18:38 now: 2015-08-20T11:18:38 1119002ms th_a witness.cpp:240 block_production_loo ] slot: 14800 scheduled_witness: 1.6.5247 scheduled_time: 2015-08-20T11:18:39 now: 2015-08-20T11:18:39 1119002ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.5247 production slot has arrived; generating a block now... 1119004ms th_a db_block.cpp:170 _push_block ] Failed to push new block: 3070000 undo_database_exception: undo database exception
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 20, 2015, 11:26:47 am: I think it should be useful if slot < 1000. But we've missed more than 10000 blocks already.
Code: [Select]
1117002ms th_a witness.cpp:240 block_production_loo ] slot: 14798 scheduled_witness: 1.6.1 scheduled_time: 2015-08 -20T11:18:37 now: 2015-08-20T11:18:37 1118002ms th_a witness.cpp:240 block_production_loo ] slot: 14799 scheduled_witness: 1.6.5248 scheduled_time: 2015 -08-20T11:18:38 now: 2015-08-20T11:18:38 1119002ms th_a witness.cpp:240 block_production_loo ] slot: 14800 scheduled_witness: 1.6.5247 scheduled_time: 2015-08-20T11:18:39 now: 2015-08-20T11:18:39 1119002ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.5247 production slot has arrived; generating a block now... 1119004ms th_a db_block.cpp:170 _push_block ] Failed to push new block: 3070000 undo_database_exception: undo database exception
At least it gives an exception now that it tried... don't think it should correlate with the number. 1000 seems to be the limit without checkpoint or so.. but really just guessing.
Going standby for the next attempt....
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 20, 2015, 12:01:31 pm: Actually there is a trick to restarting block production after so much time has passed.

First add a the following checkpoint

[HEADNUM+1, "00000000.....00"]

With that checkpoint you will be able to produce the next block. Once you have produced the block, other nodes can add a checkpoint with that freshly produced block and you will be up and running again.

Every time a checkpoint is reached it resets the required undo history to 0. Adding a checkpoint at HEADNUM will reset it to 0, but the next block you produce will have missed over 1000 blocks so is immediately beyond the reach. Therefore, we need to "checkpoint" the "next block" for which we do not know the ID yet.

So the real question is, why were we missing so many blocks? Who got voted in and why did you stop producing?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 20, 2015, 12:10:57 pm: Quote from: puppies on August 19, 2015, 09:31:55 pm
Quote from: abit on August 19, 2015, 09:27:37 pm
Quote from: puppies on August 19, 2015, 09:23:43 pm
Quote from: abit on August 19, 2015, 09:10:43 pm
My node is online now. Witness id 1.6.5247.
But number of active witnesses is still 10?
Code: [Select]
{ "head_block_num": 11773, "head_block_id": "00002dfdab35043defebc42a6ae9d5a96767fd97", "head_block_age": "1 second old", "next_maintenance_time": "82 seconds in the future", "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.5", "1.6.6", "1.6.1525", "1.6.4435", "1.6.5246", "1.6.5247" ], "active_committee_members": [ "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8", "1.5.9" ], "entropy": "73f47170212775453a20de79b10d927e9d3b761d" }
for some reason the info and get_global_properties screen dont show all witnesses. There may have been something I should have changed in the genesis. There are 101 delegate slots though.
By looking at the screen of witness_node, it's true that only the 11 witnesses are producing blocks.

//Edit: it's 11, not 10

Yeah. You're right.

Thats funny because I had 100 going earlier. I could tell because I set the genesis to 101, but set my server witness node to 100, and so 1.6.100 was missing blocks every single rotation.

This is because the blockchain has a MIN WITNESS count of 11, to get more than 11 requires the majority of the voting stake to actively vote for more than 11. So once people started voting "just for their witness" it quickly reverted back to 11.
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 12:41:43 pm: Quote from: bytemaster on August 20, 2015, 12:01:31 pm
Actually there is a trick to restarting block production after so much time has passed.

First add a the following checkpoint

[HEADNUM+1, "00000000.....00"]

With that checkpoint you will be able to produce the next block. Once you have produced the block, other nodes can add a checkpoint with that freshly produced block and you will be up and running again.

Every time a checkpoint is reached it resets the required undo history to 0. Adding a checkpoint at HEADNUM will reset it to 0, but the next block you produce will have missed over 1000 blocks so is immediately beyond the reach. Therefore, we need to "checkpoint" the "next block" for which we do not know the ID yet.

So the real question is, why were we missing so many blocks? Who got voted in and why did you stop producing?
~~Witnesses please add this so we can go on:~~
Code: [Select]
./witness_node ...... --checkpoint '[40903,"00009fc7e518d750f653ba0ca25a3067bd304f30"]'[/s]
//Update: 1000 seconds have passed so quickly. Rescue failed. Have to wait until enough witnesses come online.
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 12:44:40 pm: Quote from: bytemaster on August 20, 2015, 12:01:31 pm

So the real question is, why were we missing so many blocks? Who got voted in and why did you stop producing?
BM please check my comment on Github. https://github.com/cryptonomex/graphene/issues/247#issuecomment-132349244
Once a witness started forking, it's hard to switch back.
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 01:08:14 pm: For those who have interest, I started another chain. Chain id is still "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb"
Code: [Select]
./witness_node -s 114.92.254.159:62015 --genesis-json aug-19-puppies-test-genesis.json
Title: Re: Test Net for Advanced Users
Post by: clayop on August 20, 2015, 01:12:06 pm: Quote from: abit on August 20, 2015, 12:41:43 pm
Quote from: bytemaster on August 20, 2015, 12:01:31 pm
Actually there is a trick to restarting block production after so much time has passed.

First add a the following checkpoint

[HEADNUM+1, "00000000.....00"]

With that checkpoint you will be able to produce the next block. Once you have produced the block, other nodes can add a checkpoint with that freshly produced block and you will be up and running again.

Every time a checkpoint is reached it resets the required undo history to 0. Adding a checkpoint at HEADNUM will reset it to 0, but the next block you produce will have missed over 1000 blocks so is immediately beyond the reach. Therefore, we need to "checkpoint" the "next block" for which we do not know the ID yet.

So the real question is, why were we missing so many blocks? Who got voted in and why did you stop producing?
Witnesses please add this so we can go on:
Code: [Select]
--checkpoint '[40903,"00009fc7e518d750f653ba0ca25a3067bd304f30"]'
//Update: 1000 seconds have passed so quickly. Rescue failed. Have to wait until enough witnesses come online.

Failed to push new blocks. What is exact command?

Code: [Select]
619838ms th_a db_block.cpp:170 _push_block ] Failed to push new block: 10 assert_exception: Assert Exception next_block.id() == itr->second: Block did not match checkpoint {"checkpoint":[40903,"00009fc7e518d750f653ba0ca25a3067bd304f30"],"block_id":"00009fc7481 4ff846dcfa61cd7a48913d775d971"} th_a db_block.cpp:367 apply_block Segmentation fault (core dumped)
Title: Re: Test Net for Advanced Users
Post by: cryptosile on August 20, 2015, 01:13:11 pm: Just woke up,
tried to restart withe the --checkpoint option , have a mix of not producing because we are stale and then some serving up block. pretty sure it's not right... I won't be able to change anything until late tonight.

Code: [Select]
530999ms th_a witness.cpp:240 block_production_loo ] slot: 21412 scheduled_witness: 1.6.5249 scheduled_time: 2015-08-20T13:08:51 now: 2015-08-20T13:08:51 530999ms th_a witness.cpp:211 operator() ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production) 531999ms th_a witness.cpp:240 block_production_loo ] slot: 21413 scheduled_witness: 1.6.5246 scheduled_time: 2015-08-20T13:08:52 now: 2015-08-20T13:08:52 532999ms th_a witness.cpp:240 block_production_loo ] slot: 21414 scheduled_witness: 1.6.0 scheduled_time: 2015-08-20T13:08:53 now: 2015-08-20T13:08:53 533999ms th_a witness.cpp:240 block_production_loo ] slot: 21415 scheduled_witness: 1.6.1536 scheduled_time: 2015-08-20T13:08:54 now: 2015-08-20T13:08:54 534999ms th_a witness.cpp:240 block_production_loo ] slot: 21416 scheduled_witness: 1.6.5245 scheduled_time: 2015-08-20T13:08:55 now: 2015-08-20T13:08:55 535999ms th_a witness.cpp:240 block_production_loo ] slot: 21417 scheduled_witness: 1.6.1525 scheduled_time: 2015-08-20T13:08:56 now: 2015-08-20T13:08:56 536999ms th_a witness.cpp:240 block_production_loo ] slot: 21418 scheduled_witness: 1.6.1 scheduled_time: 2015-08-20T13:08:57 now: 2015-08-20T13:08:57 537604ms th_a application.cpp:487 get_blockchain_synop ] reference_point: 0000000000000000000000000000000000000000 number_of_blocks_after_reference_point: 0 result: ["00001fc61a621678e92fc941b58b08d13afa2268","00005fc6559ab7b6f2b0035b0accec1ca7bb9110","00007fc615d686c893fe81c7b3790565bd3ccac3","00008fc6ef374fa2e6b8a03a490dfc6f274d1b8c","000097c68746555744ecea0a5753eabbb540cb4b","00009bc6d4d50fefd8cca7e61cf243a1820d8add","00009dc666f08e568fddfe6ef99968363b649c16","00009ec6b4958ad1910cfd3d3d5451634b8c948a","00009f46f5a6a32bbe673fb3990ae69d80d29779","00009f863b8da93c16cd47c9a591d7a9071e92e1","00009fa6414eb1adf2e7a4e0ec81fa58bb2f0802","00009fb612985adcce921f4e1e47326e45b088dd","00009fbe0bbfc979683d479ba4abd6242dd0b7b0","00009fc2c4081a76afbad31337249726a2d06515","00009fc4a66df9d134e85476353bae7af2715909","00009fc50fe983dde2e975f6aed7d69f4f2cd952","00009fc6d4e24db66e13af461b94063165999bfa"] 537999ms th_a witness.cpp:240 block_production_loo ] slot: 21419 scheduled_witness: 1.6.4435 scheduled_time: 2015-08-20T13:08:58 now: 2015-08-20T13:08:58 538115ms th_a application.cpp:487 get_blockchain_synop ] reference_point: 00009cb4e54f640a0cef1aeab7aab0dfc955d333 number_of_blocks_after_reference_point: 0 result: ["00001fc61a621678e92fc941b58b08d13afa2268","00005fc6559ab7b6f2b0035b0accec1ca7bb9110","00007fc615d686c893fe81c7b3790565bd3ccac3","00008fc6ef374fa2e6b8a03a490dfc6f274d1b8c","000097c68746555744ecea0a5753eabbb540cb4b","00009bc6d4d50fefd8cca7e61cf243a1820d8add","00009dc666f08e568fddfe6ef99968363b649c16","00009ec6b4958ad1910cfd3d3d5451634b8c948a","00009f46f5a6a32bbe673fb3990ae69d80d29779","00009f863b8da93c16cd47c9a591d7a9071e92e1","00009fa6414eb1adf2e7a4e0ec81fa58bb2f0802","00009fb612985adcce921f4e1e47326e45b088dd","00009fbe0bbfc979683d479ba4abd6242dd0b7b0","00009fc2c4081a76afbad31337249726a2d06515","00009fc4a66df9d134e85476353bae7af2715909","00009fc50fe983dde2e975f6aed7d69f4f2cd952","00009fc6d4e24db66e13af461b94063165999bfa"] 538276ms th_a application.cpp:438 get_item ] Request for item {"item_type":1001,"item_hash":"00009cb5f3657547f191efd666aa7aaca57b3a8f"} 538276ms th_a application.cpp:446 get_item ] Serving up block #40117 538276ms th_a application.cpp:438 get_item ] Request for item {"item_type":1001,"item_hash":"00009cb5f3657547f191efd666aa7aaca57b3a8f"} 538276ms th_a application.cpp:446 get_item ] Serving up block #40117 538467ms th_a application.cpp:487 get_blockchain_synop ] reference_point: 00009cb4e54f640a0cef1aeab7aab0dfc955d333 number_of_blocks_after_reference_point: 0 result: ["00001fc61a621678e92fc941b58b08d13afa2268","00005fc6559ab7b6f2b0035b0accec1ca7bb9110","00007fc615d686c893fe81c7b3790565bd3ccac3","00008fc6ef374fa2e6b8a03a490dfc6f274d1b8c","000097c68746555744ecea0a5753eabbb540cb4b","00009bc6d4d50fefd8cca7e61cf243a1820d8add","00009dc666f08e568fddfe6ef99968363b649c16","00009ec6b4958ad1910cfd3d3d5451634b8c948a","00009f46f5a6a32bbe673fb3990ae69d80d29779","00009f863b8da93c16cd47c9a591d7a9071e92e1","00009fa6414eb1adf2e7a4e0ec81fa58bb2f0802","00009fb612985adcce921f4e1e47326e45b088dd","00009fbe0bbfc979683d479ba4abd6242dd0b7b0","00009fc2c4081a76afbad31337249726a2d06515","00009fc4a66df9d134e85476353bae7af2715909","00009fc50fe983dde2e975f6aed7d69f4f2cd952","00009fc6d4e24db66e13af461b94063165999bfa"]
Title: Re: Test Net for Advanced Users
Post by: clayop on August 20, 2015, 01:20:43 pm: Quote from: bytemaster on August 20, 2015, 12:01:31 pm
So the real question is, why were we missing so many blocks? Who got voted in and why did you stop producing?

This severe problem may start from my witness. After I ran spam transactions with my witness account (I entered over 1000 txs in a moment), many witnesses including mine began to experience "Last block was generated by the same witness" problem.
Title: Re: Test Net for Advanced Users
Post by: betax on August 20, 2015, 01:32:50 pm: Quote from: abit on August 20, 2015, 12:44:40 pm
Quote from: bytemaster on August 20, 2015, 12:01:31 pm

So the real question is, why were we missing so many blocks? Who got voted in and why did you stop producing?
BM please check my comment on Github. https://github.com/cryptonomex/graphene/issues/247#issuecomment-132349244
Once a witness started forking, it's hard to switch back.

I could not rejoin to the network after many errors... abit Ill try yours later on.
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 01:39:34 pm: Quote from: clayop on August 20, 2015, 01:12:06 pm
Failed to push new blocks. What is exact command?
Yes it's too late, and I'm re-syncing.
In order to keep the chain running, we need at least 8 witnesses online;
in order to rescue the chain we need at least 8 witnesses add the checkpoint parameter to their startup command IN TIME.
Title: Re: Test Net for Advanced Users
Post by: cryptosile on August 20, 2015, 03:27:11 pm: Bytemaster, on the next testnet would it be possible to use a git tag? That way a tag refers to a specific commit and is static rather than a dynamic branch.

....Also, my automated build server will see a tag and build a docker image with the witness binary in about 20 minutes from the commit.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 20, 2015, 03:32:47 pm: I'm having the hardest time getting on your chain abit

Stuck at work. So limited access.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 20, 2015, 03:34:35 pm: Bytemaster is the minimum witness count hard coded or in the genesis?
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 20, 2015, 03:59:16 pm: I've got a witness in abits chain finally but chain halted now. Nodes don't like my blocks :-[:
Code: [Select]
2015-08-20T15:55:57 p2p:message read_loop on_closing_connectio ] Peer 46.101.138.170:59332 is disconnecting us because of an error: You offered us a block that we reject as invalid, exception: {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context": {"level":"error","file":"fork_database.cpp","line":67,"method":"_push_block","hostname":"","thread_name":"th_a","timestamp":"2015-08-20T15:55:56"},"format":"item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":176,"method":"_push_block","hostname":"","thread_name":"th_a","timestamp":"2015-08-20T15:55:56"},"format":"","data":{"new_block":{"previous":"0000000000000000000000000000000000000000","timestamp":"2015-08-20T13:02:51","witness":"1.6.71","next_secret_hash":"86b9b6883182c63a63bbcd76fedb0a36d5e569ca","previous_secret":"0000000000000000000000000000000000000000","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions": [],"witness_signature":"203037bdf94500a31b9d890ab55c46f8010f2b4ce8f1e385da149d5529a48b694866730aa203f63f5d75a5fd915cc3925daaa4d37b258a6c67a9fb12b486c2637f","transactions":[]}}},{"context":{"level":"warn","file":"application.cpp","line":379,"method":"handle_block","hostname":"","thread_name":"th_a","timestamp":"2015-08-20T15:55:56"},"format":"","data":{"blk_msg":{"block":{"previous":"0000000000000000000000000000000000000000","timestamp":"2015-08-20T13:02:51","witness":"1.6.71","next_secret_hash":"86b9b6883182c63a63bbcd76fedb0a36d5e569ca","previous_secret":"0000000000000000000000000000000000000000","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"203037bdf94500a31b9d890ab55c46f8010f2b4ce8f1e385da149d5529a48b694866730aa203f63f5d75a5fd915cc3925daaa4d37b258a6c67a9fb12b486c2637f","transactions":[]},"block_id":"00000001e6f900ccb1fe3acf156074820b2e708e"},"sync_mode":true}}]}
Are we all on the same github version? How can I check on this, is there some versioning inside the programs, too? :)
Title: Re: Test Net for Advanced Users
Post by: Thom on August 20, 2015, 04:25:03 pm: Quote from: abit on August 20, 2015, 01:08:14 pm
For those who have interest, I started another chain. Chain id is still "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb"
Code: [Select]
./witness_node -s 114.92.254.159:62015 --genesis-json aug-19-puppies-test-genesis.json

OK, finally have some answers, trying to catch up with everyone. Just reviewed several pages of this thread, but can't find the aug-19th genesis download URL. Are we all moving to abit's chain now? I'll add --checkpoint '[40903,"00009fc7e518d750f653ba0ca25a3067bd304f30"]' to the witness startup too.

Still need to get voted in, not sure if 0.9.2 balance migration is necessary at this point tho...
Title: Re: Test Net for Advanced Users
Post by: puppies on August 20, 2015, 04:26:53 pm: It looks like dan just pushed a commit that increases minimum witness to 101. We can run a network that won't die if 4 witnesses go down. I think we should all build again and start a new network. I am at work, but I can start a seed node on my VPS. If someone else that is going to have more time, would like to start a server node instead let me know.

Code: [Select]
commit 8a9120e5179eed2640a8d0b926b7e61980bb42a2 Author: Daniel Larimer <dan@bitshares.org> Date: Thu Aug 20 08:47:38 2015 -0400 increasing the default minimum number of witnesses to 101 for testing
Although looks like 714261b02a55002f05ea647aa29ab3900b490407 is even newer, so thats what I am planning on building[/code]
Title: Re: Test Net for Advanced Users
Post by: puppies on August 20, 2015, 04:28:21 pm: Quote from: Thom on August 20, 2015, 04:25:03 pm
Quote from: abit on August 20, 2015, 01:08:14 pm
For those who have interest, I started another chain. Chain id is still "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb"
Code: [Select]
./witness_node -s 114.92.254.159:62015 --genesis-json aug-19-puppies-test-genesis.json

OK, finally have some answers, trying to catch up with everyone. Just reviewed several pages of this thread, but can't find the aug-19th genesis download URL. Are we all moving to abit's chain now? I'll add --checkpoint '[40903,"00009fc7e518d750f653ba0ca25a3067bd304f30"]' to the witness startup too.

Still need to get voted in, not sure if 0.9.2 balance migration is necessary at this point tho...
https://www.dropbox.com/s/xzlnoyn4tdpdede/aug-19-puppies-test-genesis.json?dl=0 (https://www.dropbox.com/s/xzlnoyn4tdpdede/aug-19-puppies-test-genesis.json?dl=0)
Title: Re: Test Net for Advanced Users
Post by: Thom on August 20, 2015, 04:30:53 pm: Thx ppuppies. I forget to ask if my build is too stale to use, sounds like it. I'll start another one on a vps.

I will see what happens with launching with the old build here locally...
Title: Re: Test Net for Advanced Users
Post by: clayop on August 20, 2015, 04:35:36 pm: Quote from: puppies on August 20, 2015, 04:26:53 pm
It looks like dan just pushed a commit that increases minimum witness to 101. We can run a network that won't die if 4 witnesses go down. I think we should all build again and start a new network. I am at work, but I can start a seed node on my VPS. If someone else that is going to have more time, would like to start a server node instead let me know.

Code: [Select]
commit 8a9120e5179eed2640a8d0b926b7e61980bb42a2 Author: Daniel Larimer <dan@bitshares.org> Date: Thu Aug 20 08:47:38 2015 -0400 increasing the default minimum number of witnesses to 101 for testing
Although looks like 714261b02a55002f05ea647aa29ab3900b490407 is even newer, so thats what I am planning on building[/code]

So you're building 714261b02a55002f05ea647aa29ab3900b490407 ?
Title: Re: Test Net for Advanced Users
Post by: Thom on August 20, 2015, 04:42:04 pm: I just kicked off a new build on a vps. I just wiped the original graphene folders and started from scratch. I presume it's the latest src we're going to use? If not would someone please post what to use instead of this:

Code: [Select]
git clone https://github.com/cryptonomex/graphene.git cd graphene git submodule update --init --recursive cmake . make
Still a bit of a newbie on git ;)
Title: Re: Test Net for Advanced Users
Post by: puppies on August 20, 2015, 04:48:28 pm: Quote from: clayop on August 20, 2015, 04:35:36 pm
Quote from: puppies on August 20, 2015, 04:26:53 pm
It looks like dan just pushed a commit that increases minimum witness to 101. We can run a network that won't die if 4 witnesses go down. I think we should all build again and start a new network. I am at work, but I can start a seed node on my VPS. If someone else that is going to have more time, would like to start a server node instead let me know.

Code: [Select]
commit 8a9120e5179eed2640a8d0b926b7e61980bb42a2 Author: Daniel Larimer <dan@bitshares.org> Date: Thu Aug 20 08:47:38 2015 -0400 increasing the default minimum number of witnesses to 101 for testing
Although looks like 714261b02a55002f05ea647aa29ab3900b490407 is even newer, so thats what I am planning on building[/code]

So you're building 714261b02a55002f05ea647aa29ab3900b490407 ?
yes
Title: Re: Test Net for Advanced Users
Post by: Thom on August 20, 2015, 05:26:18 pm: Almost there guys... I think. Running on local system, code built (from scratch) on 8/17. Lauched with:

Code: [Select]
./witness_node --resync-blockchain -d test_net --checkpoint '[40902,"00009fc6d4e24db66e13af461b94063165999bfa"]' --enable-stale-production
All other params in config.ini:
Code: [Select]
#Endpoint for P2P node to listen on p2p-endpoint = 0.0.0.0:1776 # P2P nodes to connect to on startup (may specify multiple times) seed-node = 45.55.6.216:1776 #seed-node = 114.92.254.159:62015 # Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints. # checkpoint = # Endpoint for websocket RPC to listen on rpc-endpoint = 127.0.0.1:8090 # Endpoint for TLS websocket RPC to listen on # rpc-tls-endpoint = # The TLS certificate file for this server # server-pem = # Password for this certificate # server-pem-password = # File to read Genesis State from #genesis-json = aug-14-test-genesis.json genesis-json = aug-19-puppies-test-genesis.json # JSON file specifying API permissions # api-access = # Enable block production, even if the chain is stale. enable-stale-production = false # Percent of witnesses (0-99) that must be participating in order to produce blocks required-participation = false # Allow block production, even if the last block was produced by the same witness. allow-consecutive = false # ID of witness controlled by this node (e.g. "1.6.0", quotes are required, may specify multiple times) witness-id = "1.6.1530" # Tuple of [PublicKey, WIF private key] (may specify multiple times) private-key = ["GPH52ms1dYJko2v5vS3rCdVLzQBogjeDRc1CpkaZ4seC4J4H7Uc71","<private signing key here>"] # Account ID to track history for (may specify multiple times) # track-account = # Track market history by grouping orders into buckets of equal size measured in seconds specified as a JSON array of numbers bucket-size = [15,60,300,3600,86400] # How far back in time to track history for each bucket size, measured in the number of buckets (default: 1000) history-per-size = 1000 # declare an appender named "stderr" that writes messages to the console [log.console_appender.stderr] stream=std_error # declare an appender named "p2p" that writes messages to p2p.log [log.file_appender.p2p] filename=logs/p2p/p2p.log # filename can be absolute or relative to this config file # route any messages logged to the default logger to the "stderr" logger we # declared above, if they are info level are higher [logger.default] level=info appenders=stderr # route messages sent to the "p2p" logger to the p2p appender declared above [logger.p2p] level=debug appenders=p2p
Tried to vote myself in:
Code: [Select]
unlocked >>> vote_for_witness delegate.verbaltech delegate.verbaltech true true vote_for_witness delegate.verbaltech delegate.verbaltech true true 893478ms th_a wallet.cpp:1590 sign_transaction ] Caught exception while broadcasting transaction with id e29704e03ea31a41fa9c28eb43841e2d55fc080f 0 exception: unspecified 3030001 tx_missing_active_auth: missing required active authority Missing Active Authority 1.2.22397
Someone care to vote me in please, and comment on anything else you think I need to do.

The build is done on the vps, but unfortunately I need to go. I'm going to leave my witness & cli_wallet running while I'm away. I'll chk back when I return.
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 20, 2015, 05:28:22 pm: It seems for voting you need the ACTIVE_KEY also
Title: Re: Test Net for Advanced Users
Post by: puppies on August 20, 2015, 05:29:58 pm: Okay. 45.55.6.216:1776 is up built on commit 714261b02a55002f05ea647aa29ab3900b490407
Title: Re: Test Net for Advanced Users
Post by: clayop on August 20, 2015, 05:49:56 pm: Quote from: puppies on August 20, 2015, 05:29:58 pm
Okay. 45.55.6.216:1776 is up built on commit 714261b02a55002f05ea647aa29ab3900b490407

Can you post the chain id?
Title: Re: Test Net for Advanced Users
Post by: puppies on August 20, 2015, 05:51:38 pm: Quote from: clayop on August 20, 2015, 05:49:56 pm
Quote from: puppies on August 20, 2015, 05:29:58 pm
Okay. 45.55.6.216:1776 is up built on commit 714261b02a55002f05ea647aa29ab3900b490407

Can you post the chain id?

{"remote_chain_id":"b8efd614e51a54d96ad6039c1210774296bf529e1c02ccbf4beb4605a2dc1ab8"
Title: Re: Test Net for Advanced Users
Post by: clayop on August 20, 2015, 06:02:38 pm: Quote from: puppies on August 20, 2015, 05:51:38 pm
Quote from: clayop on August 20, 2015, 05:49:56 pm
Quote from: puppies on August 20, 2015, 05:29:58 pm
Okay. 45.55.6.216:1776 is up built on commit 714261b02a55002f05ea647aa29ab3900b490407

Can you post the chain id?

{"remote_chain_id":"b8efd614e51a54d96ad6039c1210774296bf529e1c02ccbf4beb4605a2dc1ab8"

Thanks. I'm in now. 1.6.1536
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 20, 2015, 07:37:13 pm: Dito. 1.6.5246
My other witness created with imported account keys wouldn't sign blocks:
Code: [Select]
2810693ms th_a witness.cpp:266 block_production_loo ] Got exception while generating block: 10 assert_exception: Assert Exception witness_obj.signing_key == block_signing_private_key.get_public_key(): {} th_a db_block.cpp:266 _generate_block {"witness_id":"1.6.5245"} th_a db_block.cpp:315 _generate_block
Then had to transfer some CORE around to a newly created account, because I couldn't import a balance to the newly created account - I guess because the owner-key of the balance was not the account-key of the newly created account ?

Now it really seems to work first time. Next time this will be done much quicker 8). Guess there will be a new genesis also? Will prepare myself a test-witness-import-account....

BTW: netstat only showing three nodes online. Will someone join later on?
Who is signing all those blocks on behalf of the inits with only three nodes online? The Seed-Node?

Regards

Matthias
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 08:35:04 pm: Quote from: puppies on August 20, 2015, 03:34:35 pm
Bytemaster is the minimum witness count hard coded or in the genesis?
I think what he means is: if we vote in more witness (maybe include init witness) then the number of active witnesses will automatically increase.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 20, 2015, 08:46:10 pm: Yeah. I just wasnt sure if there was something I had missed in the genesis, or if the minimum was coded into the client.

This was answered when bm changed it in the client.
Title: Re: Test Net for Advanced Users
Post by: cryptosile on August 20, 2015, 08:47:17 pm: Bytemaster just pushed a new commit with a tag of test1. That is available as a docker image at sile16/graphene-witness:test1
Title: Re: Test Net for Advanced Users
Post by: clayop on August 20, 2015, 09:14:08 pm: Let's join to the official testnet
https://github.com/cryptonomex/graphene/releases/tag/test1
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 09:14:57 pm: Ok, rebuilding.
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 09:20:09 pm: Quote from: puppies on August 20, 2015, 08:46:10 pm
Yeah. I just wasnt sure if there was something I had missed in the genesis, or if the minimum was coded into the client.

This was answered when bm changed it in the client.
Looks like we need a new genesis file.
Code: [Select]
commit 2f0065d593dfd06deda970f9a8df59a930c50bff Author: Daniel Larimer <dan@bitshares.org> Date: Thu Aug 20 13:23:25 2015 -0400 genesis file specifies 101 min
//Edit: ah, found it on the release/tag page.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 20, 2015, 09:25:39 pm: Quote from: abit on August 20, 2015, 09:20:09 pm
Quote from: puppies on August 20, 2015, 08:46:10 pm
Yeah. I just wasnt sure if there was something I had missed in the genesis, or if the minimum was coded into the client.

This was answered when bm changed it in the client.
Looks like we need a new genesis file.
Code: [Select]
commit 2f0065d593dfd06deda970f9a8df59a930c50bff Author: Daniel Larimer <dan@bitshares.org> Date: Thu Aug 20 13:23:25 2015 -0400 genesis file specifies 101 min
//Edit: ah, found it on the release/tag page.
awesome. Thanks.
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 10:00:36 pm: Quote from: clayop on August 20, 2015, 09:14:08 pm
Let's join to the official testnet
https://github.com/cryptonomex/graphene/releases/tag/test1
I'm in. Witness id 1.6.5247.
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 20, 2015, 10:09:26 pm: In. Witness-Id "1.6.5248"
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 20, 2015, 10:30:52 pm: Quote from: abit on August 20, 2015, 10:00:36 pm
Quote from: clayop on August 20, 2015, 09:14:08 pm
Let's join to the official testnet
https://github.com/cryptonomex/graphene/releases/tag/test1
I'm in. Witness id 1.6.5247.

You guys don't miss a thing!
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 20, 2015, 10:44:29 pm: https://graphene.bitshares.org is now up to date with the latest test network.

We are working on a bug with voting by proxy... don't enter text into that field at this time it will lockup your browser window.

I have been able to import everything from my BTS wallet successfully. Still a lot of work to do on the GUI, but it is coming together at a consistent rate.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 20, 2015, 11:32:43 pm: It seems dead...

Code: [Select]
956998ms th_a witness.cpp:240 block_production_loo ] slot: 71 scheduled_ witness: 1.6.44 scheduled_time: 2015-08-20T23:15:57 now: 2015-08-20T23:15:57 957313ms th_a application.cpp:348 handle_block ] Got block #18559 fr om network 957313ms th_a application.cpp:370 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception second_branch_itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:186 fetch_branch_from {"first":"0000487f7a7025de308d52dc7b4967bb1ee8e0ac","second":"0000483cecce88706ed008ec83 18fab4816954b2"} th_a fork_database.cpp:217 fetch_branch_from {"new_block":{"previous":"0000487e8a4ecb97cccf50052ca6ccfe984e5082","timestamp":"2015-08 -20T23:15:57","witness":"1.6.73","next_secret_hash":"b0d5a6c59704871873528d2499ba024825b2d0d b","previous_secret":"9cd95d648f739607207427ba9f1a3ed4186286be","transaction_merkle_root":"0 000000000000000000000000000000000000000","extensions":[],"witness_signature":"204942e6396e76 4f268a3db0cb17d009d729315fa3ca88501ce01bd8b2e4b1258b526ce28a440e7b28e42ffdf3a329902677f3a277 57b3bd8d47c80d5d634a66f8","transactions":[]}} th_a db_block.cpp:176 _push_block 957497ms th_a application.cpp:348 handle_block ] Got block #18559 fr om network 957498ms th_a application.cpp:370 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception second_branch_itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:186 fetch_branch_from {"first":"0000487f7a7025de308d52dc7b4967bb1ee8e0ac","second":"0000483cecce88706ed008ec83 18fab4816954b2"} th_a fork_database.cpp:217 fetch_branch_from {"new_block":{"previous":"0000487e8a4ecb97cccf50052ca6ccfe984e5082","timestamp":"2015-08 -20T23:15:57","witness":"1.6.73","next_secret_hash":"b0d5a6c59704871873528d2499ba024825b2d0d b","previous_secret":"9cd95d648f739607207427ba9f1a3ed4186286be","transaction_merkle_root":"0 000000000000000000000000000000000000000","extensions":[],"witness_signature":"204942e6396e76 4f268a3db0cb17d009d729315fa3ca88501ce01bd8b2e4b1258b526ce28a440e7b28e42ffdf3a329902677f3a277 57b3bd8d47c80d5d634a66f8","transactions":[]}} th_a db_block.cpp:176 _push_block 957998ms th_a witness.cpp:240 block_production_loo ] slot: 72 scheduled_ witness: 1.6.1537 scheduled_time: 2015-08-20T23:15:58 now: 2015-08-20T23:15:58 957998ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.1537 pr oduction slot has arrived; generating a block now... Segmentation fault (core dumped)
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 11:33:39 pm: Quote from: bytemaster on August 20, 2015, 10:44:29 pm
https://graphene.bitshares.org is now up to date with the latest test network.

We are working on a bug with voting by proxy... don't enter text into that field at this time it will lockup your browser window.

I have been able to import everything from my BTS wallet successfully. Still a lot of work to do on the GUI, but it is coming together at a consistent rate.
Good!

Unable to create account?
Code: [Select]
Failed to create wallet: TypeError: Invalid value undefined supplied to WalletTcomb/chain_id: String
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 11:34:25 pm: Quote from: clayop on August 20, 2015, 11:32:43 pm
It seems dead...

Code: [Select]
956998ms th_a witness.cpp:240 block_production_loo ] slot: 71 scheduled_ witness: 1.6.44 scheduled_time: 2015-08-20T23:15:57 now: 2015-08-20T23:15:57 957313ms th_a application.cpp:348 handle_block ] Got block #18559 fr om network 957313ms th_a application.cpp:370 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception second_branch_itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:186 fetch_branch_from {"first":"0000487f7a7025de308d52dc7b4967bb1ee8e0ac","second":"0000483cecce88706ed008ec83 18fab4816954b2"} th_a fork_database.cpp:217 fetch_branch_from {"new_block":{"previous":"0000487e8a4ecb97cccf50052ca6ccfe984e5082","timestamp":"2015-08 -20T23:15:57","witness":"1.6.73","next_secret_hash":"b0d5a6c59704871873528d2499ba024825b2d0d b","previous_secret":"9cd95d648f739607207427ba9f1a3ed4186286be","transaction_merkle_root":"0 000000000000000000000000000000000000000","extensions":[],"witness_signature":"204942e6396e76 4f268a3db0cb17d009d729315fa3ca88501ce01bd8b2e4b1258b526ce28a440e7b28e42ffdf3a329902677f3a277 57b3bd8d47c80d5d634a66f8","transactions":[]}} th_a db_block.cpp:176 _push_block 957497ms th_a application.cpp:348 handle_block ] Got block #18559 fr om network 957498ms th_a application.cpp:370 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception second_branch_itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:186 fetch_branch_from {"first":"0000487f7a7025de308d52dc7b4967bb1ee8e0ac","second":"0000483cecce88706ed008ec83 18fab4816954b2"} th_a fork_database.cpp:217 fetch_branch_from {"new_block":{"previous":"0000487e8a4ecb97cccf50052ca6ccfe984e5082","timestamp":"2015-08 -20T23:15:57","witness":"1.6.73","next_secret_hash":"b0d5a6c59704871873528d2499ba024825b2d0d b","previous_secret":"9cd95d648f739607207427ba9f1a3ed4186286be","transaction_merkle_root":"0 000000000000000000000000000000000000000","extensions":[],"witness_signature":"204942e6396e76 4f268a3db0cb17d009d729315fa3ca88501ce01bd8b2e4b1258b526ce28a440e7b28e42ffdf3a329902677f3a277 57b3bd8d47c80d5d634a66f8","transactions":[]}} th_a db_block.cpp:176 _push_block 957998ms th_a witness.cpp:240 block_production_loo ] slot: 72 scheduled_ witness: 1.6.1537 scheduled_time: 2015-08-20T23:15:58 now: 2015-08-20T23:15:58 957998ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.1537 pr oduction slot has arrived; generating a block now... Segmentation fault (core dumped)
I'm forking too.. will post logs here later. Have you restarted?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 20, 2015, 11:36:51 pm: Dang. Can you give me a core dump backtrace?
Title: Re: Test Net for Advanced Users
Post by: clayop on August 20, 2015, 11:44:23 pm: Here's my log

https://drive.google.com/file/d/0B9wS1MU8AsmNTHBabURsVm5wUHM/view?usp=sharing
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on August 20, 2015, 11:45:36 pm: I'm not running a witness, but at first glance the network appears to be chugging along normally.
Title: Re: Test Net for Advanced Users
Post by: abit on August 20, 2015, 11:56:54 pm: Quote from: bytemaster on August 20, 2015, 10:30:52 pm
Quote from: abit on August 20, 2015, 10:00:36 pm
Quote from: clayop on August 20, 2015, 09:14:08 pm
Let's join to the official testnet
https://github.com/cryptonomex/graphene/releases/tag/test1
I'm in. Witness id 1.6.5247.

You guys don't miss a thing!
Forking ...
Code: [Select]
2015-08-20T23:22:09 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.4 scheduled_time: 2015-08-20T2 3:22:09 now: 2015-08-20T23:22:09 witness.cpp:240 2015-08-20T23:22:09 th_a:invoke handle_block handle_block ] Got block #18921 from network application.cp p:348 2015-08-20T23:22:10 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.28 scheduled_time: 2015-08-20T 23:22:10 now: 2015-08-20T23:22:10 witness.cpp:240 2015-08-20T23:22:11 th_a:Witness Block Production block_production_loo ] slot: 2 scheduled_witness: 1.6.5247 scheduled_time: 2015-08-2 0T23:22:11 now: 2015-08-20T23:22:11 witness.cpp:240 2015-08-20T23:22:11 th_a:Witness Block Production block_production_loo ] Witness 1.6.5247 production slot has arrived; generating a block now... witness.cpp:243 2015-08-20T23:22:11 th_a:Witness Block Production block_production_loo ] Generated block #18922 with timestamp 2015-08-20T23:22:11 at time 2015-08-20T23:22:11 witness.cpp:256 2015-08-20T23:22:11 th_a:invoke get_item get_item ] Request for item {"item_type":1001,"item_hash":"000049ea9c48e746def3d171e8bd9a6f7efef9c4"} application.cpp:443 2015-08-20T23:22:11 th_a:invoke get_item get_item ] Serving up block #18922 application.cpp:451 2015-08-20T23:22:11 th_a:invoke get_item get_item ] Request for item {"item_type":1001,"item_hash":"000049ea9c48e746def3d171e8bd9a6f7efef9c4"} application.cpp:443 2015-08-20T23:22:11 th_a:invoke get_item get_item ] Serving up block #18922 application.cpp:451 2015-08-20T23:22:11 th_a:invoke get_item get_item ] Request for item {"item_type":1001,"item_hash":"000049ea9c48e746def3d171e8bd9a6f7efef9c4"} application.cpp:443 2015-08-20T23:22:11 th_a:invoke get_item get_item ] Serving up block #18922 application.cpp:451 2015-08-20T23:22:11 th_a:invoke get_item get_item ] Request for item {"item_type":1001,"item_hash":"000049ea9c48e746def3d171e8bd9a6f7efef9c4"} application.cpp:443 2015-08-20T23:22:11 th_a:invoke get_item get_item ] Serving up block #18922 application.cpp:451 2015-08-20T23:22:11 th_a:invoke handle_block handle_block ] Got block #18922 from network application.cpp:348 2015-08-20T23:22:11 th_a:invoke get_item get_item ] Request for item {"item_type":1001,"item_hash":"000049ea9c48e746def3d171e8bd9a6f7efef9c4"} application.cpp:443 2015-08-20T23:22:11 th_a:invoke get_item get_item ] Serving up block #18922 application.cpp:451 2015-08-20T23:22:12 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.94 scheduled_time: 2015-08-20T23:22:12 now: 2015-08-20T23:22:12 witness.cpp:240 2015-08-20T23:22:12 th_a:invoke handle_block handle_block ] Got block #18923 from network application.cpp:348 2015-08-20T23:22:13 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.89 scheduled_time: 2015-08-20T23:22:13 now: 2015-08-20T23:22:13 witness.cpp:240 2015-08-20T23:22:13 th_a:invoke handle_block handle_block ] Got block #18924 from network application.cpp:348 2015-08-20T23:22:14 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.85 scheduled_time: 2015-08-20T23:22:14 now: 2015-08-20T23:22:14 witness.cpp:240 2015-08-20T23:22:14 th_a:invoke handle_block handle_block ] Got block #18925 from network application.cpp:348 2015-08-20T23:22:15 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.79 scheduled_time: 2015-08-20T23:22:15 now: 2015-08-20T23:22:15 witness.cpp:240 2015-08-20T23:22:15 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:383 2015-08-20T23:22:16 th_a:Witness Block Production block_production_loo ] slot: 2 scheduled_witness: 1.6.39 scheduled_time: 2015-08-20T23:22:16 now: 2015-08-20T23:22:16 witness.cpp:240 2015-08-20T23:22:16 th_a:invoke handle_block handle_block ] Got block #18927 from network application.cpp:348 2015-08-20T23:22:16 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57 2015-08-20T23:22:16 th_a:invoke handle_block handle_block ] Got block #18926 from network application.cpp:348 2015-08-20T23:22:16 th_a:invoke handle_block handle_block ] Error when pushing block: 6 key_not_found_exception: Key Not Found Block 000049ee6bfb5462c87a7cc631983d36b2d5e40e not contained in block database {"id":"000049ee6bfb5462c87a7cc631983d36b2d5e40e"} th_a block_database.cpp:91 remove {"id":"000049ee6bfb5462c87a7cc631983d36b2d5e40e"} th_a block_database.cpp:102 remove {} th_a db_block.cpp:329 pop_block {"new_block":{"previous":"000049ed587a0c63625259c90a08814b49dd48ad","timestamp":"2015-08-20T23:22:15","witness":"1.6.79","next_secret_hash":"be915a90267de27c859ea9b5bf2f81dd5a0075e0","previous_secret":"0286d358d2287db7ed6d1db7a3b26677cd5285b3","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"201d3dfc11a454871f2fe8b97e2bed38214e3796c8406561ca0190300a7ae6d67d6c17a904b6fbc7780450fc2fbf953d8be5a4bbd7e5604b6463a1ab00d6c05d12","transactions":[]}} th_a db_block.cpp:176 _push_block application.cpp:370 2015-08-20T23:22:17 th_a:Witness Block Production block_production_loo ] slot: 3 scheduled_witness: 1.6.5246 scheduled_time: 2015-08-20T23:22:17 now: 2015-08-20T23:22:17 witness.cpp:240 2015-08-20T23:22:18 th_a:Witness Block Production block_production_loo ] slot: 4 scheduled_witness: 1.6.35 scheduled_time: 2015-08-20T23:22:18 now: 2015-08-20T23:22:18 witness.cpp:240 2015-08-20T23:22:18 th_a:invoke handle_block handle_block ] Got block #18928 from network application.cpp:348 2015-08-20T23:22:18 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57
Code: [Select]
2015-08-20T23:23:28 th_a:Witness Block Production block_production_loo ] slot: 74 scheduled_witness: 1.6.5247 scheduled_time: 2015-08- 20T23:23:28 now: 2015-08-20T23:23:28 witness.cpp:240 2015-08-20T23:23:28 th_a:Witness Block Production block_production_loo ] Witness 1.6.5247 production slot has arrived; generating a bl ock now... witness.cpp:243 2015-08-20T23:23:28 th_a:Witness Block Production push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57 2015-08-20T23:23:28 th_a:Witness Block Production block_production_loo ] Generated block #18927 with timestamp 2015-08-20T23:23:28 at time 2015-08-20T23:23:28 witness.cpp:256 2015-08-20T23:23:29 th_a:Witness Block Production block_production_loo ] slot: 75 scheduled_witness: 1.6.78 scheduled_time: 2015-08-20T23:23:29 now: 2015-08-20T23:23:29 witness.cpp:240 2015-08-20T23:23:29 th_a:invoke handle_block handle_block ] Got block #18998 from network application.cpp:348 2015-08-20T23:23:29 th_a:invoke handle_block handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num < _head->num + MAX_BLOCK_REORDERING: {} th_a fork_database.cpp:70 _push_block {"new_block":{"previous":"00004a357deb88db9cd862e9f9915d69d352c526","timestamp":"2015-08-20T23:23:29","witness":"1.6.78","next_secret_hash":"89e22e27a13aef32fd3787b7c368d645dcf660ec","previous_secret":"61d9377a3602fb16f3ba640e83e2a7284a2da511","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"200fe0611f97331d08bcdae3c01a35e3ceeee11d84784cd0529b1bb9e9b448d35a38a7f0058419a51d3c2dbbebdfa2eeb537db1bcf39a377db6ba4ca41f7d26437","transactions":[]}} th_a db_block.cpp:176 _push_block application.cpp:370
Code: [Select]
2015-08-20T23:25:23 th_a:Witness Block Production block_production_loo ] slot: 189 scheduled_witness: 1.6.5247 scheduled_time: 2015-08 -20T23:25:23 now: 2015-08-20T23:25:23 witness.cpp:240 2015-08-20T23:25:23 th_a:Witness Block Production block_production_loo ] Witness 1.6.5247 production slot has arrived; generating a bl ock now... witness.cpp:243 2015-08-20T23:25:23 th_a:Witness Block Production push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57 2015-08-20T23:25:23 th_a:Witness Block Production block_production_loo ] Generated block #18927 with timestamp 2015-08-20T23:25:23 at time 2015-08-20T23:25:23 witness.cpp:256 2015-08-20T23:25:23 th_a:invoke get_blockchain_synopsis get_blockchain_synop ] reference_point: 0000451829aa62b7545bae4ea469b750003bf4 1f number_of_blocks_after_reference_point: 0 result: ["000009ef501ed09bea4e32d71077b13bcd3c28a1","000029ef11981d056e1a70afd0fdac952774 b2f7","000039ef9f6d0c5d83c52767cd98c710ac7a2d46","000041efa457c0e455f2569bc98b2e097baf8ace","000045ef42cf7a74580c57dd77cf3be887575d14" ,"000047ef9621e0266c0a7a9195a57cbb0aef6550","000048efd72770d20925e6e74a83d7a93f213f0a","0000496fa7fcba2947cc187a5fa9e7e30d8b5f3a","000 049afce3550f6f3a26efa67968d465ac16268","000049cfbf02c4d519b393a93430ee4785076736","000049df2dad0b1b7eb473d9eb6d2e6a31cc3080","000049e7 c78642267a650db5c41ae256f9112e76","000049eb39306a1360497002faeea118732d6761","000049ed587a0c63625259c90a08814b49dd48ad","0000000000000 000000000000000000000000000","000049efc4646a99bad9d78607972719e1a2d79d"] application.cpp:492
Strange "slot: 0" and "scheduled_time: 1970-01-01T00:00:00" here. Happened 3 times. Also strange block id "0000000000000000000000000000000000000000".
Are they maintenance blocks? Or someone generated a checkpoint block?

Code: [Select]
2015-08-20T23:25:23 th_a:invoke get_blockchain_synopsis get_blockchain_synop ] reference_point: 000007d0fc03ea61aacb907a0fd791e5384fa2 2a number_of_blocks_after_reference_point: 0 result: ["000009ef501ed09bea4e32d71077b13bcd3c28a1","000029ef11981d056e1a70afd0fdac952774 b2f7","000039ef9f6d0c5d83c52767cd98c710ac7a2d46","000041efa457c0e455f2569bc98b2e097baf8ace","000045ef42cf7a74580c57dd77cf3be887575d14" ,"000047ef9621e0266c0a7a9195a57cbb0aef6550","000048efd72770d20925e6e74a83d7a93f213f0a","0000496fa7fcba2947cc187a5fa9e7e30d8b5f3a","000 049afce3550f6f3a26efa67968d465ac16268","000049cfbf02c4d519b393a93430ee4785076736","000049df2dad0b1b7eb473d9eb6d2e6a31cc3080","000049e7 c78642267a650db5c41ae256f9112e76","000049eb39306a1360497002faeea118732d6761","000049ed587a0c63625259c90a08814b49dd48ad","0000000000000000000000000000000000000000","000049efc4646a99bad9d78607972719e1a2d79d"] application.cpp:492 2015-08-20T23:25:24 th_a:Witness Block Production block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-20T23:25:24 witness.cpp:240
Code: [Select]
2015-08-20T23:25:26 th_a:Witness Block Production block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T0 0:00:00 now: 2015-08-20T23:25:26 witness.cpp:240 2015-08-20T23:25:27 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.0 scheduled_time: 2015-08-20T2 3:25:27 now: 2015-08-20T23:25:27 witness.cpp:240 2015-08-20T23:25:27 th_a:invoke get_blockchain_synopsis get_blockchain_synop ] reference_point: 000007d0fc03ea61aacb907a0fd791e5384fa2 2a number_of_blocks_after_reference_point: 0 result: ["000009ef501ed09bea4e32d71077b13bcd3c28a1","000029ef11981d056e1a70afd0fdac952774 b2f7","000039ef9f6d0c5d83c52767cd98c710ac7a2d46","000041efa457c0e455f2569bc98b2e097baf8ace","000045ef42cf7a74580c57dd77cf3be887575d14" ,"000047ef9621e0266c0a7a9195a57cbb0aef6550","000048efd72770d20925e6e74a83d7a93f213f0a","0000496fa7fcba2947cc187a5fa9e7e30d8b5f3a","000 049afce3550f6f3a26efa67968d465ac16268","000049cfbf02c4d519b393a93430ee4785076736","000049df2dad0b1b7eb473d9eb6d2e6a31cc3080","000049e7 c78642267a650db5c41ae256f9112e76","000049eb39306a1360497002faeea118732d6761","000049ed587a0c63625259c90a08814b49dd48ad","0000000000000 000000000000000000000000000","000049efc4646a99bad9d78607972719e1a2d79d"] application.cpp:492 ... 2015-08-20T23:25:28 th_a:Witness Block Production block_production_loo ] slot: 2 scheduled_witness: 1.6.18 scheduled_time: 2015-08-20T23:25:28 now: 2015-08-20T23:25:28 witness.cpp:240
Code: [Select]
2015-08-20T23:26:40 th_a:Witness Block Production block_production_loo ] slot: 74 scheduled_witness: 1.6.20 scheduled_time: 2015-08-20T23:26:40 now: 2015-08-20T23:26:40 witness.cpp:240 2015-08-20T23:26:41 th_a:Witness Block Production block_production_loo ] slot: 75 scheduled_witness: 1.6.36 scheduled_time: 2015-08-20T23:26:41 now: 2015-08-20T23:26:41 witness.cpp:240 2015-08-20T23:26:42 th_a:Witness Block Production block_production_loo ] slot: 76 scheduled_witness: 1.6.5247 scheduled_time: 2015-08-20T23:26:42 now: 2015-08-20T23:26:42 witness.cpp:240 2015-08-20T23:26:42 th_a:Witness Block Production block_production_loo ] Witness 1.6.5247 production slot has arrived; generating a block now... witness.cpp:243 2015-08-20T23:26:42 th_a:Witness Block Production block_production_loo ] Got exception while generating block: 10 assert_exception: Assert Exception _consecutive_production_enabled || db.get_dynamic_global_properties().current_witness != scheduled_witness: Last block was generated by the same witness, this node is probably disconnected from the network so block production has been disabled. Disable this check with --allow-consecutive option. {} th_a witness.cpp:248 block_production_loop witness.cpp:266
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 12:06:39 am: default.log uploaded https://drive.google.com/open?id=0B3xrm70jSHn4d2ZDckJGM2ZGNGs.
I also have p2p.log, but it's a bit too large. @bytemaster do you need it?
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 12:13:44 am: The seed node down?
Code: [Select]
$ telnet 104.236.51.238 1776 Trying 104.236.51.238... telnet: Unable to connect to remote host: Connection refused
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on August 21, 2015, 12:19:05 am: Code: [Select]
info { "head_block_num": 21949, "head_block_id": "000055bd60276952c37246d38eee3cf9780c71d6", "head_block_age": "0 second old", "next_maintenance_time": "18 seconds in the future", "chain_id": "d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.5", "1.6.6", "1.6.7", "1.6.8", "1.6.9", "1.6.10", "1.6.11", "1.6.12", "1.6.13", "1.6.14", "1.6.15", "1.6.16", "1.6.17", "1.6.18", "1.6.19", "1.6.20", "1.6.21", "1.6.22", "1.6.23", "1.6.24", "1.6.25", "1.6.26", "1.6.27", "1.6.28", "1.6.29", "1.6.30", "1.6.31", "1.6.32", "1.6.33", "1.6.34", "1.6.35", "1.6.36", "1.6.37", "1.6.38", "1.6.39", "1.6.40", "1.6.41", "1.6.42", "1.6.43", "1.6.44", "1.6.45", "1.6.46", "1.6.47", "1.6.48", "1.6.49", "1.6.50", "1.6.51", "1.6.52", "1.6.53", "1.6.54", "1.6.55", "1.6.56", "1.6.57", "1.6.58", "1.6.59", "1.6.60", "1.6.61", "1.6.62", "1.6.63", "1.6.64", "1.6.65", "1.6.66", "1.6.67", "1.6.68", "1.6.69", "1.6.70", "1.6.71", "1.6.72", "1.6.73", "1.6.74", "1.6.75", "1.6.76", "1.6.77", "1.6.78", "1.6.79", "1.6.80", "1.6.81", "1.6.82", "1.6.83", "1.6.84", "1.6.85", "1.6.86", "1.6.87", "1.6.88", "1.6.89", "1.6.90", "1.6.91", "1.6.92", "1.6.93", "1.6.94", "1.6.95", "1.6.96", "1.6.1537", "1.6.5246", "1.6.5247", "1.6.5248" ], "active_committee_members": [ "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8", "1.5.9", "1.5.10" ], "entropy": "a04cd87714d3013b2ed9b14599ae2b2ad7b7e8e1" }
I'm seeing a few brief pauses occasionally that are most likely missed blocks, but no sign of a serious failure yet. I'll dig into the logs and see what I can find. Is there a command I'm missing to get delegate participation, or recent missed blocks, or list forks?
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 12:21:06 am: Quote from: Troglodactyl on August 21, 2015, 12:19:05 am
Code: [Select]
info { "head_block_num": 21949, "head_block_id": "000055bd60276952c37246d38eee3cf9780c71d6", "head_block_age": "0 second old", "next_maintenance_time": "18 seconds in the future", "chain_id": "d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.5", "1.6.6", "1.6.7", "1.6.8", "1.6.9", "1.6.10", "1.6.11", "1.6.12", "1.6.13", "1.6.14", "1.6.15", "1.6.16", "1.6.17", "1.6.18", "1.6.19", "1.6.20", "1.6.21", "1.6.22", "1.6.23", "1.6.24", "1.6.25", "1.6.26", "1.6.27", "1.6.28", "1.6.29", "1.6.30", "1.6.31", "1.6.32", "1.6.33", "1.6.34", "1.6.35", "1.6.36", "1.6.37", "1.6.38", "1.6.39", "1.6.40", "1.6.41", "1.6.42", "1.6.43", "1.6.44", "1.6.45", "1.6.46", "1.6.47", "1.6.48", "1.6.49", "1.6.50", "1.6.51", "1.6.52", "1.6.53", "1.6.54", "1.6.55", "1.6.56", "1.6.57", "1.6.58", "1.6.59", "1.6.60", "1.6.61", "1.6.62", "1.6.63", "1.6.64", "1.6.65", "1.6.66", "1.6.67", "1.6.68", "1.6.69", "1.6.70", "1.6.71", "1.6.72", "1.6.73", "1.6.74", "1.6.75", "1.6.76", "1.6.77", "1.6.78", "1.6.79", "1.6.80", "1.6.81", "1.6.82", "1.6.83", "1.6.84", "1.6.85", "1.6.86", "1.6.87", "1.6.88", "1.6.89", "1.6.90", "1.6.91", "1.6.92", "1.6.93", "1.6.94", "1.6.95", "1.6.96", "1.6.1537", "1.6.5246", "1.6.5247", "1.6.5248" ], "active_committee_members": [ "1.5.0", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.5.5", "1.5.6", "1.5.7", "1.5.8", "1.5.9", "1.5.10" ], "entropy": "a04cd87714d3013b2ed9b14599ae2b2ad7b7e8e1" }
I'm seeing a few brief pauses occasionally that are most likely missed blocks, but no sign of a serious failure yet. I'll dig into the logs and see what I can find. Is there a command I'm missing to get delegate participation, or recent missed blocks, or list forks?
Sounds good. May I have your p2p IP/port so that I can re-sync?
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on August 21, 2015, 12:33:59 am: Code: [Select]
new >>> get_dynamic_global_properties get_dynamic_global_properties { "id": "2.1.0", "random": "42f2b51fa6a239642d8394d1806f9f8036b55f4b", "head_block_number": 22475, "head_block_id": "000057cbdb4a4e158cb39094bc7c078c86680be6", "time": "2015-08-21T00:23:49", "current_witness": "1.6.1", "next_maintenance_time": "2015-08-21T00:25:00", "witness_budget": 0, "accounts_registered_this_interval": 0, "recently_missed_count": 2, "dynamic_flags": 0 }
Try connecting to 176.221.43.130:33323, that's where all the blocks I get seem to be coming from, so I'm guessing that's my peer with lowest latency to the rest of the network.
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 01:01:16 am: Quote from: Troglodactyl on August 21, 2015, 12:33:59 am
Try connecting to 176.221.43.130:33323, that's where all the blocks I get seem to be coming from, so I'm guessing that's my peer with lowest latency to the rest of the network.
Yes that's one.
And puppies' node 45.55.6.216:1776
But it's hard for my node to connect to them.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 21, 2015, 01:03:37 am: Quote from: abit on August 21, 2015, 01:01:16 am
Quote from: Troglodactyl on August 21, 2015, 12:33:59 am
Try connecting to 176.221.43.130:33323, that's where all the blocks I get seem to be coming from, so I'm guessing that's my peer with lowest latency to the rest of the network.
Yes that's one.
And puppies' node 45.55.6.216:1776
But it's hard for my node to connect to them.

I just got my node back up. This time with gdb

My home node is forked again though.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 21, 2015, 02:23:02 am: My home node keeps losing sync.
Code: [Select]
2015-08-21T01:57:22 p2p:message read_loop process_block_during ] Successfully pushed block 27866 (id:00006cda44c0d8b2e2566d15dfe7a2610430a774) node.cpp:3109 2015-08-21T01:57:22 p2p:message read_loop process_block_during ] client validated the block, advertising it to other peers node.cpp:3133 2015-08-21T01:57:22 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 1 items advertised to peer (114 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T01:57:22 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (0 left), and 0 advertised to us (115 left) peer_connection.cpp:479 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] beginning an iteration of advertise inventory node.cpp:1175 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: false node.cpp:1188 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] inventory_to_advertise: [{"item_type":1001,"item_hash":"0a1c44a16235a09d4c84668842c85471b45e40e0"}] node.cpp:1196 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_advertised_to_peer.find(item_to_advertise): {"item":{"item_type":3624437200,"item_hash":"ff7f00002b00000000000000ffffffffff7f0000"},"timestamp":"2023-11-27T10:29:02"} node.cpp:1200 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_peer_advertised_to_us.find(item_to_advertise): {"item":{"item_type":3624438048,"item_hash":"ff7f00000000000000000000c8b007d8ff7f0000"},"timestamp":"1948-10-02T17:47:20"} node.cpp:1202 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] advertising item 0a1c44a16235a09d4c84668842c85471b45e40e0 to peer 176.221.43.130:33323 node.cpp:1212 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] advertising 1 new item(s) of 1 type(s) to peer 176.221.43.130:33323 node.cpp:1218 2015-08-21T01:57:22 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 0 items advertised to peer (115 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: false node.cpp:1188 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] inventory_to_advertise: [{"item_type":1001,"item_hash":"0a1c44a16235a09d4c84668842c85471b45e40e0"}] node.cpp:1196 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_advertised_to_peer.find(item_to_advertise): {"item":{"item_type":3623881952,"item_hash":"ff7f0000000000000000000068a305d8ff7f0000"},"timestamp":"1948-09-25T19:23:04"} node.cpp:1200 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] advertising 0 new item(s) of 0 type(s) to peer 45.55.6.216:1776 node.cpp:1218 2015-08-21T01:57:22 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (0 left), and 0 advertised to us (115 left) peer_connection.cpp:479 2015-08-21T01:57:22 p2p:advertise_inventory_loop send_message ] peer_connection::send_message() enqueueing message of type 5001 for peer 176.221.43.130:33323 peer_connection.cpp:365 2015-08-21T01:57:22 p2p:advertise_inventory_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-21T01:57:22 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104 2015-08-21T01:57:22 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-21T01:57:22 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5001 for peer 176.221.43.130:33323 peer_connection.cpp:291 2015-08-21T01:57:22 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 176.221.43.130:33323 peer_connection.cpp:294 2015-08-21T01:57:22 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-21T01:57:22 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-21T01:57:22 p2p:connect_to_task connect_to ] established outbound connection to 114.92.254.159:62015 peer_connection.cpp:251 2015-08-21T01:57:22 p2p:connect_to_task send_message ] peer_connection::send_message() enqueueing message of type 5006 for peer 114.92.254.159:62015 peer_connection.cpp:365 2015-08-21T01:57:22 p2p:connect_to_task send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-21T01:57:22 p2p:connect_to_task connect_to_task ] Sent "hello" to peer 114.92.254.159:62015 node.cpp:4093 2015-08-21T01:57:22 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-21T01:57:22 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5006 for peer 114.92.254.159:62015 peer_connection.cpp:291 2015-08-21T01:57:22 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 114.92.254.159:62015 peer_connection.cpp:294 2015-08-21T01:57:22 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-21T01:57:22 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-21T01:57:23 p2p:message read_loop on_message ] handling message hello_message_type 1ee7de2b2696aece8234a8c1198d21bbee1d4e29 size 528 from peer 114.92.254.159:62015 node.cpp:1651 2015-08-21T01:57:23 p2p:message read_loop send_message ] peer_connection::send_message() enqueueing message of type 5007 for peer 114.92.254.159:62015 peer_connection.cpp:365 2015-08-21T01:57:23 p2p:message read_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-21T01:57:23 p2p:message read_loop on_hello_message ] Received a hello_message from peer 114.92.254.159:62015, sending reply to accept connection node.cpp:1967 2015-08-21T01:57:23 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-21T01:57:23 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5007 for peer 114.92.254.159:62015 peer_connection.cpp:291 2015-08-21T01:57:23 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 114.92.254.159:62015 peer_connection.cpp:294 2015-08-21T01:57:23 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-21T01:57:23 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-21T01:57:23 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 161f660391f8a231b70a77010704f124db1196af size 25 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-21T01:57:23 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (0 left), and 1 advertised to us (114 left) peer_connection.cpp:479 2015-08-21T01:57:23 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-21T01:57:23 p2p:message read_loop on_item_ids_inventor ] adding item 07eb3cbe0052b4a4ee0ed8dec43655b6965f0b1d from inventory message to our list of items to fetch node.cpp:2647 2015-08-21T01:57:23 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:1104 2015-08-21T01:57:23 p2p:fetch_items_loop fetch_items_loop ] requesting item 07eb3cbe0052b4a4ee0ed8dec43655b6965f0b1d from peer 45.55.6.216:1776 node.cpp:1123 2015-08-21T01:57:23 p2p:fetch_items_loop send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:365 2015-08-21T01:57:23 p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-21T01:57:23 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-21T01:57:23 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:291 2015-08-21T01:57:23 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 45.55.6.216:1776 peer_connection.cpp:294 2015-08-21T01:57:23 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-21T01:57:23 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-21T01:57:23 p2p:message read_loop on_message ] handling message block_message_type 07eb3cbe0052b4a4ee0ed8dec43655b6965f0b1d size 172 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-21T01:57:23 p2p:message read_loop process_block_during ] received a block from peer 45.55.6.216:1776, passing it to client node.cpp:3087 2015-08-21T01:57:23 p2p:message read_loop process_block_during ] Failed to push block 27867 (id:00006cdb2f8937565fe6b272e3b43073be37a0de), client rejected block sent by peer node.cpp:3198and a little while later
Code: [Select]
1671470ms th_a application.cpp:348 handle_block ] Got block #29623 from network 1672475ms th_a application.cpp:348 handle_block ] Got block #29624 from network 1675558ms th_a application.cpp:348 handle_block ] Got block #29627 from network 1675558ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1675722ms th_a application.cpp:348 handle_block ] Got block #29626 from network 1675722ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1676472ms th_a application.cpp:348 handle_block ] Got block #29628 from network 1676472ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1677471ms th_a application.cpp:348 handle_block ] Got block #29629 from network 1677471ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1678473ms th_a application.cpp:348 handle_block ] Got block #29630 from network
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on August 21, 2015, 02:31:07 am: Quote from: puppies on August 21, 2015, 02:23:02 am
My home node keeps losing sync.
Code: [Select]
2015-08-21T01:57:22 p2p:message read_loop process_block_during ] Successfully pushed block 27866 (id:00006cda44c0d8b2e2566d15dfe7a2610430a774) node.cpp:3109 2015-08-21T01:57:22 p2p:message read_loop process_block_during ] client validated the block, advertising it to other peers node.cpp:3133 2015-08-21T01:57:22 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 1 items advertised to peer (114 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T01:57:22 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (0 left), and 0 advertised to us (115 left) peer_connection.cpp:479 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] beginning an iteration of advertise inventory node.cpp:1175 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: false node.cpp:1188 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] inventory_to_advertise: [{"item_type":1001,"item_hash":"0a1c44a16235a09d4c84668842c85471b45e40e0"}] node.cpp:1196 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_advertised_to_peer.find(item_to_advertise): {"item":{"item_type":3624437200,"item_hash":"ff7f00002b00000000000000ffffffffff7f0000"},"timestamp":"2023-11-27T10:29:02"} node.cpp:1200 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_peer_advertised_to_us.find(item_to_advertise): {"item":{"item_type":3624438048,"item_hash":"ff7f00000000000000000000c8b007d8ff7f0000"},"timestamp":"1948-10-02T17:47:20"} node.cpp:1202 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] advertising item 0a1c44a16235a09d4c84668842c85471b45e40e0 to peer 176.221.43.130:33323 node.cpp:1212 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] advertising 1 new item(s) of 1 type(s) to peer 176.221.43.130:33323 node.cpp:1218 2015-08-21T01:57:22 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 0 items advertised to peer (115 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: false node.cpp:1188 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] inventory_to_advertise: [{"item_type":1001,"item_hash":"0a1c44a16235a09d4c84668842c85471b45e40e0"}] node.cpp:1196 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_advertised_to_peer.find(item_to_advertise): {"item":{"item_type":3623881952,"item_hash":"ff7f0000000000000000000068a305d8ff7f0000"},"timestamp":"1948-09-25T19:23:04"} node.cpp:1200 2015-08-21T01:57:22 p2p:advertise_inventory_loop advertise_inventory_ ] advertising 0 new item(s) of 0 type(s) to peer 45.55.6.216:1776 node.cpp:1218 2015-08-21T01:57:22 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (0 left), and 0 advertised to us (115 left) peer_connection.cpp:479 2015-08-21T01:57:22 p2p:advertise_inventory_loop send_message ] peer_connection::send_message() enqueueing message of type 5001 for peer 176.221.43.130:33323 peer_connection.cpp:365 2015-08-21T01:57:22 p2p:advertise_inventory_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-21T01:57:22 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104 2015-08-21T01:57:22 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-21T01:57:22 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5001 for peer 176.221.43.130:33323 peer_connection.cpp:291 2015-08-21T01:57:22 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 176.221.43.130:33323 peer_connection.cpp:294 2015-08-21T01:57:22 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-21T01:57:22 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-21T01:57:22 p2p:connect_to_task connect_to ] established outbound connection to 114.92.254.159:62015 peer_connection.cpp:251 2015-08-21T01:57:22 p2p:connect_to_task send_message ] peer_connection::send_message() enqueueing message of type 5006 for peer 114.92.254.159:62015 peer_connection.cpp:365 2015-08-21T01:57:22 p2p:connect_to_task send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-21T01:57:22 p2p:connect_to_task connect_to_task ] Sent "hello" to peer 114.92.254.159:62015 node.cpp:4093 2015-08-21T01:57:22 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-21T01:57:22 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5006 for peer 114.92.254.159:62015 peer_connection.cpp:291 2015-08-21T01:57:22 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 114.92.254.159:62015 peer_connection.cpp:294 2015-08-21T01:57:22 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-21T01:57:22 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-21T01:57:23 p2p:message read_loop on_message ] handling message hello_message_type 1ee7de2b2696aece8234a8c1198d21bbee1d4e29 size 528 from peer 114.92.254.159:62015 node.cpp:1651 2015-08-21T01:57:23 p2p:message read_loop send_message ] peer_connection::send_message() enqueueing message of type 5007 for peer 114.92.254.159:62015 peer_connection.cpp:365 2015-08-21T01:57:23 p2p:message read_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-21T01:57:23 p2p:message read_loop on_hello_message ] Received a hello_message from peer 114.92.254.159:62015, sending reply to accept connection node.cpp:1967 2015-08-21T01:57:23 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-21T01:57:23 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5007 for peer 114.92.254.159:62015 peer_connection.cpp:291 2015-08-21T01:57:23 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 114.92.254.159:62015 peer_connection.cpp:294 2015-08-21T01:57:23 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-21T01:57:23 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-21T01:57:23 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 161f660391f8a231b70a77010704f124db1196af size 25 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-21T01:57:23 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (0 left), and 1 advertised to us (114 left) peer_connection.cpp:479 2015-08-21T01:57:23 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-21T01:57:23 p2p:message read_loop on_item_ids_inventor ] adding item 07eb3cbe0052b4a4ee0ed8dec43655b6965f0b1d from inventory message to our list of items to fetch node.cpp:2647 2015-08-21T01:57:23 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:1104 2015-08-21T01:57:23 p2p:fetch_items_loop fetch_items_loop ] requesting item 07eb3cbe0052b4a4ee0ed8dec43655b6965f0b1d from peer 45.55.6.216:1776 node.cpp:1123 2015-08-21T01:57:23 p2p:fetch_items_loop send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:365 2015-08-21T01:57:23 p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-21T01:57:23 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-21T01:57:23 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:291 2015-08-21T01:57:23 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 45.55.6.216:1776 peer_connection.cpp:294 2015-08-21T01:57:23 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-21T01:57:23 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-21T01:57:23 p2p:message read_loop on_message ] handling message block_message_type 07eb3cbe0052b4a4ee0ed8dec43655b6965f0b1d size 172 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-21T01:57:23 p2p:message read_loop process_block_during ] received a block from peer 45.55.6.216:1776, passing it to client node.cpp:3087 2015-08-21T01:57:23 p2p:message read_loop process_block_during ] Failed to push block 27867 (id:00006cdb2f8937565fe6b272e3b43073be37a0de), client rejected block sent by peer node.cpp:3198
Code: [Select]
1671470ms th_a application.cpp:348 handle_block ] Got block #29623 from network 1672475ms th_a application.cpp:348 handle_block ] Got block #29624 from network 1675558ms th_a application.cpp:348 handle_block ] Got block #29627 from network 1675558ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1675722ms th_a application.cpp:348 handle_block ] Got block #29626 from network 1675722ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1676472ms th_a application.cpp:348 handle_block ] Got block #29628 from network 1676472ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1677471ms th_a application.cpp:348 handle_block ] Got block #29629 from network 1677471ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1678473ms th_a application.cpp:348 handle_block ] Got block #29630 from network

Code: [Select]
get_block 27867 { "previous": "00006cda44c0d8b2e2566d15dfe7a2610430a774", "timestamp": "2015-08-21T01:57:23", "witness": "1.6.71", "next_secret_hash": "74adc395b0e7aff2e854300a0d0e913fc83da333", "previous_secret": "2c2d4cb66202a45f75a7fd8876f4886694ee7bf5", "transaction_merkle_root": "0000000000000000000000000000000000000000", "extensions": [], "witness_signature": "1f14fa5a625f2e7f21a2fb80dff311f2da97da5834f7f21718dde7d904c848043e04fa596927d006090356854d0d19bd0e741b0f186c8c54f0070eddd2635e5608", "transactions": [] }
There's what I have for that block.

Code: [Select]
new >>> get_dynamic_global_properties get_dynamic_global_properties { "id": "2.1.0", "random": "b8c6bfb33a7c6806f4d1d02784f8020891935417", "head_block_number": 29773, "head_block_id": "0000744d5eb7d745a0de9541172ce4898de459c9", "time": "2015-08-21T02:30:29", "current_witness": "1.6.6", "next_maintenance_time": "2015-08-21T02:35:00", "witness_budget": 96821279, "accounts_registered_this_interval": 0, "recently_missed_count": 0, "dynamic_flags": 0 }
And my current blockchain state.
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on August 21, 2015, 02:34:35 am: Code: [Select]
get_block 27868 { "previous": "00006cdb2f8937565fe6b272e3b43073be37a0de", "timestamp": "2015-08-21T01:57:24", "witness": "1.6.78", "next_secret_hash": "202f2a4a975f81e64b6caa1d46f9423ca1cbdde4", "previous_secret": "93d75a091fe435d5e92e66c29f2c55ae9449ea56", "transaction_merkle_root": "0000000000000000000000000000000000000000", "extensions": [], "witness_signature": "1f1b27b0e3b05b097eb773e11306513f46b90ca1f2f5c394a54836533d988887471813ddf0c4526687b13d2edbb43b2e2389b75245e4c48d4e3ab78f9015a1287a", "transactions": [] }
Getting the next block confirms that it's "previous block" id matches the one your node rejected, so now we just have to figure out why your node rejected that block.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 21, 2015, 02:44:57 am: And it keeps happening over and over again on that node. Meanwhile my vps is chugging along. Is there a way to turn on more logging options. All I currently see is the p2p.log

Lots and lots of this from my most recent
Code: [Select]
th_a db_block.cpp:176 _push_block 2697067ms th_a witness.cpp:240 block_production_loo ] slot: 653 scheduled_witness: 1.6.6 scheduled_time: 2015-08-21T02:44:57 now: 2015-08-21T02:44:57 2697483ms th_a application.cpp:348 handle_block ] Got block #30610 from network 2697483ms th_a application.cpp:370 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num < _head->num + MAX_BLOCK_REORDERING: {} th_a fork_database.cpp:70 _push_block {"new_block":{"previous":"00007791ba405833b20a74e788cfc1c3e5b2909e","timestamp":"2015-08-21T02:44:57","witness":"1.6.0","next_secret_hash":"d0120d9cae36b654773f0285cd27224f5a66882b","previous_secret":"5dc2e1ffee2e6df079a5da200c9f6a0c89f0ab73","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f5a9dfeeb9eadcee4d6171a7f615476ef0f441faf3c4193d8b0febae1fea965ac1ca260a72fff57b5c5de4b6af62bddf3fe22c6a43c6a6f23ba456de8c2711453","transactions":[]}} th_a db_block.cpp:176 _push_block 2697701ms th_a application.cpp:348 handle_block ] Got block #30610 from network 2697702ms th_a application.cpp:370 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num < _head->num + MAX_BLOCK_REORDERING: {} th_a fork_database.cpp:70 _push_block {"new_block":{"previous":"00007791ba405833b20a74e788cfc1c3e5b2909e","timestamp":"2015-08-21T02:44:57","witness":"1.6.0","next_secret_hash":"d0120d9cae36b654773f0285cd27224f5a66882b","previous_secret":"5dc2e1ffee2e6df079a5da200c9f6a0c89f0ab73","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f5a9dfeeb9eadcee4d6171a7f615476ef0f441faf3c4193d8b0febae1fea965ac1ca260a72fff57b5c5de4b6af62bddf3fe22c6a43c6a6f23ba456de8c2711453","transactions":[]}} th_a db_block.cpp:176 _push_block 2698061ms th_a witness.cpp:240 block_production_loo ] slot: 654 scheduled_witness: 1.6.60 scheduled_time: 2015-08-21T02:44:58 now: 2015-08-21T02:44:58 2698483ms th_a application.cpp:348 handle_block ] Got block #30611 from network 2698483ms th_a application.cpp:370 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num < _head->num + MAX_BLOCK_REORDERING: {} th_a fork_database.cpp:70 _push_block {"new_block":{"previous":"000077927c5de70811b512694832fc9d12f36eb0","timestamp":"2015-08-21T02:44:58","witness":"1.6.93","next_secret_hash":"fc999ce474e5b02294da89b547e132814b8ec344","previous_secret":"48ac013a4ad1d99ad366e527c8fb1fbca696a4ee","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f7630ab0ddb7677a285515e8de19f66c6d649ed1ac7cc486c730e99633455d7c23ea243286ec1ef4100276f8e317f9cccbd01cb1a2556ed397e0c82a4e85a6275","transactions":[]}} th_a db_block.cpp:176 _push_block 2698703ms th_a application.cpp:348 handle_block ] Got block #30611 from network 2698703ms th_a application.cpp:370 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num < _head->num + MAX_BLOCK_REORDERING: {} th_a fork_database.cpp:70 _push_block {"new_block":{"previous":"000077927c5de70811b512694832fc9d12f36eb0","timestamp":"2015-08-21T02:44:58","witness":"1.6.93","next_secret_hash":"fc999ce474e5b02294da89b547e132814b8ec344","previous_secret":"48ac013a4ad1d99ad366e527c8fb1fbca696a4ee","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f7630ab0ddb7677a285515e8de19f66c6d649ed1ac7cc486c730e99633455d7c23ea243286ec1ef4100276f8e317f9cccbd01cb1a2556ed397e0c82a4e85a6275","transactions":[]}} th_a db_block.cpp:176 _push_block
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on August 21, 2015, 02:52:06 am: Quote from: puppies on August 21, 2015, 02:44:57 am
And it keeps happening over and over again on that node. Meanwhile my vps is chugging along. Is there a way to turn on more logging options. All I currently see is the p2p.log

Lots and lots of this from my most recent
...

Look in the config file, you should see:
Code: [Select]
# declare an appender named "stderr" that writes messages to the console [log.console_appender.stderr] stream=std_error # declare an appender named "p2p" that writes messages to p2p.log [log.file_appender.p2p] filename=logs/p2p/p2p.log # filename can be absolute or relative to this config file # route any messages logged to the default logger to the "stderr" logger we # declared above, if they are info level are higher [logger.default] level=info appenders=stderr # route messages sent to the "p2p" logger to the p2p appender declared above [logger.p2p] level=debug appenders=p2p
At the end. Try changing that to:

Code: [Select]
# declare an appender named "stderr" that writes messages to the console [log.file_appender.stderr] filename=logs/stderr/stderr.log # declare an appender named "p2p" that writes messages to p2p.log [log.file_appender.p2p] filename=logs/p2p/p2p.log # filename can be absolute or relative to this config file # route any messages logged to the default logger to the "stderr" logger we # declared above, if they are info level are higher [logger.default] level=info appenders=stderr # route messages sent to the "p2p" logger to the p2p appender declared above [logger.p2p] level=debug appenders=p2p
But watch it, I haven't tried it and it's likely very verbose. Keep an eye on how much space it's eating before you leave it running.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 21, 2015, 02:55:34 am: Quote from: Troglodactyl on August 21, 2015, 12:33:59 am
Try connecting to 176.221.43.130:33323, that's where all the blocks I get seem to be coming from, so I'm guessing that's my peer with lowest latency to the rest of the network.

Connected to this node and started producing blocks again
Title: Re: Test Net for Advanced Users
Post by: puppies on August 21, 2015, 02:59:25 am: Thanks. I am running with the new logging now.

Interestingly enough those changes prevent anything from showing up in the terminal
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on August 21, 2015, 03:11:02 am: Quote from: puppies on August 21, 2015, 02:59:25 am
Thanks. I am running with the new logging now.

Interestingly enough those changes prevent anything from showing up in the terminal

Yeah, you can change it so it shows up both places, just define whichever appenders you want, and then direct each logger to one or more of them. Here's what mine looks like now:

Code: [Select]
# declare an appender named "stderr" that writes messages to the console [log.console_appender.stderr] stream=std_error # declare an appender named "p2p" that writes messages to p2p.log [log.file_appender.p2p] filename=logs/p2p/p2p.log # filename can be absolute or relative to this config file # route any messages logged to the default logger to the "stderr" logger we # declared above, if they are info level are higher [logger.default] level=info appenders=stderr # route messages sent to the "p2p" logger to the p2p appender declared above [logger.p2p] level=debug appenders=p2p,stderr
We need to find what all other loggers are in use and at what levels...
Title: Re: Test Net for Advanced Users
Post by: clayop on August 21, 2015, 03:14:02 am: Massive transactions seem to crash witness node. I will check it again and will upload error messages.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 21, 2015, 03:17:15 am: Code: [Select]
921000ms th_a witness.cpp:240 block_production_loo ] slot: 2 scheduled_witness: 1.6.93 scheduled_time: 2015-08-21T03:15:21 now: 2015-08-21T03:15:21 922000ms th_a witness.cpp:240 block_production_loo ] slot: 3 scheduled_witness: 1.6.1537 scheduled_time: 2015-08-21T03:15:22 now: 2015-08-1T03:15:22 922000ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.1537 production slot has arrived; generating a block now... 922019ms th_a witness.cpp:256 block_production_loo ] Generated block #32355 with timestamp 2015-08-21T03:15:22 at time 2015-08-21T03:15:22 923000ms th_a witness.cpp:240 block_production_loo ] slot: 1 scheduled_witness: 1.6.21 scheduled_time: 2015-08-21T03:15:23 now: 2015-08-21T03:15:23 924000ms th_a witness.cpp:240 block_production_loo ] slot: 2 scheduled_witness: 1.6.37 scheduled_time: 2015-08-21T03:15:24 now: 2015-08-21T03:15:24 925000ms th_a witness.cpp:240 block_production_loo ] slot: 3 scheduled_witness: 1.6.96 scheduled_time: 2015-08-21T03:15:25 now: 2015-08-21T03:15:25 926000ms th_a witness.cpp:240 block_production_loo ] slot: 4 scheduled_witness: 1.6.14 scheduled_time: 2015-08-21T03:15:26 now: 2015-08-21T03:15:26 927000ms th_a witness.cpp:240 block_production_loo ] slot: 5 scheduled_witness: 1.6.60 scheduled_time: 2015-08-21T03:15:27 now: 2015-08-21T03:15:27 928000ms th_a witness.cpp:240 block_production_loo ] slot: 6 scheduled_witness: 1.6.32 scheduled_time: 2015-08-21T03:15:28 now: 2015-08-21T03:15:28 929000ms th_a witness.cpp:240 block_production_loo ] slot: 7 scheduled_witness: 1.6.84 scheduled_time: 2015-08-21T03:15:29 now: 2015-08-21T03:15:29 930000ms th_a witness.cpp:240 block_production_loo ] slot: 8 scheduled_witness: 1.6.26 scheduled_time: 2015-08-21T03:15:30 now: 2015-08-21T03:15:30 931000ms th_a witness.cpp:240 block_production_loo ] slot: 9 scheduled_witness: 1.6.76 scheduled_time: 2015-08-21T03:15:31 now: 2015-08-21T03:15:31 931268ms th_a application.cpp:492 get_blockchain_synop ] reference_point: 0000000000000000000000000000000000000000 number_of_blocks_after_reference_point: 0 result: ["00003e63934b84f27b5a0afde42a7627fda771d4","00005e63bcf5fb27247d2a611a50f0b5fa559755","00006e633c250ba066e1848bf2907518cd81febf","000076635430a274998a8ffe6e76d9895cb36042","00007a63bc5b0d4009fc46e0572bbeed45b838a6","00007c6304c038950fa23836fd3be4c98296850f","00007d633081235cec1462b6954df2dea5aaa55b","00007de36fb03c220c6cdfa4b367f16f122f9da0","00007e230bf4f5b3813f0c28df1b2b73b2d0c8fc","00007e43af64f90d3c03fff6ce2f7cfbc0edfcf2","00007e53cbc14d88598fe80fa4250164f3d87272","00007e5b37b41f58639a14686db50a9d415332fe","00007e5f84a48d00a63bf9efa6a7748add0bad43","00007e6193119832728d72fd742288c7919233bf","00007e624f4b577b2f9bdffde6666cdbbb96345e","00007e6386f99dd87b9ef26cbe7704723ce60e03"] 932000ms th_a witness.cpp:240 block_production_loo ] slot: 10 scheduled_witness: 1.6.55 scheduled_time: 2015-08-21T03:15:32 now: 2015-08-21T03:15:32 932331ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00007e6386f99dd87b9ef26cbe7704723ce60e03"} 932331ms th_a application.cpp:451 get_item ] Serving up block #32355 932333ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00007e6386f99dd87b9ef26cbe7704723ce60e03"} 932333ms th_a application.cpp:451 get_item ] Serving up block #32355 932352ms th_a application.cpp:370 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception !_stack.empty(): {} th_a undo_database.cpp:155 pop_commit {} th_a object_database.cpp:102 pop_undo {} th_a db_block.cpp:329 pop_block {"new_block":{"previous":"00007e63713b745a74f3988377f6b520e1fe1361","timestamp":"2015-08 -21T03:15:21","witness":"1.6.93","next_secret_hash":"5bb6e0b4cd3a80a374a284ad762aa12fb0ae564 5","previous_secret":"5a45616623bb4cfe020e8ca712aa77067b41a8d1","transaction_merkle_root":"5 01b214c34702ed6be5410f66e464c358c3bc30a","extensions":[],"witness_signature":"205b6985a09cd3 b66500a1189fa6deae7133a80a492c7984b0414aef957ec9b53022851a3bc4a48da945f3c699de19b1c9d35b3bb0 33e6a029939e3837ab70148a","transactions":[{"ref_block_num":32351,"ref_block_prefix":9282692, "expiration":"2015-08-21T03:15:49","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3 .0"},"from":"1.2.22309","to":"1.2.63354","amount":{"amount":100000,"asset_id":"1.3.0"},"exte nsions":[]}]],"extensions":[],"signatures":["1f0b1a1ad0ab2a3df9f0f4019aa6237cebbf1f982786e5f 9aa1ce356b1af2a77c02368be41a9079060b8b74100fbbe631e6290a4d785a88da362a4215eb472fe34"],"opera tion_results":[[0,{}]]}]}} th_a db_block.cpp:176 _push_block
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on August 21, 2015, 03:23:27 am: Here are the available logging levels: all debug info warn error off

Not sure why I'm not getting any more peers:

Code: [Select]
1503270ms p2p node.cpp:4404 dump_node_status ] ----------------- PEER STATUS UPDATE -------------------- 1503270ms p2p node.cpp:4407 dump_node_status ] number of peers: 1 active, 0, 0 closing. attempting to maintain 20 - 200 peers 1503271ms p2p node.cpp:4412 dump_node_status ] active peer 176.221.43.130:33323 peer_is_in_sync_with_us:true we_are_in_sync_with_peer:true 1503271ms p2p node.cpp:4425 dump_node_status ] --------- MEMORY USAGE ------------ 1503271ms p2p node.cpp:4426 dump_node_status ] node._active_sync_requests size: 0 1503271ms p2p node.cpp:4427 dump_node_status ] node._received_sync_items size: 0 1503271ms p2p node.cpp:4428 dump_node_status ] node._new_received_sync_items size: 0 1503271ms p2p node.cpp:4429 dump_node_status ] node._items_to_fetch size: 0 1503271ms p2p node.cpp:4430 dump_node_status ] node._new_inventory size: 0 1503271ms p2p node.cpp:4431 dump_node_status ] node._message_cache size: 2 1503271ms p2p node.cpp:4434 dump_node_status ] peer 176.221.43.130:33323 1503272ms p2p node.cpp:4435 dump_node_status ] peer.ids_of_items_to_get size: 0 1503272ms p2p node.cpp:4436 dump_node_status ] peer.inventory_peer_advertised_to_us size: 117 1503272ms p2p node.cpp:4437 dump_node_status ] peer.inventory_advertised_to_peer size: 0 1503272ms p2p node.cpp:4438 dump_node_status ] peer.items_requested_from_peer size: 0 1503272ms p2p node.cpp:4439 dump_node_status ] peer.sync_items_requested_from_peer size: 0 1503272ms p2p node.cpp:4441 dump_node_status ] --------- END MEMORY USAGE ------------
Title: Re: Test Net for Advanced Users
Post by: clayop on August 21, 2015, 03:27:33 am: Can somebody reproduce a bug I found? I just copied and pasted multiple (over 300) number of transactions to CLI. Then witness node stopped.

eg)
transfer delegate-clayop puppy 1 CORE "" true
transfer delegate-clayop puppy 1 CORE "" true
...
transfer delegate-clayop puppy 1 CORE "" true
transfer delegate-clayop puppy 1 CORE "" true
transfer delegate-clayop puppy 1 CORE "" true
Title: Re: Test Net for Advanced Users
Post by: puppies on August 21, 2015, 03:39:51 am: sterr log
Code: [Select]
2015-08-21T03:09:24 th_a:invoke handle_block handle_block ] Got block #32017 from network application.cpp:348 2015-08-21T03:09:24 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.5 scheduled_time: 2015-08-21T03:09:25 now: 2015-08-21T03:09:25 witness.cpp:240 2015-08-21T03:09:25 th_a:Witness Block Production block_production_loo ] slot: 2 scheduled_witness: 1.6.5248 scheduled_time: 2015-08-21T03:09:26 now: 2015-08-21T03:09:26 witness.cpp:240 2015-08-21T03:09:26 th_a:Witness Block Production block_production_loo ] slot: 3 scheduled_witness: 1.6.15 scheduled_time: 2015-08-21T03:09:27 now: 2015-08-21T03:09:27 witness.cpp:240 2015-08-21T03:09:27 th_a:Witness Block Production block_production_loo ] slot: 4 scheduled_witness: 1.6.58 scheduled_time: 2015-08-21T03:09:28 now: 2015-08-21T03:09:28 witness.cpp:240 2015-08-21T03:09:28 th_a:Witness Block Production block_production_loo ] slot: 5 scheduled_witness: 1.6.17 scheduled_time: 2015-08-21T03:09:29 now: 2015-08-21T03:09:29 witness.cpp:240 2015-08-21T03:09:29 th_a:Witness Block Production block_production_loo ] slot: 6 scheduled_witness: 1.6.11 scheduled_time: 2015-08-21T03:09:30 now: 2015-08-21T03:09:30 witness.cpp:240 2015-08-21T03:09:30 th_a:Witness Block Production block_production_loo ] slot: 7 scheduled_witness: 1.6.83 scheduled_time: 2015-08-21T03:09:31 now: 2015-08-21T03:09:31 witness.cpp:240 2015-08-21T03:09:31 th_a:Witness Block Production block_production_loo ] slot: 8 scheduled_witness: 1.6.61 scheduled_time: 2015-08-21T03:09:32 now: 2015-08-21T03:09:32 witness.cpp:240 2015-08-21T03:09:32 th_a:Witness Block Production block_production_loo ] slot: 9 scheduled_witness: 1.6.69 scheduled_time: 2015-08-21T03:09:33 now: 2015-08-21T03:09:33 witness.cpp:240 2015-08-21T03:09:33 th_a:invoke handle_block handle_block ] Got block #32024 from network application.cpp:348 2015-08-21T03:09:33 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link.
Code: [Select]
2015-08-21T03:09:23 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (111 left), and 0 advertised to us (6 left) peer_connection.cpp:479 2015-08-21T03:09:23 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-21T03:09:24 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 9f6bdadc2780239f7460b94b263593cf5b0288a4 size 25 from peer 176.221.43.130:33323 node.cpp:1651 2015-08-21T03:09:24 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 0 items advertised to peer (3 left), and 1 advertised to us (113 left) peer_connection.cpp:479 2015-08-21T03:09:24 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 176.221.43.130:33323 node.cpp:2613 2015-08-21T03:09:24 p2p:message read_loop on_item_ids_inventor ] adding item bb51709a4c2a3c64bdf260e28908c05b1f849a7b from inventory message to our list of items to fetch node.cpp:2647 2015-08-21T03:09:24 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:1104 2015-08-21T03:09:24 p2p:fetch_items_loop fetch_items_loop ] requesting item bb51709a4c2a3c64bdf260e28908c05b1f849a7b from peer 176.221.43.130:33323 node.cpp:1123 2015-08-21T03:09:24 p2p:fetch_items_loop send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 176.221.43.130:33323 peer_connection.cpp:365 2015-08-21T03:09:24 p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-21T03:09:24 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-21T03:09:24 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 176.221.43.130:33323 peer_connection.cpp:291 2015-08-21T03:09:24 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 176.221.43.130:33323 peer_connection.cpp:294 2015-08-21T03:09:24 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-21T03:09:24 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-21T03:09:24 p2p:message read_loop on_message ] handling message block_message_type bb51709a4c2a3c64bdf260e28908c05b1f849a7b size 172 from peer 176.221.43.130:33323 node.cpp:1651 2015-08-21T03:09:24 p2p:message read_loop process_block_during ] received a block from peer 176.221.43.130:33323, passing it to client node.cpp:3087 2015-08-21T03:09:24 p2p:message read_loop process_block_during ] Successfully pushed block 32017 (id:00007d11685f540f83aab26800d7afd880cd154d) node.cpp:3109 2015-08-21T03:09:24 p2p:message read_loop process_block_during ] client validated the block, advertising it to other peers node.cpp:3133 2015-08-21T03:09:24 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 0 items advertised to peer (3 left), and 0 advertised to us (114 left) peer_connection.cpp:479 2015-08-21T03:09:24 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 1 items advertised to peer (110 left), and 0 advertised to us (6 left) peer_connection.cpp:479 2015-08-21T03:09:24 p2p:advertise_inventory_loop advertise_inventory_ ] beginning an iteration of advertise inventory node.cpp:1175 2015-08-21T03:09:24 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: false node.cpp:1188 2015-08-21T03:09:24 p2p:advertise_inventory_loop advertise_inventory_ ] inventory_to_advertise: [{"item_type":1001,"item_hash":"bb51709a4c2a3c64bdf260e28908c05b1f849a7b"}] node.cpp:1196 2015-08-21T03:09:24 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_advertised_to_peer.find(item_to_advertise): {"item":{"item_type":3624261264,"item_hash":"ff7f00002b00000000000000ffffffffff7f0000"},"timestamp":"2023-11-27T10:29:02"} node.cpp:1200 2015-08-21T03:09:24 p2p:advertise_inventory_loop advertise_inventory_ ] advertising 0 new item(s) of 0 type(s) to peer 176.221.43.130:33323 node.cpp:1218 2015-08-21T03:09:24 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 0 items advertised to peer (3 left), and 0 advertised to us (114 left) peer_connection.cpp:479 2015-08-21T03:09:24 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: false node.cpp:1188 2015-08-21T03:09:24 p2p:advertise_inventory_loop advertise_inventory_ ] inventory_to_advertise: [{"item_type":1001,"item_hash":"bb51709a4c2a3c64bdf260e28908c05b1f849a7b"}] node.cpp:1196 2015-08-21T03:09:24 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_advertised_to_peer.find(item_to_advertise): {"item":{"item_type":3623881952,"item_hash":"ff7f0000000000000000000068a305d8ff7f0000"},"timestamp":"1948-09-25T19:23:04"} node.cpp:1200 2015-08-21T03:09:24 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_peer_advertised_to_us.find(item_to_advertise): {"item":{"item_type":3624248128,"item_hash":"ff7f00002c00000000000000ffffffffcccccccc"},"timestamp":"2023-12-08T00:51:00"} node.cpp:1202 2015-08-21T03:09:24 p2p:advertise_inventory_loop advertise_inventory_ ] advertising item bb51709a4c2a3c64bdf260e28908c05b1f849a7b to peer 45.55.6.216:1776 node.cpp:1212 2015-08-21T03:09:24 p2p:advertise_inventory_loop advertise_inventory_ ] advertising 1 new item(s) of 1 type(s) to peer 45.55.6.216:1776 node.cpp:1218 2015-08-21T03:09:24 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (111 left), and 0 advertised to us (6 left) peer_connection.cpp:479 2015-08-21T03:09:24 p2p:advertise_inventory_loop send_message ] peer_connection::send_message() enqueueing message of type 5001 for peer 45.55.6.216:1776 peer_connection.cpp:365 2015-08-21T03:09:24 p2p:advertise_inventory_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-21T03:09:24 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104 2015-08-21T03:09:24 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-21T03:09:24 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5001 for peer 45.55.6.216:1776 peer_connection.cpp:291 2015-08-21T03:09:24 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 45.55.6.216:1776 peer_connection.cpp:294 2015-08-21T03:09:24 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-21T03:09:24 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-21T03:09:24 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 9f6bdadc2780239f7460b94b263593cf5b0288a4 size 25 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-21T03:09:24 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (111 left), and 0 advertised to us (6 left) peer_connection.cpp:479 2015-08-21T03:09:24 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-21T03:09:31 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 4db8f599f0ef6e3741c3638775acdaab5dcc63e8 size 25 from peer 176.221.43.130:33323 node.cpp:1651 2015-08-21T03:09:31 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 0 items advertised to peer (3 left), and 7 advertised to us (107 left) peer_connection.cpp:479 2015-08-21T03:09:31 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 176.221.43.130:33323 node.cpp:2613 2015-08-21T03:09:31 p2p:message read_loop on_item_ids_inventor ] adding item 1d6ff20ecc62c13c5a2dbb02cfbb0a8fee17c365 from inventory message to our list of items to fetch node.cpp:2647 2015-08-21T03:09:31 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:1104 2015-08-21T03:09:31 p2p:fetch_items_loop fetch_items_loop ] requesting item 1d6ff20ecc62c13c5a2dbb02cfbb0a8fee17c365 from peer 176.221.43.130:33323 node.cpp:1123 2015-08-21T03:09:31 p2p:fetch_items_loop send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 176.221.43.130:33323 peer_connection.cpp:365 2015-08-21T03:09:31 p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-21T03:09:31 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-21T03:09:31 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 176.221.43.130:33323 peer_connection.cpp:291 2015-08-21T03:09:31 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 176.221.43.130:33323 peer_connection.cpp:294 2015-08-21T03:09:31 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-21T03:09:31 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 2dabf66b081dc63e56840276d7d655a5bb1fec58 size 25 from peer 176.221.43.130:33323 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 0 items advertised to peer (3 left), and 1 advertised to us (107 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 176.221.43.130:33323 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] adding item 5867c371be07002a8b1b42d3336a63ceb1f7cbef from inventory message to our list of items to fetch node.cpp:2647 2015-08-21T03:09:32 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:1104 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type d32fb20dbd657a2ea730340ef8db9ef3c79bc93c size 25 from peer 176.221.43.130:33323 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 0 items advertised to peer (3 left), and 0 advertised to us (108 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 176.221.43.130:33323 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] adding item a94d298df6526af3e66da0322376b6ed2f951825 from inventory message to our list of items to fetch node.cpp:2647 2015-08-21T03:09:32 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (2 items to fetch) node.cpp:1104 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type c3fec5988ab78731328eca88332078a7b3b15284 size 25 from peer 176.221.43.130:33323 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 0 items advertised to peer (3 left), and 0 advertised to us (109 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 176.221.43.130:33323 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] adding item 9f6a0e098495a36f16f34c8ab857c831d1b2e29e from inventory message to our list of items to fetch node.cpp:2647 2015-08-21T03:09:32 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (3 items to fetch) node.cpp:1104 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type a7534938c031313fd745885500d2864d0f6a359b size 25 from peer 176.221.43.130:33323 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 0 items advertised to peer (3 left), and 0 advertised to us (110 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 176.221.43.130:33323 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] adding item 01e5235516c64efd7aab3195677de74e59a4d96c from inventory message to our list of items to fetch node.cpp:2647 2015-08-21T03:09:32 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (4 items to fetch) node.cpp:1104 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 91cd39de6b1f58353fbdc1ae5f0270bc3fd5865f size 25 from peer 176.221.43.130:33323 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 0 items advertised to peer (3 left), and 0 advertised to us (111 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 176.221.43.130:33323 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] adding item 19007e79d3b857e7e4efeb2cd98c7c8977062504 from inventory message to our list of items to fetch node.cpp:2647 2015-08-21T03:09:32 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (5 items to fetch) node.cpp:1104 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 77292c73fc07a4802219190f28442c875b2ffd85 size 25 from peer 176.221.43.130:33323 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 0 items advertised to peer (3 left), and 0 advertised to us (112 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 176.221.43.130:33323 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] adding item d56255b170661695aaf2604e78d023939ee918c7 from inventory message to our list of items to fetch node.cpp:2647 2015-08-21T03:09:32 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (6 items to fetch) node.cpp:1104 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_not_available_message_type 03f536044511199afe37d02786d0a39fac0a83b6 size 24 from peer 176.221.43.130:33323 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop on_item_not_availabl ] Peer doesn't have the requested item. node.cpp:2581 2015-08-21T03:09:32 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (6 items to fetch) node.cpp:1104 2015-08-21T03:09:32 p2p:fetch_items_loop fetch_items_loop ] requesting item 5867c371be07002a8b1b42d3336a63ceb1f7cbef from peer 176.221.43.130:33323 node.cpp:1123 2015-08-21T03:09:32 p2p:fetch_items_loop send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 176.221.43.130:33323 peer_connection.cpp:365 2015-08-21T03:09:32 p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-21T03:09:32 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-21T03:09:32 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 176.221.43.130:33323 peer_connection.cpp:291 2015-08-21T03:09:32 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 176.221.43.130:33323 peer_connection.cpp:294 2015-08-21T03:09:32 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-21T03:09:32 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type bcd547d726b0f393e6aee051278cb990247141bd size 25 from peer 176.221.43.130:33323 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 176.221.43.130:33323: removing 0 items advertised to peer (3 left), and 0 advertised to us (112 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 176.221.43.130:33323 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] adding item 890e4ce407f50879d21b4ecd700cc4d3e5cc58d6 from inventory message to our list of items to fetch node.cpp:2647 2015-08-21T03:09:32 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (6 items to fetch) node.cpp:1104 2015-08-21T03:09:32 p2p:p2p_network_connect_loop p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:881 2015-08-21T03:09:32 p2p:p2p_network_connect_loop display_current_conn ] Currently have 2 of [20/200] connections node.cpp:1625 2015-08-21T03:09:32 p2p:p2p_network_connect_loop display_current_conn ] my id is 267adcc6efc0ca128ac187fd47665b93e6eac6ffbcf6a14f1a2eb5c658e3348708 node.cpp:1626 2015-08-21T03:09:32 p2p:p2p_network_connect_loop display_current_conn ] active: 176.221.43.130:33323 with 0a69dc25fca6f9e85284deda98c92a51bc0f659adfa976e017ebf61620ab32d2c1 [outbound] node.cpp:1633 2015-08-21T03:09:32 p2p:p2p_network_connect_loop display_current_conn ] active: 45.55.6.216:1776 with a7cb5e17e25898bb1bef2feb31a341c4c22bc489e700dfbe41f0933b9e145261a1 [outbound] node.cpp:1633 2015-08-21T03:09:32 p2p:p2p_network_connect_loop display_current_conn ] Currently have 2 of [20/200] connections node.cpp:1625 2015-08-21T03:09:32 p2p:p2p_network_connect_loop display_current_conn ] my id is 267adcc6efc0ca128ac187fd47665b93e6eac6ffbcf6a14f1a2eb5c658e3348708 node.cpp:1626 2015-08-21T03:09:32 p2p:p2p_network_connect_loop display_current_conn ] active: 176.221.43.130:33323 with 0a69dc25fca6f9e85284deda98c92a51bc0f659adfa976e017ebf61620ab32d2c1 [outbound] node.cpp:1633 2015-08-21T03:09:32 p2p:p2p_network_connect_loop display_current_conn ] active: 45.55.6.216:1776 with a7cb5e17e25898bb1bef2feb31a341c4c22bc489e700dfbe41f0933b9e145261a1 [outbound] node.cpp:1633 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 4db8f599f0ef6e3741c3638775acdaab5dcc63e8 size 25 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 8 items advertised to peer (103 left), and 0 advertised to us (6 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] adding item 1d6ff20ecc62c13c5a2dbb02cfbb0a8fee17c365 from inventory message to our list of items to fetch node.cpp:2647 2015-08-21T03:09:32 p2p:fetch_items_loop fetch_items_loop ] beginning an iteration of fetch items (7 items to fetch) node.cpp:1104 2015-08-21T03:09:32 p2p:fetch_items_loop fetch_items_loop ] requesting item 1d6ff20ecc62c13c5a2dbb02cfbb0a8fee17c365 from peer 45.55.6.216:1776 node.cpp:1123 2015-08-21T03:09:32 p2p:fetch_items_loop send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:365 2015-08-21T03:09:32 p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354 2015-08-21T03:09:32 p2p:send_queued_messages_task counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279 2015-08-21T03:09:32 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:291 2015-08-21T03:09:32 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 45.55.6.216:1776 peer_connection.cpp:294 2015-08-21T03:09:32 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326 2015-08-21T03:09:32 p2p:send_queued_messages_task ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 2dabf66b081dc63e56840276d7d655a5bb1fec58 size 25 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (103 left), and 0 advertised to us (7 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type d32fb20dbd657a2ea730340ef8db9ef3c79bc93c size 25 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (103 left), and 0 advertised to us (8 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type c3fec5988ab78731328eca88332078a7b3b15284 size 25 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (103 left), and 0 advertised to us (9 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type a7534938c031313fd745885500d2864d0f6a359b size 25 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (103 left), and 0 advertised to us (10 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 91cd39de6b1f58353fbdc1ae5f0270bc3fd5865f size 25 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (103 left), and 0 advertised to us (11 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 77292c73fc07a4802219190f28442c875b2ffd85 size 25 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (103 left), and 0 advertised to us (12 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-21T03:09:32 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type bcd547d726b0f393e6aee051278cb990247141bd size 25 from peer 45.55.6.216:1776 node.cpp:1651 2015-08-21T03:09:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (103 left), and 0 advertised to us (13 left) peer_connection.cpp:479 2015-08-21T03:09:32 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-21T03:09:33 p2p:message read_loop on_message ] handling message item_not_available_message_type 03f536044511199afe37d02786d0a39fac0a83b6 size 24 from peer 45.55.6.216:1776 node.cpp:1651what happened here
Code: [Select]
2015-08-21T03:09:24 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613 2015-08-21T03:09:31 p2p:message read_loop on_message ] handling message item_ids_inventory_message_type 4db8f599f0ef6e3741c3638775acdaab5dcc63e8 size 25 from peer 176.221.43.130:33323 node.cpp:1651
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 21, 2015, 03:55:52 am: Did the chain ID change or am I on a fork?

test5 is a brand new data directory.

Code: [Select]
./witness_node -d test5 genesis-json /home/james/Downloads/aug-20-test-genesis.json --resync-blockchain --witness-id '"1.6.5250"' --private-key '["GPH7kNZtp64ZR1R4yC2w9bDLFNHkM8L2AFZSj1E", "5Jnwg...JC7Ur"]' -s "104.236.51.238:1776"
Code: [Select]
3270744ms th_a thread.cpp:95 thread ] name:p2p tid:139985686546176 3270851ms ntp ntp.cpp:81 request_now ] sending request to 198.60.22.240:123 3270851ms th_a application.cpp:117 reset_p2p_node ] Adding seed node 104.236.51.238:1776 3270853ms th_a application.cpp:129 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:59551 3270854ms th_a witness.cpp:107 plugin_startup ] WARNING: Unable to find witness 1.6.5250. Postponing initialization until syncing finishes. 3270854ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks. 3270854ms th_a main.cpp:166 main ] Chain ID is b6ff5d956ca601b3682edbc52c5678819a63dd80f5c0fad00a289d1a09c4662e 3270928ms ntp ntp.cpp:147 read_loop ] received ntp reply from 198.60.22.240:123 3270928ms ntp ntp.cpp:161 read_loop ] ntp offset: -7351300, round_trip_delay 77122 3270929ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to -7351300
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on August 21, 2015, 04:04:03 am: Quote from: Riverhead on August 21, 2015, 03:55:52 am

Did the chain ID change or am I on a fork?

test5 is a brand new data directory.

Code: [Select]
./witness_node -d test5 genesis-json /home/james/Downloads/aug-20-test-genesis.json --resync-blockchain --witness-id '"1.6.5250"' --private-key '["GPH7kNZtp64ZR1R4yC2w9bDLFNHkM8L2AFZSj1E", "5Jnwg...JC7Ur"]' -s "104.236.51.238:1776"
Code: [Select]
3270744ms th_a thread.cpp:95 thread ] name:p2p tid:139985686546176 3270851ms ntp ntp.cpp:81 request_now ] sending request to 198.60.22.240:123 3270851ms th_a application.cpp:117 reset_p2p_node ] Adding seed node 104.236.51.238:1776 3270853ms th_a application.cpp:129 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:59551 3270854ms th_a witness.cpp:107 plugin_startup ] WARNING: Unable to find witness 1.6.5250. Postponing initialization until syncing finishes. 3270854ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks. 3270854ms th_a main.cpp:166 main ] Chain ID is b6ff5d956ca601b3682edbc52c5678819a63dd80f5c0fad00a289d1a09c4662e 3270928ms ntp ntp.cpp:147 read_loop ] received ntp reply from 198.60.22.240:123 3270928ms ntp ntp.cpp:161 read_loop ] ntp offset: -7351300, round_trip_delay 77122 3270929ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to -7351300

Chain ID should be "d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083". Try this node as seed: 176.221.43.130:33323
Title: Re: Test Net for Advanced Users
Post by: puppies on August 21, 2015, 04:29:11 am: Quote from: Riverhead on August 21, 2015, 03:55:52 am

Code: [Select]
./witness_node -d test5 genesis-json /home/james/Downloads/aug-20-test-genesis.json --resync-blockchain --witness-id '"1.6.5250"' --private-key '["GPH7kNZtp64ZR1R4yC2w9bDLFNHkM8L2AFZSj1E", "5Jnwg...JC7Ur"]' -s "104.236.51.238:1776"

Also should be
Code: [Select]
./witness_node -d test5 --genesis-json /home/james/Downloads/aug-20-test-genesis.json --resync-blockchain --witness-id '"1.6.5250"' --private-key '["GPH7kNZtp64ZR1R4yC2w9bDLFNHkM8L2AFZSj1E", "5Jnwg...JC7Ur"]' -s "104.236.51.238:1776"
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 04:43:55 am: Quote from: Riverhead on August 21, 2015, 03:55:52 am

Did the chain ID change or am I on a fork?

test5 is a brand new data directory.

Code: [Select]
./witness_node -d test5 genesis-json /home/james/Downloads/aug-20-test-genesis.json --resync-blockchain --witness-id '"1.6.5250"' --private-key '["GPH7kNZtp64ZR1R4yC2w9bDLFNHkM8L2AFZSj1E", "5Jnwg...JC7Ur"]' -s "104.236.51.238:1776"
./witness_node -d test5 --genesis-json ...
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 05:23:13 am: Back online now.
Title: Re: Test Net for Advanced Users
Post by: brainbug on August 21, 2015, 06:01:14 am: Quote from: abit on August 20, 2015, 11:15:58 am
Quote from: brainbug on August 20, 2015, 11:03:42 am
General question (since I could not find this elsewhere):

Is there a genuine place from where I can download "an up-to-date" BitShares blockchain? Setting up a new client is easy, but syncing it takes long and sometimes does not work such that the whole process needs to be repeated again and again (my slow little pc, c847/8gb, often has problems here and it takes days to re-sync/re-download the chain)... As such, it would be awesome to have an official and always "up-to-date" download link for the BitShares blockchain.

That said, my question is if such a download link is already there (and I could not find it), or would it be a great addition to the BitShare's homepage?

EDIT: Also 8gb ram seem sometimes not enough for a re-sync (using v0.9.2)... is that true? Did some one else make similar experiences?
I don't know if there is a download link for the blockchain.
8GB RAM is more than enough. If you're using Windows or Linux, try run 'bitshares_client' rather than GUI for initial syncing. After in-sync you can press ctrl+d to close it then open GUI.
Wish you good luck.

Thanks :-) It turned out that 8gb are not enough (using the Win7 v0.9.2 GUI-client) when syncing from scratch. So, I downloaded a blockchain found on the web (1.6gb compressed; July 2015). Using that "bootstrap", things worked flawlessly, consuming 4gb ram at max.
Title: Re: Test Net for Advanced Users
Post by: cryptosile on August 21, 2015, 06:20:58 am: my witness is now producing blocks:
Code: [Select]
get_witness everydaycrypto { "id": "1.6.5251", "witness_account": "1.2.27645", "vote_id": "1:5468", "url": "https://everydaycrypto.com" .... get_dynamic_global_properties { "id": "2.1.0", "random": "4fc3d0459cf6eb73a00a0a9f9128b83a46a7dfc3", "head_block_number": 42483, ...
Here are the commands I used to run this using docker... (you all are probably tired of the docker thing by now... I'm not sure it's even that useful, pretty much just a way to distribute binaries... but I've come this far and can't go back now!)

Code: [Select]
cd mkdir test1 cd test1 wget https://github.com/cryptonomex/graphene/releases/download/test1/aug-20-test-genesis.json cd .. sudo docker run --net=host -it -d -v ~/test1:/test1 sile16/graphene-witness:test1 -d test1 --genesis-json /test1/aug-20-test-genesis.json -s "176.221.43.1:33323" --rpc-endpoint "0.0.0.0:8090" sudo docker run --net=host -it --rm sile16/graphene-cli:test1 --chain-id d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083 ###In Graphene CLI >>> set_password <pass> >>> unlock <pass> >>> import_key everydaycrypto <owner wif key> >>> import_balance everydaycrypto [<balance wif key>] true >>> upgrade_account everydaycrypto true >>> create_witness everydaycrypto "https://everydaycrypto.com" true >>> vote_for_witness everydaycrypto everydaycrypto true true >>> dump_private_keys #Kill witness the nice way via a control C, docker kill container ID would work too but blows away graphene DB #get container IDs docker ps docker attach aefe50505f89 ^C #just docker kill the cli container docker kill 3a8cbffabc5d nano test1/config.ini #set witness-id and private-keys items sudo docker run --net=host -it -d -v ~/test1:/test1 sile16/graphene-witness:test1 -d test1 --genesis-json /test1/aug-20-test-genesis.json -s "104.236.51.238:1776" --rpc-endpoint "0.0.0.0:8090" -s "45.55.6.216:1776"
Title: Re: Test Net for Advanced Users
Post by: betax on August 21, 2015, 07:00:05 am: Docker is great thanks, but at the moment not for me as I might want to fiddle with the code :), But if I spin up more vms... that will be the way !
Title: Re: Test Net for Advanced Users
Post by: clayop on August 21, 2015, 07:29:56 am: I found some problems related to spam transactions.

1) In a normal node without block production, when spam transactions occurred (in my case 100 txs in few seconds), block sync stops for about 3 minutes.

2) In a witness node with block production, spam transactions caused witness node crash. In this case, I have to resync my witness node.

3) Only part of spam transactions are accepted. I sent a hundred transactions but only 9 out of 100 are shown.
Title: Re: Test Net for Advanced Users
Post by: betax on August 21, 2015, 07:33:02 am: Quote from: clayop on August 21, 2015, 07:29:56 am
I found some problems related to spam transactions.

1) In a normal node without block production, when spam transactions occurred (in my case 100 txs in few seconds), block sync stops for about 3 minutes.

2) In a witness node with block production, spam transactions caused witness node crash. In this case, I have to resync my witness node.

3) Only part of spam transactions are accepted. I sent a hundred transactions but only 9 out of 100 are shown.

Im rebuilding, was travelling yesterday, once done I will do the same and confirm on my side.
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 08:18:13 am: My node crashed while generating a block. >:(
No interesting info found in logs.
Will launch in gdb this time.
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 08:29:51 am: Hey Everyone,

Just got back "Online". 10 AM in the morning. Seems most of you are in the western hemisphere....
However, I also don't see original seed-node "104.236.51.238:1776" anymore (but I think it already left when i went to bed), my node on port 33323 doesn't seem to have major issues (at least not like the last times) and is now running ~10h nonstop. Here's some error grepped from my p2p log rigth now:

Code: [Select]
2015-08-21T08:22:23 p2p:send_queued_messages_task send_queued_messages ] Error sending message: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":37,"method":"operator()","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:22:23"},"format":"${message} ","data":{"message":"Bad file descriptor"}},{"context":{"level":"warn","file":"stcp_socket.cpp","line":153,"method":"writesome","hostname":"","thread_name":"p2p","timestamp":"2015-08-21T08:22:23"},"format":"","data":{"len":16}},{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":264,"method":"send_message","hostname":"","thread_name":"p2p","timestamp":"2015-08-21T08:22:23"},"format":"unable to send message","data":{}}]}. Closing connection. peer_connection.cpp:303

and then

Code: [Select]
2015-08-21T08:26:38 p2p:connect_to_task connect_to ] fatal: error connecting to peer 104.156.226.183:58884: 0 exception: unspecified asio asio.cpp:59 error_handler peer_connection.cpp:255 2015-08-21T08:26:38 p2p:delayed_peer_deletion_task destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:38"},"format":"${message} ","data":{"message":"Operation canceled"}}]} peer_connection.cpp:158 2015-08-21T08:26:42 p2p:connect_to_task connect_to ] fatal: error connecting to peer 104.236.255.53:36548: 0 exception: unspecified asio asio.cpp:59 error_handler peer_connection.cpp:255 2015-08-21T08:26:42 p2p:delayed_peer_deletion_task destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:158 2015-08-21T08:26:42 p2p:connect_to_task connect_to ] fatal: error connecting to peer 104.236.51.238:1776: 0 exception: unspecified asio asio.cpp:59 error_handler peer_connection.cpp:255 2015-08-21T08:26:42 p2p:delayed_peer_deletion_task destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:158 2015-08-21T08:26:42 p2p:connect_to_task connect_to ] fatal: error connecting to peer 104.131.205.149:44815: 0 exception: unspecified asio asio.cpp:59 error_handler peer_connection.cpp:255 2015-08-21T08:26:42 p2p:delayed_peer_deletion_task destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:158
~~So it seems it is complaining about some peer-nodes not online anymore...~~
To be more precise these nodes seem to online and offline. I can see them in netstat but they seem to have changed the port because they have been restarted without a fixed p2p-prt in the config? Maybe it's a good idea to fix that port or not? Is the networking part supoosed to sort this out or is it even for a purpose that the ports change everytime you restart your node?
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 08:40:17 am: Quote from: mudshark79 on August 21, 2015, 08:29:51 am
Hey Everyone,

Just got back "Online". 10 AM in the morning. Seems most of you are in the western hemisphere....
However, I also don't see original seed-node "104.236.51.238:1776" anymore (but I think it already left when i went to bed), my node on port 33323 doesn't seem to have major issues (at least not like the last times) and is now running ~10h nonstop. Here's some error grepped from my p2p log rigth now:

Code: [Select]
2015-08-21T08:22:23 p2p:send_queued_messages_task send_queued_messages ] Error sending message: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":37,"method":"operator()","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:22:23"},"format":"${message} ","data":{"message":"Bad file descriptor"}},{"context":{"level":"warn","file":"stcp_socket.cpp","line":153,"method":"writesome","hostname":"","thread_name":"p2p","timestamp":"2015-08-21T08:22:23"},"format":"","data":{"len":16}},{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":264,"method":"send_message","hostname":"","thread_name":"p2p","timestamp":"2015-08-21T08:22:23"},"format":"unable to send message","data":{}}]}. Closing connection. peer_connection.cpp:303

and then

Code: [Select]
2015-08-21T08:26:38 p2p:connect_to_task connect_to ] fatal: error connecting to peer 104.156.226.183:58884: 0 exception: unspecified asio asio.cpp:59 error_handler peer_connection.cpp:255 2015-08-21T08:26:38 p2p:delayed_peer_deletion_task destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:38"},"format":"${message} ","data":{"message":"Operation canceled"}}]} peer_connection.cpp:158 2015-08-21T08:26:42 p2p:connect_to_task connect_to ] fatal: error connecting to peer 104.236.255.53:36548: 0 exception: unspecified asio asio.cpp:59 error_handler peer_connection.cpp:255 2015-08-21T08:26:42 p2p:delayed_peer_deletion_task destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:158 2015-08-21T08:26:42 p2p:connect_to_task connect_to ] fatal: error connecting to peer 104.236.51.238:1776: 0 exception: unspecified asio asio.cpp:59 error_handler peer_connection.cpp:255 2015-08-21T08:26:42 p2p:delayed_peer_deletion_task destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:158 2015-08-21T08:26:42 p2p:connect_to_task connect_to ] fatal: error connecting to peer 104.131.205.149:44815: 0 exception: unspecified asio asio.cpp:59 error_handler peer_connection.cpp:255 2015-08-21T08:26:42 p2p:delayed_peer_deletion_task destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:158
~~So it seems it is complaining about some peer-nodes not online anymore...~~
To be more precise these nodes seem to online and offline. I can see them in netstat but they seem to have changed the port because they have been restarted without a fixed p2p-prt in the config? Maybe it's a good idea to fix that port or not? Is the networking part supoosed to sort this out or is it even for a purpose that the ports change everytime you restart your node?
Hi, is the chain still alive? I'm stuck at about a hour ago and unable to connect right now.
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 08:42:02 am: Quote from: abit on August 21, 2015, 08:18:13 am
My node crashed while generating a block. >:(
No interesting info found in logs.
Will launch in gdb this time.

Did you have
-DCMAKE_BUILD_TYPE=Debug
while building? Mine is commenting on everything quite detailed about everything in the console....
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 08:44:03 am: Quote from: abit on August 21, 2015, 08:40:17 am
Quote from: mudshark79 on August 21, 2015, 08:29:51 am
Hey Everyone,

Just got back "Online". 10 AM in the morning. Seems most of you are in the western hemisphere....
However, I also don't see original seed-node "104.236.51.238:1776" anymore (but I think it already left when i went to bed), my node on port 33323 doesn't seem to have major issues (at least not like the last times) and is now running ~10h nonstop. Here's some error grepped from my p2p log rigth now:

Code: [Select]
2015-08-21T08:22:23 p2p:send_queued_messages_task send_queued_messages ] Error sending message: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":37,"method":"operator()","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:22:23"},"format":"${message} ","data":{"message":"Bad file descriptor"}},{"context":{"level":"warn","file":"stcp_socket.cpp","line":153,"method":"writesome","hostname":"","thread_name":"p2p","timestamp":"2015-08-21T08:22:23"},"format":"","data":{"len":16}},{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":264,"method":"send_message","hostname":"","thread_name":"p2p","timestamp":"2015-08-21T08:22:23"},"format":"unable to send message","data":{}}]}. Closing connection. peer_connection.cpp:303

and then

Code: [Select]
2015-08-21T08:26:38 p2p:connect_to_task connect_to ] fatal: error connecting to peer 104.156.226.183:58884: 0 exception: unspecified asio asio.cpp:59 error_handler peer_connection.cpp:255 2015-08-21T08:26:38 p2p:delayed_peer_deletion_task destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:38"},"format":"${message} ","data":{"message":"Operation canceled"}}]} peer_connection.cpp:158 2015-08-21T08:26:42 p2p:connect_to_task connect_to ] fatal: error connecting to peer 104.236.255.53:36548: 0 exception: unspecified asio asio.cpp:59 error_handler peer_connection.cpp:255 2015-08-21T08:26:42 p2p:delayed_peer_deletion_task destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:158 2015-08-21T08:26:42 p2p:connect_to_task connect_to ] fatal: error connecting to peer 104.236.51.238:1776: 0 exception: unspecified asio asio.cpp:59 error_handler peer_connection.cpp:255 2015-08-21T08:26:42 p2p:delayed_peer_deletion_task destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:158 2015-08-21T08:26:42 p2p:connect_to_task connect_to ] fatal: error connecting to peer 104.131.205.149:44815: 0 exception: unspecified asio asio.cpp:59 error_handler peer_connection.cpp:255 2015-08-21T08:26:42 p2p:delayed_peer_deletion_task destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:158
~~So it seems it is complaining about some peer-nodes not online anymore...~~
To be more precise these nodes seem to online and offline. I can see them in netstat but they seem to have changed the port because they have been restarted without a fixed p2p-prt in the config? Maybe it's a good idea to fix that port or not? Is the networking part supoosed to sort this out or is it even for a purpose that the ports change everytime you restart your node?
Hi, is the chain still alive? I'm stuck at about a hour ago and unable to connect right now.

Yes it's alive nonstop. Which is your node? Try 176.221.43.130:33323 as a seed.
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 08:45:31 am: Quote from: mudshark79 on August 21, 2015, 08:44:03 am

Yes it's alive nonstop. Which is your node? I see some coming and going in netstat, maybe your's is somehow blacklisted or so...
Mine is 114.92.254.159:62015 or other ports.
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 08:46:54 am: Quote from: abit on August 21, 2015, 08:45:31 am
Quote from: mudshark79 on August 21, 2015, 08:44:03 am

Yes it's alive nonstop. Which is your node? I see some coming and going in netstat, maybe your's is somehow blacklisted or so...
Mine is 114.92.254.159:62015 or other ports.
Try 176.221.43.130:33323 as seed... if not already doing so. Will have a look if I see reference to your ip somewhere..
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 08:48:38 am: Quote from: mudshark79 on August 21, 2015, 08:42:02 am
Quote from: abit on August 21, 2015, 08:18:13 am
My node crashed while generating a block. >:(
No interesting info found in logs.
Will launch in gdb this time.

Did you have
-DCMAKE_BUILD_TYPE=Debug
while building? Mine is commenting on everything quite detailed about everything in the console....
Yes I think I have.
Code: [Select]
cmake -DBOOST_ROOT="/app/boost_1_57_0.bin" -DCMAKE_BUILD_TYPE=Debug .But the 'crash' last time looks like a clean exit. No info at all.
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 08:50:25 am: Quote from: mudshark79 on August 21, 2015, 08:46:54 am
Quote from: abit on August 21, 2015, 08:45:31 am
Quote from: mudshark79 on August 21, 2015, 08:44:03 am

Yes it's alive nonstop. Which is your node? I see some coming and going in netstat, maybe your's is somehow blacklisted or so...
Mine is 114.92.254.159:62015 or other ports.
Try 176.221.43.130:33323 as seed... if not already doing so. Will have a look if I see reference to your ip somewhere..
Already set it as seed. Maybe it is just because of slow/unstable connection? The node is in China.
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 08:51:39 am: Quote from: mudshark79 on August 21, 2015, 08:46:54 am
Quote from: abit on August 21, 2015, 08:45:31 am
Quote from: mudshark79 on August 21, 2015, 08:44:03 am

Yes it's alive nonstop. Which is your node? I see some coming and going in netstat, maybe your's is somehow blacklisted or so...
Mine is 114.92.254.159:62015 or other ports.
Try 176.221.43.130:33323 as seed... if not already doing so. Will have a look if I see reference to your ip somewhere..

I see things like this in reference to your ip:
Code: [Select]
2015-08-21T08:46:31 p2p:message read_loop forward_firewall_che ] forwarding firewall check for node 114.92.254.159:63542 to peer 176.9.234.167:58896 node.cpp:3301 2015-08-21T08:46:32 p2p:message read_loop on_check_firewall_re ] Peer 176.9.234.167:58896 reports firewall check status unable_to_connect for 114.92.254.159:63542 node.cpp:3394 2015-08-21T08:46:32 p2p:message read_loop send_message ] peer_connection::send_message() enqueueing message of type 5015 for peer 114.92.254.159:63542 peer_connection.cpp:365 2015-08-21T08:46:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:32 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:32 p2p:p2p_network_connect_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:32 p2p:p2p_network_connect_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:32 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:33 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:33 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:33 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:33 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:33 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:33 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:33 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:33 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:34 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:34 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:36 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:36 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:37 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:37 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:38 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:38 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:39 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:39 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:40 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:40 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:41 p2p:message read_loop on_connection_closed ] Remote peer 114.92.254.159:63542 closed their connection to us node.cpp:2724 2015-08-21T08:46:41 p2p:message read_loop schedule_peer_for_de ] scheduling peer for deletion: 114.92.254.159:63542 (this will not block)
Those line with firewall sounds like there is some potentail for being blacklisted. It seems to use a third node to check wether your port is open and reachable and it seems you don't pass this test ? On the other hand it clearly states you are not blocked.

Do you know it is on purpose that the port changes everytime one fires up the node? Have you already tried moving to fixed port?
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 09:03:02 am: Quote from: mudshark79 on August 21, 2015, 08:51:39 am
Quote from: mudshark79 on August 21, 2015, 08:46:54 am
Quote from: abit on August 21, 2015, 08:45:31 am
Quote from: mudshark79 on August 21, 2015, 08:44:03 am

Yes it's alive nonstop. Which is your node? I see some coming and going in netstat, maybe your's is somehow blacklisted or so...
Mine is 114.92.254.159:62015 or other ports.
Try 176.221.43.130:33323 as seed... if not already doing so. Will have a look if I see reference to your ip somewhere..

I see things like this in reference to your ip:
Code: [Select]
2015-08-21T08:46:31 p2p:message read_loop forward_firewall_che ] forwarding firewall check for node 114.92.254.159:63542 to peer 176.9.234.167:58896 node.cpp:3301 2015-08-21T08:46:32 p2p:message read_loop on_check_firewall_re ] Peer 176.9.234.167:58896 reports firewall check status unable_to_connect for 114.92.254.159:63542 node.cpp:3394 2015-08-21T08:46:32 p2p:message read_loop send_message ] peer_connection::send_message() enqueueing message of type 5015 for peer 114.92.254.159:63542 peer_connection.cpp:365 2015-08-21T08:46:32 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:32 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:32 p2p:p2p_network_connect_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:32 p2p:p2p_network_connect_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:32 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:33 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:33 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:33 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:33 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:33 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:33 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:33 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:33 p2p:message read_loop display_current_conn ] active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9 [inbound] node.cpp:1633 2015-08-21T08:46:34 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:34 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:36 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:36 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:37 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:37 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:38 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:38 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:39 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:39 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:40 p2p:message read_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:40 p2p:advertise_inventory_loop clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left) peer_connection.cpp:479 2015-08-21T08:46:41 p2p:message read_loop on_connection_closed ] Remote peer 114.92.254.159:63542 closed their connection to us node.cpp:2724 2015-08-21T08:46:41 p2p:message read_loop schedule_peer_for_de ] scheduling peer for deletion: 114.92.254.159:63542 (this will not block)
Those line with firewall sounds like there is some potentail for being blacklisted. ON the other hand it clearly states you are not blocked.

Do you know it is on purpose that the port changes everytime one fires up the node? Have you already tried moving to fixed port?
I have two nodes running, both have fixed p2p port, one is 62015 and the other is 60002.
Nodes might have been introducing correct p2p-ports to other peers for inbound connection, but may use other ports for outbound connection.

//Edit: I enabled NAT for 62015 but not for 60002. That's why some firewall tests failed.
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 09:17:26 am: Code: [Select]
2015-08-21T09:07:54 p2p:p2p_network_connect_loop display_current_conn ] my id is 2a9dd11186ee39434fc36139417a1a83ab671f79cc9a3d112f6c49f8302ccf02a1 node.cpp:1626 2015-08-21T09:07:54 p2p:p2p_network_connect_loop display_current_conn ] active: 176.221.43.130:33323 with 0a69dc25fca6f9e85284deda98c92a51bc0f659adfa976e017ebf61620ab32d2c1 [outbound] node.cpp:1633 ... 2015-08-21T09:07:57 p2p:message read_loop on_message ] handling message current_time_reply_message_type 6d669ff6f384895b812201eb0187f850f0bd8224 size 24 from peer 176.221.43.130:33323 node.cpp:1651 ... 2015-08-21T09:08:00 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Disconnecting peer 176.221.43.130:33323 because they didn't respond to my request for sync item ids after 0000000000000000000000000000000000000000 node.cpp:1317
Code: [Select]
2015-08-21T09:08:04 p2p:p2p_network_connect_loop display_current_conn ] handshaking: 176.221.43.130:33323 with 000000000000000000000000000000000000000000000000000000000000000000 [unknown] node.cpp:1640 2015-08-21T09:08:04 p2p:connect_to_task connect_to ] fatal: error connecting to peer 176.221.43.130:33323: 0 exception: unspecified Cannot assign requested address {"message":"Cannot assign requested address"} asio asio.cpp:59 error_handler peer_connection.cpp:255
Title: Re: Test Net for Advanced Users
Post by: alt on August 21, 2015, 09:38:13 am: +5%
good job abit, add oil
Quote from: abit on August 21, 2015, 08:18:13 am
My node crashed while generating a block. >:(
No interesting info found in logs.
Will launch in gdb this time.
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 09:53:45 am: Quote from: abit on August 21, 2015, 09:17:26 am
Code: [Select]
2015-08-21T09:07:54 p2p:p2p_network_connect_loop display_current_conn ] my id is 2a9dd11186ee39434fc36139417a1a83ab671f79cc9a3d112f6c49f8302ccf02a1 node.cpp:1626 2015-08-21T09:07:54 p2p:p2p_network_connect_loop display_current_conn ] active: 176.221.43.130:33323 with 0a69dc25fca6f9e85284deda98c92a51bc0f659adfa976e017ebf61620ab32d2c1 [outbound] node.cpp:1633 ... 2015-08-21T09:07:57 p2p:message read_loop on_message ] handling message current_time_reply_message_type 6d669ff6f384895b812201eb0187f850f0bd8224 size 24 from peer 176.221.43.130:33323 node.cpp:1651 ... 2015-08-21T09:08:00 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Disconnecting peer 176.221.43.130:33323 because they didn't respond to my request for sync item ids after 0000000000000000000000000000000000000000 node.cpp:1317
Code: [Select]
2015-08-21T09:08:04 p2p:p2p_network_connect_loop display_current_conn ] handshaking: 176.221.43.130:33323 with 000000000000000000000000000000000000000000000000000000000000000000 [unknown] node.cpp:1640 2015-08-21T09:08:04 p2p:connect_to_task connect_to ] fatal: error connecting to peer 176.221.43.130:33323: 0 exception: unspecified Cannot assign requested address {"message":"Cannot assign requested address"} asio asio.cpp:59 error_handler peer_connection.cpp:255

OK, then I'm clueless. Sorry for confusing things, of course my logs will also reference your outgoing connections. I could look up the timestamp in my p2p-log but unfortunately now I'm already late for work and won't be able to check back until in 5 hours or so...
Title: Re: Test Net for Advanced Users
Post by: ebit on August 21, 2015, 09:58:49 am: +5%
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 21, 2015, 10:20:44 am: I am getting this error after a while:
Code: [Select]
10 assert_exception: Assert Exception item->num < _head->num + MAX_BLOCK_REORDERING: {} th_a fork_database.cpp:70 _push_block {"new_block":{"previous":"0000dc531bf16468f148ff973ac29a377c02b82a","timestamp":"2015-08-21T10:19:59","witness":"1.6.91","next_secret_hash":"10afef88b577df92e7c64e01c6813c57deece7f9","previous_secret":"1313e555ed2c3b697736fcb7daf888d53a347ec7","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f78b7eac30a0c237f3cc16ab454f6e51cce267538df0c462a76f7ce59204f55572da90894b55ff90d488b0341c4a885ac043f855d4405e9f243174c5ed0ad6041","transactions":[]}} th_a db_block.cpp:176 _push_block
Title: Re: Test Net for Advanced Users
Post by: betax on August 21, 2015, 11:48:51 am: Anybody having problems with transactions?

It has taking me lots of attempts to import my balances, and I cannot vote myself. I had but the votes remain 0.
Title: Re: Test Net for Advanced Users
Post by: betax on August 21, 2015, 11:58:36 am: Quote from: betax on August 21, 2015, 11:48:51 am
Anybody having problems with transactions?

It has taking me lots of attempts to import my balances, and I cannot vote myself. I had but the votes remain 0.

you can vote me in to test ;) @ betaxtrade
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on August 21, 2015, 12:40:26 pm: Looks like my node fell off the chain over the night, probably because I never got more than one peer connection consistently.

Code: [Select]
get_dynamic_global_properties { "id": "2.1.0", "random": "e96759cb979ef4620404d4a116c64d4e6b9bd0e8", "head_block_number": 43793, "head_block_id": "0000ab110f83c3641467c59ae7daec0c26e9537d", "time": "2015-08-21T06:35:29", "current_witness": "1.6.72", "next_maintenance_time": "2015-08-21T06:40:00", "witness_budget": 95817007, "accounts_registered_this_interval": 0, "recently_missed_count": 0, "dynamic_flags": 0 }
Code: [Select]
2344668ms p2p node.cpp:4404 dump_node_status ] ----------------- PEER STATUS UPDATE -------------------- 2344668ms p2p node.cpp:4407 dump_node_status ] number of peers: 1 active, 0, 0 closing. attempting to maintain 20 - 200 peers 2344668ms p2p node.cpp:4412 dump_node_status ] active peer 45.55.6.216:1776 peer_is_in_sync_with_us:true we_are_in_sync_with_peer:true 2344668ms p2p node.cpp:4425 dump_node_status ] --------- MEMORY USAGE ------------ 2344668ms p2p node.cpp:4426 dump_node_status ] node._active_sync_requests size: 0 2344669ms p2p node.cpp:4427 dump_node_status ] node._received_sync_items size: 3588 2344669ms p2p node.cpp:4428 dump_node_status ] node._new_received_sync_items size: 0 2344669ms p2p node.cpp:4429 dump_node_status ] node._items_to_fetch size: 0 2344669ms p2p node.cpp:4430 dump_node_status ] node._new_inventory size: 0 2344669ms p2p node.cpp:4431 dump_node_status ] node._message_cache size: 2 2344669ms p2p node.cpp:4434 dump_node_status ] peer 45.55.6.216:1776 2344669ms p2p node.cpp:4435 dump_node_status ] peer.ids_of_items_to_get size: 0 2344669ms p2p node.cpp:4436 dump_node_status ] peer.inventory_peer_advertised_to_us size: 5 2344670ms p2p node.cpp:4437 dump_node_status ] peer.inventory_advertised_to_peer size: 104 2344670ms p2p node.cpp:4438 dump_node_status ] peer.items_requested_from_peer size: 0 2344670ms p2p node.cpp:4439 dump_node_status ] peer.sync_items_requested_from_peer size: 0 2344670ms p2p node.cpp:4441 dump_node_status ] --------- END MEMORY USAGE ------------ 2345990ms p2p node.cpp:1340 terminate_inactive_c ] Sending a keepalive message to peer 45.55.6.216:1776 who hasn't sent us any messages in the last 37 seconds
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 21, 2015, 12:46:33 pm: The seed node crashed in the P2P code due to an assert exception.

https://github.com/cryptonomex/graphene/issues/260

The annoying thing is that this is the same P2P code BitShares is using without issue!

I am rebuilding it in release mode where the assert statement will not be there. Hopefully that will prevent it from crashing.

The blockchain is still alive and well on block #64497 at the time of this writing. It is clear that there is something very wrong with fork handling. We are attempting to work out ways to reproduce this easily because it hasn't happened in our own performance tests.
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on August 21, 2015, 12:51:22 pm: Restarted my node and seem to be back on chain:

Code: [Select]
get_dynamic_global_properties { "id": "2.1.0", "random": "35ece2ef7aac03b97de7c75e54830f57d2c8100c", "head_block_number": 64591, "head_block_id": "0000fc4f697a5655e44786cfea52ab4c6025ea86", "time": "2015-08-21T12:46:15", "current_witness": "1.6.85", "next_maintenance_time": "2015-08-21T12:50:00", "witness_budget": 51808059, "accounts_registered_this_interval": 0, "recently_missed_count": 0, "dynamic_flags": 0 }
Seems like the main issue I'm having is that I'm not getting enough connections. If every node is only getting one or two connections, and running lower performance servers, it could be forking from latency issues. How many connections are other people getting?
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 01:03:23 pm: Quote from: betax on August 21, 2015, 11:58:36 am
Quote from: betax on August 21, 2015, 11:48:51 am
Anybody having problems with transactions?

It has taking me lots of attempts to import my balances, and I cannot vote myself. I had but the votes remain 0.

you can vote me in to test ;) @ betaxtrade
Meanwhile you're in it seems.
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 01:09:44 pm: Quote from: Troglodactyl on August 21, 2015, 12:51:22 pm
Restarted my node and seem to be back on chain:

Code: [Select]
get_dynamic_global_properties { "id": "2.1.0", "random": "35ece2ef7aac03b97de7c75e54830f57d2c8100c", "head_block_number": 64591, "head_block_id": "0000fc4f697a5655e44786cfea52ab4c6025ea86", "time": "2015-08-21T12:46:15", "current_witness": "1.6.85", "next_maintenance_time": "2015-08-21T12:50:00", "witness_budget": 51808059, "accounts_registered_this_interval": 0, "recently_missed_count": 0, "dynamic_flags": 0 }
Seems like the main issue I'm having is that I'm not getting enough connections. If every node is only getting one or two connections, and running lower performance servers, it could be forking from latency issues. How many connections are other people getting?

I've never seen more than 5 or 6 and Abit and me saw issues connecting our nodes for no apparent reason. At the moment this is the connection count:

root@localhost:~/graphene/programs/cli_wallet# netstat -tuapen | grep "witness"
tcp 0 0 176.221.43.130:33323 0.0.0.0:* LISTEN 0 150060 21758/witness_node
tcp 0 0 127.0.0.1:8090 0.0.0.0:* LISTEN 0 150065 21758/witness_node
tcp 0 0 176.221.43.130:33323 176.9.234.167:36713 ESTABLISHED 0 269002 21758/witness_node
tcp 0 0 127.0.0.1:8090 127.0.0.1:50714 ESTABLISHED 0 388908 21758/witness_node
tcp 0 0 176.221.43.130:33323 104.156.226.183:51054 ESTABLISHED 0 204158 21758/witness_node
tcp 0 0 176.221.43.130:33323 70.114.143.108:47834 ESTABLISHED 0 373346 21758/witness_node
tcp 0 1 176.221.43.130:33323 104.156.226.183:49584 SYN_SENT 0 383968 21758/witness_node
tcp 0 0 176.221.43.130:33323 216.252.204.69:51525 ESTABLISHED 0 150127 21758/witness_node
tcp 0 0 176.221.43.130:33323 107.167.187.88:55405 ESTABLISHED 0 221553 21758/witness_node
udp 0 0 0.0.0.0:54304 0.0.0.0:* 0 150054 21758/witness_node
Title: Re: Test Net for Advanced Users
Post by: betax on August 21, 2015, 01:19:34 pm: Quote from: mudshark79 on August 21, 2015, 01:03:23 pm
Quote from: betax on August 21, 2015, 11:58:36 am
Quote from: betax on August 21, 2015, 11:48:51 am
Anybody having problems with transactions?

It has taking me lots of attempts to import my balances, and I cannot vote myself. I had but the votes remain 0.

you can vote me in to test ;) @ betaxtrade
Meanwhile you're in it seems.

Yes.. going for lunch helps :)
Title: Re: Test Net for Advanced Users
Post by: puppies on August 21, 2015, 01:29:21 pm: I was showing 16 peers on one of my nodes before it stopped working overnight
Code: [Select]
2015-08-21T13:00:01 p2p:message read_loop on_connection_closed ] Remote peer 50.116.4.37:1676 closed their connection to us $2015-08-21T13:00:01 p2p:message read_loop display_current_conn ] Currently have 16 of [20/200] connections $2015-08-21T13:00:01 p2p:message read_loop display_current_conn ] my id is a7cb5e17e25898bb1bef2feb31a341c4c22bc489e700dfbe41$2015-08-21T13:00:01 p2p:message read_loop display_current_conn ] active: 66.41.46.104:59770 with 2ca89a93fe6239371f1498$2015-08-21T13:00:01 p2p:message read_loop display_current_conn ] handshaking: 104.236.82.250:2009 with 000000000000000000000$2015-08-21T13:00:01 p2p:message read_loop display_current_conn ] handshaking: 46.101.12.138:1776 with 0000000000000000000000$2015-08-21T13:00:01 p2p:message read_loop display_current_conn ] handshaking: 104.223.111.102:1776 with 00000000000000000000$2015-08-21T13:00:01 p2p:message read_loop display_current_conn ] handshaking: 213.52.129.25:1776 with 0000000000000000000000$2015-08-21T13:00:01 p2p:message read_loop display_current_conn ] handshaking: 188.166.63.136:1776 with 000000000000000000000$2015-08-21T13:00:01 p2p:message read_loop display_current_conn ] handshaking: 46.226.109.66:1779 with 0000000000000000000000$2015-08-21T13:00:01 p2p:message read_loop display_current_conn ] handshaking: 188.166.63.136:36395 with 00000000000000000000$2015-08-21T13:00:01 p2p:message read_loop display_current_conn ] handshaking: 188.166.31.251:2881 with 000000000000000000000$
Title: Re: Test Net for Advanced Users
Post by: betax on August 21, 2015, 01:48:00 pm: puppies I have just "flood" you some 1 CORE transactions.

On my second round I sent 8,421. :o :o :o :o at 1 core interval. This was done brute forced Hyper Olympics style https://www.youtube.com/watch?v=8va4YGGA3wE, so I am not convinced I did submit as many in 1 minute.

Anyway my witness has not died, can you check you got something?
Title: Re: Test Net for Advanced Users
Post by: roadscape on August 21, 2015, 02:40:12 pm: Left it running overnight and found this:

Quote
2121482ms th_a application.cpp:348 handle_block ] Got block #43785 from network
2122598ms th_a application.cpp:348 handle_block ] Got block #43786 from network
2123581ms th_a application.cpp:348 handle_block ] Got block #43787 from network
2124485ms th_a application.cpp:348 handle_block ] Got block #43788 from network
2125530ms th_a application.cpp:348 handle_block ] Got block #43789 from network
2126480ms th_a application.cpp:348 handle_block ] Got block #43790 from network
2131760ms th_a application.cpp:348 handle_block ] Got block #43791 from network
2132949ms th_a application.cpp:348 handle_block ] Got block #43795 from network
2132949ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2133339ms th_a application.cpp:348 handle_block ] Got block #43796 from network
2133340ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2133543ms th_a application.cpp:348 handle_block ] Got block #43797 from network
2133543ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2134473ms th_a application.cpp:348 handle_block ] Got block #43798 from network
2134474ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2135482ms th_a application.cpp:348 handle_block ] Got block #43799 from network
2135482ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2136479ms th_a application.cpp:348 handle_block ] Got block #43800 from network
2136479ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2137482ms th_a application.cpp:348 handle_block ] Got block #43801 from network
2137482ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
[......snip......]
2160479ms th_a application.cpp:348 handle_block ] Got block #43822 from network
2160479ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2161493ms th_a application.cpp:348 handle_block ] Got block #43823 from network
2161494ms th_a application.cpp:370 handle_block ] Error when pushing block:
10 assert_exception: Assert Exception
item->num < _head->num + MAX_BLOCK_REORDERING:
[..snip..]
2162497ms th_a application.cpp:348 handle_block ] Got block #43824 from network
2162498ms th_a application.cpp:370 handle_block ] Error when pushing block:
10 assert_exception: Assert Exception
item->num < _head->num + MAX_BLOCK_REORDERING:
[..etc..]
Title: Re: Test Net for Advanced Users
Post by: roadscape on August 21, 2015, 04:16:54 pm: Finally got the witness registered and the witness_node syncing reliably.

Code: [Select]
get_witness roadscape { "id": "1.6.5249", "witness_account": "1.2.67334",
But haven't yet produced a block:
Code: [Select]
807002ms th_a witness.cpp:240 block_production_loo ] slot: 1 scheduled_witness: 1.6.5249 scheduled_time: 2015-08-21T16:13:27 now: 2015-08-21T16:13:27 807002ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.5249 production slot has arrived; generating a block now... 807002ms th_a witness.cpp:266 block_production_loo ] Got exception while generating block: 10 assert_exception: Assert Exception witness_obj.signing_key == block_signing_private_key.get_public_key(): {} th_a db_block.cpp:266 _generate_block {"witness_id":"1.6.5249"} th_a db_block.cpp:315 _generate_block
Will continue to fiddle with it..
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 04:22:34 pm: Quote from: roadscape on August 21, 2015, 04:16:54 pm
Finally got the witness registered and the witness_node syncing reliably.

Code: [Select]
get_witness roadscape { "id": "1.6.5249", "witness_account": "1.2.67334",
But haven't yet produced a block:
Code: [Select]
807002ms th_a witness.cpp:240 block_production_loo ] slot: 1 scheduled_witness: 1.6.5249 scheduled_time: 2015-08-21T16:13:27 now: 2015-08-21T16:13:27 807002ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.5249 production slot has arrived; generating a block now... 807002ms th_a witness.cpp:266 block_production_loo ] Got exception while generating block: 10 assert_exception: Assert Exception witness_obj.signing_key == block_signing_private_key.get_public_key(): {} th_a db_block.cpp:266 _generate_block {"witness_id":"1.6.5249"} th_a db_block.cpp:315 _generate_block
Will continue to fiddle with it..

Also had this. My workaround was to creat a new account, send the new account some funds, upgrade newaccount, create witness ....

I read this error as it's not possible to have an Account WIF as the Block-Signing WIF also. This was the case when I Imported my Founder-Id WIF which was also the Balance WIF and after Upgrading and "Witnessing" the account also the Block-Signing WIF. So it's still not crystal clear for me somehow but creating a new account worked. You can lookup the methods for account creation and transfer in the code or somehow there is also some man-help.... am really noobish on all this.
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 04:27:25 pm: Btw: How do you read this:

Code: [Select]
1522956ms th_a witness.cpp:240 block_production_loo ] slot: 1 scheduled_witness: 1.6.1537 scheduled_time: 2015-08-21T16:25:21 now: 2015-08-21T16:25:21 1523956ms th_a witness.cpp:240 block_production_loo ] slot: 2 scheduled_witness: 1.6.56 scheduled_time: 2015-08-21T16:25:22 now: 2015-08-21T16:25:22 1524185ms th_a application.cpp:348 handle_block ] Got block #76718 from network 1524234ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"} 1524234ms th_a application.cpp:451 get_item ] Serving up block #76718 1524386ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"} 1524386ms th_a application.cpp:451 get_item ] Serving up block #76718
Did Witness 1.6.1537 produce his block? Why is the init-witness directly "queueing up" or getting another slot then?
Title: Re: Test Net for Advanced Users
Post by: puppies on August 21, 2015, 04:30:22 pm: Quote from: betax on August 21, 2015, 01:48:00 pm
puppies I have just "flood" you some 1 CORE transactions.

On my second round I sent 8,421. :o :o :o :o at 1 core interval. This was done brute forced Hyper Olympics style https://www.youtube.com/watch?v=8va4YGGA3wE, so I am not convinced I did submit as many in 1 minute.

Anyway my witness has not died, can you check you got something?
sorry betax I'm at work and don't have puppies keys on any vps
Title: Re: Test Net for Advanced Users
Post by: roadscape on August 21, 2015, 04:31:49 pm: Somehow I think I lost the private signing key because dump_private_keys only shows one set, and it belongs to the account itself. I guess I will have to register a new witness.. unless there's a way to generate a new signing key pair?

Quote from: mudshark79 on August 21, 2015, 04:27:25 pm
Btw: How do you read this:

Code: [Select]
1522956ms th_a witness.cpp:240 block_production_loo ] slot: 1 scheduled_witness: 1.6.1537 scheduled_time: 2015-08-21T16:25:21 now: 2015-08-21T16:25:21 1523956ms th_a witness.cpp:240 block_production_loo ] slot: 2 scheduled_witness: 1.6.56 scheduled_time: 2015-08-21T16:25:22 now: 2015-08-21T16:25:22 1524185ms th_a application.cpp:348 handle_block ] Got block #76718 from network 1524234ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"} 1524234ms th_a application.cpp:451 get_item ] Serving up block #76718 1524386ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"} 1524386ms th_a application.cpp:451 get_item ] Serving up block #76718
Did Witness 1.6.1537 produce his block? Why is the init-witness directly "queueing up" or getting another slot then?

I read it as 1.6.1537 missed the slot, and 1.6.56 filled in.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 21, 2015, 04:32:33 pm: Quote from: betax on August 21, 2015, 01:48:00 pm
puppies I have just "flood" you some 1 CORE transactions.

On my second round I sent 8,421. :o :o :o :o at 1 core interval. This was done brute forced Hyper Olympics style https://www.youtube.com/watch?v=8va4YGGA3wE, so I am not convinced I did submit as many in 1 minute.

Anyway my witness has not died, can you check you got something?

How did you do this? Can you send me some to delegate-clayop?
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 04:34:49 pm: Quote from: roadscape on August 21, 2015, 04:31:49 pm
Somehow I think I lost the private signing key because dump_private_keys only shows one set, and it belongs to the account itself. I guess I will have to register a new witness.. unless there's a way to generate a new signing key pair?

Quote from: mudshark79 on August 21, 2015, 04:27:25 pm
Btw: How do you read this:

Code: [Select]
1522956ms th_a witness.cpp:240 block_production_loo ] slot: 1 scheduled_witness: 1.6.1537 scheduled_time: 2015-08-21T16:25:21 now: 2015-08-21T16:25:21 1523956ms th_a witness.cpp:240 block_production_loo ] slot: 2 scheduled_witness: 1.6.56 scheduled_time: 2015-08-21T16:25:22 now: 2015-08-21T16:25:22 1524185ms th_a application.cpp:348 handle_block ] Got block #76718 from network 1524234ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"} 1524234ms th_a application.cpp:451 get_item ] Serving up block #76718 1524386ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"} 1524386ms th_a application.cpp:451 get_item ] Serving up block #76718
Did Witness 1.6.1537 produce his block? Why is the init-witness directly "queueing up" or getting another slot then?

I read it as 1.6.1537 missed the slot, and 1.6.56 filled in.

This pattern repeats for all non-init-witnesses except for my own ...
Title: Re: Test Net for Advanced Users
Post by: roadscape on August 21, 2015, 04:40:21 pm: What's your chain_id?

edit: I'm on d011....5083 which appears to be the legit one
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 05:02:52 pm: Quote from: roadscape on August 21, 2015, 04:40:21 pm
What's your chain_id?

edit: I'm on d011....5083 which appears to be the legit one

yes, that's the one I'm on. got it running nonstop now since yesterday. My node also seems to be used as seed-node throughout the day. Possibly the pattern doesn't repeat for all non-init-witnesses but for most. Is there some wallet-method to see block-statistics for witnesses?
Title: Re: Test Net for Advanced Users
Post by: betax on August 21, 2015, 05:15:29 pm: Quote from: puppies on August 21, 2015, 04:30:22 pm
Quote from: betax on August 21, 2015, 01:48:00 pm
puppies I have just "flood" you some 1 CORE transactions.

On my second round I sent 8,421. :o :o :o :o at 1 core interval. This was done brute forced Hyper Olympics style https://www.youtube.com/watch?v=8va4YGGA3wE, so I am not convinced I did submit as many in 1 minute.

Anyway my witness has not died, can you check you got something?
sorry betax I'm at work and don't have puppies keys on any vps

Don't worry!
Title: Re: Test Net for Advanced Users
Post by: roadscape on August 21, 2015, 05:18:14 pm: Quote from: mudshark79 on August 21, 2015, 05:02:52 pm
Quote from: roadscape on August 21, 2015, 04:40:21 pm
What's your chain_id?

edit: I'm on d011....5083 which appears to be the legit one

yes, that's the one I'm on. got it running nonstop now since yesterday. My node also seems to be used as seed-node throughout the day. Possibly the pattern doesn't repeat for all non-init-witnesses but for most. Is there some wallet-method to see block-statistics for witnesses?

I'm guessing most witnesses are offline, so you're fine. Mine is still stuck.
Are you 176.221.43.130:33323? If so.. thanks :) And I couldn't find a way to see block statistics.

@bytemaster, is there a way to recover/regenerate a signing key for the witness node?
Title: Re: Test Net for Advanced Users
Post by: betax on August 21, 2015, 05:22:04 pm: Quote from: clayop on August 21, 2015, 04:32:33 pm
Quote from: betax on August 21, 2015, 01:48:00 pm
puppies I have just "flood" you some 1 CORE transactions.

On my second round I sent 8,421. :o :o :o :o at 1 core interval. This was done brute forced Hyper Olympics style https://www.youtube.com/watch?v=8va4YGGA3wE, so I am not convinced I did submit as many in 1 minute.

Anyway my witness has not died, can you check you got something?

How did you do this? Can you send me some to delegate-clayop?

Physically is impossible, hence my question. I am down at the moment.. ill try tomorrow.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 21, 2015, 05:22:21 pm: Quote from: roadscape on August 21, 2015, 04:31:49 pm
Somehow I think I lost the private signing key because dump_private_keys only shows one set, and it belongs to the account itself. I guess I will have to register a new witness.. unless there's a way to generate a new signing key pair?

Quote from: mudshark79 on August 21, 2015, 04:27:25 pm
Btw: How do you read this:

Code: [Select]
1522956ms th_a witness.cpp:240 block_production_loo ] slot: 1 scheduled_witness: 1.6.1537 scheduled_time: 2015-08-21T16:25:21 now: 2015-08-21T16:25:21 1523956ms th_a witness.cpp:240 block_production_loo ] slot: 2 scheduled_witness: 1.6.56 scheduled_time: 2015-08-21T16:25:22 now: 2015-08-21T16:25:22 1524185ms th_a application.cpp:348 handle_block ] Got block #76718 from network 1524234ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"} 1524234ms th_a application.cpp:451 get_item ] Serving up block #76718 1524386ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"} 1524386ms th_a application.cpp:451 get_item ] Serving up block #76718
Did Witness 1.6.1537 produce his block? Why is the init-witness directly "queueing up" or getting another slot then?

I read it as 1.6.1537 missed the slot, and 1.6.56 filled in.

Ben had this problem too. Will look into this.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 21, 2015, 05:22:57 pm: Quote from: roadscape on August 21, 2015, 02:40:12 pm
Left it running overnight and found this:

Quote
2121482ms th_a application.cpp:348 handle_block ] Got block #43785 from network
2122598ms th_a application.cpp:348 handle_block ] Got block #43786 from network
2123581ms th_a application.cpp:348 handle_block ] Got block #43787 from network
2124485ms th_a application.cpp:348 handle_block ] Got block #43788 from network
2125530ms th_a application.cpp:348 handle_block ] Got block #43789 from network
2126480ms th_a application.cpp:348 handle_block ] Got block #43790 from network
2131760ms th_a application.cpp:348 handle_block ] Got block #43791 from network
2132949ms th_a application.cpp:348 handle_block ] Got block #43795 from network
2132949ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2133339ms th_a application.cpp:348 handle_block ] Got block #43796 from network
2133340ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2133543ms th_a application.cpp:348 handle_block ] Got block #43797 from network
2133543ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2134473ms th_a application.cpp:348 handle_block ] Got block #43798 from network
2134474ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2135482ms th_a application.cpp:348 handle_block ] Got block #43799 from network
2135482ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2136479ms th_a application.cpp:348 handle_block ] Got block #43800 from network
2136479ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2137482ms th_a application.cpp:348 handle_block ] Got block #43801 from network
2137482ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
[......snip......]
2160479ms th_a application.cpp:348 handle_block ] Got block #43822 from network
2160479ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link.
2161493ms th_a application.cpp:348 handle_block ] Got block #43823 from network
2161494ms th_a application.cpp:370 handle_block ] Error when pushing block:
10 assert_exception: Assert Exception
item->num < _head->num + MAX_BLOCK_REORDERING:
[..snip..]
2162497ms th_a application.cpp:348 handle_block ] Got block #43824 from network
2162498ms th_a application.cpp:370 handle_block ] Error when pushing block:
10 assert_exception: Assert Exception
item->num < _head->num + MAX_BLOCK_REORDERING:
[..etc..]

This is very useful information because it shows that the network code actually skipped some blocks!
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 05:36:57 pm: Quote from: bytemaster on August 21, 2015, 05:22:21 pm
Quote from: roadscape on August 21, 2015, 04:31:49 pm
Somehow I think I lost the private signing key because dump_private_keys only shows one set, and it belongs to the account itself. I guess I will have to register a new witness.. unless there's a way to generate a new signing key pair?

Quote from: mudshark79 on August 21, 2015, 04:27:25 pm
Btw: How do you read this:

Code: [Select]
1522956ms th_a witness.cpp:240 block_production_loo ] slot: 1 scheduled_witness: 1.6.1537 scheduled_time: 2015-08-21T16:25:21 now: 2015-08-21T16:25:21 1523956ms th_a witness.cpp:240 block_production_loo ] slot: 2 scheduled_witness: 1.6.56 scheduled_time: 2015-08-21T16:25:22 now: 2015-08-21T16:25:22 1524185ms th_a application.cpp:348 handle_block ] Got block #76718 from network 1524234ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"} 1524234ms th_a application.cpp:451 get_item ] Serving up block #76718 1524386ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"} 1524386ms th_a application.cpp:451 get_item ] Serving up block #76718
Did Witness 1.6.1537 produce his block? Why is the init-witness directly "queueing up" or getting another slot then?

I read it as 1.6.1537 missed the slot, and 1.6.56 filled in.

Ben had this problem too. Will look into this.

Just found some miutes to look at it again (partly for recreational purposes) and now I saw 1.6.1537 filling his block. So I guess it's really that simple, that most witnesses actually do not produce blocks yet or anymore. Even though I see a lot of connected nodes at the moment and one would expect them to be manned and producing?
Title: Re: Test Net for Advanced Users
Post by: clayop on August 21, 2015, 05:43:24 pm: Quote from: mudshark79 on August 21, 2015, 05:36:57 pm
Just found some miutes to look at it again (partly for recreational purposes) and now I saw 1.6.1537 filling his block. So I guess it's really that simple, that most witnesses actually do not produce blocks yet or anymore. Even though I see a lot of connected nodes at the moment and one would expect them to be manned and producing?

1.6.1537 is me (delegate-clayop). I was resyncing.
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 21, 2015, 06:24:21 pm: I see 16 nodes connected now and quite some resyncing happening all the time. CPU Load never under 15% now... (but can't say what CPU-rating that VPS actually has) 8)
Title: Re: Test Net for Advanced Users
Post by: clayop on August 21, 2015, 06:28:38 pm: Here is a video capture about an error I experienced.

I ran 100*10 transfers on my witness node. When my witness have its produce turn, it failed to produce a block.

http://youtu.be/D1eRD2nIHJk
Title: Re: Test Net for Advanced Users
Post by: puppies on August 21, 2015, 07:04:12 pm: Quote from: betax on August 21, 2015, 05:15:29 pm
Quote from: puppies on August 21, 2015, 04:30:22 pm
Quote from: betax on August 21, 2015, 01:48:00 pm
puppies I have just "flood" you some 1 CORE transactions.

On my second round I sent 8,421. :o :o :o :o at 1 core interval. This was done brute forced Hyper Olympics style https://www.youtube.com/watch?v=8va4YGGA3wE, so I am not convinced I did submit as many in 1 minute.

Anyway my witness has not died, can you check you got something?
sorry betax I'm at work and don't have puppies keys on any vps

Don't worry!

History only shows
Code: [Select]
unlocked >>> get_account_history puppies 10 get_account_history puppies 10 2015-08-21T03:05:27 Update Account 'puppies' (Fee: 20.14453 CORE) 2015-08-21T02:36:35 Update Account 'puppies' (Fee: 20.14062 CORE) 2015-08-21T02:03:08 balance_claim_operation puppies fee: 0 CORE 2015-08-21T02:03:08 balance_claim_operation puppies fee: 0 CORE 2015-08-21T02:03:08 balance_claim_operation puppies fee: 0 CORE 2015-08-21T02:03:08 balance_claim_operation puppies fee: 0 CORE 2015-08-21T02:03:08 balance_claim_operation puppies fee: 0 CORE 2015-08-21T02:03:08 balance_claim_operation puppies fee: 0 CORE 2015-08-21T02:03:08 balance_claim_operation puppies fee: 0 CORE 2015-08-21T02:03:08 balance_claim_operation puppies fee: 0 CORE unlocked >>>[Code]
Title: Re: Test Net for Advanced Users
Post by: abit on August 21, 2015, 08:04:19 pm: Here is my theory:
Current testnet is too centralized.
Because the init node have about 90% of active witnesses, if it didn't receive a block produced by other witness (networking issue or so), most time next slot is the init node itself, so it just produce one, and next, next, next, certainly it will be the longest chain. That's why the network is 'robust', but it's not true, it's not safe, we can say we're encountering 51% attack indeed.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 21, 2015, 08:21:10 pm: The network is robust because it is centralized right now. When the network is under heavy load network propagation delays cause minority witnesses to miss their slots.

We have been studying this problem and have concluded that the current P2P algorithm is not well suited to 1 second blocks.

Assuming 2 nodes are across the globe and have a 250 ms latency, then the following handshake takes 0.75 seconds with 0 data and CPU delays:

notify inventory
request item
receive item

That is barely good enough for two peers to keep in sync if directly connected. But when you have 2 peers connected through a middle man then we are talking 1.5 seconds which breaks down with 1 second blocks.

This is the one part of the code that we have been reusing from BTS 1.0 and it appears it is not up to the task. So today Ben and I came up with a new, simple, protocol that should dramatically improve network performance.

Code: [Select]
# Network Protocol 2 Building a low-latency network requires P2P nodes that have low-latency connections and a protocol designed to minimize latency. for the purpose of this document we will assume that two nodes are located on opposite sides of the globe with a ping time of 250ms. ## Announce, Request, Send Protocol Under the prior network archtiecture, transactions and blocks were broadcast in a manner similar to the Bitcoin protocol: inventory messages notify peers of transactions and blocks, then peers fetch the transaction or block from one peer. After validating the item a node will broadcast an inventory message to its peers. Under this model it will take 0.75 seconds for a peer to communicate a transaction or block to another peer even if their size was 0 and there was no processing overhead. This level of performance is unacceptable for a network attempting to produce one block every second. This prior protocol also sent every transaction twice: initial broadcast, and again as part of a block. ## Push Protocol To minimize latency each node needs to immediately broadcast the data it receives to its peers after validating it. Given the average transaction size is less than 100 bytes, it is almost as effecient to send the transaction as it is to send the notice (assuming a 20 byte transaction id) Each node implements the following protocol: onReceiveTransaction( from_peer, transaction ) if( isKnown( transaction.id() ) ) return markKnown( transaction.id() ) if( !validate( transaction ) ) return for( peer : peers ) if( peer != from_peer ) send( peer, transaction ) onReceiveBlock( from_peer, block_summary ) if( isKnown( block_summary ) return full_block = reconstructFullBlcok( from_peer, block_summary ) if( !full_block ) disconnect from_peer markKnown( block_summary ) if( !pushBlock( full_block ) ) disconnect from_peer for( peer : peers ) if( peer != from_peer ) send( peer, block_summary ) onConnect( new_peer, new_peer_head_block_num ) if( peers.size() >= max_peers ) send( new_peer, peers ) disconnect( new_peer ) return while( new_peer_head_block_num < our_head_block_num ) sendFullBlock( new_peer, ++new_peer_head_block_num ) new_peer.synced = true for( peer : peers ) send( peer, new_peer ) onReceivePeers( from_peer, peers ) addToPotentialPeers( peers ) onUpdateConnectionsTimer if( peers.size() < desired_peers ) connect( random_potential_peer ) onFullBlock( from_peer, full_block ) if( !pushBlock( full_block ) ) disconnect from_peer onStartup init_potential_peers from config start onUpdateConnectionsTimer
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 21, 2015, 08:24:57 pm: Under the new protocol transactions only get sent once (vs twice under the current protocol) so bandwidth should be lower and block latencies will be lower because we do not send transaction data with the blocks like we do today.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 21, 2015, 08:35:55 pm: Quote from: bytemaster on August 21, 2015, 08:24:57 pm
Under the new protocol transactions only get sent once (vs twice under the current protocol) so bandwidth should be lower and block latencies will be lower because we do not send transaction data with the blocks like we do today.

+5%
Title: Re: Test Net for Advanced Users
Post by: triox on August 21, 2015, 08:44:48 pm: Guys, what am I doing wrong when trying to import_balance?

Code: [Select]
0 exception: unspecified 3030001 tx_missing_active_auth: missing required active authority
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on August 22, 2015, 02:27:46 am: Quote from: bytemaster on August 21, 2015, 08:24:57 pm
Under the new protocol transactions only get sent once (vs twice under the current protocol) so bandwidth should be lower and block latencies will be lower because we do not send transaction data with the blocks like we do today.

So assuming 250ms ping times (125ms one way), the new system should support forkless operation with witnesses up to 6 hops apart as long as block production time + ((block validation time + block transmission time) * 6) all add up to less than 250ms. At 4 hops of separation between witnesses that allows 500ms for block production time + ((block validation time + block transmission time) * 4). Does this sound right?

Is one second block time just because it sounds good and it's a challenging goal, or would moving to 2 second intervals be significantly detrimental to some particular use case? 1 second seems doable, just wondering.
Title: Re: Test Net for Advanced Users
Post by: cryptosile on August 22, 2015, 02:56:14 am: The engineer in me says make the system work for 1s but then actually use 10s order of magnitude sadety
Title: Re: Test Net for Advanced Users
Post by: lafona on August 22, 2015, 04:45:31 am: I built using the test1 tag and it seems to eventually crash with something like this:
Code: [Select]
1475279ms th_a application.cpp:348 handle_block ] Got block #113022 from network 1475280ms th_a application.cpp:370 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception second_branch_itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:186 fetch_branch_from {"first":"0001b97efde7f8735edf4f0e9a0bf8861bedc272","second":"0001b8e8da3980ecd944f089517017859760d770"} th_a fork_database.cpp:217 fetch_branch_from {"new_block":{"previous":"0001b97dcd02515b154d14bee9b4c5a15b05e03c","timestamp":"2015-08-22T03:24:35","witness":"1.6.64","next_secret_hash":"baf2320a0c7779529c41e52ee54e661140034669","previous_secret":"49b271b871ea785fae64cba2f1e10f7bcd218cc2","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"201195222d96d0b21529707eb7ae0d3aa7f653da76bbc1495a72e5b0d0c710ac6e66a4cb06502d1649e1b702d8c951c0e0705ad0c89a6a9c1ed0ba52dfb2b62324","transactions":[]}} th_a db_block.cpp:176 _push_block [....snip....] 1475783ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"0001ae6ac8e3a8a26cc2aecb308c1150892e7fe4"} 1475783ms th_a application.cpp:451 get_item ] Serving up block #110186 1475784ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"0001ae6bc410e0e184a6d0a024a612b05ce4c01b"} 1475784ms th_a application.cpp:451 get_item ] Serving up block #110187 1475784ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"0001ae6c60d1aec7d5c24446dbf842a4b601033d"} 1475784ms th_a application.cpp:451 get_item ] Serving up block #110188 1475784ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"0001ae6d84528ff70008714ca1ed7977310535ac"} 1475785ms th_a application.cpp:451 get_item ] Serving up block #110189 1475785ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"0001ae6e323f7799e02346474a64e890fa79ab11"} 1475785ms th_a application.cpp:451 get_item ] Serving up block #110190 1475785ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"0001ae6fbc4e341c9d0387ab939ed1d7f99f7497"} 1475785ms th_a application.cpp:451 get_item ] Serving up block #110191 1476037ms th_a witness.cpp:240 block_production_loo ] slot: 166 scheduled_witness: 1.6.1530 scheduled_time: 2015-08-22T03:24:36 now: 2015-08-22T03:24:36 1476037ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.1530 production slot has arrived; generating a block now... Segmentation fault (core dumped)
Is this the assert exception issue from https://github.com/cryptonomex/graphene/issues/260? Is there a good way to get around this?
I tried building from master but that ended up crashing differently. Here is the last output if it is helpful.

Code: [Select]
1800055ms th_a application.cpp:348 handle_block ] Got block #116582 from network 1800055ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1800171ms th_a application.cpp:370 handle_block ] Error when pushing block: 13 NSt8ios_base7failureE: basic_ios::clear basic_ios::clear: {"new_block":{"previous":"0001c7654456dc221956bf0b1a9f20e686865f97","timestamp":"2015-08-22T04:30:00","witness":"1.6.29","next_secret_hash":"2df6b7104fa19d2c938a9636b5bc6b7eb20b7900","previous_secret":"c55c74f80a07f39dc6996976894c1cf8a507ec78","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"20427e5c13761a8923e780808a1b85d32376cc556fb60ef7e828a84a1ae22beefd6c03c2e271ac718573237ffc53a4b97572373ee5c7ce8b553c66a73592ee8e6c","transactions":[]},"what":"basic_ios::clear"} th_a db_block.cpp:176 _push_block 1800336ms th_a application.cpp:492 get_blockchain_synop ] reference_point: 00018b78f3052a0ce0fbac70df02f31634305dc1 number_of_blocks_after_reference_point: 0 result: ["0000c756375599f45ec17cbbc52a18f31b25abf6","00014756adffcc733dca7791fedaf42573352c9c","000187564a3607bd8feaf45ede04a2a4e44ad83e","0001a7561760fe72f9de51d3a5e3bc4415d3463e","0001b7560bfefc10d57f0a18f4b415bc986e7a16","0001bf56be84f86a5b4bdca2008ffba59c5ce198","0001c35601b57967bf33f286f1b44b7d4646bca0","0001c5569d398257fcd046cfc6c86fc2765fd3e3","0001c656ec0cee80adbf59f139cf19bcd3d598a6","0001c6d69e121f19e81a9d7faace9188ec247291","0001c716a2707e4331683f820f70e9e51abbe1b0","0001c73676aeaf757eb2de7cf6a5b829372e3c9a","0001c746a973f6e9c1871038af253bd6e848ff6d","0001c74ef58f2c455a58a2813fcc566148d9f85c","0001c7521b40eff5ff0e580031c8c3011400103b","0001c7544b407028c1d6456f6cf6648fa9701af6","0001c75594757f5330406d8d237547d13fc4ea32","0001c756f0ba255380208bca3bf6a7e7cd44690f"] 1800500ms th_a application.cpp:492 get_blockchain_synop ] reference_point: 0001ada79445f13682e34a31fa122cbcbbfba68f number_of_blocks_after_reference_point: 0 result: ["0000c756375599f45ec17cbbc52a18f31b25abf6","00014756adffcc733dca7791fedaf42573352c9c","000187564a3607bd8feaf45ede04a2a4e44ad83e","0001a7561760fe72f9de51d3a5e3bc4415d3463e","0001b7560bfefc10d57f0a18f4b415bc986e7a16","0001bf56be84f86a5b4bdca2008ffba59c5ce198","0001c35601b57967bf33f286f1b44b7d4646bca0","0001c5569d398257fcd046cfc6c86fc2765fd3e3","0001c656ec0cee80adbf59f139cf19bcd3d598a6","0001c6d69e121f19e81a9d7faace9188ec247291","0001c716a2707e4331683f820f70e9e51abbe1b0","0001c73676aeaf757eb2de7cf6a5b829372e3c9a","0001c746a973f6e9c1871038af253bd6e848ff6d","0001c74ef58f2c455a58a2813fcc566148d9f85c","0001c7521b40eff5ff0e580031c8c3011400103b","0001c7544b407028c1d6456f6cf6648fa9701af6","0001c75594757f5330406d8d237547d13fc4ea32","0001c756f0ba255380208bca3bf6a7e7cd44690f"] 1800688ms th_a application.cpp:492 get_blockchain_synop ] reference_point: 00018b78f3052a0ce0fbac70df02f31634305dc1 number_of_blocks_after_reference_point: 0 result: ["0000c756375599f45ec17cbbc52a18f31b25abf6","00014756adffcc733dca7791fedaf42573352c9c","000187564a3607bd8feaf45ede04a2a4e44ad83e","0001a7561760fe72f9de51d3a5e3bc4415d3463e","0001b7560bfefc10d57f0a18f4b415bc986e7a16","0001bf56be84f86a5b4bdca2008ffba59c5ce198","0001c35601b57967bf33f286f1b44b7d4646bca0","0001c5569d398257fcd046cfc6c86fc2765fd3e3","0001c656ec0cee80adbf59f139cf19bcd3d598a6","0001c6d69e121f19e81a9d7faace9188ec247291","0001c716a2707e4331683f820f70e9e51abbe1b0","0001c73676aeaf757eb2de7cf6a5b829372e3c9a","0001c746a973f6e9c1871038af253bd6e848ff6d","0001c74ef58f2c455a58a2813fcc566148d9f85c","0001c7521b40eff5ff0e580031c8c3011400103b","0001c7544b407028c1d6456f6cf6648fa9701af6","0001c75594757f5330406d8d237547d13fc4ea32","0001c756f0ba255380208bca3bf6a7e7cd44690f"] 1801000ms th_a witness.cpp:240 block_production_loo ] slot: 18 scheduled_witness: 1.6.1530 scheduled_time: 2015-08-22T04:30:01 now: 2015-08-22T04:30:01 1801000ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.1530 production slot has arrived; generating a block now... 1801003ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1801191ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1801332ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1801448ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1801557ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1801665ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1801772ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1801880ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1801994ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1802108ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1802217ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1802331ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1802440ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1802549ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1802657ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1802766ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. Segmentation fault (core dumped)
Title: Re: Test Net for Advanced Users
Post by: rnglab on August 22, 2015, 08:24:09 am: Happy to join testnet and help wherever I can, new witness is almost up.
Code: [Select]
get_witness bitshares-argentina { "id": "1.6.707", "witness_account": "1.2.8572",
It has no funds yet, I've imported a delegate account that we registered just before 2.0 announce (so we decided to wait). Sent some bts recently but import_balance returns 0, I guess because tx was made after aug-20 genesis block, so votes are welcome.

Do you see any issue using an existing delegate on testnet?

Code: [Select]
3514165ms th_a thread.cpp:95 thread ] name:ntp tid:140288926934784 3514166ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 3514166ms th_a thread.cpp:95 thread ] name:p2p tid:140288904390400 3514173ms th_a application.cpp:117 reset_p2p_node ] Adding seed node 104.236.51.238:1776 3514173ms ntp ntp.cpp:81 request_now ] sending request to 62.75.202.83:123 3514175ms th_a application.cpp:129 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:56445 3514177ms th_a application.cpp:179 reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090 3514177ms th_a witness.cpp:139 plugin_startup ] Launching block production for 1 witnesses. 3514178ms th_a main.cpp:165 main ] Started witness node on a chain with 127829 blocks. 3514178ms th_a main.cpp:166 main ] Chain ID is d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083 3514184ms ntp ntp.cpp:147 read_loop ] received ntp reply from 62.75.202.83:123 3514184ms ntp ntp.cpp:161 read_loop ] ntp offset: 294, round_trip_delay 10707 3514184ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 294 3514673ms th_a application.cpp:492 get_blockchain_synop ] reference_point: 0000000000000000000000000000000000000000 number_of_blocks_after_reference_point: 0 result: ["0000f3559d98bf93dd1f7901ac2ccbd452e611bc","00017355c1af25485603b9cc7c699def8cd995dc","0001b355ff6383082c0e5f20bcdaa6048ac2ae8a","0001d3559442c82f0570f0b36981b56eff5c43c3","0001e3554a0f694c82fb1b6c14c1327172bc4b56","0001eb55257a6d3c563ecd7519141499c2360ca6","0001ef559d44b8744c47f764bb0e49dc41f557f2","0001f155035c6c94533e706ed3bc728d948f7e50","0001f255ecca702f4c77dd8ea6177c8f96ff5a3d","0001f2d544532e44118fa11695bfd6f6282c5b3b","0001f315d65810292c0807101bfb8dd62ba798a0","0001f33554daf2c617ea4b4aa99471b0b8b5f37b","0001f345a165261885cbce3c6069b2818b5a3474","0001f34d1df9d508573c9d8bb41f2a90928343f6","0001f351735c35b128914ab19a5623a461058b11","0001f3534999a19244ca2b6d0c06d0c3001bca7d","0001f3545becc61c1fae72171c8e7ee7ab2497bd","0001f3558fde448eb58f504cf29751608f5a8ebe"] 3515000ms th_a witness.cpp:240 block_production_loo ] slot: 70 scheduled_witness: 1.6.14 scheduled_time: 2015-08-22T07:58:35 now: 2015-08-22T07:58:35 3515182ms th_a application.cpp:492 get_blockchain_synop ] reference_point: 0001f3950d68963e625bb00635af319e5c92d65c number_of_blocks_after_reference_point: 0 result: ["0000f395cb92dbb98048570fe4f9d15bec86a063","000173959fe061b2101f1eb98db0c2ff76214f2d","0001b3956efdabb08e5a922c44e8ebd246d984e7","0001d39542424e5722239c5ae5acf96c52fb3a2f","0001e395e2e07858fb2a023fc3b88a48c02ae186","0001eb955d23d037dc15a3a6f1400f78b231dd8b","0001ef95740613cd17502a0eb8c4b8cc8a3a8e76","0001f1958ad16b018fb0d59aca314c5b35861402","0001f2957f0a4a8fe88626f98e85f3a148708a60","0001f315d65810292c0807101bfb8dd62ba798a0","0001f3558fde448eb58f504cf29751608f5a8ebe","0001f375b59b9d9d5e1592f50b6080663566d36c","0001f3850c9e99994e9ecaff2d3e1ff722ed03ef","0001f38d4344efed8da646f862994826c0e990fb","0001f3910665edad95cf6f8286a5b98e74f1373c","0001f393c5d1a0e37b7141f3b434c818ca87d6b2","0001f394560a95f0090ae089cff6c8e46c4425a3","0001f3950d68963e625bb00635af319e5c92d65c"] 3515349ms th_a application.cpp:492 get_blockchain_synop ] reference_point: 0001f396c3191b6a65a7da41a79cfc75c71f57d8 number_of_blocks_after_reference_point: 0 result: ["0000f3961b99f42a7ec4454156616b6933183f36","00017396077234751f0884ce6dd1554066dc2cc1","0001b3969bc73c9878e6ac262860bc0ab7c94ad1","0001d39639b9edb3aafb7e436412a37569033ec3","0001e39664d0531007c9b55dc57b22533c3e7932","0001eb9689d05637742379e327446384064d9c14","0001ef96bf242122f4470fa5c6c3185f5b067da0","0001f196880be06943bc51626fd66ff87c8653d9","0001f296e81daa34ce339d804ac55056ef3ac93d","0001f3163223c4eb858f0e0db96f6fe99130755a","0001f3563cdb919fa7544386e428fe4ee2cdf5bd","0001f3760c24b81bd20d2833b440d6f49d9615f6","0001f3867c0411c9a6ee6af1ae77d9a3b3d16a88","0001f38e037953bb72c82f0babde0361c8192fb1","0001f3928baff42b1ed9df6c96821d0906f837a6","0001f394560a95f0090ae089cff6c8e46c4425a3","0001f3950d68963e625bb00635af319e5c92d65c","0001f396c3191b6a65a7da41a79cfc75c71f57d8"] 3516000ms th_a witness.cpp:240 block_production_loo ] slot: 1 scheduled_witness: 1.6.21 scheduled_time: 2015-08-22T07:5

Code: [Select]
info { "head_block_num": 129066, "head_block_id": "0001f82ae17a57d9c8250d00f14448704b603ae0", "head_block_age": "3 seconds old", "next_maintenance_time": "5 minutes in the future", "chain_id": "d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083",
Code: [Select]
get_dynamic_global_properties { "id": "2.1.0", "random": "701a35b3f5901fa6b42dd4901c65583786ec4c5c", "head_block_number": 129117, "head_block_id": "0001f85d6294ba131378697035b571bd26dd8aa6", "time": "2015-08-22T08:20:59", "current_witness": "1.6.28", "next_maintenance_time": "2015-08-22T08:25:00", "witness_budget": 70776456, "accounts_registered_this_interval": 0, "recently_missed_count": 0, "dynamic_flags": 0 }
Title: Re: Test Net for Advanced Users
Post by: abit on August 22, 2015, 09:52:58 am: Run out of disk space :(
p2p.log too large.
Title: Re: Test Net for Advanced Users
Post by: rnglab on August 22, 2015, 10:03:35 am: Quote from: abit on August 22, 2015, 09:52:58 am
Run out of disk space :(
p2p.log too large.

Same here, p2p.log grows like 1Gb/h
have you tried setting log level from debug to info? I'll try it now.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 22, 2015, 12:46:20 pm: Witness node up and running stable for a day :)

Code: [Select]
get_witness ihashfury { "id": "1.6.2561", "witness_account": "1.2.38482",
If anyone would like to vote me in it would be appreciated until I get some balance keys imported
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 22, 2015, 01:54:19 pm: Quote from: triox on August 21, 2015, 08:44:48 pm
Guys, what am I doing wrong when trying to import_balance?

Code: [Select]
0 exception: unspecified 3030001 tx_missing_active_auth: missing required active authority
You need to also import the active_key

wallet_dump_account_private_key account active_key
Title: Re: Test Net for Advanced Users
Post by: lafona on August 22, 2015, 02:02:44 pm: You should be voted in IHashFury. Also what I have found to be easier for importing balances. If you know when the snapshot was taken you can pull up the transaction history for your account and look for a transaction which would have added bts to your account right before the snapshot. Then you can look up the transaction on the blockchain using the ID given in the transaction history(blockchain_get_transaction). From there you can use the listed active key in the json output and dump the private key from that. It should make it easier to find a key with a balance in it at the snapshot. Hope that helps
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 22, 2015, 02:50:05 pm: Quote from: lafona on August 22, 2015, 02:02:44 pm
You should be voted in IHashFury. Also what I have found to be easier for importing balances. If you know when the snapshot was taken you can pull up the transaction history for your account and look for a transaction which would have added bts to your account right before the snapshot. Then you can look up the transaction on the blockchain using the ID given in the transaction history(blockchain_get_transaction). From there you can use the listed active key in the json output and dump the private key from that. It should make it easier to find a key with a balance in it at the snapshot. Hope that helps

Thank you for the votes - much appreciated

Witness is producing blocks :)

I'm checking my transaction history now too see what I can import
Title: Re: Test Net for Advanced Users
Post by: fundomatic on August 22, 2015, 04:05:36 pm: Hi,

What is current testnet seed ip, as in ...
Code: [Select]
./witness_node -s "104.200.28.117:61705"
The mentioned ip address is from

https://github.com/cryptonomex/graphene/wiki/Howto-become-an-active-witness-in-BitShares-2.0

and it does not work for me.

And what is the testnet chain_id?

Any ip I try seem to "closed their connection to us"
Seems like I get "incorrect chain_id".
Code: [Select]
p2p stcp_socket.cpp:111 readsome message_oriented_connection.cpp:199 2015-08-22T15:40:59 p2p:message read_loop on_connection_closed ] Remote peer 176.221.43.130:33323 closed their connection to us node.cpp:2724 2015-08-22T15:40:59 p2p:message read_loop display_current_conn ] Currently have 0 of [20/200] connections node.cpp:1625 2015-08-22T15:40:59 p2p:message read_loop display_current_conn ] my id is 79f5f5a4305f4496e2cb1e3f2dd48b4031d1b535bf391c91d7279545a87ed10b06 node.cpp:1626 2015-08-22T15:40:59 p2p:message read_loop trigger_p2p_network_ ] Triggering connect loop now node.cpp:974 2015-08-22T15:40:59 p2p:message read_loop schedule_peer_for_de ] scheduling peer for deletion: 176.221.43.130:33323 (this will not block) node.cpp:1534 2015-08-22T15:40:59 p2p:message read_loop schedule_peer_for_de ] asyncing delayed_peer_deletion_task to delete 1 peers node.cpp:1539 2015-08-22T15:40:59 p2p:delayed_peer_deletion_task delayed_peer_deletio ] beginning an iteration of delayed_peer_deletion_task with 1 in queue node.cpp:1498 2015-08-22T15:40:59 p2p:delayed_peer_deletion_task destroy ] calling close_connection() peer_connection.cpp:122 2015-08-22T15:40:59 p2p:delayed_peer_deletion_task destroy ] close_connection completed normally peer_connection.cpp:124 2015-08-22T15:40:59 p2p:delayed_peer_deletion_task destroy ] canceling _send_queued_messages task peer_connection.cpp:137 2015-08-22T15:40:59 p2p:delayed_peer_deletion_task destroy ] cancel_and_wait completed normally peer_connection.cpp:139 2015-08-22T15:40:59 p2p:delayed_peer_deletion_task destroy ] canceling accept_or_connect_task peer_connection.cpp:152 2015-08-22T15:40:59 p2p:delayed_peer_deletion_task destroy ] accept_or_connect_task completed normally peer_connection.cpp:154 2015-08-22T15:40:59 p2p:delayed_peer_deletion_task destroy_connection ] in destroy_connection() for message_oriented_connection.cpp:280 2015-08-22T15:40:59 p2p:delayed_peer_deletion_task destroy_connection ] Exception thrown while canceling message_oriented_connection's read_loop, ignoring: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":201,"method":"read_loop","hostname":"","thread_name":"p2p","timestamp":"2015-08-22T15:40:59"},"format":"disconnected: ${e}","data":{"e":"0 exception: unspecified\nBad file descriptor \n {\"message\":\"Bad file descriptor\"}\n asio asio.cpp:37 operator()\n\n {\"len\":16}\n p2p stcp_socket.cpp:111 readsome"}}]} message_oriented_connection.cpp:293 2015-08-22T15:40:59 p2p:delayed_peer_deletion_task destroy_connection ] in destroy_connection() for message_oriented_connection.cpp:280 2015-08-22T15:40:59 p2p:delayed_peer_deletion_task destroy_connection ] Exception thrown while canceling message_oriented_connection's read_loop, ignoring: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":201,"method":"read_loop","hostname":"","thread_name":"p2p","timestamp":"2015-08-22T15:40:59"},"format":"disconnected: ${e}","data":{"e":"0 exception: unspecified\nBad file descriptor \n {\"message\":\"Bad file descriptor\"}\n asio asio.cpp:37 operator()\n\n {\"len\":16}\n p2p stcp_socket.cpp:111 readsome"}}]} message_oriented_connection.cpp:293 2015-08-22T15:40:59 p2p:delayed_peer_deletion_task delayed_peer_deletio ] leaving delayed_peer_deletion_task node.cpp:1501 2015-08-22T15:41:08 p2p:p2p_network_connect_loop p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:881 2015-08-22T15:41:08 p2p:p2p_network_connect_loop display_current_conn ] Currently have 0 of [20/200] connections node.cpp:1625 2015-08-22T15:41:08 p2p:p2p_network_connect_loop display_current_conn ] my id is 79f5f5a4305f4496e2cb1e3f2dd48b4031d1b535bf391c91d7279545a87ed10b06 node.cpp:1626 2015-08-22T15:41:08 p2p:p2p_network_connect_loop display_current_conn ] Currently have 0 of [20/200] connections node.cpp:1625 2015-08-22T15:41:08 p2p:p2p_network_connect_loop display_current_conn ] my id is 79f5f5a4305f4496e2cb1e3f2dd48b4031d1b535bf391c91d7279545a87ed10b06
Any help is appreciated.
Title: Re: Test Net for Advanced Users
Post by: lafona on August 22, 2015, 04:16:52 pm: You can get the info on the current testnet here afaik: https://github.com/cryptonomex/graphene/releases/tag/test1
The original conversation is a few pages back here: https://bitsharestalk.org/index.php/topic,17962.330.html
Title: Re: Test Net for Advanced Users
Post by: fundomatic on August 22, 2015, 04:32:26 pm: Quote from: lafona on August 22, 2015, 04:16:52 pm
You can get the info on the current testnet here afaik: https://github.com/cryptonomex/graphene/releases/tag/test1
The original conversation is a few pages back here: https://bitsharestalk.org/index.php/topic,17962.330.html

Thanks.
Title: Re: Test Net for Advanced Users
Post by: abit on August 22, 2015, 05:27:47 pm: Quote from: rnglab on August 22, 2015, 10:03:35 am
Quote from: abit on August 22, 2015, 09:52:58 am
Run out of disk space :(
p2p.log too large.

Same here, p2p.log grows like 1Gb/h
have you tried setting log level from debug to info? I'll try it now.
On my side it's 4~5GB/h for one node. Hadn't had time to tweak the settings. Just mounted a larger partition, will try.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 22, 2015, 06:19:44 pm: Witness perky
{
"id": "1.6.3705",

running on a home network on a little cubox :)

Don't kill my little box testing the test net ;)
Title: Re: Test Net for Advanced Users
Post by: mudshark79 on August 22, 2015, 07:44:39 pm: Lol, my box was killed by logging also. Had a look this morning but thougth the space would last through the day but the logs from this afternoon were huge. serveral GBs per hour. Meanwhile blockchain seems "a bit" broken. Too tired to really look into it.... so 176.221.43.130:33323 is offline for now.
Title: Re: Test Net for Advanced Users
Post by: rnglab on August 22, 2015, 08:39:51 pm: Quote from: abit on August 22, 2015, 05:27:47 pm
Quote from: rnglab on August 22, 2015, 10:03:35 am
Quote from: abit on August 22, 2015, 09:52:58 am
Run out of disk space :(
p2p.log too large.

Same here, p2p.log grows like 1Gb/h
have you tried setting log level from debug to info? I'll try it now.
On my side it's 4~5GB/h for one node. Hadn't had time to tweak the settings. Just mounted a larger partition, will try.

setting log level from debug to info for [logger.p2p] reduced its size about an order of magnitude.

Code: [Select]
107M Aug 22 16:30 p2p.log 103M Aug 22 06:59 p2p.log.20150822T100000 183M Aug 22 07:59 p2p.log.20150822T110000 116M Aug 22 08:59 p2p.log.20150822T120000 101M Aug 22 09:59 p2p.log.20150822T130000 182M Aug 22 10:59 p2p.log.20150822T140000 137M Aug 22 11:59 p2p.log.20150822T150000 243M Aug 22 13:59 p2p.log.20150822T170000 390M Aug 22 14:59 p2p.log.20150822T180000 293M Aug 22 15:59 p2p.log.20150822T190000 107M Aug 22 16:30 p2p.log.20150822T200000
Title: Re: Test Net for Advanced Users
Post by: Thom on August 22, 2015, 08:55:50 pm: Quote from: fundomatic on August 22, 2015, 04:32:26 pm
Quote from: lafona on August 22, 2015, 04:16:52 pm
You can get the info on the current testnet here afaik: https://github.com/cryptonomex/graphene/releases/tag/test1

Thanks.

I got a few more things figured out, making another attempt to join in the fun.

Is the above where most are testing now? Where do you need an extra set of dev eyes to focus?

Are the download links on that github page the best way to get the code to compile, or is that another method to download a tagged commit from github similar to "git clone https://github.com/cryptonomex/graphene.git" only using a tag reference?
Title: Re: Test Net for Advanced Users
Post by: puppies on August 22, 2015, 09:00:32 pm: Quote from: Thom on August 22, 2015, 08:55:50 pm
Quote from: fundomatic on August 22, 2015, 04:32:26 pm
Quote from: lafona on August 22, 2015, 04:16:52 pm
You can get the info on the current testnet here afaik: https://github.com/cryptonomex/graphene/releases/tag/test1

Thanks.

I got a few more things figured out, making another attempt to join in the fun.

Is the above where most are testing now? Where do you need an extra set of dev eyes to focus?

Are the download links on that github page the best way to get the code to compile, or is that another method to download a tagged commit from github similar to "git clone https://github.com/cryptonomex/graphene.git" only using a tag reference?
git checkout test1
Title: Re: Test Net for Advanced Users
Post by: clout on August 22, 2015, 09:01:43 pm: I'm using the web GUI and trying to import keys. I was able to import the keys of a wallet json file that I downloaded from hosted wallet but I can't import the keys of my primary bitshares account from my local bitshares wallet. One of the wallet.json files I am using was recognized in prior versions of the GUI but is not recognized by the current version. Additionally, while the GUI previously recognized the wallet.json format it was not able to import keys or balances (this is a wallet with more than 500 keys and several short positions).
Title: Re: Test Net for Advanced Users
Post by: Thom on August 22, 2015, 09:47:26 pm: Quote from: puppies on August 22, 2015, 09:00:32 pm
Quote from: Thom on August 22, 2015, 08:55:50 pm
Quote from: fundomatic on August 22, 2015, 04:32:26 pm
Quote from: lafona on August 22, 2015, 04:16:52 pm
You can get the info on the current testnet here afaik: https://github.com/cryptonomex/graphene/releases/tag/test1

Thanks.

I got a few more things figured out, making another attempt to join in the fun.

Is the above where most are testing now? Where do you need an extra set of dev eyes to focus?

Are the download links on that github page the best way to get the code to compile, or is that another method to download a tagged commit from github similar to "git clone https://github.com/cryptonomex/graphene.git" only using a tag reference?
git checkout test1

Dog gone it puppies, not enough info. You tried to answer 1 question, but neglected to say if test1 is what I should be trying to run.

Remember, I'm not a git expert. I am using a slight variation of the Vagrant script to build, which is in part:

Code: [Select]
if [ ! -d "graphene" ]; then echo_msg "building bitshares graphene toolkit.." git clone https://github.com/cryptonomex/graphene.git cd graphene git submodule update --init --recursive cmake . make cd ~/bts2.0 fi
Changed it to:

Code: [Select]
#if [ ! -d "graphene" ]; then echo_msg "building bitshares graphene toolkit.." # git clone https://github.com/cryptonomex/graphene.git cd graphene git checkout test1 git submodule update --init --recursive cmake . make cd ~/bts2.0 #fi
which produces this error: pathspec 'test1' did not match any file(s) known to git.

Please help...
Title: Re: Test Net for Advanced Users
Post by: puppies on August 22, 2015, 09:54:36 pm: Quote from: Thom on August 22, 2015, 09:47:26 pm
Quote from: puppies on August 22, 2015, 09:00:32 pm
Quote from: Thom on August 22, 2015, 08:55:50 pm
Quote from: fundomatic on August 22, 2015, 04:32:26 pm
Quote from: lafona on August 22, 2015, 04:16:52 pm
You can get the info on the current testnet here afaik: https://github.com/cryptonomex/graphene/releases/tag/test1

Thanks.

I got a few more things figured out, making another attempt to join in the fun.

Is the above where most are testing now? Where do you need an extra set of dev eyes to focus?

Are the download links on that github page the best way to get the code to compile, or is that another method to download a tagged commit from github similar to "git clone https://github.com/cryptonomex/graphene.git" only using a tag reference?
git checkout test1

Dog gone it puppies, not enough info. You tried to answer 1 question, but neglected to say if test1 is what I should be trying to run.

Remember, I'm not a git expert. I am using a slight variation of the Vagrant script to build, which is in part:

Code: [Select]
if [ ! -d "graphene" ]; then echo_msg "building bitshares graphene toolkit.." git clone https://github.com/cryptonomex/graphene.git cd graphene git submodule update --init --recursive cmake . make cd ~/bts2.0 fi
Changed it to:

Code: [Select]
#if [ ! -d "graphene" ]; then echo_msg "building bitshares graphene toolkit.." # git clone https://github.com/cryptonomex/graphene.git cd graphene git checkout test1 git submodule update --init --recursive cmake . make cd ~/bts2.0 #fi
which produces this error: pathspec 'test1' did not match any file(s) known to git.

Please help...
I havent used the vagrant script myself. git checkout test1 is not a replacement for git clone, it is used after git clone and before git submodule update.
I think that this will work.
Code: [Select]
#if [ ! -d "graphene" ]; then echo_msg "building bitshares graphene toolkit.." git clone https://github.com/cryptonomex/graphene.git cd graphene git checkout test1 git submodule update --init --recursive cmake . make cd ~/bts2.0 #fi
Title: Re: Test Net for Advanced Users
Post by: Thom on August 22, 2015, 10:01:58 pm: Nope, that gave the same error.

The git clone does a fresh download if you don't have any source, it creates a local repository.

git checkout says update the local repository based on <whatever>, in this case the test1 branch/tag.

How are you building the code based on this "test1" tag?

Is the clone still necessary? Seems like the checkout should just update what was already cloned, rather than having to dl the whole repository again.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 22, 2015, 10:06:58 pm: to build from scratch should be
Code: [Select]
git clone https://github.com/cryptonomex/graphene.git cd graphene git checkout test1 git submodule update --init --recursive cmake . make
Title: Re: Test Net for Advanced Users
Post by: Thom on August 22, 2015, 10:13:09 pm: Then what you replied with should work I would think, they're about the same thing.

Could it be you're assuming I have more git privileges than I do? Like I say, I'm a git noob. I usually use clone. In working with wackou he explained how to make a duplicate repository, makes changes to it & submit a pull request for those changes to be incorporated into his repository I duplicated under my git account.

That's pretty much my level of knowlege.

Git is a tool, and I don't want to learn any more of it that I have to to get a job done.

The error I get is: "error: pathspec 'test1' did not match any file(s) known to git."
Title: Re: Test Net for Advanced Users
Post by: clout on August 22, 2015, 10:16:12 pm: Get this error:

Code: [Select]
10 assert_exception: Assert Exception operations.size() > 0: A transaction must have at least one operation {"trx":{"ref_block_num":0,"ref_block_prefix":0,"expiration":"1970-01-01T00:00:00","operations":[],"extensions":[]}} th_a transaction.cpp:51 validate {"name_or_id":"the-ae"} th_a wallet.cpp:2762 import_balance
when I try to import balance...
Title: Re: Test Net for Advanced Users
Post by: Thom on August 22, 2015, 10:16:27 pm: Wait a sec, when you say to build from scratch you mean in a new folder.

Ok, I bet THAT will work, but there ought to be a way to simply get what has changed and compile the changes.

I'll start from scratch instead. Thanks.

Building from scratch using the test1 checkout now. The time it takes to download the whole repository from scratch is minimal and not worth screwing around with trying to be "efficient" with source management.

In fact I'm not even going to build the gui just yet until I can get to the point where I can function as a witness in graphene. Hoping I understand enough of what's going on here to do that now but we'll see.

Using this in a new subdir:

Code: [Select]
if [ ! -d "graphene" ]; then echo_msg "building bitshares graphene toolkit test1..." git clone https://github.com/cryptonomex/graphene.git cd graphene git checkout test1 git submodule update --init --recursive cmake . make cd ~/bts2.0/aug20 fi
Title: Re: Test Net for Advanced Users
Post by: puppies on August 22, 2015, 10:48:48 pm: Quote from: clout on August 22, 2015, 10:16:12 pm
Get this error:

Code: [Select]
10 assert_exception: Assert Exception operations.size() > 0: A transaction must have at least one operation {"trx":{"ref_block_num":0,"ref_block_prefix":0,"expiration":"1970-01-01T00:00:00","operations":[],"extensions":[]}} th_a transaction.cpp:51 validate {"name_or_id":"the-ae"} th_a wallet.cpp:2762 import_balance
when I try to import balance...
pretty sure that means that key has no balance.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 22, 2015, 11:40:56 pm: I just fired up the witness node using abit's seed (114.92.254.159:62015) and this chain-id: d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083

Puppies, would you vote my witness in please? delegate.verbaltech

Thx!
Title: Re: Test Net for Advanced Users
Post by: cryptosile on August 23, 2015, 12:12:15 am: For building you can also try my docker build box:

Example for target build directory of ~/graphene
Code: [Select]
docker run -v ~:/build sile16/graphene-build test1
The source code for the build box can be inspected at:
https://github.com/sile16/bts2/tree/master/Docker/graphene-build (https://github.com/sile16/bts2/tree/master/Docker/graphene-build)

Also, can someone help me vote in my delegate everydaycrypto ? I don't have enough votes, thanks!
Title: Re: Test Net for Advanced Users
Post by: Thom on August 23, 2015, 12:27:22 am: Quote from: cryptosile on August 23, 2015, 12:12:15 am
For building you can also try my docker build box:

Example for target build directory of ~/graphene
Code: [Select]
docker run -v ~:/build sile16/graphene-build test1
The source code for the build box can be inspected at:
https://github.com/sile16/bts2/tree/master/Docker/graphene-build (https://github.com/sile16/bts2/tree/master/Docker/graphene-build)

Also, can someone help me vote in my delegate everydaycrypto ? I don't have enough votes, thanks!

I'm in a similar boat.

I managed to get a balance imported, and I voted for delegate.verbaltech. When I looked at the results it doesn't look like it took:

Code: [Select]
get_witness delegate.verbaltech { "id": "1.6.1621", "witness_account": "1.2.22408", "signing_key": "GPHxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "next_secret_hash": "ghfghfghfghfhfghfghfghfghf", "previous_secret": "0000000000000000000000000000000000000000", "vote_id": "1:1621", "total_votes": 0, "url": "" }
However, I changed the --private-key values for the witness to match the account I imported the balance into rather than those of the witness. I thought that was necessary to get the balance transfered, but all I think I really needed was the active_key for the balance transfer. So I will go back and replace the --private-key with the one for the witness and try again.

Also, I may need to wait for that maintenance interval to see the votes applied. Still foggy on many of these details.

Once I manage to get my delegate voted in I will vote yours in also. Apparently puppies isn't paying attention at the moment.

Edit: BTW, I tried to use docker as you suggested. I installed it with "apt-get install docker", seemed to go OK, no errors. Started a new shell, but there is no "docker" in the path, so I don't know what else I need to do to use it.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 23, 2015, 12:35:18 am: Dont know if this has already been found and fixed but my witness node died. I'll get it back up in a few minutes and vote those needing it.
Code: [Select]
{"new_block":{"previous":"0002a82166d023fa7d649b09e5d81098fb7bf60b","timestamp":"2015-08-22T22:21:18","witness":"1.6.27","next_secret_hash":"22230db1a0563e301b74c59ef7e1ff1612bff7b7","previous_secret":"9eabe79eb0d03d3c8630c0886c58462516913db4","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f1109216757ffd893766ca55fd2e8b6b870ce120eb8ac0b8d2b5fe308bb33b5441a3d8e49d7de51cad7163d71febab7eb119bf6cc1c0ca6a2bf9dfd29e85f879a","transactions":[]}} th_a db_block.cpp:176 _push_block 1279000ms th_a witness.cpp:240 block_production_loo ] slot: 66 scheduled_witness: 1.6.1526 scheduled_time: 2015-08-22T22:21:19 now: 2015-08-22T22:21:19 1279000ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.1526 production slot has arrived; generating a block now... Program received signal SIGSEGV, Segmentation fault. 0x0000000002851792 in SHA256_Update.part.0 () (gdb) bt second_branch_itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:186 fetch_branch_from {"first":"0002a822214f6038949b2585653866af1da863a3","second":"0002a7e8b9613cd334a36aeccdb1d32460d8fa53"} th_a fork_database.cpp:217 fetch_branch_from {"new_block":{"previous":"0002a82166d023fa7d649b09e5d81098fb7bf60b","timestamp":"2015-08-22T22:21:18","witness":"1.6.27","next_secret_hash":"22230db1a0563e301b74c59ef7e1ff1612bff7b7","previous_secret":"9eabe79eb0d03d3c8630c0886c58462516913db4","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f1109216757ffd893766ca55fd2e8b6b870ce120eb8ac0b8d2b5fe308bb33b5441a3d8e49d7de51cad7163d71febab7eb119bf6cc1c0ca6a2bf9dfd29e85f879a","transactions":[]}} th_a db_block.cpp:176 _push_block 1279000ms th_a witness.cpp:240 block_production_loo ] slot: 66 scheduled_witness: 1.6.1526 scheduled_time: 2015-08-22T22:21:19 now: 2015-08-22T22:21:19 1279000ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.1526 production slot has arrived; generating a block now... Program received signal SIGSEGV, Segmentation fault. 0x0000000002851792 in SHA256_Update.part.0 () (gdb) bt #0 0x0000000002851792 in SHA256_Update.part.0 () #1 0x0000000002851b29 in SHA224_Update () #2 0x0000000002574131 in fc::sha224::encoder::write (this=0x7ffff585a220, d=0x7ffff585a077 "\366\v", dlen=1) at /home/user/src/graphene/libraries/fc/src/crypto/sha224.cpp:43 #3 0x00000000023c4c99 in fc::raw::pack<fc::sha224::encoder> (s=..., v=...) at /home/user/src/graphene/libraries/fc/include/fc/io/raw.hpp:141 #4 0x00000000023c4f34 in fc::raw::detail::pack_object_visitor<fc::sha224::encoder, graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object> >::operator()<fc::unsigned_int, graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object>, &graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object>::instance> (this=0x7ffff585a0e0, name=0x29d9a9e "instance") at /home/user/src/graphene/libraries/fc/include/fc/io/raw.hpp:250 #5 0x00000000023c4eba in fc::reflector<graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object> >::visit<fc::raw::detail::pack_object_visitor<fc::sha224::encoder, graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object> > > ( visitor=...) at /home/user/src/graphene/libraries/db/include/graphene/db/object_id.hpp:143 #6 0x00000000023c4dbc in fc::raw::detail::if_enum<fc::false_type>::pack<fc::sha224::encoder, graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object> > (s=..., v=...) at /home/user/src/graphene/libraries/fc/include/fc/io/raw.hpp:296 #7 0x00000000023c4c38 in fc::raw::detail::if_reflected<fc::true_type>::pack<fc::sha224::encoder, graphene::db::object_id<(unsigned char)1, (unsigned char---Type <return> to continue, or q <return> to quit--- )6, graphene::chain::witness_object> > (s=..., v=...) at /home/user/src/graphene/libraries/fc/include/fc/io/raw.hpp:332 #8 0x00000000023c4adc in fc::raw::pack<fc::sha224::encoder, graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object> > (s=..., v=...) at /home/user/src/graphene/libraries/fc/include/fc/io/raw.hpp:478 #9 0x00000000023c481b in fc::raw::detail::pack_object_visitor<fc::sha224::encoder, graphene::chain::signed_block_header>::operator()<graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object>, graphene::chain::block_header, &graphene::chain::block_header::witness> ( this=0x7ffff585a1b0, name=0x29d9a40 "witness") at /home/user/src/graphene/libraries/fc/include/fc/io/raw.hpp:250 #10 0x00000000023c45a7 in fc::reflector<graphene::chain::block_header>::visit<fc::raw::detail::pack_object_visitor<fc::sha224::encoder, graphene::chain::signed_block_header> > (v=...) at /home/user/src/graphene/libraries/chain/include/graphene/chain/protocol/block.hpp:56 #11 0x00000000023c42e1 in fc::reflector<graphene::chain::signed_block_header>::visit<fc::raw::detail::pack_object_visitor<fc::sha224::encoder, graphene::chain::signed_block_header> > (v=...) at /home/user/src/graphene/libraries/chain/include/graphene/chain/protocol/block.hpp:58 #12 0x00000000023c40bc in fc::raw::detail::if_enum<fc::false_type>::pack<fc::sha224::encoder, graphene::chain::signed_block_header> (s=..., v=...) at /home/user/src/graphene/libraries/fc/include/fc/io/raw.hpp:296 #13 0x00000000023c3e06 in fc::raw::detail::if_reflected<fc::true_type>::pack<fc::sha224::encoder, graphene::chain::signed_block_header> (s=..., v=...) ---Type <return> to continue, or q <return> to quit--- at /home/user/src/graphene/libraries/fc/include/fc/io/raw.hpp:332 #14 0x00000000023c3a62 in fc::raw::pack<fc::sha224::encoder, graphene::chain::signed_block_header> (s=..., v=...) at /home/user/src/graphene/libraries/fc/include/fc/io/raw.hpp:478 #15 0x00000000023c37c4 in fc::sha224::hash<graphene::chain::signed_block_header> (t=...) at /home/user/src/graphene/libraries/fc/include/fc/crypto/sha224.hpp:29 #16 0x00000000023c2f97 in graphene::chain::signed_block_header::id ( this=0x7ffff585a360) at /home/user/src/graphene/libraries/chain/protocol/block.cpp:36 #17 0x000000000238b0ac in graphene::chain::fork_item::fork_item ( this=0x86a3858, d=...) at /home/user/src/graphene/libraries/chain/include/graphene/chain/fork_database.hpp:35 #18 0x0000000002392226 in __gnu_cxx::new_allocator<graphene::chain::fork_item>::construct<graphene::chain::fork_item<graphene::chain::signed_block const&> > (this=0x7ffff585a54f, __p=0x86a3858) at /usr/include/c++/4.8/ext/new_allocator.h:120 #19 0x0000000002392045 in std::allocator_traits<std::allocator<graphene::chain::fork_item> >::_S_construct<graphene::chain::fork_item<graphene::chain::signed_block const&> >(std::allocator<graphene::chain::fork_item>&, std::allocator_traits<std::allocator<graphene::chain::fork_item> >::__construct_helper*, (graphene::chain::fork_item<graphene::chain::signed_block const&>&&)...) ( __a=..., __p=0x86a3858) at /usr/include/c++/4.8/bits/alloc_traits.h:254 #20 0x0000000002391f9d in std::allocator_traits<std::allocator<graphene::chain::fork_item> >::construct<graphene::chain::fork_item<graphene::chain::signed_block const&> >(std::allocator<graphene::chain::fork_item>&, graphene::chain---Type <return> to continue, or q <return> to quit--- ::fork_item<graphene::chain::signed_block const&>*, (graphene::chain::fork_item<graphene::chain::signed_block const&>&&)...) (__a=..., __p=0x86a3858) at /usr/include/c++/4.8/bits/alloc_traits.h:393 #21 0x0000000002391bce in std::_Sp_counted_ptr_inplace<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, (__gnu_cxx::_Lock_policy)2>::_Sp_counted_ptr_inplace<graphene::chain::signed_block const&> ( this=0x86a3840, __a=...) at /usr/include/c++/4.8/bits/shared_ptr_base.h:399 #22 0x0000000002390f37 in __gnu_cxx::new_allocator<std::_Sp_counted_ptr_inplace<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, (__gnu_cxx::_Lock_policy)2> >::construct<std::_Sp_counted_ptr_inplace<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, (__gnu_cxx::_Lock_policy)2><std::allocator<graphene::chain::fork_item> const, graphene::chain::signed_block const&> > (this=0x7ffff585a627, __p=0x86a3840) at /usr/include/c++/4.8/ext/new_allocator.h:120 #23 0x00000000023902dd in std::allocator_traits<std::allocator<std::_Sp_counted_ptr_inplace<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, (__gnu_cxx::_Lock_policy)2> > >::_S_construct<std::_Sp_counted_ptr_inplace<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, (__gnu_cxx::_Lock_policy)2><std::allocator<graphene::chain::fork_item> const, graphene::chain::signed_block const&> >(std::allocator<std::_Sp_counted_ptr_inplace<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, (__gnu_cxx::_Lock_policy)2> >&, std::allocator_traits<std::allocator<std::_Sp_counted_ptr_inplace<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, (__gnu_cxx::_Lock_policy)2> > >::__construct_helper*, (std::_Sp_counted_ptr_inplace<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, (__gnu_cxx::_Lock_policy)2><std::allocator<graphene::---Type <return> to continue, or q <return> to quit--- chain::fork_item> const, graphene::chain::signed_block const&>&&)...) ( __a=..., __p=0x86a3840) at /usr/include/c++/4.8/bits/alloc_traits.h:254 #24 0x000000000238f9ae in std::allocator_traits<std::allocator<std::_Sp_counted_ptr_inplace<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, (__gnu_cxx::_Lock_policy)2> > >::construct<std::_Sp_counted_ptr_inplace<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, (__gnu_cxx::_Lock_policy)2><std::allocator<graphene::chain::fork_item> const, graphene::chain::signed_block const&> >(std::allocator<std::_Sp_counted_ptr_inplace<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, (__gnu_cxx::_Lock_policy)2> >&, std::_Sp_counted_ptr_inplace<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, (__gnu_cxx::_Lock_policy)2><std::allocator<graphene::chain::fork_item> const, graphene::chain::signed_block const&>*, (std::_Sp_counted_ptr_inplace<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, (__gnu_cxx::_Lock_policy)2><std::allocator<graphene::chain::fork_item> const, graphene::chain::signed_block const&>&&)...) (__a=..., __p=0x86a3840) at /usr/include/c++/4.8/bits/alloc_traits.h:393 #25 0x000000000238f29f in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::__shared_count<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, graphene::chain::signed_block const&> (this=0x7ffff585a808, __a=...) at /usr/include/c++/4.8/bits/shared_ptr_base.h:502 #26 0x000000000238e832 in std::__shared_ptr<graphene::chain::fork_item, (__gnu_cxx::_Lock_policy)2>::__shared_ptr<std::allocator<graphene::chain::fork_item>, graphene::chain::signed_block const&> (this=0x7ffff585a800, __tag=..., __a=...) at /usr/include/c++/4.8/bits/shared_ptr_base.h:957 #27 0x000000000238d76a in std::shared_ptr<graphene::chain::fork_item>::shared_ptr<std::allocator<graphene::chain::fork_item>, graphene::chain::signed_bloc---Type <return> to continue, or q <return> to quit--- k const&> (this=0x7ffff585a800, __tag=..., __a=...) at /usr/include/c++/4.8/bits/shared_ptr.h:316 #28 0x000000000238c683 in std::allocate_shared<graphene::chain::fork_item, std::allocator<graphene::chain::fork_item>, graphene::chain::signed_block const&> (__a=...) at /usr/include/c++/4.8/bits/shared_ptr.h:598 #29 0x000000000238b9e3 in std::make_shared<graphene::chain::fork_item, graphene::chain::signed_block const&> () at /usr/include/c++/4.8/bits/shared_ptr.h:614 #30 0x0000000002387bd9 in graphene::chain::fork_database::push_block ( this=0x39b0200, b=...) at /home/user/src/graphene/libraries/chain/fork_database.cpp:51 #31 0x00000000021d15ca in graphene::chain::database::_push_block ( this=0x39b0018, new_block=...) at /home/user/src/graphene/libraries/chain/db_block.cpp:103 #32 0x00000000021d14e9 in graphene::chain::database::__lambda15::operator() (__closure=0x7ffff585aba0) at /home/user/src/graphene/libraries/chain/db_block.cpp:90 #33 0x00000000021f304f in graphene::chain::database::with_skip_flags<graphene::chain::database::push_block(const graphene::chain::signed_block&, uint32_t)::__lambda15>(uint32_t, graphene::chain::database::__lambda15) ( this=0x39b0018, skip_flags=0, callback=...) at /home/user/src/graphene/libraries/chain/include/graphene/chain/database.hpp:285 #34 0x00000000021d1548 in graphene::chain::database::push_block ( this=0x39b0018, new_block=..., skip=0) at /home/user/src/graphene/libraries/chain/db_block.cpp:91 #35 0x00000000021d498f in graphene::chain::database::_generate_block ( this=0x39b0018, when=..., witness_id=..., block_signing_private_key=...) at /home/user/src/graphene/libraries/chain/db_block.cpp:299 #36 0x00000000021d4a7e in graphene::chain::database::_generate_block ( this=0x39b0018, when=..., witness_id=..., block_signing_private_key=...) at /home/user/src/graphene/libraries/chain/db_block.cpp:312 #37 0x00000000021d4a7e in graphene::chain::database::_generate_block ( this=0x39b0018, when=..., witness_id=..., block_signing_private_key=...) at /home/user/src/graphene/libraries/chain/db_block.cpp:312 #38 0x00000000021d4a7e in graphene::chain::database::_generate_block ( this=0x39b0018, when=..., witness_id=..., block_signing_private_key=...) at /home/user/src/graphene/libraries/chain/db_block.cpp:312 #39 0x00000000021d4a7e in graphene::chain::database::_generate_block ( this=0x39b0018, when=..., witness_id=..., block_signing_private_key=...) at /home/user/src/graphene/libraries/chain/db_block.cpp:312 #40 0x00000000021d4a7e in graphene::chain::database::_generate_block ( this=0x39b0018, when=..., witness_id=..., block_signing_private_key=...) at /home/user/src/graphene/libraries/chain/db_block.cpp:312 #41 0x00000000021d4a7e in graphene::chain::database::_generate_block ( this=0x39b0018, when=..., witness_id=..., block_signing_private_key=...) at /home/user/src/graphene/libraries/chain/db_block.cpp:312 #42 0x00000000021d4a7e in graphene::chain::database::_generate_block ( this=0x39b0018, when=..., witness_id=..., block_signing_private_key=...) at /home/user/src/graphene/libraries/chain/db_block.cpp:312 #43 0x00000000021d4a7e in graphene::chain::database::_generate_block ( this=0x39b0018, when=..., witness_id=..., block_signing_private_key=...) at /home/user/src/graphene/libraries/chain/db_block.cpp:312 #44 0x00000000021d4a7e in graphene::chain::database::_generate_block (
Title: Re: Test Net for Advanced Users
Post by: Thom on August 23, 2015, 12:40:12 am: Kewlness. Please vote me in, I'm up and running now.

everydaycrypto, I tried to vote you in with my 50K BTS balance but the wallet said everydaycrypto is not registered as a witness.

Puppies, I was under the impression it didn't take much of a balance to vote witnesses in on this test net. Isn't 50K BTS (CORE?) enough, or is it that the maintenance interval must pass to accumulate the votes and I haven't waited long enough yet?

Quote from: puppies on August 23, 2015, 12:35:18 am
Dont know if this has already been found and fixed but my witness node died. I'll get it back up in a few minutes and vote those needing it.
Code: [Select]
{"new_block":{"previous":"0002a82166d023fa7d649b09e5d81098fb7bf60b","timestamp":"2015-08-22T22:21:18","witness":"1.6.27","next_secret_hash":"22230db1a0563e301b74c59ef7e1ff1612bff7b7","previous_secret":"9eabe79eb0d03d3c8630c0886c58462516913db4","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f1109216757ffd893766ca55fd2e8b6b870ce120eb8ac0b8d2b5fe308bb33b5441a3d8e49d7de51cad7163d71febab7eb119bf6cc1c0ca6a2bf9dfd29e85f879a","transactions":[]}} th_a db_block.cpp:176 _push_block 1279000ms th_a witness.cpp:240 block_production_loo ] slot: 66 scheduled_witness: 1.6.1526 scheduled_time: 2015-08-22T22:21:19 now: 2015-08-22T22:21:19 1279000ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.1526 production slot has arrived; generating a block now... Program received signal SIGSEGV, Segmentation fault. 0x0000000002851792 in SHA256_Update.part.0 () (gdb) bt second_branch_itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:186 fetch_branch_from {"first":"0002a822214f6038949b2585653866af1da863a3","second":"0002a7e8b9613cd334a36aeccdb1d32460d8fa53"} th_a fork_database.cpp:217 fetch_branch_from {"new_block":{"previous":"0002a82166d023fa7d649b09e5d81098fb7bf60b","timestamp":"2015-08-22T22:21:18","witness":"1.6.27","next_secret_hash":"22230db1a0563e301b74c59ef7e1ff1612bff7b7","previous_secret":"9eabe79eb0d03d3c8630c0886c58462516913db4","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f1109216757ffd893766ca55fd2e8b6b870ce120eb8ac0b8d2b5fe308bb33b5441a3d8e49d7de51cad7163d71febab7eb119bf6cc1c0ca6a2bf9dfd29e85f879a","transactions":[]}} th_a db_block.cpp:176 _push_block 1279000ms th_a witness.cpp:240 block_production_loo ] slot: 66 scheduled_witness: 1.6.1526 scheduled_time: 2015-08-22T22:21:19 now: 2015-08-22T22:21:19 1279000ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.1526 production slot has arrived; generating a block now... Program received signal SIGSEGV, Segmentation fault. 0x0000000002851792 in SHA256_Update.part.0 () (gdb) bt #0 0x0000000002851792 in SHA256_Update.part.0 () #1 0x0000000002851b29 in SHA224_Update () #2 0x0000000002574131 in fc::sha224::encoder::write (this=0x7ffff585a220, d=0x7ffff585a077 "\366\v", dlen=1) at /home/user/src/graphene/libraries/fc/src/crypto/sha224.cpp:43 #3 0x00000000023c4c99 in fc::raw::pack<fc::sha224::encoder> (s=..., v=...) at /home/user/src/graphene/libraries/fc/include/fc/io/raw.hpp:141 #4 0x00000000023c4f34 in fc::raw::detail::pack_object_visitor<fc::sha224::encoder, graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object> >::operator()<fc::unsigned_int, graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object>, &graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object>::instance> (this=0x7ffff585a0e0, name=0x29d9a9e "instance") at /home/user/src/graphene/libraries/fc/include/fc/io/raw.hpp:250 #5 0x00000000023c4eba in fc::reflector<graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object> >::visit<fc::raw::detail::pack_object_visitor<fc::sha224::encoder, graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object> > > ( visitor=...) at /home/user/src/graphene/libraries/db/include/graphene/db/object_id.hpp:143 #6 0x00000000023c4dbc in fc::raw::detail::if_enum<fc::false_type>::pack<fc::sha224::encoder, graphene::db::object_id<(unsigned char)1, (unsigned char)6, graphene::chain::witness_object> > (s=..., v=...) at /home/user/src/graphene/libraries/fc/include/fc/io/raw.hpp:296 #7 0x00000000023c4c38 in fc::raw::detail::if_reflected<fc::true_type>::pack<fc::sha224::encoder, graphene::db::object_id<(unsigned char)1, (unsigned char---Type <return> to continue, or q <return> to quit---
Title: Re: Test Net for Advanced Users
Post by: puppies on August 23, 2015, 12:47:19 am: You do have to wait for the maintenance period. 50k is plenty.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 23, 2015, 12:53:52 am: Dang, shit keeps changing!

I had to restart the witness after I saw the witness-id for delegate.verbaltech changed. Is that b/c of the different genesis block? I'm using the aug-20th gen. blk now, with d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083 and seed node=104.200.28.117:61705.

After that I had to go thru the rig-a-ma-role of importing the balance all over again. SO, if the above params are correct whenever that maintenance interval passes I should be voted in.

What's the api call to chk if I'm producing blocks?

will the total_votes go up in this api call after the maintenance interval passes? I just looked for dele-puppy and it's still shows total_votes as 0.

Code: [Select]
get_witness delegate.verbaltech { "id": "1.6.1621", "witness_account": "1.2.22408", "signing_key": "GPHxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "next_secret_hash": "556678686970979675674876785---jhjbvth, "previous_secret": "0000000000000000000000000000000000000000", "vote_id": "1:1621", "total_votes": 0, <---------------- will this change? "url": "" }
Title: Re: Test Net for Advanced Users
Post by: Thom on August 23, 2015, 01:15:20 am: Well, I believe I've FINALLY jumped through all the hurdles to start producing blocks, assuming 50K CORE is enough AND all of the parameters are correct like chain-id, genesis block, seed node.......

It makes my head spin!

If all the required params were posted whenever they change (and perhaps a reference to them every other page or so) it would be a hell of a lot easier to get involved with this testing effort.

But then I guess I'm slow in learning that abrupt / unannounced changes are par for the course around here.

Just noticed this from the info API call:
Code: [Select]
info { "head_block_num": 0, "head_block_id": "0000000000000000000000000000000000000000", "head_block_age": "5 days old", "next_maintenance_time": "45 years ago", <----------------------------- Does this mean there will not be another one to apply the votes I cast???????? "chain_id": "d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083",
BTW, until I started trying to get involved with this testing I never heard anyone mention the terms "committee member" or CORE asset. When did these get added to the BitShares buzzwords?
Title: Re: Test Net for Advanced Users
Post by: Thom on August 23, 2015, 01:22:14 am: I'm going to leave my witness node running until tomorrow, but I'n tired of waiting for puppies to vote me in or for the maintenance interval to pass that should do the same.

I'll have to try again Monday.

Good luck to your efforts puppies!
Title: Re: Test Net for Advanced Users
Post by: abit on August 23, 2015, 02:28:53 am: Quote from: Thom on August 23, 2015, 12:53:52 am
Dang, shit keeps changing!

I had to restart the witness after I saw the witness-id for delegate.verbaltech changed. Is that b/c of the different genesis block? I'm using the aug-20th gen. blk now, with d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083 and seed node=104.200.28.117:61705.

After that I had to go thru the rig-a-ma-role of importing the balance all over again. SO, if the above params are correct whenever that maintenance interval passes I should be voted in.

What's the api call to chk if I'm producing blocks?

will the total_votes go up in this api call after the maintenance interval passes? I just looked for dele-puppy and it's still shows total_votes as 0.

Code: [Select]
get_witness delegate.verbaltech { "id": "1.6.1621", "witness_account": "1.2.22408", "signing_key": "GPHxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "next_secret_hash": "556678686970979675674876785---jhjbvth, "previous_secret": "0000000000000000000000000000000000000000", "vote_id": "1:1621", "total_votes": 0, <---------------- will this change? "url": "" }
See https://github.com/cryptonomex/graphene/releases

Code: [Select]
./witness_node -s "104.236.51.238:1776" --genesis-json aug-20-test-genesis.json ./cli_wallet --chain-id d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083
Title: Re: Test Net for Advanced Users
Post by: abit on August 23, 2015, 02:37:40 am: Quote from: Thom on August 23, 2015, 01:22:14 am
I'm going to leave my witness node running until tomorrow, but I'n tired of waiting for puppies to vote me in or for the maintenance interval to pass that should do the same.

I'll have to try again Monday.

Good luck to your efforts puppies!
You've been voted in. 8)
Title: Re: Test Net for Advanced Users
Post by: Thom on August 23, 2015, 04:22:14 am: Thanks for the info abit. Did you vote me in or did you just observe it was so?

If you haven't noticed by now I'm full of questions. Being voted in will last until the next test or code revision, or ? At which time one must run thru the process of balance import and getting voted in right?

I just tried to check the node to see if I could find evidence it was producing blocks or was voted in but could not figure out how.

I did a forum search for "voted in" and "producing blocks" and of all the messages that had those phrases NOT ONE gave an API call or method for checking those things. Nice communication there folks. Real nice :(
Title: Re: Test Net for Advanced Users
Post by: puppies on August 23, 2015, 05:01:24 am: Quote from: Thom on August 23, 2015, 04:22:14 am
Thanks for the info abit. Did you vote me in or did you just observe it was so?

If you haven't noticed by now I'm full of questions. Being voted in will last until the next test or code revision, or ? At which time one must run thru the process of balance import and getting voted in right?

I just tried to check the node to see if I could find evidence it was producing blocks or was voted in but could not figure out how.

I did a forum search for "voted in" and "producing blocks" and of all the messages that had those phrases NOT ONE gave an API call or method for checking those things. Nice communication there folks. Real nice :(
You will stay voted in until we start a new chain, at which point you will need to import your keys again, and get voted in again.

I don't know of any direct way to check witness statistics. Some alternatives are to watch the wtiness_node, and watch for your delegate number going by. or in the cli wallet you can use the get_witness command and look at the previous secret, and the next secret hash readouts. Those two entries will change every time you generate a block. (if anyone else has a good way of checking I would appreciate it.)

I understand you are frustrated with the information being spread out throughout this thread. I have been responding to this thread mostly from work, typing on a cellphone, and have not have the time nor the wherewithal to collect everything into a single post.
Title: Re: Test Net for Advanced Users
Post by: bitcard on August 23, 2015, 06:23:09 am: the test url is broken?
Title: Re: Test Net for Advanced Users
Post by: Thom on August 23, 2015, 06:50:06 am: Quote from: puppies on August 23, 2015, 05:01:24 am
I understand you are frustrated with the information being spread out throughout this thread. I have been responding to this thread mostly from work, typing on a cellphone, and have not have the time nor the wherewithal to collect everything into a single post.

You and xeroc have been the more helpful ones here puppies. Xeroc mostly via PMs. A few others here and there.

I do understand your constraints related to your work environment, and I don't expect anyone to consolidate the posts in this lengthy thread. However, given the effort I see put forth here to post various things, it would only take slightly more effort for (anyone participating) to post the essential parameters when they change.

TBH some of the frustrations I've experienced are my own internal "demons", so for that I offer my apologies. My style of learning usually involves asking a lot of questions which can be annoying to some people, and may put them off from answering them. Sometimes I can figure things out on my own but often I can't.

Since Wednesday this week I have also had many interruptions which has interfered with my ability to stay focused all day. When I am involved it has been later in the day when many are probably ramping down their efforts.

Thus there are several contributing factors to the difficulties I've had.

Going forward if the essential parameters (genesis json, chain-id, src code used [i.e. test1 etc], and seed node IP) are posted in the forum at least whenever any of them change it would help tremendously in being able to get on the same page.

I feel like I've learned a lot today and can now successfully import a 0.9.2 balance. It wasn't clear to me that could be done for any registered 0.9.2 account (I didn't see any explanation of what 0.9.2 accounts were included in this test net, presumably in the genesis json file?). I figured it out experimentally today. I believe I was able to vote my delegate in, but not sure about that yet. I didn't get any errors from the API calls, and they did return a json object, but I also never performed any "lifetime member" upgrade either. abit said I was voted in, but not sure how he knows that and I'm not sure if it was me or some else that made that happen.

So despite my sense that I have learned much there are still some basic gaps in my understanding. I'm sure I'm not the only one, I just happen to be more vocal about expressing them I guess.
Title: Re: Test Net for Advanced Users
Post by: betax on August 23, 2015, 08:01:04 am: Full Instructions for Test 1, maybe the op can change.. or we can start a new thread changing the nodes / chain id so is easier for everyone to start / get started again.

It is a summary of everyone findings in this thread, so credit to everyone. (@puppies, @abit, @clayop, @maqifrnswa, @lafona, @IHashfury, @Riverhead, @testz, @cryptosile, @Thom) plus of course @xeroc original tutorials, and help here.

I have published this now on the Wiki: https://github.com/cryptonomex/graphene/wiki/How-to-setup-your-witness-for-test-net-(Ubuntu-14.04)

Installation of dependencies
Extracted from xerocs instructions here: https://github.com/cryptonomex/graphene/wiki/build-ubuntu
If you already have done your installation move to next step.

Code: [Select]
sudo apt-get updateInstall gcc-49 etc
Code: [Select]
sudo apt-get install gcc-4.9 g++-4.9 cmake make libbz2-dev libdb++-dev libdb-dev libssl-dev openssl libreadline-dev autoconf libtool gitIf you cannot install gcc-4.9, you will need to add this repository before hand and try again.
Code: [Select]
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
Installation of BOOST
Code: [Select]
BOOST_ROOT=$HOME/opt/boost_1_57_0 sudo apt-get update sudo apt-get install autotools-dev build-essential g++ libbz2-dev libicu-dev python-dev wget -c 'http://sourceforge.net/projects/boost/files/boost/1.57.0/boost_1_57_0.tar.bz2/download' -O boost_1_57_0.tar.bz2 [ $( sha256sum boost_1_57_0.tar.bz2 | cut -d ' ' -f 1 ) == "910c8c022a33ccec7f088bd65d4f14b466588dda94ba2124e78b8c57db264967" ] || ( echo 'Corrupt download' ; exit 1 ) tar xjf boost_1_57_0.tar.bz2 cd boost_1_57_0/ ./bootstrap.sh "--prefix=$BOOST_ROOT" ./b2 install
Git checkout and build
Ensure your boost path is correct
Code: [Select]
BOOST_ROOT=$HOME/opt/boost_1_57_0Check out and build
Code: [Select]
cd ~ git clone https://github.com/cryptonomex/graphene.git cd graphene
Check out test 1 (specific to this chain)
Code: [Select]
git checkout test1
Code: [Select]
git submodule update --init --recursive cmake -DBOOST_ROOT="$BOOST_ROOT" -DCMAKE_BUILD_TYPE=Debug . make
Setup witness / import balances

2. Go to the witness directory:
Code: [Select]
cd ~/graphene/programs/witness_node
3. Download genesis Path specific for Test 1
Code: [Select]
wget https://github.com/cryptonomex/graphene/releases/download/test1/aug-20-test-genesis.json
4.Start a new terminal screen
Code: [Select]
screen5. Run the witness Current nodes for test 1 (replace for other tests)
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-20-test-genesis.json -d test_net_1 -s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015"
Note:
-d parameter is for the directory you want the witness data to be stored
-s is the node you want to connect

If you have problems, you might need to put the whole path for the genesis
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json ~/graphene/programs/witness-node/aug-20-test-genesis.json -d test_net_1 -s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015"

6. Detach from screen
Code: [Select]
Ctrl A Ctrl D7. Extract your wif keys for user and balances as per xeroc's instructions https://github.com/cryptonomex/graphene/wiki/Howto-become-an-active-witness-in-BitShares-2.0
8. Navigate to cli_wallet
Code: [Select]
cd ~/graphene/programs/cli_wallet9. Run cli Current chain id for test 1
Code: [Select]
./cli_wallet -w test_wallet_puppies --chain-id d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083Note:
-w is your directory wallet
10. Setup witness as per xerocs instructions https://github.com/cryptonomex/graphene/wiki/Howto-become-an-active-witness-in-BitShares-2.0
Remember to copy your keys, witness id
Note you need to wait for a maintenance period to be voted in
11. Exit
12. Go back to your witness terminal
Code: [Select]
screen -r 13. Exit your witness ctrl c
14. Restart with parameters to start block producing (block producing needs your witness id and private keys) Current nodes for test 1 (replace for other tests)
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-20-test-genesis.json -d test_net_1 -s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015" --witness-id '"1.6.5156"' --private-key '["GPH6JhL..your.signing.key..bc5mWyCvERV3coy","5K..your.secret..a"]'15. See your witness producing blocks and
you can Ctrl A Ctrl D to detach from screen.

Edit: As per abit's comments adding other nodes, correcting genesis in last step.
Title: Re: Test Net for Advanced Users
Post by: cass on August 23, 2015, 10:43:58 am: great tut @betax - thx for sharing !
Title: Re: Test Net for Advanced Users
Post by: abit on August 23, 2015, 12:18:23 pm: Quote from: betax on August 23, 2015, 08:01:04 am
14. Restart with parameters to start block producing (block producing needs your witness id and private keys) Current node abit's for test 1
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-14-test-genesis.json -d test_net_1 -s 114.92.254.159:62015 --witness-id '"1.6.5156"' --private-key '["GPH6JhL..your.signing.key..bc5mWyCvERV3coy","5K..your.secret..a"]'15. See your witness producing blocks and
you can Ctrl A Ctrl D to detach from screen.
Thanks for sharing, but don't use my node(at least not only use my node), it breaks now and then.
And the genesis file in step 14 should be aug-20-test-genesis.json.

Here is a list of nodes I'm using (still breaks sometimes):
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-20-test-genesis.json -d test_net_1 -s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015"
Title: Re: Test Net for Advanced Users
Post by: liondani on August 23, 2015, 12:21:50 pm: thanks @betax for the nice tutorial!

@bytemaster
betax deserves some Brownies for the tutorial about how to install a Graphene node. Please send him some extra Brownies. I am sure everybody here aggrees with that.
Title: Re: Test Net for Advanced Users
Post by: spartako on August 23, 2015, 12:52:35 pm: Just back from holiday and I have good internet connection now.

I followed various tutorial (thanks @betax for your tutorial, deserves Brownies) and now I have spartako witness ready:

Code: [Select]
get_witness spartako { "id": "1.6.4231", "witness_account": "1.2.72727",
I voted for myself but I don't see it in the current active witness list, please someone give me some love ;)

There is a command where I can see the blocks produced by a witness and the missed blocks?
Title: Re: Test Net for Advanced Users
Post by: puppies on August 23, 2015, 01:30:28 pm: That's odd spartako I see
Code: [Select]
ocked >>> get_witness spartako get_witness spartako { "id": "1.6.4231", "witness_account": "1.2.72727", "signing_key": "GPH5mgup8evDqMnT86L7scVebRYDC2fwAWmygPEUL43LjstQegYCC", "next_secret_hash": "7933c3cad5ce7cf05646dd36a4da6882fbd74255", "previous_secret": "311664bc1ac2a3accdc31761f36835c9c985b1e2", "pay_vb": "1.13.185", "vote_id": "1:4231", "total_votes": "64999598829", "url": ""
But I don't see you in info. I do see double representations of 1.6.1526 1530 1537 and 1595 so maybe it's a display issue.

In regards to checking witness stats. I don't think there is currently a way to see them directly. You can use the get_witness command to check that the next secret hash and previous secret are changing. Watch your witness node for your witness number or use the gui and go to the block explorer page.

Also great job betax, and thanks for the nodes abit.
Title: Re: Test Net for Advanced Users
Post by: spartako on August 23, 2015, 01:49:06 pm: Quote from: puppies on August 23, 2015, 01:30:28 pm
That's odd spartako I see
Code: [Select]
ocked >>> get_witness spartako get_witness spartako { "id": "1.6.4231", "witness_account": "1.2.72727", "signing_key": "GPH5mgup8evDqMnT86L7scVebRYDC2fwAWmygPEUL43LjstQegYCC", "next_secret_hash": "7933c3cad5ce7cf05646dd36a4da6882fbd74255", "previous_secret": "311664bc1ac2a3accdc31761f36835c9c985b1e2", "pay_vb": "1.13.185", "vote_id": "1:4231", "total_votes": "64999598829", "url": ""
But I don't see you in info. I do see double representations of 1.6.1526 1530 1537 and 1595 so maybe it's a display issue.

I have removed my votes and voted again and now I can see in info, probably a display issue.

Quote from: puppies on August 23, 2015, 01:30:28 pm
In regards to checking witness stats. I don't think there is currently a way to see them directly. You can use the get_witness command to check that the next secret hash and previous secret are changing. Watch your witness node for your witness number or use the gui and go to the block explorer page.

Also great job betax, and thanks for the nodes abit.

Ok, interesting tricks ;)

Thanks puppies!!!
Title: Re: Test Net for Advanced Users
Post by: cryptosile on August 23, 2015, 01:53:07 pm: if the --resync-blockchain is specified, does that prevent the witness form signing blocks? I coudn't get my witness to start signed by then tried removing that and it seemed to work. Also, if it has to resync from scratch (like empty folder) then it also doesn't seem to sign blocks. Not 100% sure but it seems I have to:

get the witiness all synced up.. then shutdown gracefully with a ^C (which doesn't always work btw, it sometimes says DB is corrupt and restarts from scratch) , then start it again , at which point it then starts to sign blocks.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 23, 2015, 02:11:23 pm: Quote from: cryptosile on August 23, 2015, 01:53:07 pm
if the --resync-blockchain is specified, does that prevent the witness form signing blocks? I coudn't get my witness to start signed by then tried removing that and it seemed to work. Also, if it has to resync from scratch (like empty folder) then it also doesn't seem to sign blocks. Not 100% sure but it seems I have to:

get the witiness all synced up.. then shutdown gracefully with a ^C (which doesn't always work btw, it sometimes says DB is corrupt and restarts from scratch) , then start it again , at which point it then starts to sign blocks.
I've seen that issue, but it's not 100%. For example dele-puppy is currently producing blocks and was launched with a --resync-blockchain. I seem to have noticed it more on my home networked boxes.
Title: Re: Test Net for Advanced Users
Post by: Xeldal on August 23, 2015, 02:28:47 pm: Are existing 0.9.2 delegates automatically imported as a witness or is it required to upgrade and create witness object? I'm hoping to skip sorting through the hundreds of balance id's for a proper balance that also existed on the 20th.

Thank you betax, your guide was very helpful. +5%
Title: Re: Test Net for Advanced Users
Post by: puppies on August 23, 2015, 02:34:43 pm: Quote from: Xeldal on August 23, 2015, 02:28:47 pm
Are existing 0.9.2 delegates automatically imported as a witness or is it required to upgrade and create witness object? I'm hoping to skip sorting through the hundreds of balance id's for a proper balance that also existed on the 20th.

Thank you betax, your guide was very helpful. +5%

All existing delegates are imported as witnesses. When you get your node set up let us know and we will vote you in.
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 23, 2015, 03:13:24 pm: @betax: could you put your tutorial into the github wiki please? If not, may I do it for you?
Title: Re: Test Net for Advanced Users
Post by: Xeldal on August 23, 2015, 03:21:59 pm: Quote from: puppies on August 23, 2015, 02:34:43 pm
Quote from: Xeldal on August 23, 2015, 02:28:47 pm
Are existing 0.9.2 delegates automatically imported as a witness or is it required to upgrade and create witness object? I'm hoping to skip sorting through the hundreds of balance id's for a proper balance that also existed on the 20th.

Thank you betax, your guide was very helpful. +5%

All existing delegates are imported as witnesses. When you get your node set up let us know and we will vote you in.

I believe I'm up now. ID: 1.6.1624
Title: Re: Test Net for Advanced Users
Post by: puppies on August 23, 2015, 03:28:49 pm: Quote from: Xeldal on August 23, 2015, 03:21:59 pm
Quote from: puppies on August 23, 2015, 02:34:43 pm
Quote from: Xeldal on August 23, 2015, 02:28:47 pm
Are existing 0.9.2 delegates automatically imported as a witness or is it required to upgrade and create witness object? I'm hoping to skip sorting through the hundreds of balance id's for a proper balance that also existed on the 20th.

Thank you betax, your guide was very helpful. +5%

All existing delegates are imported as witnesses. When you get your node set up let us know and we will vote you in.

I believe I'm up now. ID: 1.6.1624
seems I don't have my owner key imported into my vps. I won't be able to vote till after work. I'm sure someone else will vote you in.
Code: [Select]
0 exception: unspecified 3030001 tx_missing_active_auth: missing required active authority Missing Active Authority 1.2.63353
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 23, 2015, 04:11:29 pm: Quote from: puppies on August 23, 2015, 03:28:49 pm
Quote from: Xeldal on August 23, 2015, 03:21:59 pm
Quote from: puppies on August 23, 2015, 02:34:43 pm
Quote from: Xeldal on August 23, 2015, 02:28:47 pm
Are existing 0.9.2 delegates automatically imported as a witness or is it required to upgrade and create witness object? I'm hoping to skip sorting through the hundreds of balance id's for a proper balance that also existed on the 20th.

Thank you betax, your guide was very helpful. +5%

All existing delegates are imported as witnesses. When you get your node set up let us know and we will vote you in.

I believe I'm up now. ID: 1.6.1624
seems I don't have my owner key imported into my vps. I won't be able to vote till after work. I'm sure someone else will vote you in.
Code: [Select]
0 exception: unspecified 3030001 tx_missing_active_auth: missing required active authority Missing Active Authority 1.2.63353
You may need to import the ACTIVE_KEY too!
Title: Re: Test Net for Advanced Users
Post by: lafona on August 23, 2015, 04:28:50 pm: Has anyone found a way to reduce the log size? Right now I have a loop running to delete the old logs, but I imagine there must be a setting somewhere. I have tried
Code: [Select]
cmake . instead of
Code: [Select]
cmake -DCMAKE_BUILD_TYPE=Debug but that didn't help. Also if it is helpful to anyone the loop is
Code: [Select]
while sleep 1800;do rm p2p.log.*; done and i just have it running in the p2p log folder to delete the archived logs every half hour or so.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 23, 2015, 04:49:39 pm: Quote from: lafona on August 23, 2015, 04:28:50 pm
Has anyone found a way to reduce the log size? Right now I have a loop running to delete the old logs, but I imagine there must be a setting somewhere. I have tried
Code: [Select]
cmake . instead of
Code: [Select]
cmake -DCMAKE_BUILD_TYPE=Debug but that didn't help. Also if it is helpful to anyone the loop is
Code: [Select]
while sleep 1800;do rm p2p.log.*; done and i just have it running in the p2p log folder to delete the archived logs every half hour or so.
Quote from: rnglab on August 22, 2015, 08:39:51 pm
Quote from: abit on August 22, 2015, 05:27:47 pm
Quote from: rnglab on August 22, 2015, 10:03:35 am
Quote from: abit on August 22, 2015, 09:52:58 am
Run out of disk space :(
p2p.log too large.

Same here, p2p.log grows like 1Gb/h
have you tried setting log level from debug to info? I'll try it now.
On my side it's 4~5GB/h for one node. Hadn't had time to tweak the settings. Just mounted a larger partition, will try.

setting log level from debug to info for [logger.p2p] reduced its size about an order of magnitude.

Code: [Select]
107M Aug 22 16:30 p2p.log 103M Aug 22 06:59 p2p.log.20150822T100000 183M Aug 22 07:59 p2p.log.20150822T110000 116M Aug 22 08:59 p2p.log.20150822T120000 101M Aug 22 09:59 p2p.log.20150822T130000 182M Aug 22 10:59 p2p.log.20150822T140000 137M Aug 22 11:59 p2p.log.20150822T150000 243M Aug 22 13:59 p2p.log.20150822T170000 390M Aug 22 14:59 p2p.log.20150822T180000 293M Aug 22 15:59 p2p.log.20150822T190000 107M Aug 22 16:30 p2p.log.20150822T200000
Title: Re: Test Net for Advanced Users
Post by: lafona on August 23, 2015, 04:55:24 pm: Thanks I will try that next.
Title: Re: Test Net for Advanced Users
Post by: spartako on August 23, 2015, 06:31:13 pm: I have found this error in my witness:

Code: [Select]
1249999ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.4231 production slot has arrived; generating a block now... 1250000ms th_a witness.cpp:266 block_production_loo ] Got exception while generating block: 10 assert_exception: Assert Exception _consecutive_production_enabled || db.get_dynamic_global_properties().current_witness != scheduled_witness: Last block was generated by the same witness, this node is probably disconnect ed from the network so block production has been disabled. Disable this check with --allow-consecutive option. {} th_a witness.cpp:248 block_production_loop
Is it related to p2p problem?
Title: Re: Test Net for Advanced Users
Post by: betax on August 23, 2015, 07:01:24 pm: Quote from: abit on August 23, 2015, 12:18:23 pm
Quote from: betax on August 23, 2015, 08:01:04 am
14. Restart with parameters to start block producing (block producing needs your witness id and private keys) Current node abit's for test 1
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-14-test-genesis.json -d test_net_1 -s 114.92.254.159:62015 --witness-id '"1.6.5156"' --private-key '["GPH6JhL..your.signing.key..bc5mWyCvERV3coy","5K..your.secret..a"]'15. See your witness producing blocks and
you can Ctrl A Ctrl D to detach from screen.
Thanks for sharing, but don't use my node(at least not only use my node), it breaks now and then.
And the genesis file in step 14 should be aug-20-test-genesis.json.

Here is a list of nodes I'm using (still breaks sometimes):
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-20-test-genesis.json -d test_net_1 -s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015"

Thanks ill add more nodes and correct it now..
Title: Re: Test Net for Advanced Users
Post by: betax on August 23, 2015, 07:02:10 pm: Quote from: xeroc on August 23, 2015, 03:13:24 pm
@betax: could you put your tutorial into the github wiki please? If not, may I do it for you?

It's here: https://github.com/cryptonomex/graphene/wiki/How-to-setup-your-witness-for-test-net-(Ubuntu-14.04)

Please feel free to correct anything.
Title: Re: Test Net for Advanced Users
Post by: abit on August 23, 2015, 08:46:38 pm: Quote from: spartako on August 23, 2015, 06:31:13 pm
I have found this error in my witness:

Code: [Select]
1249999ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.4231 production slot has arrived; generating a block now... 1250000ms th_a witness.cpp:266 block_production_loo ] Got exception while generating block: 10 assert_exception: Assert Exception _consecutive_production_enabled || db.get_dynamic_global_properties().current_witness != scheduled_witness: Last block was generated by the same witness, this node is probably disconnect ed from the network so block production has been disabled. Disable this check with --allow-consecutive option. {} th_a witness.cpp:248 block_production_loop
Is it related to p2p problem?
Looks like you're on a fork.. Try restart, if it happen again try restart with --resync-blockchain.
Title: Re: Test Net for Advanced Users
Post by: abit on August 23, 2015, 08:54:10 pm: Quote
-s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015"
It seems that the seed nodes are all dead. If anyone know any good node please post here. Thanks.

//EDIT:
To become a seed node, add "--p2p-endpoint" parameter when launching witness_node, and remember to configure firewall/NAT to allow incoming connection, since witness_node doesn't enable uPNP by default.
Code: [Select]
./witness_node --p2p-endpoint "0.0.0.0:A_FIXED_PORT" --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-20-test-genesis.json -d test_net_1 -s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015"
Note it's better to use a new node but not your block-producing node for seed node.
Title: Re: Test Net for Advanced Users
Post by: puppies on August 23, 2015, 09:26:33 pm: 45.55.6.216:1776 is still up
Code: [Select]
} unlocked >>> info info { "head_block_num": 245425, "head_block_id": "0003beb1a638ed50d318117d014424d44c2b2360", "head_block_age": "0 second old", "next_maintenance_time": "5 minutes in the future", "chain_id": "d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083", "active_witnesses":
Title: Re: Test Net for Advanced Users
Post by: abit on August 23, 2015, 09:42:22 pm: Quote from: puppies on August 23, 2015, 09:26:33 pm
45.55.6.216:1776 is still up
Code: [Select]
} unlocked >>> info info { "head_block_num": 245425, "head_block_id": "0003beb1a638ed50d318117d014424d44c2b2360", "head_block_age": "0 second old", "next_maintenance_time": "5 minutes in the future", "chain_id": "d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083", "active_witnesses":

Yes, the port is open, but it doesn't response with a handshake message when connected.
Code: [Select]
2015-08-23T21:27:10 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Forcibly disconnecting from handshaking peer 45.55.6.216:1776 due to inactivity of at least 5 seconds node.cpp:1270 2015-08-23T21:27:10 p2p:connect_to_task connect_to ] fatal: error connecting to peer 45.55.6.216:1776: 0 exception: unspecified
Can you check p2p.log and see if there is any successful incoming connection?
Code: [Select]
grep inbound p2p.log|grep active
By check p2p.log we can also found what seed nodes we're connected with:
Code: [Select]
grep onbound p2p.log|grep active
Title: Re: Test Net for Advanced Users
Post by: abit on August 23, 2015, 09:49:43 pm: At present I'm using these seed nodes, but I don't know which ones are started with fixed ports.
Code: [Select]
-s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015" -s 104.156.226.183:60715 -s 104.156.226.183:40479 -s 104.236.255.53:52995 -s 176.9.234.167:34858 -s 176.9.234.167:57727 -s 178.62.88.151:59148 -s 178.62.88.151:41574 -s 188.226.252.109:58843 -s 45.115.36.171:57281 -s 45.55.6.216:37308
Title: Re: Test Net for Advanced Users
Post by: puppies on August 23, 2015, 09:51:09 pm: I'm at work and only have access to my vps through my phone. Corporate vpn blocks port 22. This is what I've got
Code: [Select]
2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] Currently have 8 of [20/200] connections $2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] my id is 9ba089ffa726097f30b96f85510d79f6e4c2a53af47$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 178.62.88.151:59148 with 00bdfa3f396cf7$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 178.62.88.151:41574 with 5d33f74a83e257$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 176.9.234.167:34858 with 86a353604829f9$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 104.156.226.183:60715 with 24f8ce11c3bd$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 45.115.36.171:57281 with 256a70048ea155$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 188.226.252.109:58843 with 7ea834eafbcd$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 216.252.204.69:65026 with e8f88c156e162$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 128.68.89.226:55445 with 8b9a48d3943899$2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(178.62.91.161:2009) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(46.226.109.66:1778) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(5.189.131.201:2009) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(46.226.15.26:40706) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(46.226.12.230:2009) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(185.25.22.21:2776) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(69.172.229.183:2883) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(66.172.11.223:1700) $
And apparently juicessh saves the output all on one line. Scroll to the right or quote of its easier.
Title: Re: Test Net for Advanced Users
Post by: abit on August 23, 2015, 10:03:48 pm: Quote from: puppies on August 23, 2015, 09:51:09 pm
I'm at work and only have access to my vps through my phone. Corporate vpn blocks port 22. This is what I've got
Code: [Select]
2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] Currently have 8 of [20/200] connections $2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] my id is 9ba089ffa726097f30b96f85510d79f6e4c2a53af47$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 178.62.88.151:59148 with 00bdfa3f396cf7$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 178.62.88.151:41574 with 5d33f74a83e257$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 176.9.234.167:34858 with 86a353604829f9$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 104.156.226.183:60715 with 24f8ce11c3bd$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 45.115.36.171:57281 with 256a70048ea155$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 188.226.252.109:58843 with 7ea834eafbcd$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 216.252.204.69:65026 with e8f88c156e162$2015-08-23T21:00:07 p2p:p2p_network_connect_loop display_current_conn ] active: 128.68.89.226:55445 with 8b9a48d3943899$2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(178.62.91.161:2009) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(46.226.109.66:1778) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(5.189.131.201:2009) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(46.226.15.26:40706) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(46.226.12.230:2009) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(185.25.22.21:2776) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(69.172.229.183:2883) $2015-08-23T21:00:07 p2p:p2p_network_connect_loop connect_to_endpoint ] node_impl::connect_to_endpoint(66.172.11.223:1700) $
And apparently juicessh saves the output all on one line. Scroll to the right or quote of its easier.
OK, I've checked them. You have 8 connections, the first 6 are in my seed node list, the last 2 are incoming.

The latter 'connect_to_endpoint' ones seem to be 'bitshares_client' but not 'graphene'.
Code: [Select]
p2p.log.20150822T220000:2015-08-22T22:04:04 p2p:message read_loop disconnect_from_peer ] Disconnecting from 178.62.91.161:2009 for You are on a different chain from me node.cpp:4493
Title: Re: Test Net for Advanced Users
Post by: spartako on August 23, 2015, 10:13:08 pm: Quote from: abit on August 23, 2015, 08:46:38 pm
Quote from: spartako on August 23, 2015, 06:31:13 pm
I have found this error in my witness:

Code: [Select]
1249999ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.4231 production slot has arrived; generating a block now... 1250000ms th_a witness.cpp:266 block_production_loo ] Got exception while generating block: 10 assert_exception: Assert Exception _consecutive_production_enabled || db.get_dynamic_global_properties().current_witness != scheduled_witness: Last block was generated by the same witness, this node is probably disconnect ed from the network so block production has been disabled. Disable this check with --allow-consecutive option. {} th_a witness.cpp:248 block_production_loop
Is it related to p2p problem?
Looks like you're on a fork.. Try restart, if it happen again try restart with --resync-blockchain.

I restarted and it seems working now, thanks!
Title: Re: Test Net for Advanced Users
Post by: puppies on August 23, 2015, 10:48:52 pm: Quote from: abit on August 23, 2015, 10:03:48 pm

The latter 'connect_to_endpoint' ones seem to be 'bitshares_client' but not 'graphene'.
Code: [Select]
p2p.log.20150822T220000:2015-08-22T22:04:04 p2p:message read_loop disconnect_from_peer ] Disconnecting from 178.62.91.161:2009 for You are on a different chain from me node.cpp:4493
that's pretty funny.

Any idea why my node would not be handshaking if it only had 8 peers?
Title: Re: Test Net for Advanced Users
Post by: abit on August 24, 2015, 01:03:26 am: Quote from: puppies on August 23, 2015, 10:48:52 pm
Quote from: abit on August 23, 2015, 10:03:48 pm

The latter 'connect_to_endpoint' ones seem to be 'bitshares_client' but not 'graphene'.
Code: [Select]
2015-08-24T00:49:39 p2p:message read_loop on_hello_message ] Received hello message from peer on a different chain: {"user_agent":"bitshares_client","core_protocol_version":106,"inbound_address":"104.255.221.100","inbound_port":1776,"outbound_port":1776,"node_public_key":"02d094583cd49e6c1c86d0bad51064c179885989aeedef46494719bc64261aca7c","signed_shared_secret":"20511eb5127270ca43e2324352c0feee15093f0c6aa0e0cf6dd7ca2b921cdef5664ccb314e6bc9b369dcf78d5532090604f4458d76471eef26175aa979e994eab9","chain_id":"bbf8cbb90532eb555f66602d3bf071609552f852cf9156d4253a33479b70a5e1","user_data":{"bitshares_git_revision_sha":"6bc091e807ba3904ee6793e58d7de3b4309ff4b2","bitshares_git_revision_unix_timestamp":1437477775,"fc_git_revision_sha":"fd4fc4f0cb21fc7b631ee2be827f6aea85e040d6","fc_git_revision_unix_timestamp":1425136084,"platform":"linux","bitness":64,"node_id":"1206c3bec35c9347110ac6ee161c493095f69655cb854dbf6b91b41bf8cc495eab","last_known_block_hash":"c9680afa36aa6061c23919d71a3a221576ecf722","last_known_block_number":1251689,"last_known_block_time":"2015-08-24T00:49:30"}} node.cpp:1835
that's pretty funny.

More info:
Code: [Select]
2015-08-24T00:49:39 p2p:message read_loop on_hello_message ] Received hello message from peer on a different chain: {"user_agent": "bitshares_client","core_protocol_version":106,"inbound_address":"104.255.221.100","inbound_port":1776,"outbound_port":1776,"node_publ ic_key":"02d094583cd49e6c1c86d0bad51064c179885989aeedef46494719bc64261aca7c","signed_shared_secret":"20511eb5127270ca43e2324352c0feee1 5093f0c6aa0e0cf6dd7ca2b921cdef5664ccb314e6bc9b369dcf78d5532090604f4458d76471eef26175aa979e994eab9","chain_id":"bbf8cbb90532eb555f66602 d3bf071609552f852cf9156d4253a33479b70a5e1","user_data":{"bitshares_git_revision_sha":"6bc091e807ba3904ee6793e58d7de3b4309ff4b2","bitsh ares_git_revision_unix_timestamp":1437477775,"fc_git_revision_sha":"fd4fc4f0cb21fc7b631ee2be827f6aea85e040d6","fc_git_revision_unix_ti mestamp":1425136084,"platform":"linux","bitness":64,"node_id":"1206c3bec35c9347110ac6ee161c493095f69655cb854dbf6b91b41bf8cc495eab","la st_known_block_hash":"c9680afa36aa6061c23919d71a3a221576ecf722","last_known_block_number":1251689,"last_known_block_time":"2015-08-24T 00:49:30"}} node.cpp:1835 2015-08-24T00:49:39 p2p:message read_loop disconnect_from_peer ] Disconnecting from 104.255.221.100:1776 for You are on a different ch ain from me node.cpp:4493 2015-08-24T00:49:39 p2p:message read_loop on_connection_reject ] Received a rejection from 104.255.221.100:1776 in response to my "hello", reason: "You're on a different chain than I am. I'm on bbf8cbb90532eb555f66602d3bf071609552f852cf9156d4253a33479b70a5e1 and you're on d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083" node.cpp:2017
Quote from: puppies on August 23, 2015, 10:48:52 pm
Any idea why my node would not be handshaking if it only had 8 peers?
Don't know.. Maybe a bug.
Title: Re: Test Net for Advanced Users
Post by: abit on August 24, 2015, 11:00:15 am: Code: [Select]
3508896ms th_a application.cpp:265 startup ] Detected unclean shutdown. Replaying blockchain...It takes too much time to replay blockchain.. How to "cleanly" shutdown the witness node?
Title: Re: Test Net for Advanced Users
Post by: betax on August 24, 2015, 11:15:36 am: Quote from: abit on August 24, 2015, 11:00:15 am
Code: [Select]
3508896ms th_a application.cpp:265 startup ] Detected unclean shutdown. Replaying blockchain...It takes too much time to replay blockchain.. How to "cleanly" shutdown the witness node?

Question bump.
Title: Re: Test Net for Advanced Users
Post by: spartako on August 24, 2015, 11:57:35 am: Quote from: betax on August 24, 2015, 11:15:36 am
Quote from: abit on August 24, 2015, 11:00:15 am
Code: [Select]
3508896ms th_a application.cpp:265 startup ] Detected unclean shutdown. Replaying blockchain...It takes too much time to replay blockchain.. How to "cleanly" shutdown the witness node?

Question bump.

I use this strategy:
When I am synced, I shutdown with C-c (it should shutdown in a clean way) and I copy the blockchain folder as backup (if it shutdown without errors).
Everytime my blockchain is corrupted, I remove the blockchain folder and I copy with the backup one and restart the witness.
Finally I backup the blockchain folder every day.
Title: Re: Test Net for Advanced Users
Post by: betax on August 24, 2015, 12:33:25 pm: Quote from: spartako on August 24, 2015, 11:57:35 am
Quote from: betax on August 24, 2015, 11:15:36 am
Quote from: abit on August 24, 2015, 11:00:15 am
Code: [Select]
3508896ms th_a application.cpp:265 startup ] Detected unclean shutdown. Replaying blockchain...It takes too much time to replay blockchain.. How to "cleanly" shutdown the witness node?

Question bump.

I use this strategy:
When I am synced, I shutdown with C-c (it should shutdown in a clean way) and I copy the blockchain folder as backup (if it shutdown without errors).
Everytime my blockchain is corrupted, I remove the blockchain folder and I copy with the backup one and restart the witness.
Finally I backup the blockchain folder every day.

Good idea !
Title: Re: Test Net for Advanced Users
Post by: betax on August 24, 2015, 12:44:01 pm: I have added a new section Tips on the wiki.

https://github.com/cryptonomex/graphene/wiki/How-to-setup-your-witness-for-test-net-(Ubuntu-14.04) (https://github.com/cryptonomex/graphene/wiki/How-to-setup-your-witness-for-test-net-(Ubuntu-14.04))

So if you have any tips, you can add them there if is not general setup. I have just added spartako's from the previous post.

Also I have put some credits to list everyone :)
Title: Re: Test Net for Advanced Users
Post by: spartako on August 24, 2015, 01:13:41 pm: Quote from: betax on August 24, 2015, 12:44:01 pm
I have added a new section Tips on the wiki.

https://github.com/cryptonomex/graphene/wiki/How-to-setup-your-witness-for-test-net-(Ubuntu-14.04) (https://github.com/cryptonomex/graphene/wiki/How-to-setup-your-witness-for-test-net-(Ubuntu-14.04))

So if you have any tips, you can add them there if is not general setup. I have just added spartako's from the previous post.

Also I have put some credits to list everyone :)

Thanks betax, good idea!
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 24, 2015, 03:00:50 pm: In the interest of not slipping the release date we are going to fall back to 3 or 5 second blocks using the current P2P code. Then after we update the P2P code we can increase the block rate to 2 and ultimately 1 second block times.

Ben is in the process of preparing instructions for committee members on how to change the block interval and we plan to dynamically update the test network to prove that we can do this on a live network.
Title: Re: Test Net for Advanced Users
Post by: abit on August 24, 2015, 03:09:36 pm: Quote from: bytemaster on August 24, 2015, 03:00:50 pm
In the interest of not slipping the release date we are going to fall back to 3 or 5 second blocks using the current P2P code. Then after we update the P2P code we can increase the block rate to 2 and ultimately 1 second block times.

Ben is in the process of preparing instructions for committee members on how to change the block interval and we plan to dynamically update the test network to prove that we can do this on a live network.
Sounds interesting.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 24, 2015, 03:21:09 pm: Quote from: bytemaster on August 24, 2015, 03:00:50 pm
In the interest of not slipping the release date we are going to fall back to 3 or 5 second blocks using the current P2P code. Then after we update the P2P code we can increase the block rate to 2 and ultimately 1 second block times.

Ben is in the process of preparing instructions for committee members on how to change the block interval and we plan to dynamically update the test network to prove that we can do this on a live network.

I previously asked about changes to terminology I've seen in this thread. I just did a search and found the only clue about "committee members" here: https://bitsharestalk.org/index.php/topic,17960.msg229223.html#msg229223 Is there a doc where this was discussed previously that I missed? If I understand correctly "committee members" are what was previously referred to as delegates in the trinity of witness / worker / delegate. Is that correct?

FYI if that is true I think it makes good sense, tho it would have been better had that change been considered when 2.0 was initially announced. Such is the nature of evolution in a fast past project. Nothing unusual or sinister going on.
Title: Re: Test Net for Advanced Users
Post by: abit on August 24, 2015, 03:54:45 pm: Quote from: spartako on August 24, 2015, 11:57:35 am
Quote from: betax on August 24, 2015, 11:15:36 am
Quote from: abit on August 24, 2015, 11:00:15 am
Code: [Select]
3508896ms th_a application.cpp:265 startup ] Detected unclean shutdown. Replaying blockchain...It takes too much time to replay blockchain.. How to "cleanly" shutdown the witness node?

Question bump.

I use this strategy:
When I am synced, I shutdown with C-c (it should shutdown in a clean way) and I copy the blockchain folder as backup (if it shutdown without errors).
Everytime my blockchain is corrupted, I remove the blockchain folder and I copy with the backup one and restart the witness.
Finally I backup the blockchain folder every day.
Thanks, it works. +5%

If witness_node was launched in gdb, we need to press ctrl+c, then from the (gdb) prompt, type 'signal SIGINT'. This will send SIGINT to the program being debugged. I always type 'kill' before I know this, so the program always shutdown uncleanly.

I have another problem, when I restart witness_node, usually it takes a long time to get connected to network, and sometimes won't get connected at all.
Title: Re: Test Net for Advanced Users
Post by: spartako on August 24, 2015, 04:03:32 pm: Quote from: abit on August 24, 2015, 03:54:45 pm

I have another problem, when I restart witness_node, usually it takes a long time to get connected to network, and sometimes won't get connected at all.

When I have connection problems I remove the p2p folder, it worked for me sometimes.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 24, 2015, 04:44:54 pm: I resumed using the exact same parameters as I used late Saturday. I was told by abit & puppies my being voted in status wouldn't change unless a new chain was started (if this occurred yesterday for example).

It looks like I'll need to wait until my blockchain is synced. It is old b/c I start with the --resync-blockchain parameter. When it is synced I expect I should start to produce blocks unless my voted in status has changed. I'm using the get_witness delegate.verbaltech API call and looking for a change in the next_secret_hash to confirm I'm producing blocks. Not seeing any change, and age of blockchain is still 7 days old.

I'm going to restart after clearing both the blockchain & p2p folders. My cmd line invocation is: ./witness_node --resync-blockchain -d test_net --enable-stale-production, all other parameters are in the config.ini. After restarting the blockchain age reported by info started at 4 days and is now down to 57 hours. The witness output is much different than before I wiped the blk chn & p2p folders. It looks like I may finally be on the verge of producing blocks! I now see my total_votes is no longer zero.

Shit! The witness crashed as it was time to produce my first block:

Code: [Select]
77061ms th_a witness.cpp:243 block_production_loo ] Witness 1.6.1621 production slot has arrived; generating a block now... ./witness: line 5: 23013 Segmentation fault ./witness_node --resync-blockchain -d test_net --enable-stale-production
Is there a checkpoint I can use to resync faster, should I need to restart?
Title: Re: Test Net for Advanced Users
Post by: Thom on August 24, 2015, 05:08:57 pm: Trying again, but forgot to remove --resync-blockchain from the cmd line. Next time it will not be there should the witness crash again.

It didn't take too long to get resynced, so in a few minutes I'll see if I produce blocks or crash...

I'd say it crashed. This time it resulted in the witness and cli locking up, then finally seg faulting after a long delay.

Trying again, this time with no resync cmd line param...

It resynced AND ignored my config.ini, witness output looks much different (not good):
Code: [Select]
deletech@Jessie:~/bts2.0/aug20$ ./witness 1247707ms th_a main.cpp:112 main ] Error parsing logging config from config file /home/deletech/bts2.0/aug20/graphene/programs/witness_node/test_net/config.ini, using default config 1247707ms th_a witness.cpp:70 plugin_initialize ] key_id_to_wif_pair: ["GPH........................","5.................................."] 1247707ms th_a application.cpp:265 startup ] Detected unclean shutdown. Replaying blockchain... 1247707ms th_a application.cpp:228 operator() ] Initializing database... 1268250ms th_a db_management.cpp:67 wipe ] Wiping database 1268295ms th_a object_database.cpp:82 wipe ] Wiping object_database. 1283059ms th_a market_history_plugin.cpp:77 operator() ] processing {"fee":{"amount":0,"asset_id":"1.3.527"},"order_id":"1.7.3","account_id":"1.2.2994","pays":{"amount":10000000,"asset_id":"1.3.0"},"receives":{"amount":4000,"asset_id":"1.3.527"}} 1283059ms th_a market_history_plugin.cpp:123 operator() ] creating bucket {"id":"5.1.0","key":{"base":"1.3.0","quote":"1.3.527","seconds":15,"open":"2015-08-20T18:28:00"},"high_base":10000000,"high_quote":4000,"low_base":10000000,"low_quote":4000,"open_base":10000000,"open_quote":4000,"close_base":10000000,"close_quote":4000,"base_volume":10000000,"quote_volume":4000} 1283059ms th_a market_history_plugin.cpp:127 operator() ] before updating bucket {"id":"5.1.0","key":{"base":"1.3.0","quote":"1.3.527","seconds":15,"open":"2015-08-20T18:28:00"},"high_base":10000000,"high_quote":4000,"low_base":10000000,"low_quote":4000,"open_base":10000000,"open_quote":4000,"close_base":10000000,"close_quote":4000,"base_volume":10000000,"quote_volume":4000} 1283059ms th_a market_history_plugin.cpp:144 operator() ] after bucket bucket {"id":"5.1.0","key":{"base":"1.3.0","
I wiped the blockchain, logs and p2p folders of the wallet and attemped to restart (without the --resync-blockchain cmd line option) and I see this in the log:

Code: [Select]
1621853ms th_a main.cpp:112 main ] Error parsing logging config from config file /home/deletech/bts2.0/aug20/graphene/programs/witness_node/test_net/config.ini, using default config
I have no idea why this started showing up. Was it always there & I missed it? anyway trying once again. If it crashes this time I'll be looking to see what top says mem or cpu is doing. Tried using --checkpoint '[40902,"00009fc6d4e24db66e13af461b94063165999bfa"]' but decided to remove it on this trial and see what top says when it comes time for my witness to generate a block.

I'm running on a 4GB RAM quad core CPU system, and top says memory is only 8.5% and cpu is at 170% with 45 hours to go to resync.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 24, 2015, 05:25:12 pm: I have been producing blocks over the weekend both at home and on a VPS.

Now I can only see the 100 init witnesses on the witness_node. No voted in witnesses.

Code: [Select]
1458062ms th_a witness.cpp:240 block_production_loo ] slot: 593448 scheduled_witness: 1.6.3 scheduled_time: 2015-08-24T17:24:18 now: 2015-08-24T17:24:18 1459048ms th_a witness.cpp:240 block_production_loo ] slot: 593449 scheduled_witness: 1.6.83 scheduled_time: 2015-08-24T17:24:19 now: 2015-08-24T17:24:19 1460043ms th_a witness.cpp:240 block_production_loo ] slot: 593450 scheduled_witness: 1.6.73 scheduled_time: 2015-08-24T17:24:20 now: 2015-08-24T17:24:20 1461044ms th_a witness.cpp:240 block_production_loo ] slot: 593451 scheduled_witness: 1.6.23 scheduled_time: 2015-08-24T17:24:21 now: 2015-08-24T17:24:21 1462044ms th_a witness.cpp:240 block_production_loo ] slot: 593452 scheduled_witness: 1.6.4 scheduled_time: 2015-08-24T17:24:22 now: 2015-08-24T17:24:22 1463052ms th_a witness.cpp:240 block_production_loo ] slot: 593453 scheduled_witness: 1.6.8 scheduled_time: 2015-08-24T17:24:23 now: 2015-08-24T17:24:23 1464049ms th_a witness.cpp:240 block_production_loo ] slot: 593454 scheduled_witness: 1.6.25 scheduled_time: 2015-08-24T17:24:24 now: 2015-08-24T17:24:24 1465055ms th_a witness.cpp:240 block_production_loo ] slot: 593455 scheduled_witness: 1.6.82 scheduled_time: 2015-08-24T17:24:25 now: 2015-08-24T17:24:25 1466072ms th_a witness.cpp:240 block_production_loo ] slot: 593456 scheduled_witness: 1.6.91 scheduled_time: 2015-08-24T17:24:26 now: 2015-08-24T17:24:26 1467044ms th_a witness.cpp:240 block_production_loo ] slot: 593457 scheduled_witness: 1.6.9 scheduled_time: 2015-08-24T17:24:27 now: 2015-08-24T17:24:27 1468045ms th_a witness.cpp:240 block_production_loo ] slot: 593458 scheduled_witness: 1.6.100 scheduled_time: 2015-08-24T17:24:28 now: 2015-08-24T17:24:28 1469042ms th_a witness.cpp:240 block_production_loo ] slot: 593459 scheduled_witness: 1.6.51 scheduled_time: 2015-08-24T17:24:29 now: 2015-08-24T17:24:29
Code: [Select]
Chain ID is d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083
I have tried
Code: [Select]
--resync-blockchain -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015" and deleting blockchain, p2p folders.

I also lost imported CORE - but it could be not detaching the wallet correctly ctrl + D before a witness_node crash

Is there any thing else I could have missed?
Title: Re: Test Net for Advanced Users
Post by: Thom on August 24, 2015, 05:54:08 pm: My witness must be voted it or it wouldn't be attempting to produce blocks, which it consistently is trying to do after the blk chn gets synced.

This time when it crashed memory was still only 9%, and cpu was at 100%.

My next attempt is to try this on a vps node. Now that I seem to have all the ingredients in place to produce blocks I don't understand what is causing the witness to crash in doing so. The vps will eliminate anything concerning my network here at home as well as the system itself. If I see the same crash symptom I am not sure what the next step should be.

iHashFury, how are you determining there are no vote in witnesses in place? Look at my last couple of posts. I noticed I had a non-zero "total_votes" earlier for example.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 24, 2015, 06:02:26 pm: Quote from: Thom on August 24, 2015, 05:54:08 pm
iHashFury, how are you determining there are no vote in witnesses in place? Look at my last couple of posts. I noticed I had a non-zero "total_votes" earlier for example.

Code: [Select]
get_global_properties in the cli_wallet and watching the output of witness_node in tmux (screen alternative)
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 24, 2015, 06:07:49 pm: info also works in the cli_wallet

Code: [Select]
info info { "head_block_num": 0, "head_block_id": "0000000000000000000000000000000000000000", "head_block_age": "7 days old", "next_maintenance_time": "45 years ago", "chain_id": "d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.5", "1.6.6", "1.6.7", "1.6.8", "1.6.9", "1.6.10", "1.6.11", "1.6.12", "1.6.13", "1.6.14", "1.6.15", "1.6.16", "1.6.17", "1.6.18", "1.6.19", "1.6.20", "1.6.21", "1.6.22", "1.6.23", "1.6.24", "1.6.25", "1.6.26", "1.6.27", "1.6.28", "1.6.29", "1.6.30", "1.6.31", "1.6.32", "1.6.33", "1.6.34", "1.6.35", "1.6.36", "1.6.37", "1.6.38", "1.6.39", "1.6.40", "1.6.41", "1.6.42", "1.6.43", "1.6.44", "1.6.45", "1.6.46", "1.6.47", "1.6.48", "1.6.49", "1.6.50", "1.6.51", "1.6.52", "1.6.53", "1.6.54", "1.6.55", "1.6.56", "1.6.57", "1.6.58", "1.6.59", "1.6.60", "1.6.61", "1.6.62", "1.6.63", "1.6.64", "1.6.65", "1.6.66", "1.6.67", "1.6.68", "1.6.69", "1.6.70", "1.6.71", "1.6.72", "1.6.73", "1.6.74", "1.6.75", "1.6.76", "1.6.77", "1.6.78", "1.6.79", "1.6.80", "1.6.81", "1.6.82", "1.6.83", "1.6.84", "1.6.85", "1.6.86", "1.6.87", "1.6.88", "1.6.89", "1.6.90", "1.6.91", "1.6.92", "1.6.93", "1.6.94", "1.6.95", "1.6.96", "1.6.97", "1.6.98", "1.6.99", "1.6.100" ], "active_committee_members": [], "entropy": "0000000000000000000000000000000000000000" }
Title: Re: Test Net for Advanced Users
Post by: Thom on August 24, 2015, 06:10:42 pm: Quote from: iHashFury on August 24, 2015, 06:02:26 pm
Quote from: Thom on August 24, 2015, 05:54:08 pm
iHashFury, how are you determining there are no vote in witnesses in place? Look at my last couple of posts. I noticed I had a non-zero "total_votes" earlier for example.

Code: [Select]
get_global_properties in the cli_wallet and watching the output of witness_node in tmux (screen alternative)

I C.

I've been using info. I use tmux as well, never used screen. However ATM I'm just using different shell windows b/c I don't know how to scroll a tmux terminal beyond the visible buffer window; pg up & pg dn keys just recall the previous cmd line options.

While the code is rebuilding on the vps I'll try the witness once more to see what get_global_props returns for me and if it shows my witness being voted in.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 24, 2015, 06:12:25 pm: You seem to be on a fork, based on the 7 day old chain. Your chain-id is correct, that's what I'm using.

Review my posts and you will see I too had the 7 day old thing going on, then I changed someting and now starting from scratch starts at 4 days old.

Make sure you remove p2p/* and logs/* too.

Restarted. Using your global API I see 3 active witnesses:

"1.6.5246",
"1.6.5247",
"1.6.5248"

Mine isn't active yet b/c the blk chn isn't yet synced. As soon as it does and my witness tries to produce a block it crashes.

I see many more active as the blk chn gets closer to being synced:

"1.6.1526",
"1.6.1530",
"1.6.1537",
"1.6.1625",
"1.6.5246",
"1.6.5247",
"1.6.5248",
"1.6.5249",
"1.6.5250",
"1.6.5251",
"1.6.5252"
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 24, 2015, 06:23:03 pm: ctrl +b then press page up or down

to scroll in tmux - you can then use the mouse wheel

Esc to cancel
Title: Re: Test Net for Advanced Users
Post by: Thom on August 24, 2015, 06:24:41 pm: at 36 hrs to go for resync, my delegate info shows:

Code: [Select]
get_witness delegate.verbaltech { "id": "1.6.1621", "witness_account": "1.2.22408", "signing_key": "GPH52ms1dYJko2v5vS3rCdVLzQBogjeDRc1CpkaZ4seC4J4H7Uc71", "next_secret_hash": "5c..........................................65", "previous_secret": "0000000000000000000000000000000000000000", "vote_id": "1:1621", "total_votes": "4389187579", "url": "" }
Still can't scroll in tmux - c-b pgUp or c-b pgDn does nothing. Scroll wheel does the same as pgUp / dn, it just scrolls the last cmd line like up or dn arrow does.

Build on vps is 95% done. Hoping for different results than on my local machine. We'll see soon...
Title: Re: Test Net for Advanced Users
Post by: abit on August 24, 2015, 06:51:02 pm: Quote from: iHashFury on August 24, 2015, 06:07:49 pm
info also works in the cli_wallet

Code: [Select]
info info { "head_block_num": 0, "head_block_id": "0000000000000000000000000000000000000000", "head_block_age": "7 days old", "next_maintenance_time": "45 years ago", "chain_id": "d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083", "active_witnesses": [ "1.6.0", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.5", "1.6.6", "1.6.7", "1.6.8", "1.6.9", "1.6.10", "1.6.11", "1.6.12", "1.6.13", "1.6.14", "1.6.15", "1.6.16", "1.6.17", "1.6.18", "1.6.19", "1.6.20", "1.6.21", "1.6.22", "1.6.23", "1.6.24", "1.6.25", "1.6.26", "1.6.27", "1.6.28", "1.6.29", "1.6.30", "1.6.31", "1.6.32", "1.6.33", "1.6.34", "1.6.35", "1.6.36", "1.6.37", "1.6.38", "1.6.39", "1.6.40", "1.6.41", "1.6.42", "1.6.43", "1.6.44", "1.6.45", "1.6.46", "1.6.47", "1.6.48", "1.6.49", "1.6.50", "1.6.51", "1.6.52", "1.6.53", "1.6.54", "1.6.55", "1.6.56", "1.6.57", "1.6.58", "1.6.59", "1.6.60", "1.6.61", "1.6.62", "1.6.63", "1.6.64", "1.6.65", "1.6.66", "1.6.67", "1.6.68", "1.6.69", "1.6.70", "1.6.71", "1.6.72", "1.6.73", "1.6.74", "1.6.75", "1.6.76", "1.6.77", "1.6.78", "1.6.79", "1.6.80", "1.6.81", "1.6.82", "1.6.83", "1.6.84", "1.6.85", "1.6.86", "1.6.87", "1.6.88", "1.6.89", "1.6.90", "1.6.91", "1.6.92", "1.6.93", "1.6.94", "1.6.95", "1.6.96", "1.6.97", "1.6.98", "1.6.99", "1.6.100" ], "active_committee_members": [], "entropy": "0000000000000000000000000000000000000000" }
You're out of sync. Try add more seed nods and resync.

Code: [Select]
-s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015" -s 104.156.226.183:60715 -s 104.156.226.183:40479 -s 104.236.255.53:52995 -s 176.9.234.167:34858 -s 176.9.234.167:57727 -s 178.62.88.151:59148 -s 178.62.88.151:41574 -s 188.226.252.109:58843 -s 45.115.36.171:57281 -s 45.55.6.216:37308
Title: Re: Test Net for Advanced Users
Post by: abit on August 24, 2015, 06:54:03 pm: Quote from: Thom on August 24, 2015, 04:44:54 pm
I'm going to restart after clearing both the blockchain & p2p folders. My cmd line invocation is: ./witness_node --resync-blockchain -d test_net --enable-stale-production, all other parameters are in the config.ini. After restarting the blockchain age reported by info started at 4 days and is now down to 57 hours. The witness output is much different than before I wiped the blk chn & p2p folders. It looks like I may finally be on the verge of producing blocks! I now see my total_votes is no longer zero.
Don't use '--enable-stale-production' parameter. It's for the init node.

Quote from: Thom on August 24, 2015, 04:44:54 pm
Is there a checkpoint I can use to resync faster, should I need to restart?

Try start with more seed nodes:
Code: [Select]
-s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015" -s 104.156.226.183:60715 -s 104.156.226.183:40479 -s 104.236.255.53:52995 -s 176.9.234.167:34858 -s 176.9.234.167:57727 -s 178.62.88.151:59148 -s 178.62.88.151:41574 -s 188.226.252.109:58843 -s 45.115.36.171:57281 -s 45.55.6.216:37308
Title: Re: Test Net for Advanced Users
Post by: betax on August 24, 2015, 07:07:12 pm: once you sync, do a backup of your blockchain it will help you later on. See spartako's comment.

Quote from: spartako on August 24, 2015, 11:57:35 am
Quote from: betax on August 24, 2015, 11:15:36 am
Quote from: abit on August 24, 2015, 11:00:15 am
Code: [Select]
3508896ms th_a application.cpp:265 startup ] Detected unclean shutdown. Replaying blockchain...It takes too much time to replay blockchain.. How to "cleanly" shutdown the witness node?

Question bump.

I use this strategy:
When I am synced, I shutdown with C-c (it should shutdown in a clean way) and I copy the blockchain folder as backup (if it shutdown without errors).
Everytime my blockchain is corrupted, I remove the blockchain folder and I copy with the backup one and restart the witness.
Finally I backup the blockchain folder every day.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 24, 2015, 07:07:52 pm: Quote from: abit on August 24, 2015, 06:54:03 pm
Quote from: Thom on August 24, 2015, 04:44:54 pm
I'm going to restart after clearing both the blockchain & p2p folders. My cmd line invocation is: ./witness_node --resync-blockchain -d test_net --enable-stale-production, all other parameters are in the config.ini. After restarting the blockchain age reported by info started at 4 days and is now down to 57 hours. The witness output is much different than before I wiped the blk chn & p2p folders. It looks like I may finally be on the verge of producing blocks! I now see my total_votes is no longer zero.
Don't use '--enable-stale-production' parameter. It's for the init node.

Quote from: Thom on August 24, 2015, 04:44:54 pm
Is there a checkpoint I can use to resync faster, should I need to restart?

Try start with more seed nodes:
Code: [Select]
-s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015" -s 104.156.226.183:60715 -s 104.156.226.183:40479 -s 104.236.255.53:52995 -s 176.9.234.167:34858 -s 176.9.234.167:57727 -s 178.62.88.151:59148 -s 178.62.88.151:41574 -s 188.226.252.109:58843 -s 45.115.36.171:57281 -s 45.55.6.216:37308

I'm using these seed nodes in the config.ini:

Code: [Select]
# P2P nodes to connect to on startup (may specify multiple times) seed-node = 114.92.254.159:62015 seed-node = 104.200.28.117:61705 seed-node = 104.236.51.238:1776 seed-node = 176.221.43.130:33323 seed-node = 45.55.6.216:1776
I'll add the others you listed and remove the enable-stale-production if it crashes on the vps.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 24, 2015, 07:17:32 pm: The vps node is up and running, the blk chn appears to be synced, and I appear to be producing blocks!!! Whew who!!!!!!!!!! Finally!!!

I haven't started with the other seed nodes, but my config.ini now lists them for the next restart:
Code: [Select]
seed-node = 45.55.6.216:1776 seed-node = 45.115.36.171:57281 seed-node = 45.55.6.216:37308 seed-node = 104.200.28.117:61705 seed-node = 104.236.51.238:1776 seed-node = 104.156.226.183:60715 seed-node = 104.156.226.183:40479 seed-node = 104.236.255.53:52995 seed-node = 114.92.254.159:62015 seed-node = 114.92.254.159:62015 seed-node = 176.221.43.130:33323 seed-node = 176.9.234.167:34858 seed-node = 176.9.234.167:57727 seed-node = 178.62.88.151:59148 seed-node = 178.62.88.151:41574 seed-node = 188.226.252.109:58843
Witness created: "1.6.1621" ("1.6.1530 if you count my previous non-producing attempts) :)
Please send my brownies reward here: BTS68hiHJQ1vBhsJYr7Bg61udi1fgmQYDr2MvGF8EkhPsaH1AAKus
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 24, 2015, 07:51:47 pm: back in the game :)

seed nodes and a new -d (chain folder) did the job

Thanks everyone for the list of seed nodes
Title: Re: Test Net for Advanced Users
Post by: abit on August 24, 2015, 08:57:53 pm: It takes about 10 minutes to resync current chain. But need at least 10 minutes to replay if crash. Backup is a good idea.
Code: [Select]
{ "head_block_num": 319236, "head_block_id": "0004df042bd2fc6c4bf3168d7116de8d0e55842f", "head_block_age": "1 second old", }
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 24, 2015, 10:12:36 pm: Quote from: abit on August 24, 2015, 08:57:53 pm
It takes about 10 minutes to resync current chain. But need at least 10 minutes to replay if crash. Backup is a good idea.
Code: [Select]
{ "head_block_num": 319236, "head_block_id": "0004df042bd2fc6c4bf3168d7116de8d0e55842f", "head_block_age": "1 second old", }

I did some looking into why it takes so long to reindex because it seemed to me that 10 minutes was entirely too long for 3 days worth of blocks. I found two spots in the code that are dramatically slowing down the reindex process:

1. There are over 2 years worth of daily maintenance intervals being performed because we have 5 minute maintenance intervals on the test network. If this were a real network then there would have only been .3% of the maintenance intervals and reindexing time would have been reduced by about 40%. Maintenance intervals are where we tally all votes and is a relatively expensive calculation, especially when the test network has all of the same accounts as BTS after 1 year.

2. The rest of the time is being spent updating the witness schedule which involves some expensive hashing and set containers. There is no reason to perform these operations during a reindex because we assume a valid blockchain while reindexing. This accounts for about 36% of the computational time.

3. We were maintaining undo history while reindexing which is unnecessary, I have just checked in a patch to resolve this. After doing this simple (and planned) optimization, reindexing takes 152 seconds on my computer.

If we remove first two factors then reindexing could be performed in 25% of the time which would be 38 seconds to reindex or about 10 seconds per day, or 1 hour per year with 1 second blocks.

There is still a lot of low-hanging fruit that can be used to accelerate this reindexing performance.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 24, 2015, 10:30:57 pm: The call that is consuming over 40% of the CPU time while reindexing only takes .00018 seconds to run on average and does so once per block.

After recent optimizations I am down to 146 seconds to reindex the past 3 days.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 24, 2015, 10:39:01 pm: Quote from: betax on August 24, 2015, 07:07:12 pm
once you sync, do a backup of your blockchain it will help you later on. See spartako's comment.

Quote from: spartako on August 24, 2015, 11:57:35 am
Quote from: betax on August 24, 2015, 11:15:36 am
Quote from: abit on August 24, 2015, 11:00:15 am
Code: [Select]
3508896ms th_a application.cpp:265 startup ] Detected unclean shutdown. Replaying blockchain...It takes too much time to replay blockchain.. How to "cleanly" shutdown the witness node?

Question bump.

I use this strategy:
When I am synced, I shutdown with C-c (it should shutdown in a clean way) and I copy the blockchain folder as backup (if it shutdown without errors).
Everytime my blockchain is corrupted, I remove the blockchain folder and I copy with the backup one and restart the witness.
Finally I backup the blockchain folder every day.

Thx betax.

Now my vps node is behaving like my home system. As soon as my witness is called on to produce a block it seg faults & dies. As soon as it gets resynced it is scheduled so I can't quit to save the chain.

The last time it died I cleared the blockchain (+ p2p and logs folders) with rm -rf graphene/programs/witness_node/test_net/blockchain/*

That has always allowed me to restart, but now I can't without this crashing. Here's the output:

Code: [Select]
./witness: line 7: 32471 Segmentation fault ./witness_node --resync-blockchain -d test_net
I almost seems like the executable gets corrupted somehow, but that seems highly unlikely. Yet 2 systems are now behaving the same way.

This time I'm also deleting the object_database folder.

@BM: are you planning on publishing that patch or providing a new tag we can build those performance improvements with?
Title: Re: Test Net for Advanced Users
Post by: ebit on August 24, 2015, 10:43:29 pm: +5%
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 24, 2015, 10:50:22 pm: Latest master should still work with the test net.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 24, 2015, 11:11:23 pm: Quote from: bytemaster on August 24, 2015, 10:50:22 pm
Latest master should still work with the test net.

@BM - Was that your answer to my post about your optimizations? I'll just build it from scratch (by "master" I presume you don't mean the test1 tagged commit so I'll comment out the git checkout test1 and see if it picks up your changes. I believe it will from looking at the commit log in git. Just not sure how the test1 tag relates is all.

I was able to kill the witness with ctrl-c, save the blockchain folder and resume producing blocks without a hitch. All of my parameters are now in the config.ini file and the witness invocation is now only: ./witness_node -d test_net

Removing the object_database folder seems to be required to recover a functional witness after the seg faults happen.

Here is my config.ini if anyone is interested:

Code: [Select]
#Endpoint for P2P node to listen on p2p-endpoint = 0.0.0.0:1776 # P2P nodes to connect to on startup (may specify multiple times) seed-node = 45.55.6.216:1776 seed-node = 45.115.36.171:57281 seed-node = 45.55.6.216:37308 seed-node = 104.200.28.117:61705 seed-node = 104.236.51.238:1776 seed-node = 104.156.226.183:60715 seed-node = 104.156.226.183:40479 seed-node = 104.236.255.53:52995 seed-node = 114.92.254.159:62015 seed-node = 114.92.254.159:62015 seed-node = 176.221.43.130:33323 seed-node = 176.9.234.167:34858 seed-node = 176.9.234.167:57727 seed-node = 178.62.88.151:59148 seed-node = 178.62.88.151:41574 seed-node = 188.226.252.109:58843 # Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints. # checkpoint = # Endpoint for websocket RPC to listen on rpc-endpoint = 127.0.0.1:8090 # Endpoint for TLS websocket RPC to listen on # rpc-tls-endpoint = # The TLS certificate file for this server # server-pem = # Password for this certificate # server-pem-password = # File to read Genesis State from #genesis-json = aug-14-test-genesis.json #genesis-json = aug-19-puppies-test-genesis.json genesis-json = aug-20-test-genesis.json # JSON file specifying API permissions # api-access = # Enable block production, even if the chain is stale. enable-stale-production = true # Percent of witnesses (0-99) that must be participating in order to produce blocks required-participation = false # Allow block production, even if the last block was produced by the same witness. allow-consecutive = false # ID of witness controlled by this node (e.g. "1.6.0", quotes are required, may specify multiple times) #witness-id = "1.6.1530" witness-id = "1.6.1621" # Tuple of [PublicKey, WIF private key] (may specify multiple times) # delegate.verbaltech private-key = ["GPH<public sigining key here>","<private siging key value here>"] # Account ID to track history for (may specify multiple times) # track-account = # Track market history by grouping orders into buckets of equal size measured in seconds specified as a JSON array of numbers bucket-size = [15,60,300,3600,86400] # How far back in time to track history for each bucket size, measured in the number of buckets (default: 1000) history-per-size = 1000 # declare an appender named "stderr" that writes messages to the console [log.console_appender.stderr] stream=std_error # declare an appender named "p2p" that writes messages to p2p.log [log.file_appender.p2p] filename=logs/p2p/p2p.log # filename can be absolute or relative to this config file # route any messages logged to the default logger to the "stderr" logger we # declared above, if they are info level are higher [logger.default] level=info appenders=stderr # route messages sent to the "p2p" logger to the p2p appender declared above [logger.p2p] level=debug appenders=p2p
Title: Re: Test Net for Advanced Users
Post by: clayop on August 24, 2015, 11:55:18 pm: Since we now have 10~15 active testers, can we have 10~15 witnesses in the next testnet for avoiding centralization issue?
Title: Re: Test Net for Advanced Users
Post by: puppies on August 25, 2015, 12:50:23 am: latest master won't build for me on Ubuntu 14.04. commit cb3c23a17b0ea99816e3c3f35cbcc7b0cbce9f42
I am getting
Code: [Select]
/usr/include/c++/4.8/bits/shared_ptr.h:614:42: required from ‘std::shared_ptr<_Tp1> std::make_shared(_Args&& ...) [with _Tp = graphene::p2p::peer_connection; _Args = {std::shared_ptr<graphene::p2p::node>&}]’ /home/user/src/graphene8.24/graphene/libraries/p2p/node.cpp:36:67: required from here /usr/include/c++/4.8/ext/new_allocator.h:120:4: error: no matching function for call to ‘graphene::p2p::peer_connection::peer_connection(std::shared_ptr<graphene::p2p::node>&)’ { ::new((void *)__p) _Up(std::forward<_Args>(__args)...); } ^ /usr/include/c++/4.8/ext/new_allocator.h:120:4: note: candidate is: In file included from /home/user/src/graphene8.24/graphene/libraries/p2p/include/graphene/p2p/node.hpp:5:0, from /home/user/src/graphene8.24/graphene/libraries/p2p/node.cpp:1: /home/user/src/graphene8.24/graphene/libraries/p2p/include/graphene/p2p/peer_connection.hpp:55:9: note: graphene::p2p::peer_connection::peer_connection() class peer_connection : public message_oriented_connection_delegate, ^ /home/user/src/graphene8.24/graphene/libraries/p2p/include/graphene/p2p/peer_connection.hpp:55:9: note: candidate expects 0 arguments, 1 provided make[2]: *** [libraries/p2p/CMakeFiles/graphene_p2p.dir/node.cpp.o] Error 1 make[1]: *** [libraries/p2p/CMakeFiles/graphene_p2p.dir/all] Error 2 make: *** [all] Error 2 user@user-desktop:~/src/graphene8.24/graphene$
Any help would be appreciated. I am going to try to checkout a different commit and build that.
Title: Re: Test Net for Advanced Users
Post by: Thom on August 25, 2015, 01:11:58 am: Confirmed. Same problem here. I'm on debian 8.1. The last step in my build process was:

Quote
[ 85%] Building CXX object libraries/p2p/CMakeFiles/graphene_p2p.dir/node.cpp.o
Title: Re: Test Net for Advanced Users
Post by: cryptosile on August 25, 2015, 04:23:55 am: BMs commit seems to have broken the build of the tests. However, if you just do a make witness_node that should work. (Or you can use my automatically generated docker build that was pushed 10 minutes after the commit :)

https://hub.docker.com/r/sile16/graphene-witness/

I'm now pushing each commit as a separate tag
Title: Re: Test Net for Advanced Users
Post by: puppies on August 25, 2015, 04:41:39 am: Quote from: cryptosile on August 25, 2015, 04:23:55 am
BMs commit seems to have broken the build of the tests. However, if you just do a make witness_node that should work. (Or you can use my automatically generated docker build that was pushed 10 minutes after the commit :)

https://hub.docker.com/r/sile16/graphene-witness/

I'm now pushing each commit as a separate tag
thanks
Title: Re: Test Net for Advanced Users
Post by: abit on August 25, 2015, 07:45:42 am: Quote from: Thom on August 24, 2015, 10:39:01 pm
That has always allowed me to restart, but now I can't without this crashing. Here's the output:

Code: [Select]
./witness: line 7: 32471 Segmentation fault ./witness_node --resync-blockchain -d test_net

I also encountered segment fault problem, most time is due to producing a block while out of sync. See https://github.com/cryptonomex/graphene/issues/261

If the program is crashing, try run it inside gdb:

Code: [Select]
$ gdb ... (gdb) file ./witness_node ... (gdb) set args --resync-blockchain -d test_net ... (gdb) run ...
Anytime you can end the program by pressing ctrl+C, then typing signal SIGINT:
Code: [Select]
(gdb) signal SIGINT
After crash, dump the back trace and post it here or to Github.
Title: Re: Test Net for Advanced Users
Post by: sudo on August 25, 2015, 08:16:14 am: Quote from: bytemaster on August 24, 2015, 03:00:50 pm
In the interest of not slipping the release date we are going to fall back to 3 or 5 second blocks using the current P2P code. Then after we update the P2P code we can increase the block rate to 2 and ultimately 1 second block times.

Ben is in the process of preparing instructions for committee members on how to change the block interval and we plan to dynamically update the test network to prove that we can do this on a live network.

+5% +5% step by step
Title: Re: Test Net for Advanced Users
Post by: iHashFury on August 25, 2015, 11:08:51 am: I forgot to set BOOST_ROOT=$HOME/tmp/boost_1_57_0

and

cmake BOOST_ROOT=$HOME/tmp/boost_1_57_0 .

Code: [Select]
#as user BOOST_ROOT=$HOME/tmp/boost_1_57_0 git clone https://github.com/cryptonomex/graphene.git cd graphene git pull #git checkout test1 git checkout master git submodule update --init --recursive #make clean #cmake -DCMAKE_BUILD_TYPE=Debug . cmake BOOST_ROOT=$HOME/tmp/boost_1_57_0 . make
but got it built on Ubuntu (change your boost folder as required)
You could also try make clean before cmake and make

Havent got it working on arm yet.
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on August 25, 2015, 12:18:09 pm: Quote from: bytemaster on August 24, 2015, 03:00:50 pm
In the interest of not slipping the release date we are going to fall back to 3 or 5 second blocks using the current P2P code. Then after we update the P2P code we can increase the block rate to 2 and ultimately 1 second block times.

Ben is in the process of preparing instructions for committee members on how to change the block interval and we plan to dynamically update the test network to prove that we can do this on a live network.

Excellent. As my martial arts instructor always says: "train the correct movement, and speed will come easily later."
Title: Re: Test Net for Advanced Users
Post by: alt on August 25, 2015, 01:15:55 pm: we should still use 10 seconds first, and release a user friendly wallet.
and we can begin the marketing work.
then we try 5 seconds, then 3 secs, then 2 secs, then 1 secs
every time we make an improve, we should look it as a big thing, it's a chance to push the marketing work.

in fact we have make so many great things.
but we give it to public too easy,
people don't cherish when they get it too easy.

Quote from: sudo on August 25, 2015, 08:16:14 am
Quote from: bytemaster on August 24, 2015, 03:00:50 pm
In the interest of not slipping the release date we are going to fall back to 3 or 5 second blocks using the current P2P code. Then after we update the P2P code we can increase the block rate to 2 and ultimately 1 second block times.

Ben is in the process of preparing instructions for committee members on how to change the block interval and we plan to dynamically update the test network to prove that we can do this on a live network.

+5% +5% step by step
Title: Re: Test Net for Advanced Users
Post by: Stan on August 25, 2015, 01:44:08 pm: Quote from: alt on August 25, 2015, 01:15:55 pm
in fact we have make so many great things.
but we give it to public too easy,
people don't cherish when they get it too easy.

Interesting point!

I can see the headlines now...
BitShares Doubles Speed
BitShares Doubles Speed Again
BitShares Doubles Speed Yet Again
and so on...

Why, that's three whole news cycle Announcements right there!

:)
Title: Re: Test Net for Advanced Users
Post by: abit on August 25, 2015, 01:49:59 pm: Quote from: cryptosile on August 25, 2015, 04:23:55 am
BMs commit seems to have broken the build of the tests. However, if you just do a make witness_node that should work. (Or you can use my automatically generated docker build that was pushed 10 minutes after the commit :)

https://hub.docker.com/r/sile16/graphene-witness/

I'm now pushing each commit as a separate tag
Thanks. Running with latest commit now.
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on August 25, 2015, 02:55:26 pm: Quote from: alt on August 25, 2015, 01:15:55 pm
we should still use 10 seconds first, and release a user friendly wallet.
and we can begin the marketing work.
then we try 5 seconds, then 3 secs, then 2 secs, then 1 secs
every time we make an improve, we should look it as a big thing, it's a chance to push the marketing work.

in fact we have make so many great things.
but we give it to public too easy,
people don't cherish when they get it too easy.

I support this idea +5%
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 25, 2015, 03:06:18 pm: Quote from: CalabiYau on August 25, 2015, 02:55:26 pm
Quote from: alt on August 25, 2015, 01:15:55 pm
we should still use 10 seconds first, and release a user friendly wallet.
and we can begin the marketing work.
then we try 5 seconds, then 3 secs, then 2 secs, then 1 secs
every time we make an improve, we should look it as a big thing, it's a chance to push the marketing work.

in fact we have make so many great things.
but we give it to public too easy,
people don't cherish when they get it too easy.

I support this idea +5%
Me too .. +1
Title: Re: Test Net for Advanced Users
Post by: cass on August 25, 2015, 03:15:21 pm: Quote from: xeroc on August 25, 2015, 03:06:18 pm
Quote from: CalabiYau on August 25, 2015, 02:55:26 pm
Quote from: alt on August 25, 2015, 01:15:55 pm
we should still use 10 seconds first, and release a user friendly wallet.
and we can begin the marketing work.
then we try 5 seconds, then 3 secs, then 2 secs, then 1 secs
every time we make an improve, we should look it as a big thing, it's a chance to push the marketing work.

in fact we have make so many great things.
but we give it to public too easy,
people don't cherish when they get it too easy.

I support this idea +5%
Me too .. +1

+5%
Title: Re: Test Net for Advanced Users
Post by: BTSdac on August 25, 2015, 03:44:18 pm: Quote from: cass on August 25, 2015, 03:15:21 pm
Quote from: xeroc on August 25, 2015, 03:06:18 pm
Quote from: CalabiYau on August 25, 2015, 02:55:26 pm
Quote from: alt on August 25, 2015, 01:15:55 pm
we should still use 10 seconds first, and release a user friendly wallet.
and we can begin the marketing work.
then we try 5 seconds, then 3 secs, then 2 secs, then 1 secs
every time we make an improve, we should look it as a big thing, it's a chance to push the marketing work.

in fact we have make so many great things.
but we give it to public too easy,
people don't cherish when they get it too easy.

I support this idea +5%
Me too .. +1

+5%
maybe I +5%
Title: Re: Test Net for Advanced Users
Post by: clayop on August 25, 2015, 04:02:20 pm: Quote from: alt on August 25, 2015, 01:15:55 pm
we should still use 10 seconds first, and release a user friendly wallet.
and we can begin the marketing work.
then we try 5 seconds, then 3 secs, then 2 secs, then 1 secs
every time we make an improve, we should look it as a big thing, it's a chance to push the marketing work.

in fact we have make so many great things.
but we give it to public too easy,
people don't cherish when they get it too easy.

IMO, 5 sec is also a good starting point.
Title: Re: Test Net for Advanced Users
Post by: CLains on August 25, 2015, 04:18:45 pm: 5, 2, 1 is good :D

Rule of 3.
Avoids 4 (China).
Avoids starting too low (BM said 3-5).
Each time it halves or more (including from where we are: 10s).
Title: Re: Test Net for Advanced Users
Post by: Akado on August 25, 2015, 05:24:46 pm: I don't know if it's the right place to ask but since we're talking about nodes. Will BitShares 2.0 allow -even if later through a worked proposal- for nodes with limited storage space, to store parts or slices of the blockchain history? Imagine storing only X latest blocks. Could allow for more people with limited storage space to join in I guess? Or would this only contribute to less nodes hosting the full blockchain? Since people could think and we know this is common: "someone else will do it".
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 25, 2015, 05:43:09 pm: Quote from: Akado on August 25, 2015, 05:24:46 pm
I don't know if it's the right place to ask but since we're talking about nodes. Will BitShares 2.0 allow -even if later through a worked proposal- for nodes with limited storage space, to store parts or slices of the blockchain history? Imagine storing only X latest blocks. Could allow for more people with limited storage space to join in I guess? Or would this only contribute to less nodes hosting the full blockchain? Since people could think and we know this is common: "someone else will do it".

The transaction history is not part of "chain state" and therefore, there is no requirement for any node to have anything other than the enough history to handle forking / reorganizing, less than 1000 blocks all kept in ram.

No hard fork required.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 25, 2015, 07:43:01 pm: Hmm, the latest build seems much more stable than before. BTW, is flood_network command disabled? I got a segmentation fault error.
Title: Re: Test Net for Advanced Users
Post by: rnglab on August 25, 2015, 08:52:43 pm: Indeed, witness_schedule_refactor builds ok and seems to run stable.

Should we start testing on this branch?

Edit: sorry, I should have read this first: https://bitsharestalk.org/index.php/topic,18126.0.html
devs, let us know if some tests helps to decide.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 25, 2015, 11:07:30 pm: Quote from: clayop on August 25, 2015, 07:43:01 pm
Hmm, the latest build seems much more stable than before. BTW, is flood_network command disabled? I got a segmentation fault error.

Did for me as well. Rebuilding the newest version now that I'm back from vacation. Nice to see a big "pull" response :D
Title: Re: Test Net for Advanced Users
Post by: alt on August 26, 2015, 12:09:59 am: can't build now, seems the new p2p source code can't work, but you have add this line at CMakeLists.txt:

+add_subdirectory( p2p )

try to checkout aeebb1be099fd325f014f4f35aa9e90bf2431839
Title: Re: Test Net for Advanced Users
Post by: clayop on August 26, 2015, 12:12:35 am: Quote from: alt on August 26, 2015, 12:09:59 am
can't build now, seems the new p2p source code can't work, but you have add this line at CMakeLists.txt:

+add_subdirectory( p2p )

try to checkout aeebb1be099fd325f014f4f35aa9e90bf2431839

make witness_node cli_wallet
Title: Re: Test Net for Advanced Users
Post by: alt on August 26, 2015, 12:52:08 am: thanks, it's sync now
Quote from: clayop on August 26, 2015, 12:12:35 am
Quote from: alt on August 26, 2015, 12:09:59 am
can't build now, seems the new p2p source code can't work, but you have add this line at CMakeLists.txt:

+add_subdirectory( p2p )

try to checkout aeebb1be099fd325f014f4f35aa9e90bf2431839

make witness_node cli_wallet
Title: Re: Test Net for Advanced Users
Post by: abit on August 26, 2015, 01:33:37 am: Quote from: clayop on August 25, 2015, 07:43:01 pm
Hmm, the latest build seems much more stable than before. BTW, is flood_network command disabled? I got a segmentation fault error.
Not so stable for me.. I still encounter segment fault error frequently. Like https://github.com/cryptonomex/graphene/issues/261. Perhaps because of my unstable network connection?

Anyway re-indexing is much faster than before, that's good.
Title: Re: Test Net for Advanced Users
Post by: sudo on August 26, 2015, 02:00:20 am: Quote from: alt on August 25, 2015, 01:15:55 pm
we should still use 10 seconds first, and release a user friendly wallet.
and we can begin the marketing work.
then we try 5 seconds, then 3 secs, then 2 secs, then 1 secs
every time we make an improve, we should look it as a big thing, it's a chance to push the marketing work.

in fact we have make so many great things.
but we give it to public too easy,
people don't cherish when they get it too easy.

Quote from: sudo on August 25, 2015, 08:16:14 am
Quote from: bytemaster on August 24, 2015, 03:00:50 pm
In the interest of not slipping the release date we are going to fall back to 3 or 5 second blocks using the current P2P code. Then after we update the P2P code we can increase the block rate to 2 and ultimately 1 second block times.

Ben is in the process of preparing instructions for committee members on how to change the block interval and we plan to dynamically update the test network to prove that we can do this on a live network.

+5% +5% step by step

good idea
as soon as possibile to release brand new BTS2.0 &keep testing
Title: Re: Test Net for Advanced Users
Post by: Riverhead on August 26, 2015, 02:20:35 am: Are we still using the Aug-20 genesis file? What's the current chain ID?
Title: Re: Test Net for Advanced Users
Post by: lafona on August 26, 2015, 02:33:47 am: Yeah it is still the Aug-20 genesis file and afaik the chain-id is d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083 although I have been having some slight problems getting synced and staying on the chain. It was producing blocks earlier though.
Title: Re: Test Net for Advanced Users
Post by: alt on August 26, 2015, 09:13:00 am: several times, my witeness node blocked at some block
I watch the p2p log, it received block 419543, then 419544, then missed 419545, then received 419546, .......
and it will never receive block 419545, I have to restart witness node, then it can request the block from other node.
I think we need a logic, when the witness node have missed a block more than 10 blocks, it should request from other node.
Title: Re: Test Net for Advanced Users
Post by: lafona on August 26, 2015, 01:00:52 pm: Just got my seed node up and running, the address is 73.182.245.244:32015
If you have any issues, let me know, it is on a raspberry pi, so I am not sure how long it will last, but I will be checking up on it regularly.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 26, 2015, 01:15:44 pm: Quote from: alt on August 26, 2015, 09:13:00 am
several times, my witeness node blocked at some block
I watch the p2p log, it received block 419543, then 419544, then missed 419545, then received 419546, .......
and it will never receive block 419545, I have to restart witness node, then it can request the block from other node.
I think we need a logic, when the witness node have missed a block more than 10 blocks, it should request from other node.

Eric checked in some fixes that may address this particular problem. We do have logic to request from another node, but the timeouts were still tuned to BTS 1 timeframes so we reduced the timeout for BTS 2.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 26, 2015, 01:29:18 pm: I just killed the chain. Will be back with a new test network later this week.
Title: Re: Test Net for Advanced Users
Post by: xeroc on August 26, 2015, 02:07:43 pm: Quote from: bytemaster on August 26, 2015, 01:29:18 pm
I just killed the chain. Will be back with a new test network later this week.
You certainly need to think about your wording .. unless you want people to believe you actually CAN kill the blockchain.

I assume you just switched of your initial witness nodes ..
Title: Re: Test Net for Advanced Users
Post by: bulletproof on August 26, 2015, 02:31:24 pm: Quote from: puppies on August 22, 2015, 10:48:48 pm
Quote from: clout on August 22, 2015, 10:16:12 pm
Get this error:

Code: [Select]
10 assert_exception: Assert Exception operations.size() > 0: A transaction must have at least one operation {"trx":{"ref_block_num":0,"ref_block_prefix":0,"expiration":"1970-01-01T00:00:00","operations":[],"extensions":[]}} th_a transaction.cpp:51 validate {"name_or_id":"the-ae"} th_a wallet.cpp:2762 import_balance
when I try to import balance...
pretty sure that means that key has no balance.

Getting this same error with test1 build while trying to import the 'nathan' account - am I doing something wrong? Witness node is running and currently at #260,000 (not producing blocks). Am I just not synced yet?

Code: [Select]
unlocked >>> import_balance nathan [5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3] true import_balance nathan [5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3] true 1417187ms th_a wallet.cpp:2721 import_balance ] balances: [] 10 assert_exception: Assert Exception operations.size() > 0: A transaction must have at least one operation {"trx":{"ref_block_num":0,"ref_block_prefix":0,"expiration":"1970-01-01T00:00:00","operations":[],"extensions":[]}} th_a transaction.cpp:51 validate {"name_or_id":"nathan"} th_a wallet.cpp:2762 import_balance unlocked >>>
Thx

EDIT: Just seen head block is at 427293 - will wait a while :)
Title: Re: Test Net for Advanced Users
Post by: abit on August 26, 2015, 03:13:36 pm: Quote from: bytemaster on August 26, 2015, 01:15:44 pm
Quote from: alt on August 26, 2015, 09:13:00 am
several times, my witeness node blocked at some block
I watch the p2p log, it received block 419543, then 419544, then missed 419545, then received 419546, .......
and it will never receive block 419545, I have to restart witness node, then it can request the block from other node.
I think we need a logic, when the witness node have missed a block more than 10 blocks, it should request from other node.

Eric checked in some fixes that may address this particular problem. We do have logic to request from another node, but the timeouts were still tuned to BTS 1 timeframes so we reduced the timeout for BTS 2.
Can't wait. Where is the new code?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 26, 2015, 04:53:58 pm: Quote from: xeroc on August 26, 2015, 02:07:43 pm
Quote from: bytemaster on August 26, 2015, 01:29:18 pm
I just killed the chain. Will be back with a new test network later this week.
You certainly need to think about your wording .. unless you want people to believe you actually CAN kill the blockchain.

I assume you just switched of your initial witness nodes ..

LOL, yes.
Title: Re: Test Net for Advanced Users
Post by: bulletproof on August 28, 2015, 08:16:27 pm: Just to follow up my ask in the Mumble - please consider getting this/a test net up again whilst one for the GUI is being worked on. I have been using it to test the cli_wallet API with the 2.0 version of my bitshares Ruby Gem & can't proceed until it is back up :-\

Thx & have a good weekend all
Title: Re: Test Net for Advanced Users
Post by: puppies on August 28, 2015, 08:37:16 pm: Quote from: bulletproof on August 28, 2015, 08:16:27 pm
Just to follow up my ask in the Mumble - please consider getting this/a test net up again whilst one for the GUI is being worked on. I have been using it to test the cli_wallet API with the 2.0 version of my bitshares Ruby Gem & can't proceed until it is back up :-\

Thx & have a good weekend all
is there a reason you need an actual network up? Couldn't you just run a local instance on and test that way?
Title: Re: Test Net for Advanced Users
Post by: bulletproof on August 28, 2015, 08:56:59 pm: Thanks puppies, will see how far I can get with that & leave 'flood_network' & other network commands until there is one
Title: Re: Test Net for Advanced Users
Post by: bytemaster on August 28, 2015, 09:19:05 pm: The test network has been delayed because we have a random crash in block production that we just now identified the cause of.

It took me 1M blocks to reproduce the issue on my local test net!
Title: Re: Test Net for Advanced Users
Post by: clayop on August 29, 2015, 06:36:29 pm: Quote from: bytemaster on August 28, 2015, 09:19:05 pm
The test network has been delayed because we have a random crash in block production that we just now identified the cause of.

It took me 1M blocks to reproduce the issue on my local test net!

Somewhat disappointed but it's understandable. Can you tell ETA?
Title: Re: Test Net for Advanced Users
Post by: puppies on August 29, 2015, 08:20:05 pm: Quote from: bulletproof on August 28, 2015, 08:56:59 pm
Thanks puppies, will see how far I can get with that & leave 'flood_network' & other network commands until there is one
the vps I'm using for testing graphene is just sitting around right now. If you need peers to join you let me know.
Title: Re: Test Net for Advanced Users
Post by: lafona on August 29, 2015, 10:14:55 pm: Quote from: puppies on August 29, 2015, 08:20:05 pm
Quote from: bulletproof on August 28, 2015, 08:56:59 pm
Thanks puppies, will see how far I can get with that & leave 'flood_network' & other network commands until there is one
the vps I'm using for testing graphene is just sitting around right now. If you need peers to join you let me know.
Yeah same here
Title: Re: Test Net for Advanced Users
Post by: lakerta06 on August 29, 2015, 10:25:32 pm: Quote from: clayop on August 29, 2015, 06:36:29 pm
Quote from: bytemaster on August 28, 2015, 09:19:05 pm
The test network has been delayed because we have a random crash in block production that we just now identified the cause of.

It took me 1M blocks to reproduce the issue on my local test net!

Somewhat disappointed but it's understandable. Can you tell ETA?

what is the nature of your disappointment, I dont understand?
Title: Re: Test Net for Advanced Users
Post by: clayop on August 29, 2015, 10:27:10 pm: Quote from: lakerta06 on August 29, 2015, 10:25:32 pm
Quote from: clayop on August 29, 2015, 06:36:29 pm
Quote from: bytemaster on August 28, 2015, 09:19:05 pm
The test network has been delayed because we have a random crash in block production that we just now identified the cause of.

It took me 1M blocks to reproduce the issue on my local test net!

Somewhat disappointed but it's understandable. Can you tell ETA?

what is the nature of your disappointment, I dont understand?

Because I eagered for the new testnet
Title: Re: Test Net for Advanced Users
Post by: clayop on August 29, 2015, 10:30:23 pm: Quote from: puppies on August 29, 2015, 08:20:05 pm
Quote from: bulletproof on August 28, 2015, 08:56:59 pm
Thanks puppies, will see how far I can get with that & leave 'flood_network' & other network commands until there is one
the vps I'm using for testing graphene is just sitting around right now. If you need peers to join you let me know.

Are you running GUI node too?
Title: Re: Test Net for Advanced Users
Post by: puppies on August 29, 2015, 10:40:42 pm: Quote from: clayop on August 29, 2015, 10:30:23 pm
Quote from: puppies on August 29, 2015, 08:20:05 pm
Quote from: bulletproof on August 28, 2015, 08:56:59 pm
Thanks puppies, will see how far I can get with that & leave 'flood_network' & other network commands until there is one
the vps I'm using for testing graphene is just sitting around right now. If you need peers to join you let me know.

Are you running GUI node too?
I'm not running anything right now. I could run a gui node, but you would not be able to sign up for new accounts with it. You would have to import.
Title: Re: Test Net for Advanced Users
Post by: clayop on August 31, 2015, 10:43:42 pm: https://github.com/cryptonomex/graphene/releases/tag/test2
Title: Re: Test Net for Advanced Users
Post by: Ander on August 31, 2015, 11:01:28 pm: Whats different in this new test net? How close is it getting?
Title: Re: Test Net for Advanced Users
Post by: lafona on September 01, 2015, 12:08:05 am: Anyone else getting this when trying to update the submodule

Code: [Select]
fatal: reference is not a tree: 80d967a70d21d26d27ef3a1544a177925b2a7bbe Unable to checkout '80d967a70d21d26d27ef3a1544a177925b2a7bbe' in submodule path 'libraries/fc'
Title: Re: Test Net for Advanced Users
Post by: clayop on September 01, 2015, 12:12:54 am: An error in CMake.

Code: [Select]
CMake Error at CMakeLists.txt:36 (include): include could not find load file: GetGitRevisionDescription CMake Error at CMakeLists.txt:37 (get_git_head_revision): Unknown CMake command "get_git_head_revision".
Title: Re: Test Net for Advanced Users
Post by: puppies on September 01, 2015, 12:24:21 am: Quote from: clayop on August 31, 2015, 10:43:42 pm
https://github.com/cryptonomex/graphene/releases/tag/test2

WOOT!!!
Title: Re: Test Net for Advanced Users
Post by: clayop on September 01, 2015, 12:29:25 am: How can I update fc submodule wit 71be796af50c407281a40e61e4199a87e0a19314 ? Please explain for a dummy
Title: Re: Test Net for Advanced Users
Post by: puppies on September 01, 2015, 12:35:11 am: Quote from: clayop on September 01, 2015, 12:29:25 am
How can I update fc submodule wit 71be796af50c407281a40e61e4199a87e0a19314 ? Please explain for a dummy
Quote from: lafona on September 01, 2015, 12:08:05 am
Anyone else getting this when trying to update the submodule

Code: [Select]
fatal: reference is not a tree: 80d967a70d21d26d27ef3a1544a177925b2a7bbe Unable to checkout '80d967a70d21d26d27ef3a1544a177925b2a7bbe' in submodule path 'libraries/fc'

AWW
Title: Re: Test Net for Advanced Users
Post by: puppies on September 01, 2015, 12:38:53 am: Quote from: clayop on September 01, 2015, 12:29:25 am
How can I update fc submodule wit 71be796af50c407281a40e61e4199a87e0a19314 ? Please explain for a dummy

This is how I did it. It is still building so I don't know if it worked yet.

Code: [Select]
git pull git checkout test2 git submodule update --init --recursive cd libraries rm -r fc git clone https://github.com/cryptonomex/fc.git cd fc git submodule update --init --recursive cd ../.. cmake . make
Title: Re: Test Net for Advanced Users
Post by: clayop on September 01, 2015, 12:47:42 am: Quote from: puppies on September 01, 2015, 12:38:53 am
Quote from: clayop on September 01, 2015, 12:29:25 am
How can I update fc submodule wit 71be796af50c407281a40e61e4199a87e0a19314 ? Please explain for a dummy

This is how I did it. It is still building so I don't know if it worked yet.

Code: [Select]
git pull git checkout test2 git submodule update --init --recursive cd libraries rm -r fc git clone https://github.com/cryptonomex/fc.git cd fc git submodule update --init --recursive cd ../.. cmake . make

Thanks! Building now.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 01, 2015, 12:57:11 am: build failed for me. Please let me know if you find a way around it.

Code: [Select]
/home/user/src/graphene/libraries/plugins/witness/witness.cpp:229:10: note: in expansion of macro ‘elog’ elog("Not producing block because node appears to be on a minority fork with only ${pct}% witness participation", (capture) ); ^ make[2]: *** [libraries/plugins/witness/CMakeFiles/graphene_witness.dir/witness.cpp.o] Error 1 make[1]: *** [libraries/plugins/witness/CMakeFiles/graphene_witness.dir/all] Error 2 make: *** [all] Error 2 user@user-desktop:~/src/graphene$
Title: Re: Test Net for Advanced Users
Post by: clayop on September 01, 2015, 01:04:10 am: Quote from: puppies on September 01, 2015, 12:57:11 am
build failed for me. Please let me know if you find a way around it.

Code: [Select]
/home/user/src/graphene/libraries/plugins/witness/witness.cpp:229:10: note: in expansion of macro ‘elog’ elog("Not producing block because node appears to be on a minority fork with only ${pct}% witness participation", (capture) ); ^ make[2]: *** [libraries/plugins/witness/CMakeFiles/graphene_witness.dir/witness.cpp.o] Error 1 make[1]: *** [libraries/plugins/witness/CMakeFiles/graphene_witness.dir/all] Error 2 make: *** [all] Error 2 user@user-desktop:~/src/graphene$

Same error occurred. Hopefully devs will fix it ASAP.
Title: Re: Test Net for Advanced Users
Post by: abit on September 01, 2015, 10:22:28 am: Quote from: clayop on September 01, 2015, 01:04:10 am
Quote from: puppies on September 01, 2015, 12:57:11 am
build failed for me. Please let me know if you find a way around it.

Code: [Select]
/home/user/src/graphene/libraries/plugins/witness/witness.cpp:229:10: note: in expansion of macro ‘elog’ elog("Not producing block because node appears to be on a minority fork with only ${pct}% witness participation", (capture) ); ^ make[2]: *** [libraries/plugins/witness/CMakeFiles/graphene_witness.dir/witness.cpp.o] Error 1 make[1]: *** [libraries/plugins/witness/CMakeFiles/graphene_witness.dir/all] Error 2 make: *** [all] Error 2 user@user-desktop:~/src/graphene$

Same error occurred. Hopefully devs will fix it ASAP.

Fixed by editing this file:
Code: [Select]
libraries/plugins/witness/witness.cppline 214:
Code: [Select]
ilog("Generated block #${n} with timestamp ${t} at time ${c}", ("n",capture)("t",capture)("c",capture));line 226:
Code: [Select]
ilog("Not producing block because I don't have the private key for ${scheduled_key}", ("scheduled_key",capture) );line 229:
Code: [Select]
elog("Not producing block because node appears to be on a minority fork with only ${pct}% witness participation", ("pct",capture) );
Pull request created: https://github.com/cryptonomex/graphene/pull/285
Title: Re: Test Net for Advanced Users
Post by: abit on September 01, 2015, 10:59:53 am: I'm up with 'test2' code and aug-31 genesis.
witness id 1.6.5247, node address 114.92.254.159:62015
Title: Re: Test Net for Advanced Users
Post by: abit on September 01, 2015, 11:58:20 am: Quote from: bytemaster on August 26, 2015, 01:15:44 pm
Quote from: alt on August 26, 2015, 09:13:00 am
several times, my witeness node blocked at some block
I watch the p2p log, it received block 419543, then 419544, then missed 419545, then received 419546, .......
and it will never receive block 419545, I have to restart witness node, then it can request the block from other node.
I think we need a logic, when the witness node have missed a block more than 10 blocks, it should request from other node.

Eric checked in some fixes that may address this particular problem. We do have logic to request from another node, but the timeouts were still tuned to BTS 1 timeframes so we reduced the timeout for BTS 2.
Still have same problem with test2 tag.
Please check this issue https://github.com/cryptonomex/graphene/issues/264
Title: Re: Test Net for Advanced Users
Post by: bulletproof on September 01, 2015, 12:09:19 pm: Quote from: abit on September 01, 2015, 10:59:53 am
I'm up with 'test2' code and aug-31 genesis.
witness id 1.6.5247, node address 114.92.254.159:62015

Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-31-testnet-genesis.json -d test_net_2 -s "104.236.118.105:1776"
Confirm test2 witness node and cli_client now working with abitmore's changes in PR #285. On block #10578 and counting :). Can see your witness with >>>info:
Code: [Select]
... "1.6.100", "1.6.5247"
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 01, 2015, 01:01:29 pm: Quote from: abit on September 01, 2015, 11:58:20 am
Quote from: bytemaster on August 26, 2015, 01:15:44 pm
Quote from: alt on August 26, 2015, 09:13:00 am
several times, my witeness node blocked at some block
I watch the p2p log, it received block 419543, then 419544, then missed 419545, then received 419546, .......
and it will never receive block 419545, I have to restart witness node, then it can request the block from other node.
I think we need a logic, when the witness node have missed a block more than 10 blocks, it should request from other node.

Eric checked in some fixes that may address this particular problem. We do have logic to request from another node, but the timeouts were still tuned to BTS 1 timeframes so we reduced the timeout for BTS 2.
Still have same problem with test2 tag.
Please check this issue https://github.com/cryptonomex/graphene/issues/264

In the test2b tag I have increase the allowance for out-of-order blocks. If it still happens then something else is going on.
Title: Re: Test Net for Advanced Users
Post by: abit on September 01, 2015, 01:45:47 pm: Quote from: bytemaster on September 01, 2015, 01:01:29 pm
Quote from: abit on September 01, 2015, 11:58:20 am
Quote from: bytemaster on August 26, 2015, 01:15:44 pm
Quote from: alt on August 26, 2015, 09:13:00 am
several times, my witeness node blocked at some block
I watch the p2p log, it received block 419543, then 419544, then missed 419545, then received 419546, .......
and it will never receive block 419545, I have to restart witness node, then it can request the block from other node.
I think we need a logic, when the witness node have missed a block more than 10 blocks, it should request from other node.

Eric checked in some fixes that may address this particular problem. We do have logic to request from another node, but the timeouts were still tuned to BTS 1 timeframes so we reduced the timeout for BTS 2.
Still have same problem with test2 tag.
Please check this issue https://github.com/cryptonomex/graphene/issues/264

In the test2b tag I have increase the allowance for out-of-order blocks. If it still happens then something else is going on.
My intuition told me that it is not fixed completely.. The "_max_size" matters.
See the last line of log at https://github.com/cryptonomex/graphene/issues/264#issuecomment-136688527

Building with new tag anyway..
Title: Re: Test Net for Advanced Users
Post by: theoretical on September 01, 2015, 03:48:31 pm: Quote from: lafona on September 01, 2015, 12:08:05 am
Anyone else getting this when trying to update the submodule

Code: [Select]
fatal: reference is not a tree: 80d967a70d21d26d27ef3a1544a177925b2a7bbe Unable to checkout '80d967a70d21d26d27ef3a1544a177925b2a7bbe' in submodule path 'libraries/fc'

Sorry about that, I goofed -- I forgot to push a commit to fc. Try again, it should be good now.
Title: Re: Test Net for Advanced Users
Post by: abit on September 01, 2015, 03:52:24 pm: Quote from: theoretical on September 01, 2015, 03:48:31 pm

Quote from: lafona on September 01, 2015, 12:08:05 am
Anyone else getting this when trying to update the submodule

Code: [Select]
fatal: reference is not a tree: 80d967a70d21d26d27ef3a1544a177925b2a7bbe Unable to checkout '80d967a70d21d26d27ef3a1544a177925b2a7bbe' in submodule path 'libraries/fc'

Sorry about that, I goofed -- I forgot to push a commit to fc. Try again, it should be good now.
Yes, the test2b tag works fine.
I'm running.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 01, 2015, 05:45:01 pm: delegate-clayop (1.6.1538) is running and producing blocks.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 01, 2015, 06:06:32 pm: dele-puppy is up an running too. Heading to work, but I will be keeping an eye on it.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 01, 2015, 07:07:33 pm: Why does the following happen? Sometimes it takes about 20 seconds to sync the block

Code: [Select]
300404ms th_a application.cpp:356 handle_block ] Got block #15325 from network 300507ms th_a api.cpp:867 on_objects_changed ] ids: ["2.8.15325","2.3.0","2.4.32","2.4.31","2.4.30","2.4.29","2.4.28","2.4.27","2.4.26","2.4.25","2.4.24","2.4.23","2.4.22","1.6.91","1.14.51","2.4.15","1.6.90","1.14.50","2.4.14","1.6.89","1.14.49","2.4.13","1.6.88","1.14.48","2.4.12","1.6.87","1.14.47","2.4.11","1.6.86","1.14.46","2.4.10","1.6.85","1.14.45","2.4.9","1.6.84","1.14.44","2.4.8","1.6.82","1.14.42","2.4.6","1.6.80","1.14.40","2.4.4","1.6.79","1.14.39","2.4.3","1.6.78","1.14.38","1.6.77","1.14.37","1.6.76","1.14.36","1.6.75","1.14.35","1.6.74","1.14.34","1.6.73","1.6.5247","1.14.33","1.6.71","1.14.31","1.6.70","1.14.30","1.6.69","1.14.29","1.6.68","1.14.28","1.6.67","1.14.27","1.6.66","1.14.26","1.6.65","1.14.25","1.6.64","1.14.24","1.6.63","1.14.23","1.6.62","1.14.22","1.6.61","2.1.0","1.14.21","1.6.60","1.14.20","1.6.59","1.14.19","1.6.58","1.14.18","1.6.56","1.14.16","1.6.54","1.14.14","1.6.53","1.14.13","1.6.52","1.14.12","1.6.51","1.14.11","1.6.50","1.14.10","1.6.49","1.14.9","1.6.48","1.14.8","1.6.47","1.14.7","1.6.46","1.14.6","1.6.45","1.6.44","1.14.4","1.6.43","1.14.3","1.6.42","1.14.2","1.6.41","1.14.1","1.6.16","1.6.15","1.6.13","1.6.12","1.6.11","1.6.10","1.6.8","1.6.55","1.14.15","1.6.81","1.14.41","2.4.5","1.14.5","1.13.74","1.6.7","1.6.6","1.6.5","2.4.2","1.5.10","1.6.14","1.6.57","1.14.17","1.6.17","1.6.83","1.14.43","2.4.7","1.6.1538","1.6.34","2.0.0","1.6.72","1.14.32","1.6.1527","1.6.23","1.6.1","1.5.6","1.6.2","1.5.7","1.6.9","1.6.30","1.6.3","2.4.0","1.5.8","1.6.4","2.4.1","1.5.9","1.6.18","1.6.19","1.6.20","1.6.21","1.6.22","1.6.24","1.6.25","1.6.26","1.6.27","1.6.28","1.6.29","1.6.31","1.6.32","1.6.33","1.6.35","1.6.36","1.6.37","1.6.38","1.6.39","1.6.40","1.14.0","1.6.92","1.14.52","2.4.16","1.6.93","1.14.53","2.4.17","1.6.94","1.14.54","2.4.18","1.6.95","1.14.55","2.4.19","1.6.96","1.14.56","2.4.20","1.6.97","1.14.57","2.4.21","1.6.98","1.2.1","1.5.0","1.5.1","1.5.2","1.5.3","1.5.4","1.5.5","1.2.0","1.2.2"] 300508ms th_a api.cpp:867 on_objects_changed ] ids: ["2.8.15325","2.3.0","2.4.32","2.4.31","2.4.30","2.4.29","2.4.28","2.4.27","2.4.26","2.4.25","2.4.24","2.4.23","2.4.22","1.6.91","1.14.51","2.4.15","1.6.90","1.14.50","2.4.14","1.6.89","1.14.49","2.4.13","1.6.88","1.14.48","2.4.12","1.6.87","1.14.47","2.4.11","1.6.86","1.14.46","2.4.10","1.6.85","1.14.45","2.4.9","1.6.84","1.14.44","2.4.8","1.6.82","1.14.42","2.4.6","1.6.80","1.14.40","2.4.4","1.6.79","1.14.39","2.4.3","1.6.78","1.14.38","1.6.77","1.14.37","1.6.76","1.14.36","1.6.75","1.14.35","1.6.74","1.14.34","1.6.73","1.6.5247","1.14.33","1.6.71","1.14.31","1.6.70","1.14.30","1.6.69","1.14.29","1.6.68","1.14.28","1.6.67","1.14.27","1.6.66","1.14.26","1.6.65","1.14.25","1.6.64","1.14.24","1.6.63","1.14.23","1.6.62","1.14.22","1.6.61","2.1.0","1.14.21","1.6.60","1.14.20","1.6.59","1.14.19","1.6.58","1.14.18","1.6.56","1.14.16","1.6.54","1.14.14","1.6.53","1.14.13","1.6.52","1.14.12","1.6.51","1.14.11","1.6.50","1.14.10","1.6.49","1.14.9","1.6.48","1.14.8","1.6.47","1.14.7","1.6.46","1.14.6","1.6.45","1.6.44","1.14.4","1.6.43","1.14.3","1.6.42","1.14.2","1.6.41","1.14.1","1.6.16","1.6.15","1.6.13","1.6.12","1.6.11","1.6.10","1.6.8","1.6.55","1.14.15","1.6.81","1.14.41","2.4.5","1.14.5","1.13.74","1.6.7","1.6.6","1.6.5","2.4.2","1.5.10","1.6.14","1.6.57","1.14.17","1.6.17","1.6.83","1.14.43","2.4.7","1.6.1538","1.6.34","2.0.0","1.6.72","1.14.32","1.6.1527","1.6.23","1.6.1","1.5.6","1.6.2","1.5.7","1.6.9","1.6.30","1.6.3","2.4.0","1.5.8","1.6.4","2.4.1","1.5.9","1.6.18","1.6.19","1.6.20","1.6.21","1.6.22","1.6.24","1.6.25","1.6.26","1.6.27","1.6.28","1.6.29","1.6.31","1.6.32","1.6.33","1.6.35","1.6.36","1.6.37","1.6.38","1.6.39","1.6.40","1.14.0","1.6.92","1.14.52","2.4.16","1.6.93","1.14.53","2.4.17","1.6.94","1.14.54","2.4.18","1.6.95","1.14.55","2.4.19","1.6.96","1.14.56","2.4.20","1.6.97","1.14.57","2.4.21","1.6.98","1.2.1","1.5.0","1.5.1","1.5.2","1.5.3","1.5.4","1.5.5","1.2.0","1.2.2"] 301000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 301000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134300997030 next_second: 2015-09-01T19:05:02 302000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 302000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134301997280 next_second: 2015-09-01T19:05:03 303000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 303000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134302997131 next_second: 2015-09-01T19:05:04 304000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 304000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134303997090 next_second: 2015-09-01T19:05:05 305000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 305000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134304997093 next_second: 2015-09-01T19:05:06 306000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 306000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134305997265 next_second: 2015-09-01T19:05:07 307000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 307000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134306997192 next_second: 2015-09-01T19:05:08 308000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 308000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134307997036 next_second: 2015-09-01T19:05:09 309000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 309000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134308997313 next_second: 2015-09-01T19:05:10 310000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 310000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134309997066 next_second: 2015-09-01T19:05:11 311000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 311000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134310997084 next_second: 2015-09-01T19:05:12 312000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 312000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134311997095 next_second: 2015-09-01T19:05:13 313000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 313000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134312997001 next_second: 2015-09-01T19:05:14 314000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 314000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134313997077 next_second: 2015-09-01T19:05:15 315000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 315000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134314997092 next_second: 2015-09-01T19:05:16 316000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 316000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134315997044 next_second: 2015-09-01T19:05:17 317000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 317000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134316997130 next_second: 2015-09-01T19:05:18 318000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 318000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134317997088 next_second: 2015-09-01T19:05:19 319000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 319000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134318997059 next_second: 2015-09-01T19:05:20 320000ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn 320000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134319997193 next_second: 2015-09-01T19:05:21 320276ms th_a application.cpp:356 handle_block ] Got block #15326 from network 320277ms th_a api.cpp:867 on_objects_changed ] ids: ["2.8.15326","1.6.20","1.13.127","2.1.0"] 320277ms th_a api.cpp:867 on_objects_changed ] ids: ["2.8.15326","1.6.20","1.13.127","2.1.0"]
Title: Re: Test Net for Advanced Users
Post by: puppies on September 01, 2015, 07:47:25 pm: Quote from: clayop on September 01, 2015, 07:07:33 pm
Why does the following happen? Sometimes it takes about 20 seconds to sync the block

Code: [Select]
300404ms th_a application.cpp:356 handle_block ] Got block #15325 from network 300507ms th_a api.cpp:867 on_objects_changed ] ids: ["2.8.15325","2.3.0","2.4.32","2.4.31","2.4.30","2.4.29","2.4.28","2.4.27","2.4.26","2.4.25","2.4.24","2.4.23","2.4.22","1.6.91","1.14.51","2.4.15","1.6.90","1.14.50","2.4.14","1.6.89","1.14.49","2.4.13","1.6.88","1.14.48","2.4.12","1.6.87","1.14.47","2.4.11","1.6.86","1.14.46","2.4.10","1.6.85","1.14.45","2.4.9","1.6.84","1.14.44","2.4.8","1.6.82","1.14.42","2.4.6","1.6.80","1.14.40","2.4.4","1.6.79","1.14.39","2.4.3","1.6.78","1.14.38","1.6.77","1.14.37","1.6.76","1.14.36","1.6.75","1.14.35","1.6.74","1.14.34","1.6.73","1.6.5247","1.14.33","1.6.71","1.14.31","1.6.70","1.14.30","1.6.69","1.14.29","1.6.68","1.14.28","1.6.67","1.14.27","1.6.66","1.14.26","1.6.65","1.14.25","1.6.64","1.14.24","1.6.63","1.14.23","1.6.62","1.14.22","1.6.61","2.1.0","1.14.21","1.6.60","1.14.20","1.6.59","1.14.19","1.6.58","1.14.18","1.6.56","1.14.16","1.6.54","1.14.14","1.6.53","1.14.13","1.6.52","1.14.12","1.6.51","1.14.11","1.6.50","1.14.10","1.6.49","1.14.9","1.6.48","1.14.8","1.6.47","1.14.7","1.6.46","1.14.6","1.6.45","1.6.44","1.14.4","1.6.43","1.14.3","1.6.42","1.14.2","1.6.41","1.14.1","1.6.16","1.6.15","1.6.13","1.6.12","1.6.11","1.6.10","1.6.8","1.6.55","1.14.15","1.6.81","1.14.41","2.4.5","1.14.5","1.13.74","1.6.7","1.6.6","1.6.5","2.4.2","1.5.10","1.6.14","1.6.57","1.14.17","1.6.17","1.6.83","1.14.43","2.4.7","1.6.1538","1.6.34","2.0.0","1.6.72","1.14.32","1.6.1527","1.6.23","1.6.1","1.5.6","1.6.2","1.5.7","1.6.9","1.6.30","1.6.3","2.4.0","1.5.8","1.6.4","2.4.1","1.5.9","1.6.18","1.6.19","1.6.20","1.6.21","1.6.22","1.6.24","1.6.25","1.6.26","1.6.27","1.6.28","1.6.29","1.6.31","1.6.32","1.6.33","1.6.35","1.6.36","1.6.37","1.6.38","1.6.39","1.6.40","1.14.0","1.6.92","1.14.52","2.4.16","1.6.93","1.14.53","2.4.17","1.6.94","1.14.54","2.4.18","1.6.95","1.14.55","2.4.19","1.6.96","1.14.56","2.4.20","1.6.97","1.14.57","2.4.21","1.6.98","1.2.1","1.5.0","1.5.1","1.5.2","1.5.3","1.5.4","1.5.5","1.2.0","1.2.2"] 300508ms th_a api.cpp:867 on_objects_changed ] ids: ["2.8.15325","2.3.0","2.4.32","2.4.31","2.4.30","2.4.29","2.4.28","2.4.27","2.4.26","2.4.25","2.4.24","2.4.23","2.4.22","1.6.91","1.14.51","2.4.15","1.6.90","1.14.50","2.4.14","1.6.89","1.14.49","2.4.13","1.6.88","1.14.48","2.4.12","1.6.87","1.14.47","2.4.11","1.6.86","1.14.46","2.4.10","1.6.85","1.14.45","2.4.9","1.6.84","1.14.44","2.4.8","1.6.82","1.14.42","2.4.6","1.6.80","1.14.40","2.4.4","1.6.79","1.14.39","2.4.3","1.6.78","1.14.38","1.6.77","1.14.37","1.6.76","1.14.36","1.6.75","1.14.35","1.6.74","1.14.34","1.6.73","1.6.5247","1.14.33","1.6.71","1.14.31","1.6.70","1.14.30","1.6.69","1.14.29","1.6.68","1.14.28","1.6.67","1.14.27","1.6.66","1.14.26","1.6.65","1.14.25","1.6.64","1.14.24","1.6.63","1.14.23","1.6.62","1.14.22","1.6.61","2.1.0","1.14.21","1.6.60","1.14.20","1.6.59","1.14.19","1.6.58","1.14.18","1.6.56","1.14.16","1.6.54","1.14.14","1.6.53","1.14.13","1.6.52","1.14.12","1.6.51","1.14.11","1.6.50","1.14.10","1.6.49","1.14.9","1.6.48","1.14.8","1.6.47","1.14.7","1.6.46","1.14.6","1.6.45","1.6.44","1.14.4","1.6.43","1.14.3","1.6.42","1.14.2","1.6.41","1.14.1","1.6.16","1.6.15","1.6.13","1.6.12","1.6.11","1.6.10","1.6.8","1.6.55","1.14.15","1.6.81","1.14.41","2.4.5","1.14.5","1.13.74","1.6.7","1.6.6","1.6.5","2.4.2","1.5.10","1.6.14","1.6.57","1.14.17","1.6.17","1.6.83","1.14.43","2.4.7","1.6.1538","1.6.34","2.0.0","1.6.72","1.14.32","1.6.1527","1.6.23","1.6.1","1.5.6","1.6.2","1.5.7","1.6.9","1.6.30","1.6.3","2.4.0","1.5.8","1.6.4","2.4.1","1.5.9","1.6.18","1.6.19","1.6.20","1.6.21","1.6.22","1.6.24","1.6.25","1.6.26","1.6.27","1.6.28","1.6.29","1.6.31","1.6.32","1.6.33","1.6.35","1.6.36","1.6.37","1.6.38","1.6.39","1.6.40","1.14.0","1.6.92","1.14.52","2.4.16","1.6.93","1.14.53","2.4.17","1.6.94","1.14.54","2.4.18","1.6.95","1.14.55","2.4.19","1.6.96","1.14.56","2.4.20","1.6.97","1.14.57","2.4.21","1.6.98","1.2.1","1.5.0","1.5.1","1.5.2","1.5.3","1.5.4","1.5.5","1.2.0","1.2.2"] 301000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 301000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134300997030 next_second: 2015-09-01T19:05:02 302000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 302000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134301997280 next_second: 2015-09-01T19:05:03 303000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 303000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134302997131 next_second: 2015-09-01T19:05:04 304000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 304000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134303997090 next_second: 2015-09-01T19:05:05 305000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 305000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134304997093 next_second: 2015-09-01T19:05:06 306000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 306000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134305997265 next_second: 2015-09-01T19:05:07 307000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 307000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134306997192 next_second: 2015-09-01T19:05:08 308000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 308000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134307997036 next_second: 2015-09-01T19:05:09 309000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 309000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134308997313 next_second: 2015-09-01T19:05:10 310000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 310000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134309997066 next_second: 2015-09-01T19:05:11 311000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 311000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134310997084 next_second: 2015-09-01T19:05:12 312000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 312000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134311997095 next_second: 2015-09-01T19:05:13 313000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 313000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134312997001 next_second: 2015-09-01T19:05:14 314000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 314000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134313997077 next_second: 2015-09-01T19:05:15 315000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 315000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134314997092 next_second: 2015-09-01T19:05:16 316000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 316000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134315997044 next_second: 2015-09-01T19:05:17 317000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 317000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134316997130 next_second: 2015-09-01T19:05:18 318000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 318000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134317997088 next_second: 2015-09-01T19:05:19 319000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 319000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134318997059 next_second: 2015-09-01T19:05:20 320000ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn 320000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441134319997193 next_second: 2015-09-01T19:05:21 320276ms th_a application.cpp:356 handle_block ] Got block #15326 from network 320277ms th_a api.cpp:867 on_objects_changed ] ids: ["2.8.15326","1.6.20","1.13.127","2.1.0"] 320277ms th_a api.cpp:867 on_objects_changed ] ids: ["2.8.15326","1.6.20","1.13.127","2.1.0"]
I think that's the maintenance period.
Title: Re: Test Net for Advanced Users
Post by: abit on September 01, 2015, 08:07:12 pm: Quote from: puppies on September 01, 2015, 07:47:25 pm
Quote from: clayop on September 01, 2015, 07:07:33 pm
Why does the following happen? Sometimes it takes about 20 seconds to sync the block
I think that's the maintenance period.
Sure it is.
But I don't think it need so much time (3 block intervals) for maintenance when the block interval is set to 5s.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 01, 2015, 08:21:21 pm: Quote from: abit on September 01, 2015, 08:07:12 pm
Quote from: puppies on September 01, 2015, 07:47:25 pm
Quote from: clayop on September 01, 2015, 07:07:33 pm
Why does the following happen? Sometimes it takes about 20 seconds to sync the block
I think that's the maintenance period.
Sure it is.
But I don't think it need so much time (3 block intervals) for maintenance when the block interval is set to 5s.
I agree. I'm guessing they just haven't updated it yet.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 01, 2015, 08:29:12 pm: I think I have missed sometiing - getting tihs error

Code: [Select]
1053509ms th_a witness.cpp:156 plugin_startup ] Unable to find key for witness 1.6.1595. Removing it from my witnesses. 1053509ms th_a witness.cpp:171 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration. 1053509ms th_a witness.cpp:172 plugin_startup ] witness plugin: plugin_startup() end 1053509ms th_a main.cpp:165 main ] Started witness node on a chain with 16114 blocks. 1053509ms th_a main.cpp:166 main ] Chain ID is ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3
and

Code: [Select]
922790ms th_a witness.cpp:156 plugin_startup ] Unable to find key for witness 1.6.2561. Removing it from my witnesses. 922790ms th_a witness.cpp:171 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration. 922790ms th_a witness.cpp:172 plugin_startup ] witness plugin: plugin_startup() end 922790ms th_a main.cpp:165 main ] Started witness node on a chain with 16114 blocks. 922790ms th_a main.cpp:166 main ] Chain ID is ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3
IDs and private keys are the same as the last test net.

Does the wallet have to be on the server if I use confi.ini ?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 01, 2015, 08:30:19 pm: Quote from: puppies on September 01, 2015, 08:21:21 pm
Quote from: abit on September 01, 2015, 08:07:12 pm
Quote from: puppies on September 01, 2015, 07:47:25 pm
Quote from: clayop on September 01, 2015, 07:07:33 pm
Why does the following happen? Sometimes it takes about 20 seconds to sync the block
I think that's the maintenance period.
Sure it is.
But I don't think it need so much time (3 block intervals) for maintenance when the block interval is set to 5s.
I agree. I'm guessing they just haven't updated it yet.

You are right, with 5 second blocks, there is no need for maintenance blocks to have any extra time over normal blocks.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 01, 2015, 08:31:05 pm: Quote from: iHashFury on September 01, 2015, 08:29:12 pm
I think I have missed sometiing - getting tihs error

Code: [Select]
1053509ms th_a witness.cpp:156 plugin_startup ] Unable to find key for witness 1.6.1595. Removing it from my witnesses. 1053509ms th_a witness.cpp:171 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration. 1053509ms th_a witness.cpp:172 plugin_startup ] witness plugin: plugin_startup() end 1053509ms th_a main.cpp:165 main ] Started witness node on a chain with 16114 blocks. 1053509ms th_a main.cpp:166 main ] Chain ID is ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3
and

Code: [Select]
922790ms th_a witness.cpp:156 plugin_startup ] Unable to find key for witness 1.6.2561. Removing it from my witnesses. 922790ms th_a witness.cpp:171 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration. 922790ms th_a witness.cpp:172 plugin_startup ] witness plugin: plugin_startup() end 922790ms th_a main.cpp:165 main ] Started witness node on a chain with 16114 blocks. 922790ms th_a main.cpp:166 main ] Chain ID is ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3
IDs and private keys are the same as the last test net.

Does the wallet have to be on the server if I use confi.ini ?

Check your witness ID by using get_witness. Mine also has been changed from the last snapshot.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 01, 2015, 08:31:43 pm: Quote from: abit on September 01, 2015, 08:07:12 pm
Quote from: puppies on September 01, 2015, 07:47:25 pm
Quote from: clayop on September 01, 2015, 07:07:33 pm
Why does the following happen? Sometimes it takes about 20 seconds to sync the block
I think that's the maintenance period.
Sure it is.
But I don't think it need so much time (3 block intervals) for maintenance when the block interval is set to 5s.

Thanks for clarifying!
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 01, 2015, 08:39:00 pm: Quote from: clayop on September 01, 2015, 08:31:05 pm
Quote from: iHashFury on September 01, 2015, 08:29:12 pm
I think I have missed sometiing - getting tihs error

Code: [Select]
1053509ms th_a witness.cpp:156 plugin_startup ] Unable to find key for witness 1.6.1595. Removing it from my witnesses. 1053509ms th_a witness.cpp:171 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration. 1053509ms th_a witness.cpp:172 plugin_startup ] witness plugin: plugin_startup() end 1053509ms th_a main.cpp:165 main ] Started witness node on a chain with 16114 blocks. 1053509ms th_a main.cpp:166 main ] Chain ID is ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3
and

Code: [Select]
922790ms th_a witness.cpp:156 plugin_startup ] Unable to find key for witness 1.6.2561. Removing it from my witnesses. 922790ms th_a witness.cpp:171 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration. 922790ms th_a witness.cpp:172 plugin_startup ] witness plugin: plugin_startup() end 922790ms th_a main.cpp:165 main ] Started witness node on a chain with 16114 blocks. 922790ms th_a main.cpp:166 main ] Chain ID is ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3
IDs and private keys are the same as the last test net.

Does the wallet have to be on the server if I use confi.ini ?

Check your witness ID by using get_witness. Mine also has been changed from the last snapshot.

Thanks id was +1 :)
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 01, 2015, 10:12:01 pm: delegate.xeldal is up and running ( 1.6.1625 )
Title: Re: Test Net for Advanced Users
Post by: lafona on September 02, 2015, 02:08:06 am: delegate-1.lafona (1.6.1531) is up and ready. Would someone mind voting me in, I am having no luck finding a key with a balance worth more than 0.1 core.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 02, 2015, 02:33:16 am: Quote from: lafona on September 02, 2015, 02:08:06 am
delegate-1.lafona (1.6.1531) is up and ready. Would someone mind voting me in, I am having no luck finding a key with a balance worth more than 0.1 core.

Done
Title: Re: Test Net for Advanced Users
Post by: alt on September 02, 2015, 02:43:05 am: happen at block 19245
Code: [Select]
2971563ms th_a application.cpp:356 handle_block ] Got block #19244 from network 2971564ms th_a api.cpp:867 on_objects_changed ] ids: ["2.8.19244","1.6.1","1.13.63","2.1.0"] 2971564ms th_a api.cpp:867 on_objects_changed ] ids: ["2.8.19244","1.6.1","1.13.63","2.1.0"] 2975337ms th_a application.cpp:356 handle_block ] Got block #19246 from network 2975337ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 2976894ms th_a application.cpp:356 handle_block ] Got block #19247 from network 2976895ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 2977641ms th_a application.cpp:356 handle_block ] Got block #19248 from network 2977641ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 2982830ms th_a application.cpp:356 handle_block ] Got block #19249 from network 2982830ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 2985413ms th_a application.cpp:356 handle_block ] Got block #19250 from network 2985413ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 2991159ms th_a application.cpp:356 handle_block ] Got block #19251 from network 2991159ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. ....... 75407ms th_a application.cpp:356 handle_block ] Got block #19379 from network 75407ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 80415ms th_a application.cpp:356 handle_block ] Got block #19380 from network 80415ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1550122ms th_a application.cpp:500 get_blockchain_synop ] reference_point: 0000000000000000000000000000000000000000 number_of_blocks_after_reference_point: 0 result: ["00000b2c27d70d418df26d4c6f7ea9c3bf278881","00002b2c4baf627959890ae6fcb7fa58a0a1fd89","00003b2c9362d330e2c2fc81702d2e365fac966f","0000432c4c5baebfdd5189f12edf44c1dd7c2d93","0000472c1bef0cf45f0e0be7fe2a60d34a83711c","0000492c197c3deeb618c982d64acdb26aa5427e","00004a2cfc255375ac702afb59a3c0516e77675f","00004aac0824351772902693a572330a2f5b5562","00004aec708a8a7265569807cc0aaf2907bb01f9","00004b0c8a04e3876fc3487ebef34d96b1e946d6","00004b1c50342d1c658d156a835e808f67a336fc","00004b247ee7327a4b4088921aa8317db8d009e5","00004b28f364f49e3e1c942a6368c8d190eba2a9","00004b2a5a9540578d4a3a03eac584f3acf88383","00004b2bad1237b1cf7c26dee14009b8812f4400","00004b2c721c0a7d372e05e78a846636be3c56e6"] 1551317ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception second_branch_itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:194 fetch_branch_from {"first":"00004bb44c5ea6f09c4523f59c1ee2d4d4c46795","second":"00004b2c721c0a7d372e05e78a846636be3c56e6"} th_a fork_database.cpp:225 fetch_branch_from {"new_block":{"previous":"00004b2c721c0a7d372e05e78a846636be3c56e6","timestamp":"2015-09-02T00:49:20","witness":"1.6.30","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f06a8c6497711b502229c690492345f8df531e3b88916acaed6cc69dba4ef31a0234bac5808e0c550f9b3c9f0627791c663fe07aee3d60d4f5777fb2f83fbf2d0","transactions":[]}} th_a db_block.cpp:176 _push_block 1551320ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19246,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b2d2c2ca421c5c1dea971536d794fb39909","timestamp":"2015-09-02T00:49:25","witness":"1.6.71","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"2000f6e8c6e35dfe28afdd202990416a3575852211b7d0b2872f5b69127da88bb9232179133fbaae82fb9c7af4d115552703ac668f9cdce4f103733099994e6ff6","transactions":[]}} th_a db_block.cpp:176 _push_block 1551320ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19247,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b2e2a410dbcbf7d98869f49d3965c4ff628","timestamp":"2015-09-02T00:49:30","witness":"1.6.92","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"2063834aa931f46e4650b465f130c88c489666e89f6635a5226f059185e6b1eeca4c12d552b3da728c58e4dc41aec3b425e0636e9ff408782371c17346e24203d1","transactions":[]}} th_a db_block.cpp:176 _push_block 1551320ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19248,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b2fbf3e595635934a9d1e0bc71c361650b8","timestamp":"2015-09-02T00:49:35","witness":"1.6.21","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"2050531102e02418d6369765e238355619d025960629043d2bf86af1b95a2c18336053cd369119a3b253fdca0c700d686187e7befaccfc4377f464c7f41987c64c","transactions":[]}} th_a db_block.cpp:176 _push_block 1551321ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19249,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b30452602f87ae249ca2b484965ff9bce20","timestamp":"2015-09-02T00:49:40","witness":"1.6.13","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"2007094c94e1f988276184214c83c584994974914d5b052e5c4060f2ad1b4baed634b6249c604ef8ffac4af06f8e92524aa4d399abe617cd14195175f947e67a4b","transactions":[]}} th_a db_block.cpp:176 _push_block 1551321ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19250,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b31be06fe671e4b289061961220d83b45d3","timestamp":"2015-09-02T00:49:45","witness":"1.6.54","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"20708f798868d17b3237e6e79a19e19397ba716c97cc92c881deb03190879904b04ffe7b3e8b50fab1ba20bd75b815bfd3ead8c5f407c480b7a2dd378faa369a74","transactions":[]}} th_a db_block.cpp:176 _push_block ................... tem->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19254,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b356ca14f441e66d190ea1316a710fbc7c6","timestamp":"2015-09-02T00:50:20","witness":"1.6.19","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"206ce785ed9cac4a4eff9d2e3c6b5c7a1eefbbd6da7a00e9ad08c4b23aa16c130940e2de4421de0a7ff654cd7b75946aaa07de0bbc34a8ffe14634746b5e8b6d78","transactions":[]}} th_a db_block.cpp:176 _push_block 1817912ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 1817919ms ntp ntp.cpp:81 request_now ] sending request to 202.118.1.130:123 1817962ms ntp ntp.cpp:147 read_loop ] received ntp reply from 202.118.1.130:123 1817962ms ntp ntp.cpp:161 read_loop ] ntp offset: 618, round_trip_delay 43201 1817962ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 618 1860115ms th_a application.cpp:500 get_blockchain_synop ] reference_point: 0000000000000000000000000000000000000000 number_of_blocks_after_reference_point: 0 result: ["00000b2c27d70d418df26d4c6f7ea9c3bf278881","00002b2c4baf627959890ae6fcb7fa58a0a1fd89","00003b2c9362d330e2c2fc81702d2e365fac966f","0000432c4c5baebfdd5189f12edf44c1dd7c2d93","0000472c1bef0cf45f0e0be7fe2a60d34a83711c","0000492c197c3deeb618c982d64acdb26aa5427e","00004a2cfc255375ac702afb59a3c0516e77675f","00004aac0824351772902693a572330a2f5b5562","00004aec708a8a7265569807cc0aaf2907bb01f9","00004b0c8a04e3876fc3487ebef34d96b1e946d6","00004b1c50342d1c658d156a835e808f67a336fc","00004b247ee7327a4b4088921aa8317db8d009e5","00004b28f364f49e3e1c942a6368c8d190eba2a9","00004b2a5a9540578d4a3a03eac584f3acf88383","00004b2bad1237b1cf7c26dee14009b8812f4400","00004b2c721c0a7d372e05e78a846636be3c56e6"] 1861225ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19245,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b2c721c0a7d372e05e78a846636be3c56e6","timestamp":"2015-09-02T00:49:20","witness":"1.6.30","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f06a8c6497711b502229c690492345f8df531e3b88916acaed6cc69dba4ef31a0234bac5808e0c550f9b3c9f0627791c663fe07aee3d60d4f5777fb2f83fbf2d0","transactions":[]}} th_a db_block.cpp:176 _push_block 1861226ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19246,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block
Quote from: bytemaster on September 01, 2015, 01:01:29 pm
Quote from: abit on September 01, 2015, 11:58:20 am
Quote from: bytemaster on August 26, 2015, 01:15:44 pm
Quote from: alt on August 26, 2015, 09:13:00 am
several times, my witeness node blocked at some block
I watch the p2p log, it received block 419543, then 419544, then missed 419545, then received 419546, .......
and it will never receive block 419545, I have to restart witness node, then it can request the block from other node.
I think we need a logic, when the witness node have missed a block more than 10 blocks, it should request from other node.

Eric checked in some fixes that may address this particular problem. We do have logic to request from another node, but the timeouts were still tuned to BTS 1 timeframes so we reduced the timeout for BTS 2.
Still have same problem with test2 tag.
Please check this issue https://github.com/cryptonomex/graphene/issues/264

In the test2b tag I have increase the allowance for out-of-order blocks. If it still happens then something else is going on.
Title: Re: Test Net for Advanced Users
Post by: lafona on September 02, 2015, 03:11:19 am: I keep getting this occasionally and it seems like it still isnt producing blocks. Does the
Code: [Select]
schedule_production_ ] now.time_since_epoch().count(): 1441163103861438 next_second: 2015-09-02T03:05:05represent a missed block

Code: [Select]
247252ms th_a application.cpp:356 handle_block ] Got block #20775 from network 252263ms th_a application.cpp:356 handle_block ] Got block #20776 from network 257272ms th_a application.cpp:356 handle_block ] Got block #20777 from network 262655ms th_a application.cpp:356 handle_block ] Got block #20778 from network 266000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 266000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441163103861438 next_second: 2015-09-02T03:05:05 282256ms th_a application.cpp:356 handle_block ] Got block #20779 from network 287257ms th_a application.cpp:356 handle_block ] Got block #20780 from network 292260ms th_a application.cpp:356 handle_block ] Got block #20781 from network 297254ms th_a application.cpp:356 handle_block ] Got block #20782 from network
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 02, 2015, 03:57:50 am: Quote from: lafona on September 02, 2015, 03:11:19 am

Code: [Select]
292260ms th_a application.cpp:356 handle_block ] Got block #20781 from network 297254ms th_a application.cpp:356 handle_block ] Got block #20782 from network

Blockchain not fully sync'd?
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 02, 2015, 11:04:12 am: I fixed my stats page for the new testnet. It is still very basic but serves its purpose:
http://stats.bitshares.eu/
it's written in plain JS/HTML/CSS and most web devs would consider the code "ugly". Anyway, you can find it here:
https://github.com/BitSharesEurope/stats.bitshares.eu
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 02, 2015, 11:11:00 am: Quote from: xeroc on September 02, 2015, 11:04:12 am
I fixed my stats page for the new testnet. It is still very basic but serves its purpose:
http://stats.bitshares.eu/ (http://stats.bitshares.eu/)
it's written in plain JS/HTML/CSS and most web devs would consider the code "ugly". Anyway, you can find it here:
https://github.com/BitSharesEurope/stats.bitshares.eu (https://github.com/BitSharesEurope/stats.bitshares.eu)

Good looking page! I like simple pages :).
Title: Re: Test Net for Advanced Users
Post by: alt on September 02, 2015, 11:27:44 am: you are always a good teacher, thanks
Quote from: xeroc on September 02, 2015, 11:04:12 am
I fixed my stats page for the new testnet. It is still very basic but serves its purpose:
http://stats.bitshares.eu/
it's written in plain JS/HTML/CSS and most web devs would consider the code "ugly". Anyway, you can find it here:
https://github.com/BitSharesEurope/stats.bitshares.eu
Title: Re: Test Net for Advanced Users
Post by: abit on September 02, 2015, 11:41:12 am: Quote from: alt on September 02, 2015, 02:43:05 am
happen at block 19245
Code: [Select]
2971563ms th_a application.cpp:356 handle_block ] Got block #19244 from network 2971564ms th_a api.cpp:867 on_objects_changed ] ids: ["2.8.19244","1.6.1","1.13.63","2.1.0"] 2971564ms th_a api.cpp:867 on_objects_changed ] ids: ["2.8.19244","1.6.1","1.13.63","2.1.0"] 2975337ms th_a application.cpp:356 handle_block ] Got block #19246 from network 2975337ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 2976894ms th_a application.cpp:356 handle_block ] Got block #19247 from network 2976895ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 2977641ms th_a application.cpp:356 handle_block ] Got block #19248 from network 2977641ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 2982830ms th_a application.cpp:356 handle_block ] Got block #19249 from network 2982830ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 2985413ms th_a application.cpp:356 handle_block ] Got block #19250 from network 2985413ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 2991159ms th_a application.cpp:356 handle_block ] Got block #19251 from network 2991159ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. ....... 75407ms th_a application.cpp:356 handle_block ] Got block #19379 from network 75407ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 80415ms th_a application.cpp:356 handle_block ] Got block #19380 from network 80415ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link. 1550122ms th_a application.cpp:500 get_blockchain_synop ] reference_point: 0000000000000000000000000000000000000000 number_of_blocks_after_reference_point: 0 result: ["00000b2c27d70d418df26d4c6f7ea9c3bf278881","00002b2c4baf627959890ae6fcb7fa58a0a1fd89","00003b2c9362d330e2c2fc81702d2e365fac966f","0000432c4c5baebfdd5189f12edf44c1dd7c2d93","0000472c1bef0cf45f0e0be7fe2a60d34a83711c","0000492c197c3deeb618c982d64acdb26aa5427e","00004a2cfc255375ac702afb59a3c0516e77675f","00004aac0824351772902693a572330a2f5b5562","00004aec708a8a7265569807cc0aaf2907bb01f9","00004b0c8a04e3876fc3487ebef34d96b1e946d6","00004b1c50342d1c658d156a835e808f67a336fc","00004b247ee7327a4b4088921aa8317db8d009e5","00004b28f364f49e3e1c942a6368c8d190eba2a9","00004b2a5a9540578d4a3a03eac584f3acf88383","00004b2bad1237b1cf7c26dee14009b8812f4400","00004b2c721c0a7d372e05e78a846636be3c56e6"] 1551317ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception second_branch_itr != _index.get<block_id>().end(): {} th_a fork_database.cpp:194 fetch_branch_from {"first":"00004bb44c5ea6f09c4523f59c1ee2d4d4c46795","second":"00004b2c721c0a7d372e05e78a846636be3c56e6"} th_a fork_database.cpp:225 fetch_branch_from {"new_block":{"previous":"00004b2c721c0a7d372e05e78a846636be3c56e6","timestamp":"2015-09-02T00:49:20","witness":"1.6.30","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f06a8c6497711b502229c690492345f8df531e3b88916acaed6cc69dba4ef31a0234bac5808e0c550f9b3c9f0627791c663fe07aee3d60d4f5777fb2f83fbf2d0","transactions":[]}} th_a db_block.cpp:176 _push_block 1551320ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19246,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b2d2c2ca421c5c1dea971536d794fb39909","timestamp":"2015-09-02T00:49:25","witness":"1.6.71","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"2000f6e8c6e35dfe28afdd202990416a3575852211b7d0b2872f5b69127da88bb9232179133fbaae82fb9c7af4d115552703ac668f9cdce4f103733099994e6ff6","transactions":[]}} th_a db_block.cpp:176 _push_block 1551320ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19247,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b2e2a410dbcbf7d98869f49d3965c4ff628","timestamp":"2015-09-02T00:49:30","witness":"1.6.92","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"2063834aa931f46e4650b465f130c88c489666e89f6635a5226f059185e6b1eeca4c12d552b3da728c58e4dc41aec3b425e0636e9ff408782371c17346e24203d1","transactions":[]}} th_a db_block.cpp:176 _push_block 1551320ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19248,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b2fbf3e595635934a9d1e0bc71c361650b8","timestamp":"2015-09-02T00:49:35","witness":"1.6.21","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"2050531102e02418d6369765e238355619d025960629043d2bf86af1b95a2c18336053cd369119a3b253fdca0c700d686187e7befaccfc4377f464c7f41987c64c","transactions":[]}} th_a db_block.cpp:176 _push_block 1551321ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19249,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b30452602f87ae249ca2b484965ff9bce20","timestamp":"2015-09-02T00:49:40","witness":"1.6.13","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"2007094c94e1f988276184214c83c584994974914d5b052e5c4060f2ad1b4baed634b6249c604ef8ffac4af06f8e92524aa4d399abe617cd14195175f947e67a4b","transactions":[]}} th_a db_block.cpp:176 _push_block 1551321ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19250,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b31be06fe671e4b289061961220d83b45d3","timestamp":"2015-09-02T00:49:45","witness":"1.6.54","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"20708f798868d17b3237e6e79a19e19397ba716c97cc92c881deb03190879904b04ffe7b3e8b50fab1ba20bd75b815bfd3ead8c5f407c480b7a2dd378faa369a74","transactions":[]}} th_a db_block.cpp:176 _push_block ................... tem->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19254,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b356ca14f441e66d190ea1316a710fbc7c6","timestamp":"2015-09-02T00:50:20","witness":"1.6.19","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"206ce785ed9cac4a4eff9d2e3c6b5c7a1eefbbd6da7a00e9ad08c4b23aa16c130940e2de4421de0a7ff654cd7b75946aaa07de0bbc34a8ffe14634746b5e8b6d78","transactions":[]}} th_a db_block.cpp:176 _push_block 1817912ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 1817919ms ntp ntp.cpp:81 request_now ] sending request to 202.118.1.130:123 1817962ms ntp ntp.cpp:147 read_loop ] received ntp reply from 202.118.1.130:123 1817962ms ntp ntp.cpp:161 read_loop ] ntp offset: 618, round_trip_delay 43201 1817962ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 618 1860115ms th_a application.cpp:500 get_blockchain_synop ] reference_point: 0000000000000000000000000000000000000000 number_of_blocks_after_reference_point: 0 result: ["00000b2c27d70d418df26d4c6f7ea9c3bf278881","00002b2c4baf627959890ae6fcb7fa58a0a1fd89","00003b2c9362d330e2c2fc81702d2e365fac966f","0000432c4c5baebfdd5189f12edf44c1dd7c2d93","0000472c1bef0cf45f0e0be7fe2a60d34a83711c","0000492c197c3deeb618c982d64acdb26aa5427e","00004a2cfc255375ac702afb59a3c0516e77675f","00004aac0824351772902693a572330a2f5b5562","00004aec708a8a7265569807cc0aaf2907bb01f9","00004b0c8a04e3876fc3487ebef34d96b1e946d6","00004b1c50342d1c658d156a835e808f67a336fc","00004b247ee7327a4b4088921aa8317db8d009e5","00004b28f364f49e3e1c942a6368c8d190eba2a9","00004b2a5a9540578d4a3a03eac584f3acf88383","00004b2bad1237b1cf7c26dee14009b8812f4400","00004b2c721c0a7d372e05e78a846636be3c56e6"] 1861225ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19245,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004b2c721c0a7d372e05e78a846636be3c56e6","timestamp":"2015-09-02T00:49:20","witness":"1.6.30","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f06a8c6497711b502229c690492345f8df531e3b88916acaed6cc69dba4ef31a0234bac5808e0c550f9b3c9f0627791c663fe07aee3d60d4f5777fb2f83fbf2d0","transactions":[]}} th_a db_block.cpp:176 _push_block 1861226ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":19246,"head":19380,"max_size":10} th_a fork_database.cpp:69 _push_block
Quote from: bytemaster on September 01, 2015, 01:01:29 pm
Quote from: abit on September 01, 2015, 11:58:20 am
Quote from: bytemaster on August 26, 2015, 01:15:44 pm
Quote from: alt on August 26, 2015, 09:13:00 am
several times, my witeness node blocked at some block
I watch the p2p log, it received block 419543, then 419544, then missed 419545, then received 419546, .......
and it will never receive block 419545, I have to restart witness node, then it can request the block from other node.
I think we need a logic, when the witness node have missed a block more than 10 blocks, it should request from other node.

Eric checked in some fixes that may address this particular problem. We do have logic to request from another node, but the timeouts were still tuned to BTS 1 timeframes so we reduced the timeout for BTS 2.
Still have same problem with test2 tag.
Please check this issue https://github.com/cryptonomex/graphene/issues/264

In the test2b tag I have increase the allowance for out-of-order blocks. If it still happens then something else is going on.

Same here at block #20188 with tag test2b.

Code: [Select]
2015-09-02T02:12:15 th_a:invoke handle_block handle_block ] Got block #20187 from network application.cpp:356 2015-09-02T02:12:15 th_a:invoke handle_block on_objects_changed ] ids: ["2.8.20187","1.6.64","1.13.72","2.1.0"] api.cpp:867 2015-09-02T02:12:15 th_a:invoke handle_block on_objects_changed ] ids: ["2.8.20187","1.6.64","1.13.72","2.1.0"] api.cpp:867 2015-09-02T02:12:25 th_a:invoke handle_block handle_block ] Got block #20189 from network application.cpp:356 2015-09-02T02:12:25 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57 2015-09-02T02:12:30 th_a:invoke handle_block handle_block ] Got block #20190 from network application.cpp:356 2015-09-02T02:12:30 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57 ... ... ... 2015-09-02T02:20:22 th_a:invoke handle_block handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":20188,"head":20278,"max_size":10} th_a fork_database.cpp:69 _push_block {"new_block":{"previous":"00004edb437dfbc741e818a8a9754a653da79111","timestamp":"2015-09-02T02:12:20","witness":"1.6.3706","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f0f14d642abd9b0d26e0d2e5960ad5b4e1d340282317fd1948f942e1f857804393bbeca54636b9f3ad68e44f9843648aa403fb5dc13024649d259558db3c119f1","transactions":[]}} th_a db_block.cpp:176 _push_block application.cpp:378
See https://github.com/cryptonomex/graphene/issues/264
Title: Re: Test Net for Advanced Users
Post by: abit on September 02, 2015, 12:49:03 pm: Quote from: theoretical on September 01, 2015, 03:48:31 pm

Quote from: lafona on September 01, 2015, 12:08:05 am
Anyone else getting this when trying to update the submodule

Code: [Select]
fatal: reference is not a tree: 80d967a70d21d26d27ef3a1544a177925b2a7bbe Unable to checkout '80d967a70d21d26d27ef3a1544a177925b2a7bbe' in submodule path 'libraries/fc'

Sorry about that, I goofed -- I forgot to push a commit to fc. Try again, it should be good now.
The latest build of graphene is broken again (master branch, commit 00a2d2dac73188e7e265163dfec04c2a523b8e23).
When you submitted new commit to fc, please remember to update graphene as well to refer to correct commit of fc.
Pull request created. https://github.com/cryptonomex/graphene/pull/289
Title: Re: Test Net for Advanced Users
Post by: spartako on September 02, 2015, 03:06:52 pm: Delegate spartako up and producing blocks:

get_witness spartako
{
"id": "1.6.4232",
"witness_account": "1.2.72728"
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 02, 2015, 08:52:56 pm: Looks like someone is broadcasting lots of transactions. Looking good. Keep it up.
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 02, 2015, 09:02:44 pm: Quote from: bytemaster on September 02, 2015, 08:52:56 pm
Looks like someone is broadcasting lots of transactions. Looking good. Keep it up.
My statspage is of by a factor of 5 since i assumed 1sec blocks .. need to pull the date from the blockchain on next update
Title: Re: Test Net for Advanced Users
Post by: clayop on September 02, 2015, 09:39:29 pm: Quote from: bytemaster on September 02, 2015, 08:52:56 pm
Looks like someone is broadcasting lots of transactions. Looking good. Keep it up.

It's me. The network is much more stable than previous testnets. Unfortunately I am only able to make 19 tps (93 txs per block)

Edit: How can I make as many transactions as possible?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 02, 2015, 09:42:58 pm: Quote from: xeroc on September 02, 2015, 09:02:44 pm
Quote from: bytemaster on September 02, 2015, 08:52:56 pm
Looks like someone is broadcasting lots of transactions. Looking good. Keep it up.
My statspage is of by a factor of 5 since i assumed 1sec blocks .. need to pull the date from the blockchain on next update

Can you record last 100 block stats (e.g. block number, witness, number of tx)
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 02, 2015, 10:33:45 pm: Quote from: clayop on September 02, 2015, 09:39:29 pm
Quote from: bytemaster on September 02, 2015, 08:52:56 pm
Looks like someone is broadcasting lots of transactions. Looking good. Keep it up.

It's me. The network is much stable than previous testnets. Unfortunately I am only able to make 19 tps (93 txs per block)

Edit: How can I make as many transactions as possible?

I think you will need multiple CLI wallets.

How much cpu usage are you using for your witness node and wallet?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 02, 2015, 10:39:30 pm: Quote from: bytemaster on September 02, 2015, 10:33:45 pm
Quote from: clayop on September 02, 2015, 09:39:29 pm
Quote from: bytemaster on September 02, 2015, 08:52:56 pm
Looks like someone is broadcasting lots of transactions. Looking good. Keep it up.

It's me. The network is much stable than previous testnets. Unfortunately I am only able to make 19 tps (93 txs per block)

Edit: How can I make as many transactions as possible?

I think you will need multiple CLI wallets.

How much cpu usage are you using for your witness node and wallet?

Normally, approximately 3%. (1vCPU, 3.75 GB memory)
With a lot of transactions, it goes up to 8750%
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 02, 2015, 10:40:54 pm: Witness Participation:

"participation": 96.09375000000000000

That means 4 of the last 128 slots were missed.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 02, 2015, 10:41:56 pm: Quote from: clayop on September 02, 2015, 10:39:30 pm
Quote from: bytemaster on September 02, 2015, 10:33:45 pm
Quote from: clayop on September 02, 2015, 09:39:29 pm
Quote from: bytemaster on September 02, 2015, 08:52:56 pm
Looks like someone is broadcasting lots of transactions. Looking good. Keep it up.

It's me. The network is much stable than previous testnets. Unfortunately I am only able to make 19 tps (93 txs per block)

Edit: How can I make as many transactions as possible?

I think you will need multiple CLI wallets.

How much cpu usage are you using for your witness node and wallet?

Normally, approximately 3%. (1vCPU, 3.75 GB memory)
With a lot of transactions, it goes up to 50%

If you can try running to witness nodes and verify that only the one that is being used with your wallet is spiking during the flood attempt. On my side I see almost no CPU usage even when you are flooding.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 02:12:42 am: My witness node does spike CPU usage when I manually spam transactions or when I flood_network from a different box.

My witness node is on a VPS, and I am spamming from home.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 03, 2015, 03:49:10 am: Quote from: bytemaster on September 02, 2015, 10:41:56 pm
Quote from: clayop on September 02, 2015, 10:39:30 pm
Quote from: bytemaster on September 02, 2015, 10:33:45 pm
Quote from: clayop on September 02, 2015, 09:39:29 pm
Quote from: bytemaster on September 02, 2015, 08:52:56 pm
Looks like someone is broadcasting lots of transactions. Looking good. Keep it up.

It's me. The network is much stable than previous testnets. Unfortunately I am only able to make 19 tps (93 txs per block)

Edit: How can I make as many transactions as possible?

I think you will need multiple CLI wallets.

How much cpu usage are you using for your witness node and wallet?

Normally, approximately 3%. (1vCPU, 3.75 GB memory)
With a lot of transactions, it goes up to 50%

If you can try running to witness nodes and verify that only the one that is being used with your wallet is spiking during the flood attempt. On my side I see almost no CPU usage even when you are flooding.

Yes you're correct. ~~But my VPS's cpu spikes a little bit (from 3% to 30%) when I was spamming from another box.~~

Edit: I have to repeat my statement. There's no spike.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 04:40:26 am: Interesting. I am just running top through ssh from my VPS, and when I either manually spam transactions or do a flood_network command I see a dramatic increase in the CPU usage of witness_node. Up to 100% (its a dual core VPS, and I think top just references the core its running on) Would there be a better way to test it locally, or would it be better to find a way to sync better between multiple users? IRC, or Mumble?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 03, 2015, 04:42:43 am: Quote from: puppies on September 03, 2015, 04:40:26 am
Interesting. I am just running top through ssh from my VPS, and when I either manually spam transactions or do a flood_network command I see a dramatic increase in the CPU usage of witness_node. Up to 100% (its a dual core VPS, and I think top just references the core its running on) Would there be a better way to test it locally, or would it be better to find a way to sync better between multiple users? IRC, or Mumble?

Whenever I tried to flood_network, I met "Segmentation fault (core dumped)" error. How can you do this command?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 03, 2015, 04:58:10 am: Sent some CORE to puppies :)
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 05:05:01 am: Quote from: clayop on September 03, 2015, 04:42:43 am
Quote from: puppies on September 03, 2015, 04:40:26 am
Interesting. I am just running top through ssh from my VPS, and when I either manually spam transactions or do a flood_network command I see a dramatic increase in the CPU usage of witness_node. Up to 100% (its a dual core VPS, and I think top just references the core its running on) Would there be a better way to test it locally, or would it be better to find a way to sync better between multiple users? IRC, or Mumble?

Whenever I tried to flood_network, I met "Segmentation fault (core dumped)" error. How can you do this command?

I am using it as
Code: [Select]
unlocked >>> flood_network test34.puppies 200 flood_network test34.puppies 200 3593111ms th_a wallet.cpp:1936 flood_network ] Created 66 accounts in 671 milliseconds 3594438ms th_a wallet.cpp:1946 flood_network ] Transferred to 132 accounts in 1327 milliseconds 3595016ms th_a wallet.cpp:1955 flood_network ] Issued to 66 accounts in 577 milliseconds null unlocked >>>test34.puppies is not a real account, but it seems to error out a lot of you use it with the same name. I have never had it cause a segmentation fault though. The errors are very very long, but not serious enough to kill the client.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 05:06:42 am: Quote from: clayop on September 03, 2015, 04:58:10 am
Sent some CORE to puppies :)
thanks clayop

I can't look far enough back to see your tranfer. What is a good account to spam tranfers too?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 03, 2015, 05:10:07 am: Quote from: puppies on September 03, 2015, 05:05:01 am
Quote from: clayop on September 03, 2015, 04:42:43 am
Quote from: puppies on September 03, 2015, 04:40:26 am
Interesting. I am just running top through ssh from my VPS, and when I either manually spam transactions or do a flood_network command I see a dramatic increase in the CPU usage of witness_node. Up to 100% (its a dual core VPS, and I think top just references the core its running on) Would there be a better way to test it locally, or would it be better to find a way to sync better between multiple users? IRC, or Mumble?

Whenever I tried to flood_network, I met "Segmentation fault (core dumped)" error. How can you do this command?

I am using it as
Code: [Select]
unlocked >>> flood_network test34.puppies 200 flood_network test34.puppies 200 3593111ms th_a wallet.cpp:1936 flood_network ] Created 66 accounts in 671 milliseconds 3594438ms th_a wallet.cpp:1946 flood_network ] Transferred to 132 accounts in 1327 milliseconds 3595016ms th_a wallet.cpp:1955 flood_network ] Issued to 66 accounts in 577 milliseconds null unlocked >>>test34.puppies is not a real account, but it seems to error out a lot of you use it with the same name. I have never had it cause a segmentation fault though. The errors are very very long, but not serious enough to kill the client.
I used any new name but all gave me the same error. Maybe a bug, but it does not have to be fixed IMO (Will someone use flood_network in real blockchain? ;) )
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 05:31:42 am: So. I set up a keyboard script to send lots of transactions. I hope clayop is a good account for you.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 03, 2015, 05:34:32 am: Quote from: clayop on September 03, 2015, 03:49:10 am
Yes you're correct. ~~But my VPS's cpu spikes a little bit (from 3% to 30%) when I was spamming from another box.~~

Edit: I have to repeat my statement. There's no spike.

My mistake. I was out of active witnesses. With puppies network flooding (from puppies to clayop account... thanks :D), my CPU usage went up to 35%
Title: Re: Test Net for Advanced Users
Post by: abit on September 03, 2015, 09:10:48 am: One of my node got out of sync when you're flooding the network. An assertion failure which is never seen before.
Here is some related log:
Code: [Select]
2015-09-03T00:30:20 th_a:invoke handle_block handle_block ] Got block #34498 from network application.cpp:356 ... ... 2015-09-03T00:30:30 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:30 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:30 th_a:invoke handle_block handle_block ] Got block #34500 from network application.cpp:356 2015-09-03T00:30:30 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57 2015-09-03T00:30:35 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:35 th_a:invoke handle_block handle_block ] Got block #34501 from network application.cpp:356 2015-09-03T00:30:35 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57 2015-09-03T00:30:37 th_a:invoke handle_block handle_block ] Got block #34499 from network application.cpp:3 ... ... 2015-09-03T00:30:37 th_a:invoke handle_block handle_block ] Error when pushing block: 10 assert_exception: Assert Exception (skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): {} th_a db_block.cpp:487 _apply_transaction {"trx":{"ref_block_num":34497,"ref_block_prefix":2564640669,"expiration":"2015-09-03T00:31:49","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.63355","amount":{"amount":100000,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["1f5f41592441c4f40af47b118e80a0c4786a1d768cf6a8d3204d7c30d79d33e971463c4dc78f1c5fc8f2ae7637ec21e8b523b089baef754422fe99108576b343c8"]}} th_a db_block.cpp:543 _apply_transaction {"next_block.block_num()":34499} th_a db_block.cpp:448 _apply_block ... ... 2015-09-03T00:30:37 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:37 th_a:invoke handle_transaction on_objects_changed ] ids: ["2.5.40","2.5.18","2.6.63354","2.7.4698"] api.cpp:867 2015-09-03T00:30:37 th_a:invoke handle_transaction on_objects_changed ] ids: ["2.5.40","2.5.18","2.6.63354","2.7.4698"] api.cpp:867 2015-09-03T00:30:40 th_a:invoke handle_block handle_block ] Got block #34502 from network application.cpp:356 2015-09-03T00:30:40 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57
Full log files are here:
https://drive.google.com/open?id=0B3xrm70jSHn4U3h3V3liOUlOakk
~~https://drive.google.com/open?id=0B3xrm70jSHn4TmtNYWNaVm1yalU~~
https://drive.google.com/open?id=0B3xrm70jSHn4SURQZjBZaE1rVGc

The other node works fine.

//Edit: updated link of log files.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 03, 2015, 09:13:16 am: I have three things to report

1. CPU usage goes up to 45% from 7:22 AM UTC (without any transactions?)
2. Log files are so gigantic. I have to delete them before they eat up my VPS disk space (around 8 G already)
3. Resync is really fast. It takes less than 5 min to catch up 40000 blocks from scratch.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 03, 2015, 09:14:24 am: Quote from: abit on September 03, 2015, 09:10:48 am
One of my node got out of sync when you're flooding the network. An assertion failure which is never seen before.
Here is some related log:
Code: [Select]
2015-09-03T00:30:20 th_a:invoke handle_block handle_block ] Got block #34498 from network application.cpp:356 ... ... 2015-09-03T00:30:30 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:30 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:30 th_a:invoke handle_block handle_block ] Got block #34500 from network application.cpp:356 2015-09-03T00:30:30 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57 2015-09-03T00:30:35 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:35 th_a:invoke handle_block handle_block ] Got block #34501 from network application.cpp:356 2015-09-03T00:30:35 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57 2015-09-03T00:30:37 th_a:invoke handle_block handle_block ] Got block #34499 from network application.cpp:3 ... ... 2015-09-03T00:30:37 th_a:invoke handle_block handle_block ] Error when pushing block: 10 assert_exception: Assert Exception (skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): {} th_a db_block.cpp:487 _apply_transaction {"trx":{"ref_block_num":34497,"ref_block_prefix":2564640669,"expiration":"2015-09-03T00:31:49","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.63355","amount":{"amount":100000,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["1f5f41592441c4f40af47b118e80a0c4786a1d768cf6a8d3204d7c30d79d33e971463c4dc78f1c5fc8f2ae7637ec21e8b523b089baef754422fe99108576b343c8"]}} th_a db_block.cpp:543 _apply_transaction {"next_block.block_num()":34499} th_a db_block.cpp:448 _apply_block ... ... 2015-09-03T00:30:37 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:37 th_a:invoke handle_transaction on_objects_changed ] ids: ["2.5.40","2.5.18","2.6.63354","2.7.4698"] api.cpp:867 2015-09-03T00:30:37 th_a:invoke handle_transaction on_objects_changed ] ids: ["2.5.40","2.5.18","2.6.63354","2.7.4698"] api.cpp:867 2015-09-03T00:30:40 th_a:invoke handle_block handle_block ] Got block #34502 from network application.cpp:356 2015-09-03T00:30:40 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57
Full log files are here:
https://drive.google.com/open?id=0B3xrm70jSHn4U3h3V3liOUlOakk
https://drive.google.com/open?id=0B3xrm70jSHn4TmtNYWNaVm1yalU

The other node works fine.

Do you have enough disk space now?
Title: Re: Test Net for Advanced Users
Post by: abit on September 03, 2015, 09:34:08 am: Quote from: clayop on September 03, 2015, 09:14:24 am
Quote from: abit on September 03, 2015, 09:10:48 am
One of my node got out of sync when you're flooding the network. An assertion failure which is never seen before.
Here is some related log:
Code: [Select]
2015-09-03T00:30:20 th_a:invoke handle_block handle_block ] Got block #34498 from network application.cpp:356 ... ... 2015-09-03T00:30:30 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:30 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:30 th_a:invoke handle_block handle_block ] Got block #34500 from network application.cpp:356 2015-09-03T00:30:30 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57 2015-09-03T00:30:35 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:35 th_a:invoke handle_block handle_block ] Got block #34501 from network application.cpp:356 2015-09-03T00:30:35 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57 2015-09-03T00:30:37 th_a:invoke handle_block handle_block ] Got block #34499 from network application.cpp:3 ... ... 2015-09-03T00:30:37 th_a:invoke handle_block handle_block ] Error when pushing block: 10 assert_exception: Assert Exception (skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): {} th_a db_block.cpp:487 _apply_transaction {"trx":{"ref_block_num":34497,"ref_block_prefix":2564640669,"expiration":"2015-09-03T00:31:49","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.63355","amount":{"amount":100000,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["1f5f41592441c4f40af47b118e80a0c4786a1d768cf6a8d3204d7c30d79d33e971463c4dc78f1c5fc8f2ae7637ec21e8b523b089baef754422fe99108576b343c8"]}} th_a db_block.cpp:543 _apply_transaction {"next_block.block_num()":34499} th_a db_block.cpp:448 _apply_block ... ... 2015-09-03T00:30:37 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:37 th_a:invoke handle_transaction on_objects_changed ] ids: ["2.5.40","2.5.18","2.6.63354","2.7.4698"] api.cpp:867 2015-09-03T00:30:37 th_a:invoke handle_transaction on_objects_changed ] ids: ["2.5.40","2.5.18","2.6.63354","2.7.4698"] api.cpp:867 2015-09-03T00:30:40 th_a:invoke handle_block handle_block ] Got block #34502 from network application.cpp:356 2015-09-03T00:30:40 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57
Full log files are here:
https://drive.google.com/open?id=0B3xrm70jSHn4U3h3V3liOUlOakk
~~https://drive.google.com/open?id=0B3xrm70jSHn4TmtNYWNaVm1yalU~~
https://drive.google.com/open?id=0B3xrm70jSHn4SURQZjBZaE1rVGc

The other node works fine.

Do you have enough disk space now?
Yes I have a 500G disk mounted, now used 110G.
Title: Re: Test Net for Advanced Users
Post by: abit on September 03, 2015, 09:50:55 am: Quote from: abit on September 03, 2015, 09:10:48 am
One of my node got out of sync when you're flooding the network. An assertion failure which is never seen before.
Here is some related log:
Code: [Select]
2015-09-03T00:30:20 th_a:invoke handle_block handle_block ] Got block #34498 from network application.cpp:356 ... ... 2015-09-03T00:30:30 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:30 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:30 th_a:invoke handle_block handle_block ] Got block #34500 from network application.cpp:356 2015-09-03T00:30:30 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57 2015-09-03T00:30:35 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:35 th_a:invoke handle_block handle_block ] Got block #34501 from network application.cpp:356 2015-09-03T00:30:35 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57 2015-09-03T00:30:37 th_a:invoke handle_block handle_block ] Got block #34499 from network application.cpp:3 ... ... 2015-09-03T00:30:37 th_a:invoke handle_block handle_block ] Error when pushing block: 10 assert_exception: Assert Exception (skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): {} th_a db_block.cpp:487 _apply_transaction {"trx":{"ref_block_num":34497,"ref_block_prefix":2564640669,"expiration":"2015-09-03T00:31:49","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.63355","amount":{"amount":100000,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["1f5f41592441c4f40af47b118e80a0c4786a1d768cf6a8d3204d7c30d79d33e971463c4dc78f1c5fc8f2ae7637ec21e8b523b089baef754422fe99108576b343c8"]}} th_a db_block.cpp:543 _apply_transaction {"next_block.block_num()":34499} th_a db_block.cpp:448 _apply_block ... ... 2015-09-03T00:30:37 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:391 2015-09-03T00:30:37 th_a:invoke handle_transaction on_objects_changed ] ids: ["2.5.40","2.5.18","2.6.63354","2.7.4698"] api.cpp:867 2015-09-03T00:30:37 th_a:invoke handle_transaction on_objects_changed ] ids: ["2.5.40","2.5.18","2.6.63354","2.7.4698"] api.cpp:867 2015-09-03T00:30:40 th_a:invoke handle_block handle_block ] Got block #34502 from network application.cpp:356 2015-09-03T00:30:40 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57
Full log files are here:
https://drive.google.com/open?id=0B3xrm70jSHn4U3h3V3liOUlOakk
~~https://drive.google.com/open?id=0B3xrm70jSHn4TmtNYWNaVm1yalU~~
https://drive.google.com/open?id=0B3xrm70jSHn4SURQZjBZaE1rVGc

The other node works fine.
Strange. Restarting doesn't help. Will try resync.

//Edit: resync worked. Will post here if I found something interesting in the log files.

//Edit2: here is related logs which possibly explains why unable to sync after restarted.
* The head_block of the chain was block 34498, id = 000086c202f51da427ebf0507404bc9b6d192f96
* Witness failed to push block 34499 last time, id = 000086c3bf20d2e5eeb1039f38c221b46880f2f0
* After restarted, the witness ignores block 34499 (id 000086c3bf20d2e5eeb1039f38c221b46880f2f0) because it's considered "seen"
* Following blocks are unable to push to chain because they're not linked (because 34499 is not on chain)

default.log:
Code: [Select]
2015-09-03T09:46:28 th_a:?unnamed? main ] Started witness node on a chain with 34498 blocks. main.cpp:165 ... 2015-09-03T09:48:39 th_a:invoke handle_block push_block ] Pushing block to fork database that failed to link. fork_database.cpp:57
p2p.log:
Code: [Select]
2015-09-03T09:46:30 p2p:message read_loop fetch_next_batch_of_ ] sync: sending a request for the next items after 000086c202f51da427ebf0507404bc9b6d192f96 to peer 176.9.234.167:40936, (full request is ["000006c280cdf25ca122561981716c74045f16fe","000046c2482fc56dda591b0bea7a47ccbd64d6b2","000066c27fc3abd468f7dd5ad1ce8939614d9d64","000076c2a8ad357d929c0967d98ba955521c11b4","00007ec23da7bcf6188fa3e6e57f0216e78cba1a","000082c22a40c3cbc1152bbd18239e9ffca051dc","000084c22add8beb2d06e3adb13c3573a56ae0b4","000085c29de6e5d439166100ab9d809c730e006c","00008642bd45a1a5711a74bacf4e73cfd5ae69cd","00008682ea2e75d79000e7a4c3411368d7a0a74a","000086a273f0cd7e751e91f6b0795486303009a2","000086b28863612b25b49a1c0a95a3525e42529c","000086ba6b31127d85ba6e1a8b5ea1145a0766e0","000086be74b88f7adb24796112e15c72b04a4e59","000086c0a1c19fb2c9b2d8d92f1caf812fda4bde","000086c19d4fdd989e8e7a62830c6f58e73f33be","000086c202f51da427ebf0507404bc9b6d192f96"]) node.cpp:2294 ... ... 2015-09-03T09:46:30 p2p:message read_loop on_blockchain_item_i ] sync: received a list of 669 available items from 192.241.198.6:39809 node.cpp:2310 2015-09-03T09:46:30 p2p:message read_loop on_blockchain_item_i ] is_first_item_for_other_peer: false. item_hashes_received.size() = 669 node.cpp:2356 2015-09-03T09:46:30 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer's last block the delegate has seen is now 000086c202f51da427ebf0507404bc9b6d192f96 (1) node.cpp:2368 2015-09-03T09:46:30 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer's last block the delegate has seen is now 000086c3bf20d2e5eeb1039f38c221b46880f2f0 (2) node.cpp:2368 2015-09-03T09:46:30 p2p:message read_loop on_blockchain_item_i ] after removing all items we have already seen, item_hashes_received.size() = 667 node.cpp:2371 2015-09-03T09:46:30 p2p:message read_loop trigger_fetch_sync_i ] Triggering fetch sync items loop now node.cpp:1084 2015-09-03T09:46:30 p2p:fetch_sync_items_loop fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:1023 2015-09-03T09:46:30 p2p:fetch_sync_items_loop request_sync_items_f ] requesting 100 item(s) ["000086c4e3da8babd770344cb8db18ee89a9d09a","000086c50ebdc7f4b5ff303fee02b53f3aec5773",...,"00008727dc9a24b61d0d51454278f2282e89672d"] from peer 192.241.198.6:39809 node.cpp:1007 ... ... 2015-09-03T09:48:39 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] Successfully pushed sync block 34500 (id:000086c4e3da8babd770344cb8db18ee89a9d09a) node.cpp:2793 2015-09-03T09:48:39 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] sync: client accpted the block, we now have only 5937 items left to fetch before we're in sync node.cpp:2831
Full default.log: https://drive.google.com/open?id=0B3xrm70jSHn4UWJ2N2QzdkVOX2M
Full p2p.log: https://drive.google.com/open?id=0B3xrm70jSHn4QVNoanZfMS13UXM
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 03, 2015, 12:09:41 pm: Good job everyone. I will look into these issues.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 03, 2015, 12:11:37 pm: Quote from: clayop on September 03, 2015, 04:42:43 am
Quote from: puppies on September 03, 2015, 04:40:26 am
Interesting. I am just running top through ssh from my VPS, and when I either manually spam transactions or do a flood_network command I see a dramatic increase in the CPU usage of witness_node. Up to 100% (its a dual core VPS, and I think top just references the core its running on) Would there be a better way to test it locally, or would it be better to find a way to sync better between multiple users? IRC, or Mumble?

Whenever I tried to flood_network, I met "Segmentation fault (core dumped)" error. How can you do this command?

Ben encountered this yesterday and has a fix for the wallet.
Title: Re: Test Net for Advanced Users
Post by: sudo on September 03, 2015, 03:17:55 pm: http://stats.bitshares.eu/

that is cool
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 03, 2015, 03:22:29 pm: Quote from: sudo on September 03, 2015, 03:17:55 pm
http://stats.bitshares.eu/

that is cool
Just installed an upgrade to this ..
sources are here:
https://github.com/BitSharesEurope/stats.bitshares.eu

definitely more to come once I figured out how trading ops look like
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 03:36:46 pm: Quote from: xeroc on September 03, 2015, 03:22:29 pm
Quote from: sudo on September 03, 2015, 03:17:55 pm
http://stats.bitshares.eu/

that is cool
Just installed an upgrade to this ..
sources are here:
https://github.com/BitSharesEurope/stats.bitshares.eu

definitely more to come once I figured out how trading ops look like

Very nice Xeroc. It seems much more stable. It still locks up pretty bad when I am flooding the network, but recovers nicely.
Title: Re: Test Net for Advanced Users
Post by: fav on September 03, 2015, 03:37:40 pm: Quote from: xeroc on September 03, 2015, 03:22:29 pm
Quote from: sudo on September 03, 2015, 03:17:55 pm
http://stats.bitshares.eu/

that is cool
Just installed an upgrade to this ..
sources are here:
https://github.com/BitSharesEurope/stats.bitshares.eu

definitely more to come once I figured out how trading ops look like

+5% very nice!

http://blog.smartcoin.pw/2015/09/bitshares-live-network-stats.html
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 03, 2015, 04:00:20 pm: Quote from: puppies on September 03, 2015, 03:36:46 pm
Very nice Xeroc. It seems much more stable. It still locks up pretty bad when I am flooding the network, but recovers nicely.
Yes .. I noticed that too .. it is currently storing all blocks .. I removed that .. I will definitely need to work more on the scalability ..
Title: Re: Test Net for Advanced Users
Post by: taoljj on September 03, 2015, 04:02:12 pm: I got the error, what is wrong?
Code: [Select]
3570357ms th_a application.cpp:228 operator() ] Initializing database... 11127ms th_a thread.cpp:95 thread ] name:ntp tid:140570790082304 11137ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 11145ms th_a thread.cpp:95 thread ] name:p2p tid:140570760709888 11153ms ntp ntp.cpp:81 request_now ] sending request to 97.107.128.58:123 11160ms th_a application.cpp:117 reset_p2p_node ] Adding seed node 104.236.118.105:1776 11166ms th_a application.cpp:129 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:34366 11169ms th_a application.cpp:179 reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090 11184ms th_a thread.cpp:115 ~thread ] calling quit() on p2p 11184ms th_a thread.cpp:160 quit ] destroying boost thread 140570760709888 11184ms p2p thread.cpp:246 exec ] thread canceled: 9 canceled_exception: Canceled cancellation reason: [none given] {"reason":"[none given]"} p2p thread_d.hpp:463 start_next_fiber 11223ms ntp ntp.cpp:147 read_loop ] received ntp reply from 97.107.128.58:123 11223ms ntp ntp.cpp:161 read_loop ] ntp offset: 1475, round_trip_delay 70059 11223ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 1475 13408ms th_a main.cpp:173 main ] Exiting with error: 13 N11websocketpp9exceptionE: Underlying Transport Error Underlying Transport Error: {"what":"Underlying Transport Error"} th_a application.cpp:182 reset_websocket_server {} th_a application.cpp:309 startup
Title: Re: Test Net for Advanced Users
Post by: betax on September 03, 2015, 04:09:32 pm: Quote from: puppies on September 03, 2015, 03:36:46 pm
Quote from: xeroc on September 03, 2015, 03:22:29 pm
Quote from: sudo on September 03, 2015, 03:17:55 pm
http://stats.bitshares.eu/

that is cool
Just installed an upgrade to this ..
sources are here:
https://github.com/BitSharesEurope/stats.bitshares.eu

definitely more to come once I figured out how trading ops look like

Very nice Xeroc. It seems much more stable. It still locks up pretty bad when I am flooding the network, but recovers nicely.

+5% +5%
Title: Re: Test Net for Advanced Users
Post by: betax on September 03, 2015, 04:12:03 pm: Hi,

I have recreated everything and when I dump_private_keys, I only get the key pair for my account, not the signing key.

Any ideas?

Edit: It is a known issue :

Quote from: bytemaster on August 21, 2015, 05:22:21 pm
Quote from: roadscape on August 21, 2015, 04:31:49 pm
Somehow I think I lost the private signing key because dump_private_keys only shows one set, and it belongs to the account itself. I guess I will have to register a new witness.. unless there's a way to generate a new signing key pair?

Quote from: mudshark79 on August 21, 2015, 04:27:25 pm
Btw: How do you read this:

Code: [Select]
1522956ms th_a witness.cpp:240 block_production_loo ] slot: 1 scheduled_witness: 1.6.1537 scheduled_time: 2015-08-21T16:25:21 now: 2015-08-21T16:25:21 1523956ms th_a witness.cpp:240 block_production_loo ] slot: 2 scheduled_witness: 1.6.56 scheduled_time: 2015-08-21T16:25:22 now: 2015-08-21T16:25:22 1524185ms th_a application.cpp:348 handle_block ] Got block #76718 from network 1524234ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"} 1524234ms th_a application.cpp:451 get_item ] Serving up block #76718 1524386ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"} 1524386ms th_a application.cpp:451 get_item ] Serving up block #76718
Did Witness 1.6.1537 produce his block? Why is the init-witness directly "queueing up" or getting another slot then?

I read it as 1.6.1537 missed the slot, and 1.6.56 filled in.

Ben had this problem too. Will look into this.

Edit 2: I found the keys on some notes, so I can get it up and running ;)
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 04:42:43 pm: I have run out of spam.

Anyone know how the fee structure works? How are lifetime member funds refunded? Is there a delay?
Title: Re: Test Net for Advanced Users
Post by: maqifrnswa on September 03, 2015, 06:10:31 pm: Reminder that
apt-add-repository ppa:showard314/ppa
has graphene Ubuntu packages built daily off of master in case you're a lurker that wants to jump in and give it a shot
Title: Re: Test Net for Advanced Users
Post by: clayop on September 03, 2015, 07:16:17 pm: Quote from: puppies on September 03, 2015, 04:42:43 pm
I have run out of spam.

Anyone know how the fee structure works? How are lifetime member funds refunded? Is there a delay?

Sent more fund.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 07:18:17 pm: Quote from: clayop on September 03, 2015, 07:16:17 pm
Quote from: puppies on September 03, 2015, 04:42:43 pm
I have run out of spam.

Anyone know how the fee structure works? How are lifetime member funds refunded? Is there a delay?

Sent more fund.

Thanks clayop. I'm gonna start an epic spam session. See if I can get something to break.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 03, 2015, 07:27:16 pm: Some delegate love for 1.6.3968 would be much appreciated :).
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 08:09:16 pm: Well that was fast. I managed to empty my wallet, and generate some giant log files, but nothing special there.
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 03, 2015, 08:32:49 pm: Quote from: puppies on September 03, 2015, 08:09:16 pm
Well that was fast. I managed to empty my wallet, and generate some giant log files, but nothing special there.
Bam! Good job
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 03, 2015, 08:43:22 pm: Quote from: xeroc on September 03, 2015, 08:32:49 pm
Quote from: puppies on September 03, 2015, 08:09:16 pm
Well that was fast. I managed to empty my wallet, and generate some giant log files, but nothing special there.
Bam! Good job

Looks like 1 block with 90 transactions in it doing 18 TPS. Good job.

We are working on some improvements in the networking code to reduce log file spam and unnecessary network communication.

We only seem to have 94% participation which given there are only 10 unique witnesses, 1 of which is responsible for 90% of blocks means the others are not producing.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 08:50:37 pm: I just generated 47457
Code: [Select]
get_block 47457 { "previous": "0000b96067bc8afae17b8e6b9a5db4312848b454", "timestamp": "2015-09-03T20:49:30", "witness": "1.6.1527", "transaction_merkle_root": "00https://bitsharestalk.org/Themes/default/images/bbc/left.gif00000000000000000000000000000000000000", "extensions": [], "witness_signature": "1f33614ffcb1e2b63110f6b0ed873a6fca3350ce0f66167505d8b11e60489f44f616201cc003c02dee28160722fcd99b4796929ffd630c1b7ba2c3fc9948d558e4", "transactions": [], "block_id": "0000b96116fe0ebf0f0a0afa47d54936287de751", "signing_key": "0321731744e219f69c9dd5cf43127205da272ca02d7927b4f0a90a33e34a812fee" }Is there any easy way to check witness production?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 03, 2015, 08:55:16 pm: Quote
"transaction_merkle_root": "00https://bitsharestalk.org/Themes/default/images/bbc/left.gif00000000000000000000000000000000000000",

What is up with this line?
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 09:05:27 pm: Quote from: bytemaster on September 03, 2015, 08:55:16 pm
Quote
"transaction_merkle_root": "00https://bitsharestalk.org/Themes/default/images/bbc/left.gif00000000000000000000000000000000000000",

What is up with this line?

lol. copy paste error.

I did find a good way of ensuring that your witness is producing blocks.

If you get_witness <witness_name>
Code: [Select]
unlocked >>> get_witness dele-puppy get_witness dele-puppy { "id": "1.6.1527", "witness_account": "1.2.22294", "last_aslot": 49430, "signing_key": "GPH75xxKG4ZeztPpnhmFch99smunUWMvDy9mB6Le497vpAA3XUXaD", "pay_vb": "1.13.163", "vote_id": "1:1526", "total_votes": "29174714611", "url": "" } unlocked >>>It will give you your vesting pay object as "pay_vb" from there you can get_object 1.13.163
Code: [Select]
unlocked >>> get_object 1.13.163 get_object 1.13.163 [{ "id": "1.13.163", "owner": "1.2.22294", "balance": { "amount": 326000000, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 86400, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "28080000000000", "coin_seconds_earned_last_update": "2015-09-03T20:56:30" } ] } ] unlocked >>>
Every time you generate a block the "amount": goes up by 1000000. So you can see that dele-puppy has generated 326 blocks. Not quite real time, but easier than watching the witness_node screen, or stats.bitshares.eu for your number.
Title: Re: Test Net for Advanced Users
Post by: abit on September 03, 2015, 09:13:18 pm: Quote from: puppies on September 03, 2015, 09:05:27 pm
I did find a good way of ensuring that your witness is producing blocks.

If you get_witness <witness_name>
Code: [Select]
unlocked >>> get_witness dele-puppy get_witness dele-puppy { "id": "1.6.1527", "witness_account": "1.2.22294", "last_aslot": 49430, "signing_key": "GPH75xxKG4ZeztPpnhmFch99smunUWMvDy9mB6Le497vpAA3XUXaD", "pay_vb": "1.13.163", "vote_id": "1:1526", "total_votes": "29174714611", "url": "" } unlocked >>>It will give you your vesting pay object as "pay_vb" from there you can get_object 1.13.163
Code: [Select]
unlocked >>> get_object 1.13.163 get_object 1.13.163 [{ "id": "1.13.163", "owner": "1.2.22294", "balance": { "amount": 326000000, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 86400, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "28080000000000", "coin_seconds_earned_last_update": "2015-09-03T20:56:30" } ] } ] unlocked >>>
Every time you generate a block the "amount": goes up by 1000000. So you can see that dele-puppy has generated 326 blocks. Not quite real time, but easier than watching the witness_node screen, or stats.bitshares.eu for your number.
Interesting. :D
I do find my block-producing witness is much more stable than last testnet. But my seed node got out of sync now and then.
Code: [Select]
get_object 1.13.160 [{ "id": "1.13.160", "owner": "1.2.38899", "balance": { "amount": 379000000, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 86400, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "32659200000000", "coin_seconds_earned_last_update": "2015-09-03T21:09:00" } ] } ]
Title: Re: Test Net for Advanced Users
Post by: clayop on September 03, 2015, 09:24:06 pm: I'm producing blocks

Code: [Select]
get_object 1.13.162 [{ "id": "1.13.162", "owner": "1.2.22310", "balance": { "amount": 174000000, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 86400, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "13755490000000", "coin_seconds_earned_last_update": "2015-09-03T21:19:15" } ] } ]
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 03, 2015, 09:39:34 pm: So far there have been 54,838 operations published on the test network and I can reindex the blockchain in 50 seconds (greater than 1000 operations per second) completely ignoring the fact that the test network has 100x as many maintenance blocks as it should.

In my profiling I see that 92% of the reindexing time is un perform_chain_maintenance which means that we are currently processing ~15K operations per second on average.

Given that the vast majority of blocks are empty the time spent doing empty block processing is lowering the average TPS my a significant margin.

Great work for everyone who has helped publish over 50K transactions on this test network so far :)
Title: Re: Test Net for Advanced Users
Post by: JA on September 03, 2015, 09:45:05 pm: Quote from: maqifrnswa on September 03, 2015, 06:10:31 pm
Reminder that
apt-add-repository ppa:showard314/ppa
has graphene Ubuntu packages built daily off of master in case you're a lurker that wants to jump in and give it a shot
can u write a little tut on how to start a witness?

i'm stuck when i try tu run ./witness_node with the latest json...no idea what i have to do :D
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 09:46:08 pm: I just need more CORE to keep spamming
Code: [Select]
"lifetime_fees_paid": "38644604445",
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 03, 2015, 09:46:36 pm: Quote from: puppies on September 03, 2015, 09:46:08 pm
I just need more CORE to keep spamming
Code: [Select]
"lifetime_fees_paid": "38644604445",

Which account should I send you core on?
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 09:49:21 pm: Quote from: bytemaster on September 03, 2015, 09:46:36 pm
Quote from: puppies on September 03, 2015, 09:46:08 pm
I just need more CORE to keep spamming
Code: [Select]
"lifetime_fees_paid": "38644604445",

Which account should I send you core on?
puppies please
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 03, 2015, 10:04:17 pm: Quote from: puppies on September 03, 2015, 09:49:21 pm
Quote from: bytemaster on September 03, 2015, 09:46:36 pm
Quote from: puppies on September 03, 2015, 09:46:08 pm
I just need more CORE to keep spamming
Code: [Select]
"lifetime_fees_paid": "38644604445",

Which account should I send you core on?
puppies please
500K core has been sent your way.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 10:05:50 pm: Thanks. Spamming away.
Title: Re: Test Net for Advanced Users
Post by: spartako on September 03, 2015, 10:08:06 pm: I'm producing blocks:

Code: [Select]
get_object 1.13.171 [{ "id": "1.13.171", "owner": "1.2.72728", "balance": { "amount": 165000000, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 86400, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "9032250000000", "coin_seconds_earned_last_update": "2015-09-03T22:04:05" } ] } ]
Title: Re: Test Net for Advanced Users
Post by: lafona on September 03, 2015, 10:09:33 pm: would there be any benefit spamming from multiple accounts? I have some time tonight and could join the party, I just don't have any core. I have my delegate on a vps and would be spamming from my home computer. Also puppies, are you using the flood network command or the script you wrote?
Title: Re: Test Net for Advanced Users
Post by: spartako on September 03, 2015, 10:14:35 pm: I have also created a script in nodejs (that I will publish tomorrow on github) with the list of last 101 blocks with delegate names to see who is producing blocks:

Code: [Select]
48340 '1.6.70' 'init69' 48339 '1.6.18' 'init17' 48338 '1.6.4232' 'spartako' 48337 '1.6.3968' 'riverhead' 48336 '1.6.64' 'init63' 48335 '1.6.7' 'init6' 48334 '1.6.75' 'init74' 48333 '1.6.46' 'init45' 48332 '1.6.5248' 'betaxtrade' 48331 '1.6.45' 'init44' 48330 '1.6.50' 'init49' 48329 '1.6.49' 'init48' 48328 '1.6.31' 'init30' 48327 '1.6.40' 'init39' 48326 '1.6.2' 'init1' 48325 '1.6.62' 'init61' 48324 '1.6.3' 'init2' 48323 '1.6.27' 'init26' 48322 '1.6.28' 'init27' 48321 '1.6.21' 'init20' 48320 '1.6.92' 'init91' 48319 '1.6.23' 'init22' 48318 '1.6.47' 'init46' 48317 '1.6.1538' 'delegate-clayop' 48316 '1.6.37' 'init36' 48315 '1.6.55' 'init54' 48314 '1.6.84' 'init83' 48313 '1.6.74' 'init73' 48312 '1.6.68' 'init67' 48311 '1.6.22' 'init21' 48310 '1.6.78' 'init77' 48309 '1.6.83' 'init82' 48308 '1.6.42' 'init41' 48307 '1.6.38' 'init37' 48306 '1.6.53' 'init52' 48305 '1.6.81' 'init80' 48304 '1.6.11' 'init10' 48303 '1.6.89' 'init88' 48302 '1.6.69' 'init68' 48301 '1.6.56' 'init55' 48300 '1.6.35' 'init34' 48299 '1.6.82' 'init81' 48298 '1.6.5247' 'in.abit' 48297 '1.6.72' 'init71' 48296 '1.6.39' 'init38' 48295 '1.6.36' 'init35' 48294 '1.6.16' 'init15' 48293 '1.6.29' 'init28' 48292 '1.6.67' 'init66' 48291 '1.6.12' 'init11' 48290 '1.6.41' 'init40' 48289 '1.6.34' 'init33' 48288 '1.6.8' 'init7' 48287 '1.6.66' 'init65' 48286 '1.6.4' 'init3' 48285 '1.6.70' 'init69' 48284 '1.6.64' 'init63' 48283 '1.6.90' 'init89' 48282 '1.6.17' 'init16' 48281 '1.6.14' 'init13' 48280 '1.6.20' 'init19' 48279 '1.6.32' 'init31' 48278 '1.6.10' 'init9' 48277 '1.6.79' 'init78' 48276 '1.6.45' 'init44' 48275 '1.6.80' 'init79' 48274 '1.6.1531' 'delegate-1.lafona' 48273 '1.6.26' 'init25' 48272 '1.6.54' 'init53' 48271 '1.6.18' 'init17' 48270 '1.6.9' 'init8' 48269 '1.6.85' 'init84' 48268 '1.6.61' 'init60' 48267 '1.6.7' 'init6' 48266 '1.6.60' 'init59' 48265 '1.6.86' 'init85' 48264 '1.6.46' 'init45' 48263 '1.6.25' 'init24' 48262 '1.6.33' 'init32' 48261 '1.6.58' 'init57' 48260 '1.6.5248' 'betaxtrade' 48259 '1.6.43' 'init42' 48258 '1.6.59' 'init58' 48257 '1.6.1' 'init0' 48256 '1.6.19' 'init18' 48255 '1.6.48' 'init47' 48254 '1.6.91' 'init90' 48253 '1.6.44' 'init43' 48252 '1.6.73' 'init72' 48251 '1.6.65' 'init64' 48250 '1.6.87' 'init86' 48249 '1.6.88' 'init87' 48248 '1.6.24' 'init23' 48247 '1.6.6' 'init5' 48246 '1.6.30' 'init29' 48245 '1.6.52' 'init51' 48244 '1.6.51' 'init50' 48243 '1.6.4232' 'spartako' 48242 '1.6.57' 'init56' 48241 '1.6.76' 'init75' 48240 '1.6.1527' 'dele-puppy'
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 10:18:47 pm: Quote from: lafona on September 03, 2015, 10:09:33 pm
would there be any benefit spamming from multiple accounts? I have some time tonight and could join the party, I just don't have any core. I have my delegate on a vps and would be spamming from my home computer. Also puppies, are you using the flood network command or the script you wrote?
I am spamming with a keyboard emulator called autokey. It allows you to set up phrases as hotkeys, I set <up><enter> a whole bunch of times, and set it to a hot key. I set up the wallet transfer once to make sure it is okay, and then spam the hotkey. Every time you hit the key it will queue up another iteration of the phrase. I spam it for 30 seconds or so, and it will go for hours.

I am sure there is a much more elegant way to handle this, but I didn't want to take the time to figure it out. I knew this would work, and would be easy to set up.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 10:36:41 pm: Quote from: jabbajabbaつ◕_◕つ on September 03, 2015, 09:45:05 pm
Quote from: maqifrnswa on September 03, 2015, 06:10:31 pm
Reminder that
apt-add-repository ppa:showard314/ppa
has graphene Ubuntu packages built daily off of master in case you're a lurker that wants to jump in and give it a shot
can u write a little tut on how to start a witness?

i'm stuck when i try tu run ./witness_node with the latest json...no idea what i have to do :D

from where you would like to run the witness node try
Code: [Select]
wget https://github.com/cryptonomex/graphene/releases/download/test2b/aug-31-testnet-genesis.json mkdir test nano test/config.iniThen copy the code below into the terminal window and hit control-x and then y and then enter.
Code: [Select]
# Endpoint for P2P node to listen on p2p-endpoint = 0.0.0.0:1776 # P2P nodes to connect to on startup (may specify multiple times) seed-node = 104.236.118.105:1776 # Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints. # checkpoint = # Endpoint for websocket RPC to listen on rpc-endpoint = 127.0.0.1:8090 # Endpoint for TLS websocket RPC to listen on # rpc-tls-endpoint = # The TLS certificate file for this server # server-pem = # Password for this certificate # server-pem-password = # File to read Genesis State from genesis-json = aug-31-testnet-genesis.json # JSON file specifying API permissions # api-access = # Enable block production, even if the chain is stale. enable-stale-production = false # Percent of witnesses (0-99) that must be participating in order to produce blocks required-participation = false # Allow block production, even if the last block was produced by the same witness. allow-consecutive = false # ID of witness controlled by this node (e.g. "1.6.5", quotes are required, may specify multiple times) # witness-id = # Tuple of [PublicKey, WIF private key] (may specify multiple times) private-key = ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"] # Account ID to track history for (may specify multiple times) # track-account = # Track market history by grouping orders into buckets of equal size measured in seconds specified as a JSON array of numbers bucket-size = [15,60,300,3600,86400] # How far back in time to track history for each bucket size, measured in the number of buckets (default: 1000) history-per-size = 1000 # declare an appender named "stderr" that writes messages to the console [log.console_appender.stderr] stream=std_error # declare an appender named "p2p" that writes messages to p2p.log [log.file_appender.p2p] filename=logs/p2p/p2p.log # filename can be absolute or relative to this config file # route any messages logged to the default logger to the "stderr" logger we # declared above, if they are info level are higher [logger.default] level=info appenders=stderr # route messages sent to the "p2p" logger to the p2p appender declared above [logger.p2p] level=debug appenders=p2pafter that type
Code: [Select]
witness_node -d testadd a ./ to the beginning of that if you have built the source code yourself and haven't used maqs ppa. Although if thats the case you will need to be running this is the same directory as your witness_node binary.

Let me know if this doesn't make sense, or you have any other questions. Once you have the witness node running you will be able to run the cli_wallet and set up a witness. I can help you with that if needed.

edit had wrong json download in there. Sorry
Title: Re: Test Net for Advanced Users
Post by: clayop on September 03, 2015, 11:05:30 pm: Quote from: puppies on September 03, 2015, 10:18:47 pm
Quote from: lafona on September 03, 2015, 10:09:33 pm
would there be any benefit spamming from multiple accounts? I have some time tonight and could join the party, I just don't have any core. I have my delegate on a vps and would be spamming from my home computer. Also puppies, are you using the flood network command or the script you wrote?
I am spamming with a keyboard emulator called autokey. It allows you to set up phrases as hotkeys, I set <up><enter> a whole bunch of times, and set it to a hot key. I set up the wallet transfer once to make sure it is okay, and then spam the hotkey. Every time you hit the key it will queue up another iteration of the phrase. I spam it for 30 seconds or so, and it will go for hours.

I am sure there is a much more elegant way to handle this, but I didn't want to take the time to figure it out. I knew this would work, and would be easy to set up.

Can you share the link of autokey?
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 11:13:38 pm: on ubuntu
Code: [Select]
sudo apt-get install autokey-gtk
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 11:20:46 pm: And I'm broke again. Spam is expensive.

Code: [Select]
get_object 2.6.63354 [{ "id": "2.6.63354", "owner": "1.2.63354", "most_recent_op": "2.9.104924", "total_core_in_orders": 0, "lifetime_fees_paid": "88442604445", "pending_fees": 0, "pending_vested_fees": 0 } ]and then when I look at
Code: [Select]
get_object 1.13.173 [{ "id": "1.13.173", "owner": "1.2.63354", "balance": { "amount": "69011678875", "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 31536000, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "2176352305002000000", "coin_seconds_earned_last_update": "2015-09-03T23:15:00"Do we really have to wait a year for the 80% refund on fees?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 03, 2015, 11:21:52 pm: Quote from: puppies on September 03, 2015, 11:13:38 pm
on ubuntu
Code: [Select]
sudo apt-get install autokey-gtk

Thanks. Could you also share your script code?
Title: Re: Test Net for Advanced Users
Post by: puppies on September 03, 2015, 11:28:20 pm: Quote from: clayop on September 03, 2015, 11:21:52 pm
Quote from: puppies on September 03, 2015, 11:13:38 pm
on ubuntu
Code: [Select]
sudo apt-get install autokey-gtk

Thanks. Could you also share your script code?
Go to new and then select phrase. Name your phrase. In the window type in <up><enter><up><enter><up><enter> a bunch. I just ctrl-c, a few and then spam ctrl-v. Then save your phrase. set a hot key down below, and you are good to go.

If you get a little bit too much spam going, click the A in your system tray and unclick enable expansions. (I think that will work. I have had to reboot a couple of times.)
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 03, 2015, 11:39:38 pm: I have spammed myself out of CORE as well. If someone could be so kind...account is: riverhead

So far it's been rock solid. Running the witness on a standalone box and the client on a laptop. Going to switch the witness to a more powerful box and try heavier stress testing.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 04, 2015, 12:02:38 am: My home spam witness_node lost sync, so I restarted and got a seg fault while replaying blockchain. Here is the bt. Hopefully helpful.
Code: [Select]
98.0572% 48000 of 48951 witness_node: /home/user/src/graphene/libraries/fc/include/fc/optional.hpp:192: T& fc::optional<T>::operator*() [with T = graphene::chain::signed_block]: Assertion `_valid' failed. Program received signal SIGABRT, Aborted. 0x00007ffff6c01cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ffff6c01cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007ffff6c050d8 in __GI_abort () at abort.c:89 #2 0x00007ffff6bfab86 in __assert_fail_base ( fmt=0x7ffff6d4b830 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x29b610d "_valid", file=file@entry=0x29b60d0 "/home/user/src/graphene/libraries/fc/include/fc/optional.hpp", line=line@entry=192, function=function@entry=0x29bb260 <fc::optional<graphene::chain::signed_block>::operator*()::__PRETTY_FUNCTION__> "T& fc::optional<T>::operator*() [with T = graphene::chain::signed_block]") at assert.c:92 #3 0x00007ffff6bfac32 in __GI___assert_fail (assertion=0x29b610d "_valid", file=0x29b60d0 "/home/user/src/graphene/libraries/fc/include/fc/optional.hpp", line=192, function=0x29bb260 <fc::optional<graphene::chain::signed_block>::operator*()::__PRETTY_FUNCTION__> "T& fc::optional<T>::operator*() [with T = graphene::chain::signed_block]") at assert.c:101 #4 0x0000000001f07028 in fc::optional<graphene::chain::signed_block>::operator*() () #5 0x0000000002268967 in graphene::chain::database::reindex(fc::path, graphene::chain::genesis_state_type const&) () #6 0x0000000001ef7a62 in graphene::app::detail::application_impl::startup() () #7 0x0000000001eebfa2 in graphene::app::application::startup() () ---Type <return> to continue, or q <return> to quit--- #8 0x0000000001ec268f in main ()
Title: Re: Test Net for Advanced Users
Post by: clayop on September 04, 2015, 01:47:51 am: Can we have a spam party after mumble session? 8)
Title: Re: Test Net for Advanced Users
Post by: puppies on September 04, 2015, 01:57:12 am: Quote from: clayop on September 04, 2015, 01:47:51 am
Can we have a spam party after mumble session? 8)

I think that would be great. I would love to see how high we could get our TPS
Title: Re: Test Net for Advanced Users
Post by: taoljj on September 04, 2015, 03:10:16 am: I am in.
witness id 1.6.234,
accout id airdrop
I need more CORE to test,thanks all.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 04, 2015, 03:18:54 am: Quote from: puppies on September 04, 2015, 01:57:12 am
Quote from: clayop on September 04, 2015, 01:47:51 am
Can we have a spam party after mumble session? 8)

I think that would be great. I would love to see how high we could get our TPS

Sent some more CORE for tomorrow's party. Enjoy!
Title: Re: Test Net for Advanced Users
Post by: clayop on September 04, 2015, 03:19:55 am: Quote from: taoljj on September 04, 2015, 03:10:16 am
I am in.
witness id 1.6.234,
accout id airdrop
I need more CORE to test,thanks all.

Sent. Can you join tomorrow's spam party?
Title: Re: Test Net for Advanced Users
Post by: taoljj on September 04, 2015, 03:22:48 am: Quote from: clayop on September 04, 2015, 03:19:55 am
Quote from: taoljj on September 04, 2015, 03:10:16 am
I am in.
witness id 1.6.234,
accout id airdrop
I need more CORE to test,thanks all.

Sent. Can you join tomorrow's spam party?

Thanks, of course.But how to join?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 04, 2015, 03:27:24 am: Quote from: taoljj on September 04, 2015, 03:22:48 am
Quote from: clayop on September 04, 2015, 03:19:55 am
Quote from: taoljj on September 04, 2015, 03:10:16 am
I am in.
witness id 1.6.234,
accout id airdrop
I need more CORE to test,thanks all.

Sent. Can you join tomorrow's spam party?

Thanks, of course.But how to join?

Make as many transaction as you can at 11AM EST (I believe 11PM in China)
Title: Re: Test Net for Advanced Users
Post by: clayop on September 04, 2015, 03:28:31 am: Quote from: puppies on September 03, 2015, 11:28:20 pm
Quote from: clayop on September 03, 2015, 11:21:52 pm
Quote from: puppies on September 03, 2015, 11:13:38 pm
on ubuntu
Code: [Select]
sudo apt-get install autokey-gtk

Thanks. Could you also share your script code?
Go to new and then select phrase. Name your phrase. In the window type in <up><enter><up><enter><up><enter> a bunch. I just ctrl-c, a few and then spam ctrl-v. Then save your phrase. set a hot key down below, and you are good to go.

If you get a little bit too much spam going, click the A in your system tray and unclick enable expansions. (I think that will work. I have had to reboot a couple of times.)

My basic script for making 3000 transactions

Code: [Select]
import time for i in range(3000): keyboard.send_keys("<up>" "<enter>") time.sleep(0.05)
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 04, 2015, 05:01:44 am: I could use some CORE for spam if possible. -> delegate.xeldal

and some votes for 1.6.1625 also, i'mguessing "total_votes" shouldn't be 0

Code: [Select]
{ "id": "1.6.1625", ... "total_votes": 0, "url": "" }
Title: Re: Test Net for Advanced Users
Post by: taoljj on September 04, 2015, 05:13:03 am: Code: [Select]
get_witness airdrop { "id": "1.6.234", "witness_account": "1.2.1854", "last_aslot": 0, "signing_key": "GPH6XXXXXXXXXXXXXXXXXXXXXXXX", "vote_id": "1:233", "total_votes": 204540615, "url": "" }
1.6.234 is not producing block and no "pay_vb"

1.6.234 is active.

Because 1.6.234 was a delegate in genesis block ?
Title: Re: Test Net for Advanced Users
Post by: puppies on September 04, 2015, 05:49:14 am: Quote from: taoljj on September 04, 2015, 05:13:03 am
Code: [Select]
get_witness airdrop { "id": "1.6.234", "witness_account": "1.2.1854", "last_aslot": 0, "signing_key": "GPH6XXXXXXXXXXXXXXXXXXXXXXXX", "vote_id": "1:233", "total_votes": 204540615, "url": "" }
1.6.234 is not producing block and no "pay_vb"

1.6.234 is active.

Because 1.6.234 was a delegate in genesis block ?

You have to launch the witness node with the proper commands. You can either put it all in the command line like,
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-31-testnet-genesis.json -s 104.236.118.105:1776 --witness-id '"1.6.234"' --private-key '["GP...................................oy", "5KW.......................P8a"]'
or you can add these parameters to the config.ini.

I hope thats what you were asking.
Title: Re: Test Net for Advanced Users
Post by: taoljj on September 04, 2015, 08:07:29 am: Thanks，I have launched the witness node.

I think maybe "airdrop"(1.6.234) is a delegate in genesis block , can not upgrade to to a lifetime member and create_witness.

Quote from: puppies on September 04, 2015, 05:49:14 am
Quote from: taoljj on September 04, 2015, 05:13:03 am
Code: [Select]
get_witness airdrop { "id": "1.6.234", "witness_account": "1.2.1854", "last_aslot": 0, "signing_key": "GPH6XXXXXXXXXXXXXXXXXXXXXXXX", "vote_id": "1:233", "total_votes": 204540615, "url": "" }
1.6.234 is not producing block and no "pay_vb"

1.6.234 is active.

Because 1.6.234 was a delegate in genesis block ?

You have to launch the witness node with the proper commands. You can either put it all in the command line like,
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json aug-31-testnet-genesis.json -s 104.236.118.105:1776 --witness-id '"1.6.234"' --private-key '["GP...................................oy", "5KW.......................P8a"]'
or you can add these parameters to the config.ini.

I hope thats what you were asking.
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 04, 2015, 08:59:39 am: Thank you puppies, with the missing link
Code: [Select]
wget https://github.com/cryptonomex/graphene/releases/download/test2b/aug-31-testnet-genesis.json]I found finally the right chain after test 1 ;)

Witness ID: 1.6.1063
Witness Acc: 1.2.14540

some votes and CORE for "calabiyau" would be appreciated to join the ~~efforts~~>> party.
Title: Re: Test Net for Advanced Users
Post by: cube on September 04, 2015, 09:38:52 am: I am joining in the testing.

ID: 1.6.624
Witness Account: 1.2.8112
Account: bitcube

Can someone send me some CORE and vote me in?
Title: Re: Test Net for Advanced Users
Post by: bitcard on September 04, 2015, 10:04:51 am: Quote from: cube on September 04, 2015, 09:38:52 am
I am joining in the testing.

ID: 1.6.624
Witness Account: 1.2.8112
Account: bitcube

Can someone send me some CORE and vote me in?

how to join? is there any guide?
Title: Re: Test Net for Advanced Users
Post by: cube on September 04, 2015, 10:17:55 am: I keep getting this but not producing blocks.

Code: [Select]
855000ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn 855000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441361655009392 next_second: 2015-09-04T10:14:16 856001ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn 856001ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441361656010598 next_second: 2015-09-04T10:14:17 857001ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn ...
What does it mean by "Not producing block because it isn't my turn"?
Title: Re: Test Net for Advanced Users
Post by: cube on September 04, 2015, 10:19:52 am: Quote from: bitcard on September 04, 2015, 10:04:51 am
how to join? is there any guide?

Check out this guide : https://github.com/cryptonomex/graphene/wiki/Howto-become-an-active-witness-in-BitShares-2.0
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 04, 2015, 10:30:02 am: Quote from: cube on September 04, 2015, 10:17:55 am
I keep getting this but not producing blocks.

Code: [Select]
855000ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn 855000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441361655009392 next_second: 2015-09-04T10:14:16 856001ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn 856001ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441361656010598 next_second: 2015-09-04T10:14:17 857001ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn ...
What does it mean by "Not producing block because it isn't my turn"?

I'm getting the same

I have tried

Code: [Select]
witness_node -d testNet2 --resync-blockchainand
Code: [Select]
rm testNet2/blockchain/ testNet2/p2p/ testNet2/logs/ object_database/ -fr witness_node -d testNet2
have we a list of active seed nodes?
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 10:35:15 am: You need the .json file of the genesis block. It can be found here:

https://github.com/cryptonomex/graphene/releases/download/test2b/aug-31-testnet-genesis.json

Once you have that you start your witness with something like:
Code: [Select]
./witness_node --rpc-endpoint "192.168.1.11:8090" -d test_net_2 -s "104.236.118.105:1776" --genesis-json aug-31-testnet-genesis.json

Quote from: cube on September 04, 2015, 10:17:55 am
I keep getting this but not producing blocks.

Code: [Select]
855000ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn 855000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441361655009392 next_second: 2015-09-04T10:14:16 856001ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn 856001ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441361656010598 next_second: 2015-09-04T10:14:17 857001ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn ...
What does it mean by "Not producing block because it isn't my turn"?

That is normal, or at least I get it as well yet still produce blocks. Puppies posted this up which works well to see if you're producing:

Code: [Select]
get_witness riverhead { "id": "1.6.3968", "witness_account": "1.2.67159", "last_aslot": 58732, "signing_key": "GPH6BJYGHftujnbttFFKX6YacnvsMd4sbJrbucg682GiU4vmXHTik", "pay_vb": "1.13.178", "vote_id": "1:3967", "total_votes": 1514765, "url": "" } unlocked >>> get_object "1.13.178" get_object "1.13.178" [{ "id": "1.13.178", "owner": "1.2.67159", "balance": { "amount": 96000000, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 86400, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "2534355000000", "coin_seconds_earned_last_update": "2015-09-04T10:32:25" } ] } ]

The pay_vb shows the vesting balance object ID. If that is accruing funds you're producing blocks.
Title: Re: Test Net for Advanced Users
Post by: bitcard on September 04, 2015, 10:42:51 am: Quote from: cube on September 04, 2015, 10:19:52 am
Quote from: bitcard on September 04, 2015, 10:04:51 am
how to join? is there any guide?

Check out this guide : https://github.com/cryptonomex/graphene/wiki/Howto-become-an-active-witness-in-BitShares-2.0

thanks, I will try it.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 10:48:00 am: Quote from: Xeldal on September 04, 2015, 05:01:44 am
I could use some CORE for spam if possible. -> delegate.xeldal

and some votes for 1.6.1625 also, i'mguessing "total_votes" shouldn't be 0

Code: [Select]
{ "id": "1.6.1625", ... "total_votes": 0, "url": "" }

Voted. Also, there is a Maintenance Interval that can be quite long by default. It can be changed via a parameter - check the links on the OP.

Also - I could use some CORE as well :).
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 04, 2015, 11:19:02 am: The brave among you can try to interface with the cli_wallet with
https://github.com/xeroc/python-graphenelib
and run the examples/flood.py script.

you have to run the cli_wallet(!!!) with
-H 127.0.0.1:8092
and unlock your wallet.

Again: Do not try to interface with the witness_node, but instead use the cli_wallet and make sure to have it unlocked!!
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 11:34:31 am: Quote from: xeroc on September 04, 2015, 11:19:02 am
you have to run the cli_wallet(!!!) with
-H 127.0.0.1:8092
and unlock your wallet.

My wallet will not run with this flag. Is there anything else needed? My two attempts:

Code: [Select]
cli_wallet -w test2b --chain-id ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3 -H 127.0.0.1:8092 Logging RPC to file: logs/rpc/rpc.log 2022756ms th_a main.cpp:111 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W 2022757ms th_a main.cpp:115 main ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV 2022757ms th_a main.cpp:116 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3 2022760ms th_a main.cpp:163 main ] wdata.ws_server: ws://localhost:8090 0 exception: unspecified Underlying Transport Error {"message":"Underlying Transport Error"} asio websocket.cpp:431 operator() {"uri":"ws://localhost:8090"} th_a websocket.cpp:616 connect
Code: [Select]
./cli_wallet -H 127.0.0.1:8092 Logging RPC to file: logs/rpc/rpc.log 2052250ms th_a main.cpp:111 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W 2052250ms th_a main.cpp:115 main ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV 2052250ms th_a main.cpp:116 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3 Starting a new wallet with chain ID 6d2141a7a5577221d3681a4b6296e330f77a4668ddcd78fbbe4fbe966e54bccc (from egenesis) 2052251ms th_a main.cpp:163 main ] wdata.ws_server: ws://localhost:8090 0 exception: unspecified Underlying Transport Error {"message":"Underlying Transport Error"} asio websocket.cpp:431 operator() {"uri":"ws://localhost:8090"} th_a websocket.cpp:616 connect
Title: Re: Test Net for Advanced Users
Post by: bulletproof on September 04, 2015, 11:35:38 am: Quote from: bytemaster on August 14, 2015, 10:39:33 pm
Download this Aug-14 snapshot of BitShares:

https://drive.google.com/open?id=0B_GVo0GoC_v_S3lPOWlUbFJFWTQ

If you have a mac, download the draft version of BitShares 0.9.2 which has a new api call
https://github.com/bitshares/bitshares/releases/tag/untagged-4166986045ff28284dc4

This bit in the OP had a link to a new 0.9.2 release with an API call to export all keys. The link is dead and there are no releases since May - is this a red herring?
Title: Re: Test Net for Advanced Users
Post by: cube on September 04, 2015, 11:40:02 am: Quote from: Riverhead on September 04, 2015, 10:35:15 am

The pay_vb shows the vesting balance object ID. If that is accruing funds you're producing blocks.

I think I am connecting to the correct test net but I do not see the 'pay_vb' object. What did I miss?

Code: [Select]
info { "head_block_num": 56624, "head_block_id": "0000dd308073d87ccb3b0d739f07ebfb6842e95c", "head_block_age": "0 second old", "next_maintenance_time": "4 minutes in the future", "chain_id": "ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3", ,,,
Code: [Select]
get_witness bitcube { "id": "1.6.624", "witness_account": "1.2.8112", "last_aslot": 0, "signing_key": "GPxxxxxxaaaaxxxx", "vote_id": "1:623", "total_votes": "64885994140", "url": "" }
Edit: I think I found the answer. It is not voted in yet. Please help vote it in.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 11:45:01 am: When you first start your witness node does it give you any errors (in blue) about the pub/priv key pair you specified for your witness?

Your slots being 0 probably means you aren't actually signing blocks however you have votes so your witness is good to go.
Title: Re: Test Net for Advanced Users
Post by: cube on September 04, 2015, 11:48:15 am: Quote from: Riverhead on September 04, 2015, 11:45:01 am

When you first start your witness node does it give you any errors (in blue) about the pub/priv key pair you specified for your witness?

Your slots being 0 probably means you aren't actually signing blocks however you have votes so your witness is good to go.

I think I found the answer. It is not voted in yet. Please help vote it in.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 11:52:39 am: Quote from: cube on September 04, 2015, 11:48:15 am
Quote from: Riverhead on September 04, 2015, 11:45:01 am

When you first start your witness node does it give you any errors (in blue) about the pub/priv key pair you specified for your witness?

Your slots being 0 probably means you aren't actually signing blocks however you have votes so your witness is good to go.

I think I found the answer. It is not voted in yet. Please help vote it in.

You have way more votes than me - not sure why you don't show up in the list. You still don't have an assigned slot either. Are you sure your witness_node recognizes your keys?
Title: Re: Test Net for Advanced Users
Post by: cube on September 04, 2015, 12:11:22 pm: Quote from: Riverhead on September 04, 2015, 11:52:39 am

You have way more votes than me - not sure why you don't show up in the list. You still don't have an assigned slot either. Are you sure your witness_node recognizes your keys?

How to be really sure?

I got the public key from the signing key in the command 'get_witness bitcube'.

Code: [Select]
get_witness bitcube { "id": "1.6.624", "witness_account": "1.2.8112", "last_aslot": 0, "signing_key": "GPxxxx-PUBLICKEY", "vote_id": "1:623", "total_votes": "64884389452", "url": "" }
I looked up the public-private key pair in dump_private_keys

Code: [Select]
dump_private_keys [[ "GPxxxx-PUBLICKEY", "5Jxxx-PRIVATEKEY" ],[ "GPxxxx-PUBLICKEY2", "5Jxxx-PRIVATEKEY2" ] ]
I entered the key pair into config.ini

Code: [Select]
# ID of witness controlled by this node (e.g. "1.6.5", quotes are required, may specify multiple times) witness-id = "1.6.624" # Tuple of [PublicKey, WIF private key] (may specify multiple times) private-key = ["GPxxxx-PUBLICKEY","5Jxxx-PRIVATEKEY"]
When I run the witness_node, the log says:

Code: [Select]
57981ms th_a witness.cpp:84 plugin_initialize ] witness plugin: plugin_initialize() begin 57981ms th_a witness.cpp:94 plugin_initialize ] key_id_to_wif_pair: ["GPxxxx-PUBLICKEY","5Jxxx-PRIVATEKEY"] 57982ms th_a witness.cpp:112 plugin_initialize ] witness plugin: plugin_initialize() end 58201ms th_a application.cpp:228 operator() ] Initializing database...
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 12:14:56 pm: What is your Chain ID? ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3

I show a different vote count for you:

Code: [Select]
get_witness bitcube { "id": "1.6.624", "witness_account": "1.2.8112", "last_aslot": 0, "signing_key": "GPH7qbi1...y..sn", "vote_id": "1:623", "total_votes": "64885994140", "url": "" }
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 12:20:09 pm: Is there a way to withdraw witness pay? Would be a good source of testing funds.
Title: Re: Test Net for Advanced Users
Post by: cube on September 04, 2015, 12:30:15 pm: Quote from: Riverhead on September 04, 2015, 12:14:56 pm

What is your Chain ID? ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3

I show a different vote count for you:

Code: [Select]
get_witness bitcube { "id": "1.6.624", "witness_account": "1.2.8112", "last_aslot": 0, "signing_key": "GPH7qbi1...y..sn", "vote_id": "1:623", "total_votes": "64885994140", "url": "" }

Chain ID matches.

Code: [Select]
{ "head_block_num": 56624, "head_block_id": "0000dd308073d87ccb3b0d739f07ebfb6842e95c", "head_block_age": "0 second old", "next_maintenance_time": "4 minutes in the future", "chain_id": "ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3", ,,,
Code: [Select]
"total_votes": "64885994140",
Vote count matches too. Yet I am not in the active list. What's wrong?
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 12:35:17 pm: The only other thing I can think of is in the witness config.ini file there is a parameter called enable-stale-production which needs to be false. I think that's the default now so that's probably not the issue.
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 04, 2015, 01:07:58 pm: Quote from: Riverhead on September 04, 2015, 11:34:31 am
Quote from: xeroc on September 04, 2015, 11:19:02 am
you have to run the cli_wallet(!!!) with
-H 127.0.0.1:8092
and unlock your wallet.

My wallet will not run with this flag. Is there anything else needed? My two attempts:

Code: [Select]
cli_wallet -w test2b --chain-id ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3 -H 127.0.0.1:8092 Logging RPC to file: logs/rpc/rpc.log 2022756ms th_a main.cpp:111 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W 2022757ms th_a main.cpp:115 main ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV 2022757ms th_a main.cpp:116 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3 2022760ms th_a main.cpp:163 main ] wdata.ws_server: ws://localhost:8090 0 exception: unspecified Underlying Transport Error {"message":"Underlying Transport Error"} asio websocket.cpp:431 operator() {"uri":"ws://localhost:8090"} th_a websocket.cpp:616 connect
Code: [Select]
./cli_wallet -H 127.0.0.1:8092 Logging RPC to file: logs/rpc/rpc.log 2052250ms th_a main.cpp:111 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W 2052250ms th_a main.cpp:115 main ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV 2052250ms th_a main.cpp:116 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3 Starting a new wallet with chain ID 6d2141a7a5577221d3681a4b6296e330f77a4668ddcd78fbbe4fbe966e54bccc (from egenesis) 2052251ms th_a main.cpp:163 main ] wdata.ws_server: ws://localhost:8090 0 exception: unspecified Underlying Transport Error {"message":"Underlying Transport Error"} asio websocket.cpp:431 operator() {"uri":"ws://localhost:8090"} th_a websocket.cpp:616 connect

Maybe I made myself a little unclear .. you need to run a witness_node and a cli_node ..
The setup would look like:

Witness (port 8090) <---> cli_wallet (port:8092) <-----> python
Title: Re: Test Net for Advanced Users
Post by: cube on September 04, 2015, 01:27:47 pm: Quote from: Riverhead on September 04, 2015, 12:35:17 pm

The only other thing I can think of is in the witness config.ini file there is a parameter called enable-stale-production which needs to be false. I think that's the default now so that's probably not the issue.

I am using 'enable-stale-production' as described in xeroc's guide. I am going to try without it.
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 04, 2015, 01:44:12 pm: Quote from: cube on September 04, 2015, 01:27:47 pm
Quote from: Riverhead on September 04, 2015, 12:35:17 pm

The only other thing I can think of is in the witness config.ini file there is a parameter called enable-stale-production which needs to be false. I think that's the default now so that's probably not the issue.

I am using 'enable-stale-production' as described in xeroc's guide. I am going to try without it.
Sorry for that .. I removed it from the wiki
Title: Re: Test Net for Advanced Users
Post by: betax on September 04, 2015, 01:47:54 pm: Quote from: bitcard on September 04, 2015, 10:04:51 am
Quote from: cube on September 04, 2015, 09:38:52 am
I am joining in the testing.

ID: 1.6.624
Witness Account: 1.2.8112
Account: bitcube

Can someone send me some CORE and vote me in?

how to join? is there any guide?

Check this guide for Ubuntu and test2b https://github.com/cryptonomex/graphene/wiki/How-to-setup-your-witness-for-test-net-(Ubuntu-14.04)
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 01:50:30 pm: Quote from: xeroc on September 04, 2015, 01:07:58 pm

Maybe I made myself a little unclear .. you need to run a witness_node and a cli_node ..
The setup would look like:

Witness (port 8090) <---> cli_wallet (port:8092) <-----> python

A bit. The directions say not to connect to a witness_node :). I see now you meant not to fire your script against the witness node.
Title: Re: Test Net for Advanced Users
Post by: cube on September 04, 2015, 01:57:56 pm: Quote from: Riverhead on September 04, 2015, 12:35:17 pm

The only other thing I can think of is in the witness config.ini file there is a parameter called enable-stale-production which needs to be false. I think that's the default now so that's probably not the issue.

I removed 'enable-stale-production' and restarted after a full blockchain resynced. I am still not in the active list. Any idea?
Title: Re: Test Net for Advanced Users
Post by: bitcard on September 04, 2015, 02:12:10 pm: how to set witness-id? I set the witness-id = "1.6.5" in config.ini, is it ok?
I get the follow info:
379000ms th_a witness.cpp:179 block_production_loo ] Not producing block because it isn't my turn
379000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375579000817 next_second: 2015-09-04T14:06:20
380000ms th_a witness.cpp:194 block_production_loo ] Not producing block because the last block was generated by the same witness.
This node is probably disconnected from the network so block production has been disabled.
Disable this check with --allow-consecutive option.
380000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375580000857 next_second: 2015-09-04T14:06:21
381000ms th_a witness.cpp:191 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
381000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375581000983 next_second: 2015-09-04T14:06:22
382000ms th_a witness.cpp:191 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
382000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375582000927 next_second: 2015-09-04T14:06:23
383000ms th_a witness.cpp:191 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
383000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375583000805 next_second: 2015-09-04T14:06:24
384000ms th_a witness.cpp:191 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
384000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375584000792 next_second: 2015-09-04T14:06:25
385000ms th_a witness.cpp:179 block_production_loo ] Not producing block because it isn't my turn

what's wrong with it?
Title: Re: Test Net for Advanced Users
Post by: betax on September 04, 2015, 02:27:01 pm: Quote from: xeroc on September 04, 2015, 11:19:02 am
The brave among you can try to interface with the cli_wallet with
https://github.com/xeroc/python-graphenelib
and run the examples/flood.py script.

you have to run the cli_wallet(!!!) with
-H 127.0.0.1:8092
and unlock your wallet.

Again: Do not try to interface with the witness_node, but instead use the cli_wallet and make sure to have it unlocked!!

How to install xeroc's flooding script

Open screen
Code: [Select]
screen
Run cli wallet with -H 127.0.0.1:8092
Code: [Select]
./cli_wallet -w test_wallet --chain-id ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3 -H 127.0.0.1:8092
unlock your wallet

Detach screen
Code: [Select]
Ctr A Ctr D
Install python dependencies
Code: [Select]
sudo apt-get install python3-setuptools sudo easy_install3 pip sudo pip3 install autobahn sudo pip3 install requests
Clone and build python graphene api
Code: [Select]
cd ~ git clone https://github.com/xeroc/python-graphenelib.git cd python* python3 setup.py install --user
Edit the flood script to configure your user

Code: [Select]
cd examples nano flood.py edit client.transfer("putyouruserhere exit save
Run the flood script
Code: [Select]
python3 flood.py
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 04, 2015, 02:47:51 pm: @betax: nice summary :)
Title: Re: Test Net for Advanced Users
Post by: betax on September 04, 2015, 02:58:38 pm: Quote from: xeroc on September 04, 2015, 02:47:51 pm
@betax: nice summary :)

you do the work.. I install and take notes ;)
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 04, 2015, 03:20:38 pm: witness lost connection
Code: [Select]
150520ms th_a application.cpp:500 get_blockchain_synop ] reference_point: 0000000000000000000000000000000000000000 number_of_blocks_after_reference_point: 0 result: ["000065b83e3d65a6cb6a68899b097d74dec01f05","0000a5b8499b89f1c7b0673b3bdf7fa92adb14d3","0000c5b8f361ee90850ddf75802f1672ff8c86a0","0000d5b85570d0422e4ad4c1ad13f361c6f464ce","0000ddb8028dc5146068837071d078c6ab12ec1f","0000e1b8ee015c5af5454b6749c8780fb21b626a","0000e3b84b50a30b086f3dfe10c14c57f87b0651","0000e4b8cabfb6ce6acbfa7dcff0ed42a69e8c23","0000e538ce0a9fdadf1b63e1889a3fc56e6fb5f9","0000e578065ea22796197c18c49653d7c057e7ae","0000e598f0097652f2038a60a4aa50c8c3d03a44","0000e5a8cedeb400c4c39380218087f0723e36d0","0000e5b065697016b88d9b1496b0e7701c5ecef4","0000e5b41632696f926b0ae2b02471e20a4711c0","0000e5b65e16b5dd65f2bfb2594ed105c440917a","0000e5b7915bd40faf619c8033500917be4a46f8","0000e5b809c38a7198be347bee54fbc90ba4c2bf"] 150538ms th_a application.cpp:391 handle_transaction ] Got transaction from network 150618ms th_a application.cpp:391 handle_transaction ] Got transaction from network 150672ms th_a application.cpp:391 handle_transaction ] Got transaction from network witness_node: /home/calabiyau/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Aborted (core dumped)
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 03:22:55 pm: Running xeroc's spam food.py my client (running on a different computer than the witness):

Code: [Select]
1058066ms th_a wallet.cpp:1574 sign_transaction ] Caught exception while broadcasting transaction with id 17fb6ef2ebb8dbbe3c8ff81416f1398889c152c6
Title: Re: Test Net for Advanced Users
Post by: puppies on September 04, 2015, 03:26:23 pm: Quote from: Riverhead on September 04, 2015, 03:22:55 pm

Running xeroc's spam food.py my client (running on a different computer than the witness):

Code: [Select]
1058066ms th_a wallet.cpp:1574 sign_transaction ] Caught exception while broadcasting transaction with id 17fb6ef2ebb8dbbe3c8ff81416f1398889c152c6

I got the same, turned out my witness node was full of errors pushing blocks.
Title: Re: Test Net for Advanced Users
Post by: betax on September 04, 2015, 03:26:42 pm: Quote from: Riverhead on September 04, 2015, 03:22:55 pm

Running xeroc's spam food.py my client (running on a different computer than the witness):

Code: [Select]
1058066ms th_a wallet.cpp:1574 sign_transaction ] Caught exception while broadcasting transaction with id 17fb6ef2ebb8dbbe3c8ff81416f1398889c152c6

Im running everything on the same server, and so far good. I have increased it to 30 tx.
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 04, 2015, 03:33:25 pm: Witness ID: 1.6.1063
Witness Acc: 1.2.14540

Some votes and CORE for "calabiyau" would help to join the party.......
Title: Re: Test Net for Advanced Users
Post by: betax on September 04, 2015, 03:39:36 pm: Strange look at the balances
Code: [Select]
unlocked >>> list_account_balances betaxtrade list_account_balances betaxtrade 403018.82583 CORE unlocked >>> list_account_balances betaxtrade list_account_balances betaxtrade 403018.82583 CORE unlocked >>> list_account_balances betaxtrade list_account_balances betaxtrade 403018.82583 CORE unlocked >>> list_account_balances betaxtrade list_account_balances betaxtrade 402391.87263 CORE unlocked >>> list_account_balances betaxtrade list_account_balances betaxtrade 402329.17731 CORE unlocked >>> list_account_balances betaxtrade list_account_balances betaxtrade 404711.59947 CORE unlocked >>> list_account_balances betaxtrade list_account_balances betaxtrade 404460.81819 CORE unlocked >>> list_account_balances betaxtrade list_account_balances betaxtrade 404439.91975 CORE unlocked >>> list_account_balances betaxtrade list_account_balances betaxtrade 404210.03691 CORE unlocked >>> list_account_balances betaxtrade list_account_balances betaxtrade 404210.03691 CORE unlocked >>> list_account_balances betaxtrade list_account_balances betaxtrade 404210.03691 CORE unlocked >>> list_account_balances betaxtrade list_account_balances betaxtrade 404419.02131 CORE
Title: Re: Test Net for Advanced Users
Post by: betax on September 04, 2015, 03:40:16 pm: Quote from: CalabiYau on September 04, 2015, 03:33:25 pm
Witness ID: 1.6.1063
Witness Acc: 1.2.14540

Some votes and CORE for "calabiyau" would help to join the party.......

ill flood you some and see if they arrive
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 03:58:08 pm: Quote from: betax on September 04, 2015, 03:40:16 pm
Quote from: CalabiYau on September 04, 2015, 03:33:25 pm
Witness ID: 1.6.1063
Witness Acc: 1.2.14540

Some votes and CORE for "calabiyau" would help to join the party.......

ill flood you some and see if they arrive

Flood some to riverhead too :D. I will flood them back.
Title: Re: Test Net for Advanced Users
Post by: betax on September 04, 2015, 04:09:38 pm: Quote from: Riverhead on September 04, 2015, 03:58:08 pm
Quote from: betax on September 04, 2015, 03:40:16 pm
Quote from: CalabiYau on September 04, 2015, 03:33:25 pm
Witness ID: 1.6.1063
Witness Acc: 1.2.14540

Some votes and CORE for "calabiyau" would help to join the party.......

ill flood you some and see if they arrive

Flood some to riverhead too :D. I will flood them back.

On their way.. im ok at the moment no need to flood back :)
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 04, 2015, 04:11:14 pm: I could use some CORE also, I'm all setup to flood. Just have a 0 balance

If you can, send to: delegate.xeldal

Thanks.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 04:20:53 pm: I see a flood loop developing :). My witness lost sync about an hour ago - will flood to you when I am back in sync.
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 04, 2015, 04:21:01 pm: Quote from: betax on September 04, 2015, 03:40:16 pm
Quote from: CalabiYau on September 04, 2015, 03:33:25 pm
Witness ID: 1.6.1063
Witness Acc: 1.2.14540

Some votes and CORE for "calabiyau" would help to join the party.......

ill flood you some and see if they arrive

Looking good, 0.02025 CORE from 2025 tx confirmed. Thank you !
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 04, 2015, 04:31:46 pm: Still not able to vote:
Code: [Select]
Insufficient Balance: calabiyau's balance of 0.02025 CORE is less than required 20.05761 CORE\n
CORE seems to be already a scarce resource :) - WORKING FOR CORE
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 04, 2015, 04:34:20 pm: ok guys .. my node (for stats.bitshares.eu) has crashed .. need to resync but am out of time ..
anyway .. today I rewrote most of the backend code so that you don't need to connect to the witness directly but to a more robust proxy node that reduces the amount of data ..
that will help the stats page to scale on heavy load (hopefully)
Title: Re: Test Net for Advanced Users
Post by: puppies on September 04, 2015, 04:43:50 pm: Quote from: CalabiYau on September 04, 2015, 04:31:46 pm
Still not able to vote:
Code: [Select]
Insufficient Balance: calabiyau's balance of 0.02025 CORE is less than required 20.05761 CORE\n
CORE seems to be already a scarce resource :) - WORKING FOR CORE
Sending you some now.
Title: Re: Test Net for Advanced Users
Post by: betax on September 04, 2015, 04:45:36 pm: Quote from: CalabiYau on September 04, 2015, 04:31:46 pm
Still not able to vote:
Code: [Select]
Insufficient Balance: calabiyau's balance of 0.02025 CORE is less than required 20.05761 CORE\n
CORE seems to be already a scarce resource :) - WORKING FOR CORE

flooding everyone who have asked now 10 each every 5 seconds
Title: Re: Test Net for Advanced Users
Post by: betax on September 04, 2015, 05:25:23 pm: I don't have any more... :( betaxtrade please
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 04, 2015, 05:38:05 pm: wallet lost sync
Code: [Select]
"head_block_num": 59289, "head_block_id": "0000e799c87dc7846ae96dc6f3a24dcf58f663a2", "head_block_age": "2 hours old", "next_maintenance_time": "2 hours ago", "chain_id": "ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3",
Thank you everybody for CORE, will see if they show up after resync.
Edit: All here :)
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 04, 2015, 06:06:14 pm: Quote from: betax on September 04, 2015, 05:25:23 pm
I don't have any more... :( betaxtrade please

The witness is in now - so I can send some....

edit:
Wallet already empty, default fees OMG:
Code: [Select]
2015-09-04T18:09:35 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:09:35 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:09:35 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:09:35 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:09:35 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:09:35 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:09:35 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:09:35 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:09:35 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:09:35 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:02:45 Transfer 1 CORE from puppies to calabiyau (Fee: 20 CORE) 2015-09-04T18:01:55 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:01:45 Transfer 1 CORE from puppies to calabiyau (Fee: 20 CORE) 2015-09-04T18:01:20 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:00:50 Transfer 1 CORE from puppies to calabiyau (Fee: 20 CORE) 2015-09-04T17:59:40 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T17:59:00 Transfer 1 CORE from puppies to calabiyau (Fee: 20 CORE) 2015-09-04T17:58:45 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE)
Title: Re: Test Net for Advanced Users
Post by: abit on September 04, 2015, 06:51:42 pm: Quote from: bitcard on September 04, 2015, 02:12:10 pm
how to set witness-id? I set the witness-id = "1.6.5" in config.ini, is it ok?
I get the follow info:
379000ms th_a witness.cpp:179 block_production_loo ] Not producing block because it isn't my turn
379000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375579000817 next_second: 2015-09-04T14:06:20
380000ms th_a witness.cpp:194 block_production_loo ] Not producing block because the last block was generated by the same witness.
This node is probably disconnected from the network so block production has been disabled.
Disable this check with --allow-consecutive option.
380000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375580000857 next_second: 2015-09-04T14:06:21
381000ms th_a witness.cpp:191 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
381000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375581000983 next_second: 2015-09-04T14:06:22
382000ms th_a witness.cpp:191 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
382000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375582000927 next_second: 2015-09-04T14:06:23
383000ms th_a witness.cpp:191 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
383000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375583000805 next_second: 2015-09-04T14:06:24
384000ms th_a witness.cpp:191 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
384000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375584000792 next_second: 2015-09-04T14:06:25
385000ms th_a witness.cpp:179 block_production_loo ] Not producing block because it isn't my turn

what's wrong with it?
Looks like you're on a minor fork.
Try resync, and don't start with parameter '--enable-stale-production'
Title: Re: Test Net for Advanced Users
Post by: Fox on September 04, 2015, 07:45:00 pm: Polite request for some CORE to continue testing.

Thanks in advance!

Account name "fox"
Title: Re: Test Net for Advanced Users
Post by: puppies on September 04, 2015, 08:58:59 pm: Quote from: Fox on September 04, 2015, 07:45:00 pm
Polite request for some CORE to continue testing.

Thanks in advance!

Account name "fox"
sent you 20k. I am pretty low as well.

My home node lost sync three times during testing requiring a resync. My witness node lost sync once as well. Is the reason for these issues already known? If not what would be the best way to help figure this out. It seems to be happening mainly during stress testing. We could have another stress test. I think that using the IRC channel might be a better way of organizing it than the mumble server. We should plan it out so that we can ensure that everyone has a decent chunk of CORE for testing purposes and has xerocs script set up. We should also wait til xeroc has his stats.bitshares.eu site back up for benchmarking. What does everyone else think?
Title: Re: Test Net for Advanced Users
Post by: Fox on September 04, 2015, 09:02:51 pm: Quote from: puppies on September 04, 2015, 08:58:59 pm
Quote from: Fox on September 04, 2015, 07:45:00 pm
Polite request for some CORE to continue testing.

Thanks in advance!

Account name "fox"
sent you 20k. I am pretty low as well.
Most appreciated! Putting them to good use shortly...
Title: Re: Test Net for Advanced Users
Post by: abit on September 04, 2015, 09:16:49 pm: Quote from: puppies on September 04, 2015, 08:58:59 pm
Quote from: Fox on September 04, 2015, 07:45:00 pm
Polite request for some CORE to continue testing.

Thanks in advance!

Account name "fox"
sent you 20k. I am pretty low as well.

My home node lost sync three times during testing requiring a resync. My witness node lost sync once as well. Is the reason for these issues already known? If not what would be the best way to help figure this out. It seems to be happening mainly during stress testing.
Me too about the sync status. Looks like it's caused by a few (different) reasons. I posted all my related logs to the issues page on Github. You can check your log files.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 09:23:32 pm: So a couple people have said they are sending me CORE via flood scripts or otherwise. I haven't received any since I ran out of my original funds. If it's the case that no one has sent CORE to riverhead that's cool but I just want to make sure it wasn't sent and not received.

My witness node is sync'd and seems to be on the active node. Anyone else having trouble receiving funds?
Title: Re: Test Net for Advanced Users
Post by: puppies on September 04, 2015, 09:25:10 pm: Quote from: Riverhead on September 04, 2015, 09:23:32 pm

So a couple people have said they are sending me CORE via flood scripts or otherwise. I haven't received any since I ran out of my original funds. If it's the case that no one has sent CORE to riverhead that's cool but I just want to make sure it wasn't sent and not received.

My witness node is sync'd and seems to be on the active node. Anyone else having trouble receiving funds?
check now.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 09:26:21 pm: Quote from: puppies on September 04, 2015, 09:25:10 pm
Quote from: Riverhead on September 04, 2015, 09:23:32 pm

So a couple people have said they are sending me CORE via flood scripts or otherwise. I haven't received any since I ran out of my original funds. If it's the case that no one has sent CORE to riverhead that's cool but I just want to make sure it wasn't sent and not received.

My witness node is sync'd and seems to be on the active node. Anyone else having trouble receiving funds?
check now.

That worked :D. I'll flood them back to you via Xeroc's script.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 04, 2015, 09:28:59 pm: The vast majority will be eaten as fees.
Code: [Select]
unlocked >>> get_object 2.6.63354 get_object 2.6.63354 [{ "id": "2.6.63354", "owner": "1.2.63354", "most_recent_op": "2.9.164629", "total_core_in_orders": 0, "lifetime_fees_paid": "105566827099", "pending_fees": 0, "pending_vested_fees": 0 } ] unlocked >>>
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 04, 2015, 09:33:42 pm: Ya. And my witness got knocked off sync in the process. Client now showing two minutes behind.

Quote from: puppies on September 04, 2015, 09:28:59 pm
The vast majority will be eaten as fees.
Code: [Select]
unlocked >>> get_object 2.6.63354 get_object 2.6.63354 [{ "id": "2.6.63354", "owner": "1.2.63354", "most_recent_op": "2.9.164629", "total_core_in_orders": 0, "lifetime_fees_paid": "105566827099", "pending_fees": 0, "pending_vested_fees": 0 } ] unlocked >>>
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 04, 2015, 10:14:39 pm: I am working on a solution for getting knocked out of sync. Syncing issues will be a thing of the past ;)
Title: Re: Test Net for Advanced Users
Post by: bitcard on September 05, 2015, 01:37:58 am: thanks a lot, I will resync it , It seems that joining the testnet and become active witnees need one bts 0.9 account valued 120$, is't true?

Quote from: abit on September 04, 2015, 06:51:42 pm
Quote from: bitcard on September 04, 2015, 02:12:10 pm
how to set witness-id? I set the witness-id = "1.6.5" in config.ini, is it ok?
I get the follow info:
379000ms th_a witness.cpp:179 block_production_loo ] Not producing block because it isn't my turn
379000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375579000817 next_second: 2015-09-04T14:06:20
380000ms th_a witness.cpp:194 block_production_loo ] Not producing block because the last block was generated by the same witness.
This node is probably disconnected from the network so block production has been disabled.
Disable this check with --allow-consecutive option.
380000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375580000857 next_second: 2015-09-04T14:06:21
381000ms th_a witness.cpp:191 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
381000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375581000983 next_second: 2015-09-04T14:06:22
382000ms th_a witness.cpp:191 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
382000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375582000927 next_second: 2015-09-04T14:06:23
383000ms th_a witness.cpp:191 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
383000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375583000805 next_second: 2015-09-04T14:06:24
384000ms th_a witness.cpp:191 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
384000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441375584000792 next_second: 2015-09-04T14:06:25
385000ms th_a witness.cpp:179 block_production_loo ] Not producing block because it isn't my turn

what's wrong with it?
Looks like you're on a minor fork.
Try resync, and don't start with parameter '--enable-stale-production'
Title: Re: Test Net for Advanced Users
Post by: cube on September 05, 2015, 02:35:13 am: Quote from: cube on September 04, 2015, 01:57:56 pm
Quote from: Riverhead on September 04, 2015, 12:35:17 pm

The only other thing I can think of is in the witness config.ini file there is a parameter called enable-stale-production which needs to be false. I think that's the default now so that's probably not the issue.

I removed 'enable-stale-production' and restarted after a full blockchain resynced. I am still not in the active list. Any idea?

I am still stuck out of the active list. Can anyone help?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 05, 2015, 03:12:33 am: My VPS is dead :(
Thanks to a pile of transactions? :D
Title: Re: Test Net for Advanced Users
Post by: Fox on September 05, 2015, 03:20:00 am: Quote from: clayop on September 05, 2015, 03:12:33 am
My VPS is dead :(
Thanks to a pile of transactions? :D
What are the specs of your VPS? I'm interested to learn what is the bottleneck: RAM, disk IOPS, network I/O, CPU.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 05, 2015, 03:27:30 am: Quote from: Fox on September 05, 2015, 03:20:00 am
Quote from: clayop on September 05, 2015, 03:12:33 am
My VPS is dead :(
Thanks to a pile of transactions? :D
What are the specs of your VPS? I'm interested to learn what is the bottleneck: RAM, disk IOPS, network I/O, CPU.

AFAIK,

Google Computing Engine
Machine type n1-standard-1 (1 vCPU, 3.75 GB memory)
CPU platform Intel Ivy Bridge
Zone asia-east1-c

~~I'm not sure it's because bottleneck or lack of disk space~~

Edit: Ah disk is full.
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 05, 2015, 05:32:04 am: Some 8 hours ago, the node had to be resynced two times.

A nice surprise this morning - witness still up & synced !

With fees so high & supply so low, ammunition for stress testing is very limited.
Can we tweak the fees ?
Title: Re: Test Net for Advanced Users
Post by: betax on September 05, 2015, 05:32:51 am: Quote from: Riverhead on September 04, 2015, 09:23:32 pm

So a couple people have said they are sending me CORE via flood scripts or otherwise. I haven't received any since I ran out of my original funds. If it's the case that no one has sent CORE to riverhead that's cool but I just want to make sure it wasn't sent and not received.

My witness node is sync'd and seems to be on the active node. Anyone else having trouble receiving funds?

I sent (flood) you lots yesterday, did you get any?
Title: Re: Test Net for Advanced Users
Post by: betax on September 05, 2015, 05:57:21 am: Quote from: betax on September 05, 2015, 05:32:51 am
Quote from: Riverhead on September 04, 2015, 09:23:32 pm

So a couple people have said they are sending me CORE via flood scripts or otherwise. I haven't received any since I ran out of my original funds. If it's the case that no one has sent CORE to riverhead that's cool but I just want to make sure it wasn't sent and not received.

My witness node is sync'd and seems to be on the active node. Anyone else having trouble receiving funds?

I sent (flood) you lots yesterday, did you get any?

| guess you did i got lots back, i am again up and running flooding to riverhead, xeldal and calabiyau if anybody wants to a be added in the loop, let me know before i ran out leave for the weekend
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 05, 2015, 07:15:27 am: Quote from: betax on September 05, 2015, 05:57:21 am
Quote from: betax on September 05, 2015, 05:32:51 am
Quote from: Riverhead on September 04, 2015, 09:23:32 pm

So a couple people have said they are sending me CORE via flood scripts or otherwise. I haven't received any since I ran out of my original funds. If it's the case that no one has sent CORE to riverhead that's cool but I just want to make sure it wasn't sent and not received.

My witness node is sync'd and seems to be on the active node. Anyone else having trouble receiving funds?

I sent (flood) you lots yesterday, did you get any?

| guess you did i got lots back, i am again up and running flooding to riverhead, xeldal and calabiyau if anybody wants to a be added in the loop, let me know before i ran out leave for the weekend

Thank you, receiving:
Code: [Select]
2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE) 2015-09-05T07:03:30 Transfer 0.00001 CORE from betaxtrade to calabiyau -- Memo: memo (Fee: 20.89843 CORE)So I wait for the > 2 Mio tx to be completed to make 1 tx myself ;)
Title: Re: Test Net for Advanced Users
Post by: puppies on September 05, 2015, 07:59:28 am: You should have a lower fee if you don't use a memo. Just use "" instead. At least I think you will have a lower fee.
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 05, 2015, 10:21:41 am: Quote from: puppies on September 05, 2015, 07:59:28 am
You should have a lower fee if you don't use a memo. Just use "" instead. At least I think you will have a lower fee.

You are right, the fee seems to be lower by 0.89843 CORE /tx
Code: [Select]
2015-09-04T18:09:35 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:09:35 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE) 2015-09-04T18:09:35 Transfer 0.05000 CORE from calabiyau to betaxtrade (Fee: 20 CORE)
It would be great if someone can send me some CORE - I send them (-Fee) back of course - thank you.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 06, 2015, 01:02:22 am: Looks like my witness got out of sync and then crashed. Here is the back trace. Let me know if anything else such as logs would be helpful
Code: [Select]
{} th_a fork_database.cpp:194 fetch_branch_from {"first":"00012d7030b8d0cf678b14e3b34dec6158526249","second":"000123cd9d50e68bef1f464076ac87fd23b78bb9"} th_a fork_database.cpp:225 fetch_branch_from {"new_block":{"previous":"00012d6f566077aab18d0405083fbc54d8ea8f00","timestamp":"2015-09-05T22:44:35","witness":"1.6.18","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f18adf004de72f4ef5aa51f8cfe25eac90fd4514684576e3ed225f4f2f4a508e3463f452e5d9d7dca7870819c94d6f4a77cac3f37a24da73198101ba43244af02","transactions":[]}} th_a db_block.cpp:176 _push_block witness_node: /home/user/src/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Program received signal SIGABRT, Aborted. 0x00007ffff6c01cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ffff6c01cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007ffff6c050d8 in __GI_abort () at abort.c:89 #2 0x00007ffff6bfab86 in __assert_fail_base (fmt=0x7ffff6d4b830 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x2a7d2c8 "std::current_exception() == std::exception_ptr()", file=file@entry=0x2a7d1a8 "/home/user/src/graphene/libraries/fc/src/thread/thread_d.hpp", line=line@entry=370, function=function@entry=0x2a7df80 <fc::thread_d::start_next_fiber(bool)::__PRETTY_FUNCTION__> "bool fc::thread_d::start_next_fiber(bool)") at assert.c:92 #3 0x00007ffff6bfac32 in __GI___assert_fail (assertion=0x2a7d2c8 "std::current_exception() == std::exception_ptr()", file=0x2a7d1a8 "/home/user/src/graphene/libraries/fc/src/thread/thread_d.hpp", line=370, function=0x2a7df80 <fc::thread_d::start_next_fiber(bool)::__PRETTY_FUNCTION__> "bool fc::thread_d::start_next_fiber(bool)") at assert.c:101 #4 0x000000000252efbf in fc::thread_d::start_next_fiber(bool) () #5 0x0000000002528c2d in fc::thread::yield(bool) () #6 0x000000000252989a in fc::yield() () #7 0x000000000253c3ed in fc::spin_yield_lock::lock() () #8 0x000000000253ad74 in fc::unique_lock<fc::spin_yield_lock&>::lock() () #9 0x000000000253ac8f in fc::unique_lock<fc::spin_yield_lock&>::unique_lock(fc::spin_yield_lock&) () #10 0x000000000253aa96 in fc::promise_base::_set_value(void const*) () #11 0x000000000253a360 in fc::promise_base::set_exception(std::shared_ptr<fc::exception> const&) () #12 0x000000000253b627 in fc::task_base::run_impl() () #13 0x000000000253b114 in fc::task_base::run() () #14 0x000000000252fb34 in fc::thread_d::run_next_task() () #15 0x000000000252ffd8 in fc::thread_d::process_tasks() () #16 0x000000000252f64b in fc::thread_d::start_process_tasks(long) () #17 0x000000000288b571 in make_fcontext () #18 0x0000000000000000 in ?? () (gdb)
Title: Re: Test Net for Advanced Users
Post by: alt on September 06, 2015, 04:33:42 am: Quote from: bytemaster on September 04, 2015, 10:14:39 pm
I am working on a solution for getting knocked out of sync. Syncing issues will be a thing of the past ;)
+5%
Title: Re: Test Net for Advanced Users
Post by: cass on September 06, 2015, 02:28:34 pm: For me the How to become a witness link seems not to be working …

How to become a witness (https://github.com/cryptonomex/graphene/wiki/How%20to%20become%20an%20active%20witness%20in%20BitShares%202.0)

this should work…
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 06, 2015, 02:43:50 pm: Apologies for the missed test-net blocks.

I put it down to anti-social school boy errors.

My p2p-endpoint was set to 127.0.0.1 . Also my VPS and home network Firewall was locked down.

#VPS
witness ihashfury "id": "1.6.2562"
witness delegate.ihashfury "id": "1.6.1596"

#Home Cubox (arm)
perky "id": "1.6.3706"

All producing blocks again :)
Title: Re: Test Net for Advanced Users
Post by: clayop on September 07, 2015, 12:52:25 am: Maybe I'm in a fork. Will resync soon.

Code: [Select]
3080422ms th_a application.cpp:356 handle_block ] Got block #92762 f rom network 3080422ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num < _head->num + MAX_BLOCK_REORDERING: {} th_a fork_database.cpp:70 _push_block {"new_block":{"previous":"00016a59c15917da032053a4df45edfa7171af68","timestamp":"2015-09 -07T00:51:20","witness":"1.6.89","transaction_merkle_root":"00000000000000000000000000000000 00000000","extensions":[],"witness_signature":"1f656d75f66d9dea393c463d259e0abbc2fa5a22bf8b1 3292e49335397a88df9180f36314007fb1738622112d4e24770a07c32e4a6decb691b3286d88d22299858","tran sactions":[]}} th_a db_block.cpp:176 _push_block
Title: Re: Test Net for Advanced Users
Post by: cass on September 07, 2015, 02:05:04 am: hey .. .could somebody send my 10k CORE for upgrading my testnet account ? I will pay all back for sure..

My 2.0 account to send to: graphene

I've transfered approx. 50k BTS before 2 weeks and using 31aug snapshot ..
but when importing balance key and owner key ... i'm getting just 0.5 CORE claimed .. idk why ..

At current state would you import your complete wallet into testnet chain? jsut curious…
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 07, 2015, 02:07:05 am: Is there a way to claim witness pay yet? It would help to fund testing :).

get_object "1.13.178"
[{
"id": "1.13.178",
"owner": "1.2.67159",
"balance": {
"amount": 437000000,
"asset_id": "1.3.0"
Title: Re: Test Net for Advanced Users
Post by: Fox on September 07, 2015, 02:16:17 am: Quote from: cass on September 07, 2015, 02:05:04 am
hey .. .could somebody send my 10k CORE for upgrading my testnet account ? I will pay all back for sure..

My 2.0 account to send to: graphene

10k CORE sent
Title: Re: Test Net for Advanced Users
Post by: cass on September 07, 2015, 02:20:28 am: Quote from: Fox on September 07, 2015, 02:16:17 am
Quote from: cass on September 07, 2015, 02:05:04 am
hey .. .could somebody send my 10k CORE for upgrading my testnet account ? I will pay all back for sure..

My 2.0 account to send to: graphene

10k CORE sent

wow that was fast :) thx
Title: Re: Test Net for Advanced Users
Post by: clayop on September 07, 2015, 03:30:57 am: FYI: Resyncing 94000 blocks takes about 8 min (3.75 memory, no SSD) without any performance lags.
Title: Re: Test Net for Advanced Users
Post by: jsidhu on September 07, 2015, 04:36:43 am: Quote from: clayop on September 07, 2015, 03:30:57 am
FYI: Resyncing 94000 blocks takes about 8 min (3.75 memory, no SSD) without any performance lags.
So if 1 second blocks it will take about 8 mins to sync each day or 2 days to sync each year?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 07, 2015, 04:48:11 am: Quote from: jsidhu on September 07, 2015, 04:36:43 am
Quote from: clayop on September 07, 2015, 03:30:57 am
FYI: Resyncing 94000 blocks takes about 8 min (3.75 memory, no SSD) without any performance lags.
So if 1 second blocks it will take about 8 mins to sync each day or 2 days to sync each year?

I think it will take less because this testnet already have considerable amount of spam transactions
Title: Re: Test Net for Advanced Users
Post by: bulletproof on September 07, 2015, 09:36:16 am: Thanks to @clayop I now have an upgraded account I'd like to turn into a witness. Apparently I am 4,000 Core short of being able to create one - anyone be able to spare a few? :) Thx

Account: "e-v"
Title: Re: Test Net for Advanced Users
Post by: cass on September 07, 2015, 11:38:26 am: Quote from: bulletproof on September 07, 2015, 09:36:16 am
Thanks to @clayop I now have an upgraded account I'd like to turn into a witness. Apparently I am 4,000 Core short of being able to create one - anyone be able to spare a few? :) Thx

Account: "e-v"

yep same on my side ^^
Title: Re: Test Net for Advanced Users
Post by: betax on September 07, 2015, 11:45:12 am: I have ran out of CORE after the flooding... :(
Title: Re: Test Net for Advanced Users
Post by: cass on September 07, 2015, 11:50:30 am: Quote from: betax on September 07, 2015, 11:45:12 am
I have ran out of CORE after the flooding... :(

no worries ..
Title: Re: Test Net for Advanced Users
Post by: bulletproof on September 07, 2015, 11:56:02 am: Quote from: CalabiYau on September 05, 2015, 05:32:04 am
With fees so high & supply so low, ammunition for stress testing is very limited.
Can we tweak the fees ?

I guess we have a liquidity crunch until fees can be recycled :-\
Title: Re: Test Net for Advanced Users
Post by: Fox on September 07, 2015, 11:58:20 am: Quote from: cass on September 07, 2015, 11:38:26 am
Quote from: bulletproof on September 07, 2015, 09:36:16 am
Thanks to @clayop I now have an upgraded account I'd like to turn into a witness. Apparently I am 4,000 Core short of being able to create one - anyone be able to spare a few? :) Thx

Account: "e-v"

yep same on my side ^^

I've sent both graphene and e-v 4000 CORE for account registration.
Title: Re: Test Net for Advanced Users
Post by: cass on September 07, 2015, 11:59:38 am: Quote from: Fox on September 07, 2015, 11:58:20 am
Quote from: cass on September 07, 2015, 11:38:26 am
Quote from: bulletproof on September 07, 2015, 09:36:16 am
Thanks to @clayop I now have an upgraded account I'd like to turn into a witness. Apparently I am 4,000 Core short of being able to create one - anyone be able to spare a few? :) Thx

Account: "e-v"

yep same on my side ^^

I've sent both graphene and e-v 4000 CORE for account registration.

awesome again .. so i borrow you now 14k CORE .. thanks again @Fox
Title: Re: Test Net for Advanced Users
Post by: bulletproof on September 07, 2015, 12:07:41 pm: Quote from: Fox on September 07, 2015, 11:58:20 am
Quote from: cass on September 07, 2015, 11:38:26 am
Quote from: bulletproof on September 07, 2015, 09:36:16 am
Thanks to @clayop I now have an upgraded account I'd like to turn into a witness. Apparently I am 4,000 Core short of being able to create one - anyone be able to spare a few? :) Thx

Account: "e-v"

yep same on my side ^^

I've sent both graphene and e-v 4000 CORE for account registration.

You are a gent @Fox. IOU
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 07, 2015, 12:09:12 pm: Quote from: clayop on September 07, 2015, 04:48:11 am
Quote from: jsidhu on September 07, 2015, 04:36:43 am
Quote from: clayop on September 07, 2015, 03:30:57 am
FYI: Resyncing 94000 blocks takes about 8 min (3.75 memory, no SSD) without any performance lags.
So if 1 second blocks it will take about 8 mins to sync each day or 2 days to sync each year?

I think it will take less because this testnet already have considerable amount of spam transactions

What is slowing the test network down is updating the votes every 5 minutes rather than once per day combined with the flood transactions creating accounts. There are almost 100K accounts that get tallied every 5 minutes.
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 07, 2015, 01:34:54 pm: Quote from: betax on September 07, 2015, 11:45:12 am
I have ran out of CORE after the flooding... :(

me too....
Title: Re: Test Net for Advanced Users
Post by: spartako on September 07, 2015, 02:35:25 pm: I have 100K CORE for testing to give to 10 people (10K per person)

Tell me your nick and I will send to you at first ten people.
Title: Re: Test Net for Advanced Users
Post by: cass on September 07, 2015, 02:38:08 pm: thx

bts: graphene
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 07, 2015, 02:39:48 pm: Quote from: spartako on September 07, 2015, 02:35:25 pm
I have 100K CORE for testing to give to 10 people (10K per person)

Tell me your nick and I will send to you at first ten people.

That`s an offer :) "calabiyau" Thank you.
Title: Re: Test Net for Advanced Users
Post by: cass on September 07, 2015, 02:41:02 pm: just got it thx :)
Title: Re: Test Net for Advanced Users
Post by: spartako on September 07, 2015, 02:46:02 pm: Code: [Select]
unlocked >>> get_account_history spartako 2 get_account_history spartako 2 2015-09-07T14:41:05 Transfer 10000 CORE from spartako to calabiyau -- could not decrypt memo (Fee: 20.89843 CORE) 2015-09-07T14:39:50 Transfer 10000 CORE from spartako to graphene -- could not decrypt memo (Fee: 20.89843 CORE)
Is It ok that I am not able to see the memo value?
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 07, 2015, 02:52:39 pm: Quote from: spartako on September 07, 2015, 02:46:02 pm
Code: [Select]
unlocked >>> get_account_history spartako 2 get_account_history spartako 2 2015-09-07T14:41:05 Transfer 10000 CORE from spartako to calabiyau -- could not decrypt memo (Fee: 20.89843 CORE) 2015-09-07T14:39:50 Transfer 10000 CORE from spartako to graphene -- could not decrypt memo (Fee: 20.89843 CORE)
Is It ok that I am not able to see the memo value?

Code: [Select]
2015-09-07T14:41:05 Transfer 10000 CORE from spartako to calabiyau -- Memo: testing (Fee: 20.89843 CORE) ]
That`s how it looks like here - thx
Title: Re: Test Net for Advanced Users
Post by: spartako on September 07, 2015, 02:59:38 pm: Quote from: CalabiYau on September 07, 2015, 02:52:39 pm

Code: [Select]
2015-09-07T14:41:05 Transfer 10000 CORE from spartako to calabiyau -- Memo: testing (Fee: 20.89843 CORE) ]
That`s how it looks like here - thx

Ok, I think it is ok because the memo is encrypted with your public key and the only one able to decrypt is you because you have the private key.
Even if from a user experience prospective could be useful storing the memo value in my wallet so I can see me too the value with the history command.
Title: Re: Test Net for Advanced Users
Post by: cass on September 07, 2015, 03:04:48 pm: Code: [Select]
199164ms th_a thread.cpp:95 thread ] name:p2p tid:4535488512 199164ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 199199ms ntp ntp.cpp:81 request_now ] sending request to 213.136.0.252:123 199199ms th_a application.cpp:117 reset_p2p_node ] Adding seed node 104.236.118.105:1776 199200ms th_a application.cpp:129 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:51700 199202ms th_a application.cpp:179 reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090 199203ms th_a witness.cpp:117 plugin_startup ] witness plugin: plugin_startup() begin 199203ms th_a witness.cpp:124 plugin_startup ] Launching block production for 1 witnesses. 199203ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441638199203280 next_second: 2015-09-07T15:03:20 199203ms th_a witness.cpp:131 plugin_startup ] witness plugin: plugin_startup() end 199203ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks. 199203ms th_a main.cpp:166 main ] Chain ID is 57a6462f35bb7fe448d22b3a8b61dd67663bfdd00b4e4e969f0f5b502813b6c5 199313ms th_a api.cpp:40 database_api ] creating database api 4527827232 199314ms th_a api.cpp:40 database_api ] creating database api 4527828384 200000ms th_a witness.cpp:176 block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production) 200000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441638200000180 next_second: 2015-09-07T15:03:21 200574ms ntp ntp.cpp:147 read_loop ] received ntp reply from 213.136.0.252:123 200574ms ntp ntp.cpp:161 read_loop ] ntp offset: -670347, round_trip_delay 1375349 200575ms ntp ntp.cpp:166 read_loop ] received stale ntp reply requested at 2015-09-07T15:03:19, send a new time request 200575ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 200576ms ntp ntp.cpp:81 request_now ] sending request to 129.250.35.250:123 200601ms ntp ntp.cpp:147 read_loop ] received ntp reply from 129.250.35.250:123 200601ms ntp ntp.cpp:161 read_loop ] ntp offset: 3814, round_trip_delay 25671 200601ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 3814
hey when trying to start witness node after registered etc .. i'm getting this message .. do i'm anything wrong here?

my account: graphene should be registered as a witness now!
Title: Re: Test Net for Advanced Users
Post by: spartako on September 07, 2015, 03:19:26 pm: Quote from: cass on September 07, 2015, 03:04:48 pm
Code: [Select]
199164ms th_a thread.cpp:95 thread ] name:p2p tid:4535488512 199164ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 199199ms ntp ntp.cpp:81 request_now ] sending request to 213.136.0.252:123 199199ms th_a application.cpp:117 reset_p2p_node ] Adding seed node 104.236.118.105:1776 199200ms th_a application.cpp:129 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:51700 199202ms th_a application.cpp:179 reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090 199203ms th_a witness.cpp:117 plugin_startup ] witness plugin: plugin_startup() begin 199203ms th_a witness.cpp:124 plugin_startup ] Launching block production for 1 witnesses. 199203ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441638199203280 next_second: 2015-09-07T15:03:20 199203ms th_a witness.cpp:131 plugin_startup ] witness plugin: plugin_startup() end 199203ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks. 199203ms th_a main.cpp:166 main ] Chain ID is 57a6462f35bb7fe448d22b3a8b61dd67663bfdd00b4e4e969f0f5b502813b6c5 199313ms th_a api.cpp:40 database_api ] creating database api 4527827232 199314ms th_a api.cpp:40 database_api ] creating database api 4527828384 200000ms th_a witness.cpp:176 block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production) 200000ms th_a witness.cpp:146 schedule_production_ ] now.time_since_epoch().count(): 1441638200000180 next_second: 2015-09-07T15:03:21 200574ms ntp ntp.cpp:147 read_loop ] received ntp reply from 213.136.0.252:123 200574ms ntp ntp.cpp:161 read_loop ] ntp offset: -670347, round_trip_delay 1375349 200575ms ntp ntp.cpp:166 read_loop ] received stale ntp reply requested at 2015-09-07T15:03:19, send a new time request 200575ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] 200576ms ntp ntp.cpp:81 request_now ] sending request to 129.250.35.250:123 200601ms ntp ntp.cpp:147 read_loop ] received ntp reply from 129.250.35.250:123 200601ms ntp ntp.cpp:161 read_loop ] ntp offset: 3814, round_trip_delay 25671 200601ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 3814
hey when trying to start witness node after registered etc .. i'm getting this message .. do i'm anything wrong here?

graphene should be registered as a witness now!

You started your witness with the chain not in sync.
Usually I start the witness without the commands for creating blocks (--witness-id and --private-key params) then when I am in sync I stop and relaunch with params for creating blocks and you should see logs similar to this:

when you are not producing blocks:
Code: [Select]
923000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 923000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441638922998106 next_second: 2015-09-07T15:15:24 924000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 924001ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441638923999016 next_second: 2015-09-07T15:15:25 925000ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn 925000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441638924998096 next_second: 2015-09-07T15:15:26 925122ms th_a application.cpp:356 handle_block ] Got block #101560 from network 926000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 926001ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441638925998416 next_second: 2015-09-07T15:15:27
When you produce a block:
Code: [Select]
999000ms th_a witness.cpp:223 block_production_loo ] Not producing block because slot has not yet arrived 999000ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441638998998117 next_second: 2015-09-07T15:16:40 1000004ms th_a witness.cpp:214 block_production_loo ] Generated block #{"n":101574,"t":"2015-09-07T15:16:40","c":"2015-09-07T15:16:40"} with timestamp {"n":101574,"t":"2 015-09-07T15:16:40","c":"2015-09-07T15:16:40"} at time {"n":101574,"t":"2015-09-07T15:16:40","c":"2015-09-07T15:16:40"} 1000004ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1441639000001898 next_second: 2015-09-07T15:16:41
Title: Re: Test Net for Advanced Users
Post by: betax on September 07, 2015, 03:20:40 pm: You need to be synced before you can produce blocks. It normally (all the time for me) requires a restart.

Also make sure you have ntp intalled

Code: [Select]
apt-get install ntp
Title: Re: Test Net for Advanced Users
Post by: spartako on September 07, 2015, 04:27:24 pm: I will not available for some hours, so I will send CORE when I back at home.

Moreover I'm creating a nodejs library for graphene:
https://github.com/spartako82/node-graphene

I have two command now (see the README in github for usage):

* lastBlocks.js -> see the last blocks with delegate name and number of tx x block
* flood.js -> spam the network creating new accounts

It is very new code and it could have some bugs but feel free to try ;)
Title: Re: Test Net for Advanced Users
Post by: bulletproof on September 07, 2015, 04:39:00 pm: Almost there with my witness - just having trouble finding/adding my witness private key. My witness signing key (starting GPH5..) isn't listed in array output from:

Code: [Select]
dump_private_keys [[ "GPH6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxV", "5xxx<private>" ],[ "GPH6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj", "5xxx<private>" ],[ "GPH7xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa", "5xxx<private>" ] ]
Is this simply because I don't have any/enough votes yet?

Code: [Select]
get_witness "e-v" { "id": "1.6.5249", "witness_account": "1.2.25428", "last_aslot": 0, "signing_key": "GPH5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxX", "vote_id": "1:5465", "total_votes": 0, "url": "url-to-proposal" }
If so I'd be grateful for some, as I'd like to see if my witness can sign blocks on the AWS free-tier VPS - all running fine on 1GB RAM so far :)
Title: Re: Test Net for Advanced Users
Post by: clayop on September 07, 2015, 05:18:29 pm: Quote from: bulletproof on September 07, 2015, 04:39:00 pm
Almost there with my witness - just having trouble finding/adding my witness private key. My witness signing key (starting GPH5..) isn't listed in array output from:

Code: [Select]
dump_private_keys [[ "GPH6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxV", "5xxx<private>" ],[ "GPH6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj", "5xxx<private>" ],[ "GPH7xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa", "5xxx<private>" ] ]
Is this simply because I don't have any/enough votes yet?

Code: [Select]
get_witness "e-v" { "id": "1.6.5249", "witness_account": "1.2.25428", "last_aslot": 0, "signing_key": "GPH5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxX", "vote_id": "1:5465", "total_votes": 0, "url": "url-to-proposal" }
If so I'd be grateful for some, as I'd like to see if my witness can sign blocks on the AWS free-tier VPS - all running fine on 1GB RAM so far :)

I think you need at least 1 vote.
Title: Re: Test Net for Advanced Users
Post by: abit on September 07, 2015, 07:12:40 pm: Quote from: bulletproof on September 07, 2015, 04:39:00 pm
Almost there with my witness - just having trouble finding/adding my witness private key. My witness signing key (starting GPH5..) isn't listed in array output from:

Code: [Select]
dump_private_keys [[ "GPH6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxV", "5xxx<private>" ],[ "GPH6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj", "5xxx<private>" ],[ "GPH7xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa", "5xxx<private>" ] ]
Is this simply because I don't have any/enough votes yet?

Code: [Select]
get_witness "e-v" { "id": "1.6.5249", "witness_account": "1.2.25428", "last_aslot": 0, "signing_key": "GPH5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxX", "vote_id": "1:5465", "total_votes": 0, "url": "url-to-proposal" }
If so I'd be grateful for some, as I'd like to see if my witness can sign blocks on the AWS free-tier VPS - all running fine on 1GB RAM so far :)
Voted in.
But I think there is a bug which caused the lost of your signing key. Maybe this issue https://github.com/cryptonomex/graphene/issues/259
I can't find my signing key as well when I re-unlock the wallet. Fortunately I copied it out when I created my witness at first.
Title: Re: Test Net for Advanced Users
Post by: bulletproof on September 07, 2015, 07:24:13 pm: Thanks @abit, it is still not showing up so maybe you are right, I'll watch that issue. Sadly I didn't have the foresight to copy it down :-\

As there isn't a destroy_witness command I guess I'd have to start with a new account to generate a new witness - not sure I can face that right now!

Many thanks for your help anyhow
Title: Re: Test Net for Advanced Users
Post by: abit on September 07, 2015, 07:38:46 pm: Quote from: bulletproof on September 07, 2015, 07:24:13 pm
Thanks @abit, it is still not showing up so maybe you are right, I'll watch that issue. Sadly I didn't have the foresight to copy it down :-\

As there isn't a destroy_witness command I guess I'd have to start with a new account to generate a new witness - not sure I can face that right now!

Many thanks for your help anyhow
I'd like to suggest that you could try start a new chain or maybe a new witness_node (don't sync with current network) and create the witness again, maybe you'll get the keys. I noticed that my keys are same every time in the past 4 test networks.
Title: Re: Test Net for Advanced Users
Post by: bulletproof on September 07, 2015, 07:44:30 pm: Quote from: abit on September 07, 2015, 07:38:46 pm
Quote from: bulletproof on September 07, 2015, 07:24:13 pm
Thanks @abit, it is still not showing up so maybe you are right, I'll watch that issue. Sadly I didn't have the foresight to copy it down :-\

As there isn't a destroy_witness command I guess I'd have to start with a new account to generate a new witness - not sure I can face that right now!

Many thanks for your help anyhow
I'd like to suggest that you could try start a new chain or maybe a new witness_node (don't sync with current network) and create the witness again, maybe you'll get the keys. I noticed that my keys are same every time in the past 4 test networks.

Good plan, will try that
Title: Re: Test Net for Advanced Users
Post by: abit on September 07, 2015, 07:51:55 pm: Quote from: Riverhead on September 07, 2015, 02:07:05 am

Is there a way to claim witness pay yet? It would help to fund testing :).

get_object "1.13.178"
[{
"id": "1.13.178",
"owner": "1.2.67159",
"balance": {
"amount": 437000000,
"asset_id": "1.3.0"

Yes, commands here:
Code: [Select]
get_vesting_balances in.abit withdraw_vesting in.abit 100 CORE true
I think you're allowed to withdraw 4370 CORE.
Title: Re: Test Net for Advanced Users
Post by: abit on September 07, 2015, 07:58:52 pm: Quote from: bulletproof on September 07, 2015, 07:44:30 pm
Quote from: abit on September 07, 2015, 07:38:46 pm
Quote from: bulletproof on September 07, 2015, 07:24:13 pm
Thanks @abit, it is still not showing up so maybe you are right, I'll watch that issue. Sadly I didn't have the foresight to copy it down :-\

As there isn't a destroy_witness command I guess I'd have to start with a new account to generate a new witness - not sure I can face that right now!

Many thanks for your help anyhow
I'd like to suggest that you could try start a new chain or maybe a new witness_node (don't sync with current network) and create the witness again, maybe you'll get the keys. I noticed that my keys are same every time in the past 4 test networks.

Good plan, will try that
Hmm maybe registering a new witness account is much easier.
Title: Re: Test Net for Advanced Users
Post by: Akado on September 07, 2015, 09:30:51 pm: If all testers could report please:
https://bitsharestalk.org/index.php/topic,18337.msg234782.html#msg234782
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 08, 2015, 12:15:59 am: I fixed some crashes with the RPC code today. In case anyone has experienced witness node crashes.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 08, 2015, 12:48:25 am: Quote from: bytemaster on September 08, 2015, 12:15:59 am
I fixed some crashes with the RPC code today. In case anyone has experienced witness node crashes.

Will we need a new test net or should this sync with current network?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 08, 2015, 04:34:26 am: Quote from: puppies on September 08, 2015, 12:48:25 am
Quote from: bytemaster on September 08, 2015, 12:15:59 am
I fixed some crashes with the RPC code today. In case anyone has experienced witness node crashes.

Will we need a new test net or should this sync with current network?

I think it is compatible, because I'm running on the latest commit version.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 08, 2015, 04:39:15 am: Quote from: clayop on September 08, 2015, 04:34:26 am
Quote from: puppies on September 08, 2015, 12:48:25 am
Quote from: bytemaster on September 08, 2015, 12:15:59 am
I fixed some crashes with the RPC code today. In case anyone has experienced witness node crashes.

Will we need a new test net or should this sync with current network?

I think it is compatible, because I'm running on the latest commit version.

Thanks clay. I'll build it now, and update all my nodes.
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 08, 2015, 06:00:19 am: Quote from: clayop on September 08, 2015, 04:34:26 am
Quote from: puppies on September 08, 2015, 12:48:25 am
Quote from: bytemaster on September 08, 2015, 12:15:59 am
I fixed some crashes with the RPC code today. In case anyone has experienced witness node crashes.

Will we need a new test net or should this sync with current network?

I think it is compatible, because I'm running on the latest commit version.
Same here
Title: Re: Test Net for Advanced Users
Post by: rnglab on September 08, 2015, 06:55:37 am: bitshares-argentina node is back with last commit version.

nathan seems to have only ~1900 CORE, not enough to vote me in.

Also getting this error when trying to import_balance from a pre snapshot balance key:

Code: [Select]
2838767ms th_a wallet.cpp:2805 import_balance ] balances: [] 10 assert_exception: Assert Exception operations.size() > 0: A transaction must have at least one operation {"trx":{"ref_block_num":0,"ref_block_prefix":0,"expiration":"1970-01-01T00:00:00","operations":[],"extensions":[]}} th_a transaction.cpp:51 validate {"name_or_id":"bitshares-argentina"} th_a wallet.cpp:2846 import_balance
Title: Re: Test Net for Advanced Users
Post by: puppies on September 08, 2015, 07:41:42 am: Quote from: rnglab on September 08, 2015, 06:55:37 am
bitshares-argentina node is back with last commit version.

nathan seems to have only ~1900 CORE, not enough to vote me in.

Also getting this error when trying to import_balance from a pre snapshot balance key:

Code: [Select]
2838767ms th_a wallet.cpp:2805 import_balance ] balances: [] 10 assert_exception: Assert Exception operations.size() > 0: A transaction must have at least one operation {"trx":{"ref_block_num":0,"ref_block_prefix":0,"expiration":"1970-01-01T00:00:00","operations":[],"extensions":[]}} th_a transaction.cpp:51 validate {"name_or_id":"bitshares-argentina"} th_a wallet.cpp:2846 import_balance
I have seen that error when attempting to claim a key that doesn't have any balance. It is not going to be your signing key or active key that has a balance associated with it.

If you can get the gui up and running it is far easier to import your balance from a json. You can automatically claim all balances.

I just upgrade the node with my balances on it. After it is done syncing I will vote your witness in.
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 08, 2015, 08:52:43 am: Quote from: rnglab on September 08, 2015, 06:55:37 am
bitshares-argentina node is back with last commit version.

nathan seems to have only ~1900 CORE, not enough to vote me in.

Also getting this error when trying to import_balance from a pre snapshot balance key:

Code: [Select]
2838767ms th_a wallet.cpp:2805 import_balance ] balances: [] 10 assert_exception: Assert Exception operations.size() > 0: A transaction must have at least one operation {"trx":{"ref_block_num":0,"ref_block_prefix":0,"expiration":"1970-01-01T00:00:00","operations":[],"extensions":[]}} th_a transaction.cpp:51 validate {"name_or_id":"bitshares-argentina"} th_a wallet.cpp:2846 import_balance

Voted you in:
Code: [Select]
get_witness bitshares-argentina { "id": "1.6.708", "witness_account": "1.2.8573", "last_aslot": 0, "signing_key": "GPH7B4bszRYW5SKGFUKuM6ta95MUR81ZsjUTyxLAn4Pezu5Ck9xsw", "vote_id": "1:707", "total_votes": 978271461, "url": "" } ]
Title: Re: Test Net for Advanced Users
Post by: puppies on September 08, 2015, 09:16:19 am: Quote from: abit on September 07, 2015, 07:51:55 pm
Quote from: Riverhead on September 07, 2015, 02:07:05 am

Is there a way to claim witness pay yet? It would help to fund testing :).

get_object "1.13.178"
[{
"id": "1.13.178",
"owner": "1.2.67159",
"balance": {
"amount": 437000000,
"asset_id": "1.3.0"

Yes, commands here:
Code: [Select]
get_vesting_balances in.abit withdraw_vesting in.abit 100 CORE true
I think you're allowed to withdraw 4370 CORE.
Nice catch abit.

You can also withdraw your fee refunds by calling the vesting balance object like this
Code: [Select]
unlocked >>> withdraw_vesting 1.13.173 23957 CORE true withdraw_vesting 1.13.173 23957 CORE true { "ref_block_num": 46692, "ref_block_prefix": 3121941031, "expiration": "2015-09-08T09:14:30", "operations": [[ 33,{ "fee": { "amount": 100000, "asset_id": "1.3.0" }, "vesting_balance": "1.13.173", "owner": "1.2.63354", "amount": { "amount": 2395700000, "asset_id": "1.3.0" } } ] ], "extensions": [], "signatures": [ "1f51a42c36cb50c3085808e14303d6e2edc407ef6d83f4d2524d438d10e4e5598818baccacf785f48f82ea8a8074975182eea23dd885ce7ac6088c2d219a19980a" ] }This will make having enough core to test much much easier.

If anyone needs CORE let me know.
Title: Re: Test Net for Advanced Users
Post by: abit on September 08, 2015, 10:06:56 am: Quote from: xeroc on September 08, 2015, 06:00:19 am
Quote from: clayop on September 08, 2015, 04:34:26 am
Quote from: puppies on September 08, 2015, 12:48:25 am
Quote from: bytemaster on September 08, 2015, 12:15:59 am
I fixed some crashes with the RPC code today. In case anyone has experienced witness node crashes.

Will we need a new test net or should this sync with current network?

I think it is compatible, because I'm running on the latest commit version.
Same here
Same here
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 08, 2015, 11:18:43 am: I have been running the latest master for 2 days - non stop
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 08, 2015, 10:00:31 pm: https://bitsharestalk.org/index.php/topic,18349.msg235091.html#msg235091

New protocol for witnesses to try to stay in sync vs P2P.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 08, 2015, 10:12:02 pm: I just saw some major spam, a block with over 100 transactions :) Good work. The Node JS code seemed to handle the spam well!
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 11, 2015, 05:10:56 pm: I've yet to see my witness produce a block.

Not sure what I'm doing wrong. The witness is all synced and it shows I've got votes but my ID is never listed under active witnesses and never produces anything. as far as I can tell.

Code: [Select]
get_witness delegate.xeldal { "id": "1.6.1625", "witness_account": "1.2.22412", "last_aslot": 61295, "signing_key": "G.................5", "pay_vb": "1.13.179", "vote_id": "1:1624", "total_votes": "89849588541", "url": "" }
Code: [Select]
"head_block_num": 156986, "head_block_id": "0002653a9daea9b627f0985b5f8f1061f3eb2afe", "head_block_age": "7 seconds old", "next_maintenance_time": "2 minutes in the future", "chain_id": "ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3", "active_witnesses": [
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 11, 2015, 07:10:32 pm: Quote from: Xeldal on September 11, 2015, 05:10:56 pm
I've yet to see my witness produce a block.

Not sure what I'm doing wrong. The witness is all synced and it shows I've got votes but my ID is never listed under active witnesses and never produces anything. as far as I can tell.

Code: [Select]
get_witness delegate.xeldal { "id": "1.6.1625", "witness_account": "1.2.22412", "last_aslot": 61295, "signing_key": "G.................5", "pay_vb": "1.13.179", "vote_id": "1:1624", "total_votes": "89849588541", "url": "" }
Code: [Select]
"head_block_num": 156986, "head_block_id": "0002653a9daea9b627f0985b5f8f1061f3eb2afe", "head_block_age": "7 seconds old", "next_maintenance_time": "2 minutes in the future", "chain_id": "ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3", "active_witnesses": [

You should be in soon.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 11, 2015, 09:59:32 pm: We just pushed some significant updates / improvements to the P2P code. Please upgrade if you can and see how they work for you.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 12, 2015, 12:07:08 am: I'm up running and producing blocks on the latest source.

I was having a hard time getting the cli wallet to run. Turns out I had an empty wallet.json file that was causing all the ruckus. I think it was an export from 0.9.2, as I had never saved a wallet on this box. Probably just an ID 10 T error on my part, but I figured I would mention it in case anyone else is having the same issue.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 12, 2015, 12:07:35 am: Updating in flight via gogo wifi. Witness ubiquitous 8)
Title: Re: Test Net for Advanced Users
Post by: puppies on September 12, 2015, 12:15:51 am: Quote from: clayop on September 12, 2015, 12:07:35 am
Updating in flight via gogo wifi. Witness ubiquitous 8)

World's first Mile high witness?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 12, 2015, 12:28:44 am: Quote from: puppies on September 12, 2015, 12:15:51 am
Quote from: clayop on September 12, 2015, 12:07:35 am
Updating in flight via gogo wifi. Witness ubiquitous 8)

World's first Mike high witness?

Altitude: 39,101 feet :)
Title: Re: Test Net for Advanced Users
Post by: abit on September 12, 2015, 03:22:22 pm: Running with the latest commit now. All work fine so far.
Will see if it's stable when next transaction flooding comes.
Title: Re: Test Net for Advanced Users
Post by: abit on September 12, 2015, 06:33:42 pm: Some warnings here. Any thought?
Code: [Select]
2015-09-12T18:10:33 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cp p:422 2015-09-12T18:10:33 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cp p:422 2015-09-12T18:10:33 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cp p:422 2015-09-12T18:10:36 th_a:invoke handle_block handle_block ] Got block #171686 from network application.cp p:383 2015-09-12T18:10:36 th_a:invoke handle_block push_block ] new_block.block_num(): 171686 new_block.id(): 00029ea6553cbe880a9e 0be95c9a0deaef46f1cf db_block.cpp:97 2015-09-12T18:10:36 th_a:invoke handle_block ~pending_transaction ] Pending transaction became invalid after switching to block 00029e a6553cbe880a9e0be95c9a0deaef46f1cf db_with.hpp:80 2015-09-12T18:10:36 th_a:invoke handle_block ~pending_transaction ] The invalid pending transaction is {"ref_block_num":40613,"ref_blo ck_prefix":4073857719,"expiration":"2015-09-12T18:11:00","operations":[[5,{"fee":{"amount":14648,"asset_id":"1.3.0"},"registrar":"1.2. 116","referrer":"1.2.116","referrer_percent":0,"name":"hello-test1","owner":{"weight_threshold":1,"account_auths":[],"key_auths":[["GP H7PuZQts1QJYkHzXvKA9hbZcww8o9xxmh2DNihXb9onb7jfPXv5",1]],"address_auths":[]},"active":{"weight_threshold":1,"account_auths":[],"key_au ths":[["GPH5BTF7xh1RzGB9vL8Rvk6kcNr5EC3cRBAC32yyqs5Pas56Gwubz",1]],"address_auths":[]},"options":{"memo_key":"GPH5BTF7xh1RzGB9vL8Rvk6k cNr5EC3cRBAC32yyqs5Pas56Gwubz","voting_account":"1.2.5","num_witness":0,"num_committee":0,"votes":[],"extensions":[]},"extensions":[]} ]],"extensions":[],"signatures":["1f35d7089c47caa4d3423b9779010495d8058e04ea6b5deeeac8aea9cc4e3d7720698e97dd6eb460ba9f7e8547f18f22173c fa4ee523bd1cca774f3c68c993d68d"],"operation_results":[[1,"1.2.97867"]]} db_with.hpp:81 2015-09-12T18:10:36 th_a:invoke handle_block ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name" :"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_appl y_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-12T18:10:36"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn", "file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-12T18:10:36"}," format":"","data":{"trx":{"ref_block_num":40613,"ref_block_prefix":4073857719,"expiration":"2015-09-12T18:11:00","operations":[[5,{"fe e":{"amount":14648,"asset_id":"1.3.0"},"registrar":"1.2.116","referrer":"1.2.116","referrer_percent":0,"name":"hello-test1","owner":{" weight_threshold":1,"account_auths":[],"key_auths":[["GPH7PuZQts1QJYkHzXvKA9hbZcww8o9xxmh2DNihXb9onb7jfPXv5",1]],"address_auths":[]}," active":{"weight_threshold":1,"account_auths":[],"key_auths":[["GPH5BTF7xh1RzGB9vL8Rvk6kcNr5EC3cRBAC32yyqs5Pas56Gwubz",1]],"address_au ths":[]},"options":{"memo_key":"GPH5BTF7xh1RzGB9vL8Rvk6kcNr5EC3cRBAC32yyqs5Pas56Gwubz","voting_account":"1.2.5","num_witness":0,"num_c ommittee":0,"votes":[],"extensions":[]},"extensions":[]}]],"extensions":[],"signatures":["1f35d7089c47caa4d3423b9779010495d8058e04ea6b 5deeeac8aea9cc4e3d7720698e97dd6eb460ba9f7e8547f18f22173cfa4ee523bd1cca774f3c68c993d68d"]}}},{"context":{"level":"warn","file":"db_bloc k.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-12T18:10:36"},"format":"","data" :{"trx":{"ref_block_num":40613,"ref_block_prefix":4073857719,"expiration":"2015-09-12T18:11:00","operations":[[5,{"fee":{"amount":1464 8,"asset_id":"1.3.0"},"registrar":"1.2.116","referrer":"1.2.116","referrer_percent":0,"name":"hello-test1","owner":{"weight_threshold" :1,"account_auths":[],"key_auths":[["GPH7PuZQts1QJYkHzXvKA9hbZcww8o9xxmh2DNihXb9onb7jfPXv5",1]],"address_auths":[]},"active":{"weight_ threshold":1,"account_auths":[],"key_auths":[["GPH5BTF7xh1RzGB9vL8Rvk6kcNr5EC3cRBAC32yyqs5Pas56Gwubz",1]],"address_auths":[]},"options ":{"memo_key":"GPH5BTF7xh1RzGB9vL8Rvk6kcNr5EC3cRBAC32yyqs5Pas56Gwubz","voting_account":"1.2.5","num_witness":0,"num_committee":0,"votes":[],"extensions":[]},"extensions":[]}]],"extensions":[],"signatures":["1f35d7089c47caa4d3423b9779010495d8058e04ea6b5deeeac8aea9cc4e3d7720698e97dd6eb460ba9f7e8547f18f22173cfa4ee523bd1cca774f3c68c993d68d"]}}}]} db_with.hpp:82 2015-09-12T18:10:45 th_a:invoke handle_block handle_block ] Got block #171687 from network application.cpp:383 2015-09-12T18:10:45 th_a:invoke handle_block push_block ] new_block.block_num(): 171687 new_block.id(): 00029ea7c3d673800f20efc331f42b4235cee25c db_block.cpp:97 2015-09-12T18:10:45 th_a:invoke handle_block ~pending_transaction ] Pending transaction became invalid after switching to block 00029ea7c3d673800f20efc331f42b4235cee25c db_with.hpp:80 2015-09-12T18:10:45 th_a:invoke handle_block ~pending_transaction ] The invalid pending transaction is {"ref_block_num":40613,"ref_block_prefix":4073857719,"expiration":"2015-09-12T18:11:00","operations":[[0,{"fee":{"amount":2105468,"asset_id":"1.3.0"},"from":"1.2.116","to":"1.2.97867","amount":{"amount":100000000,"asset_id":"1.3.0"},"memo":{"from":"GPH5WCj1mMiiqEE4QRs7xhaFfSaiFroejUp3GuZE9wvfue9nxhPPn","to":"GPH5BTF7xh1RzGB9vL8Rvk6kcNr5EC3cRBAC32yyqs5Pas56Gwubz","nonce":"18015840590915049172","message":"4df7d8d7d3392b82281fd353f4ac8edad7a5ec58328ff795838fe77850c4de69"},"extensions":[]}]],"extensions":[],"signatures":["1f3ee5eefd1a1e93be6ddb75b709a8fa1e90c817fdca7f01133c39a29f172cecae53db1bb034397985b33642839a5e1a088dbb55c635352f30cac1fb137b69497a"],"operation_results":[[0,{}]]} db_with.hpp:81 2015-09-12T18:10:45 th_a:invoke handle_block ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-12T18:10:45"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-12T18:10:45"},"format":"","data":{"trx":{"ref_block_num":40613,"ref_block_prefix":4073857719,"expiration":"2015-09-12T18:11:00","operations":[[0,{"fee":{"amount":2105468,"asset_id":"1.3.0"},"from":"1.2.116","to":"1.2.97867","amount":{"amount":100000000,"asset_id":"1.3.0"},"memo":{"from":"GPH5WCj1mMiiqEE4QRs7xhaFfSaiFroejUp3GuZE9wvfue9nxhPPn","to":"GPH5BTF7xh1RzGB9vL8Rvk6kcNr5EC3cRBAC32yyqs5Pas56Gwubz","nonce":"18015840590915049172","message":"4df7d8d7d3392b82281fd353f4ac8edad7a5ec58328ff795838fe77850c4de69"},"extensions":[]}]],"extensions":[],"signatures":["1f3ee5eefd1a1e93be6ddb75b709a8fa1e90c817fdca7f01133c39a29f172cecae53db1bb034397985b33642839a5e1a088dbb55c635352f30cac1fb137b69497a"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-12T18:10:45"},"format":"","data":{"trx":{"ref_block_num":40613,"ref_block_prefix":4073857719,"expiration":"2015-09-12T18:11:00","operations":[[0,{"fee":{"amount":2105468,"asset_id":"1.3.0"},"from":"1.2.116","to":"1.2.97867","amount":{"amount":100000000,"asset_id":"1.3.0"},"memo":{"from":"GPH5WCj1mMiiqEE4QRs7xhaFfSaiFroejUp3GuZE9wvfue9nxhPPn","to":"GPH5BTF7xh1RzGB9vL8Rvk6kcNr5EC3cRBAC32yyqs5Pas56Gwubz","nonce":"18015840590915049172","message":"4df7d8d7d3392b82281fd353f4ac8edad7a5ec58328ff795838fe77850c4de69"},"extensions":[]}]],"extensions":[],"signatures":["1f3ee5eefd1a1e93be6ddb75b709a8fa1e90c817fdca7f01133c39a29f172cecae53db1bb034397985b33642839a5e1a088dbb55c635352f30cac1fb137b69497a"]}}}]} db_with.hpp:82
Code: [Select]
2015-09-12T18:17:21 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cp p:422 2015-09-12T18:17:25 th_a:invoke handle_block handle_block ] Got block #171750 from network application.cp p:383 2015-09-12T18:17:25 th_a:invoke handle_block push_block ] new_block.block_num(): 171750 new_block.id(): 00029ee60757de7e83bd 50d871de89f73ae312fe db_block.cpp:97 2015-09-12T18:17:25 th_a:invoke handle_block ~pending_transaction ] Pending transaction became invalid after switching to block 00029ee60757de7e83bd50d871de89f73ae312fe db_with.hpp:80 2015-09-12T18:17:25 th_a:invoke handle_block ~pending_transaction ] The invalid pending transaction is {"ref_block_num":40676,"ref_block_prefix":3655628590,"expiration":"2015-09-12T18:29:50","operations":[[1,{"fee":{"amount":500000,"asset_id":"1.3.0"},"seller":"1.2.97867","amount_to_sell":{"amount":100000,"asset_id":"1.3.0"},"min_to_receive":{"amount":2900000,"asset_id":"1.3.325"},"expiration":"2020-09-12T18:19:00","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["1f1af6117c8f0857b1be1904b66c594e8ef29facc0307417c0e9c6bbb0bde829ad10d3642c14ff60af3cb222d1d3a89a9f12471d160900992f671509f04d928b4d"],"operation_results":[[1,"1.7.53"]]} db_with.hpp:81 2015-09-12T18:17:25 th_a:invoke handle_block ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-12T18:17:25"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-12T18:17:25"},"format":"","data":{"trx":{"ref_block_num":40676,"ref_block_prefix":3655628590,"expiration":"2015-09-12T18:29:50","operations":[[1,{"fee":{"amount":500000,"asset_id":"1.3.0"},"seller":"1.2.97867","amount_to_sell":{"amount":100000,"asset_id":"1.3.0"},"min_to_receive":{"amount":2900000,"asset_id":"1.3.325"},"expiration":"2020-09-12T18:19:00","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["1f1af6117c8f0857b1be1904b66c594e8ef29facc0307417c0e9c6bbb0bde829ad10d3642c14ff60af3cb222d1d3a89a9f12471d160900992f671509f04d928b4d"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-12T18:17:25"},"format":"","data":{"trx":{"ref_block_num":40676,"ref_block_prefix":3655628590,"expiration":"2015-09-12T18:29:50","operations":[[1,{"fee":{"amount":500000,"asset_id":"1.3.0"},"seller":"1.2.97867","amount_to_sell":{"amount":100000,"asset_id":"1.3.0"},"min_to_receive":{"amount":2900000,"asset_id":"1.3.325"},"expiration":"2020-09-12T18:19:00","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["1f1af6117c8f0857b1be1904b66c594e8ef29facc0307417c0e9c6bbb0bde829ad10d3642c14ff60af3cb222d1d3a89a9f12471d160900992f671509f04d928b4d"]}}}]} db_with.hpp:82
Title: Re: Test Net for Advanced Users
Post by: abit on September 13, 2015, 02:43:01 pm: Stuck at block 172074. Running with commit https://github.com/cryptonomex/graphene/commit/30ae8e4f3433d4ee500f0b98e30f05e1ebe806ea

Code: [Select]
2015-09-12T18:51:20 th_a:invoke handle_block handle_block ] Got block #172075 from network application.cp p:383 2015-09-12T18:51:20 th_a:invoke handle_block push_block ] new_block.block_num(): 172075 new_block.id(): 0002a02b392ec29a32bb de7460a81895ab5e4d39 db_block.cpp:97 2015-09-12T18:51:20 th_a:invoke handle_block _push_block ] Failed to push new block: 10 assert_exception: Assert Exception vbo.is_withdraw_allowed( now, op.amount ): {} th_a vesting_balance_evaluator.cpp:103 do_evaluate {"op":{"fee":{"amount":100000,"asset_id":"1.3.0"},"vesting_balance":"1.13.182","owner":"1.2.14540","amount":{"amount":28200000,"as set_id":"1.3.0"}}} th_a vesting_balance_evaluator.cpp:109 do_evaluate {} th_a evaluator.cpp:42 start_evaluate {} th_a db_block.cpp:580 apply_operation {"trx":{"ref_block_num":41002,"ref_block_prefix":1338163065,"expiration":"2015-09-12T18:51:45","operations":[[33,{"fee":{"amount":100000,"asset_id":"1.3.0"},"vesting_balance":"1.13.182","owner":"1.2.14540","amount":{"amount":28200000,"asset_id":"1.3.0"}}]],"extensions":[],"signatures":["1f48e31b530bf16c32b99809c509de9938f639c68bbb523819ecef3aa03d703c2d6cad44e48f56c8aaf091098022a2cd8a860f2e4cab1c16991221482317e14bee"]}} th_a db_block.cpp:563 _apply_transaction {"next_block.block_num()":172075} th_a db_block.cpp:468 _apply_block db_block.cpp:180 2015-09-12T18:51:20 th_a:invoke handle_block handle_block ] Error when pushing block: 10 assert_exception: Assert Exception vbo.is_withdraw_allowed( now, op.amount ): {} th_a vesting_balance_evaluator.cpp:103 do_evaluate {"op":{"fee":{"amount":100000,"asset_id":"1.3.0"},"vesting_balance":"1.13.182","owner":"1.2.14540","amount":{"amount":28200000,"asset_id":"1.3.0"}}} th_a vesting_balance_evaluator.cpp:109 do_evaluate {} th_a evaluator.cpp:42 start_evaluate {} th_a db_block.cpp:580 apply_operation {"trx":{"ref_block_num":41002,"ref_block_prefix":1338163065,"expiration":"2015-09-12T18:51:45","operations":[[33,{"fee":{"amount":100000,"asset_id":"1.3.0"},"vesting_balance":"1.13.182","owner":"1.2.14540","amount":{"amount":28200000,"asset_id":"1.3.0"}}]],"extensions":[],"signatures":["1f48e31b530bf16c32b99809c509de9938f639c68bbb523819ecef3aa03d703c2d6cad44e48f56c8aaf091098022a2cd8a860f2e4cab1c16991221482317e14bee"]}} th_a db_block.cpp:563 _apply_transaction {"next_block.block_num()":172075} th_a db_block.cpp:468 _apply_block {"new_block":{"previous":"0002a02a79bfc24fc1bcc0db170fb597260c44aa","timestamp":"2015-09-12T18:51:20","witness":"1.6.9","transaction_merkle_root":"eedebcfcebf08658829eaa863a420f0ac36d569e","extensions":[],"witness_signature":"1f767254f096a7223017f32c6e4ca81f0db4f981c37fe43de4f2605a4bf4015ecc2bf90dcb738dee71321d7b3de12dcb179ba7a41c8eb7e5a1333ae10dc1ec0bd9","transactions":[{"ref_block_num":41002,"ref_block_prefix":1338163065,"expiration":"2015-09-12T18:51:45","operations":[[33,{"fee":{"amount":100000,"asset_id":"1.3.0"},"vesting_balance":"1.13.182","owner":"1.2.14540","amount":{"amount":28200000,"asset_id":"1.3.0"}}]],"extensions":[],"signatures":["1f48e31b530bf16c32b99809c509de9938f639c68bbb523819ecef3aa03d703c2d6cad44e48f56c8aaf091098022a2cd8a860f2e4cab1c16991221482317e14bee"],"operation_results":[[0,{}]]}]}} th_a db_block.cpp:186 _push_block application.cpp:409
Title: Re: Test Net for Advanced Users
Post by: puppies on September 13, 2015, 10:45:42 pm: I am about to start some more spam tests. If anyone needs some CORE to join in let me know. I will also be in IRC if someone wants to chat more in real time.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 13, 2015, 10:50:22 pm: witness node stopped with the following error

Code: [Select]
3599870ms th_a application.cpp:422 handle_transaction ] Got transaction from network 1ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 172076 new_block.id(): 0002a02c211ed6b4ab4ab 41989d9f0007ad02fef witness_node: /home/clayop/graphene/libraries /chain/db_maint.cpp:333: void graphene::chain ::database::process_budget(): Assertion `time _to_maint > 0' failed. Aborted (core dumped)
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 13, 2015, 11:01:11 pm: Quote from: clayop on September 13, 2015, 10:50:22 pm
witness node stopped with the following error

Code: [Select]
3599870ms th_a application.cpp:422 handle_transaction ] Got transaction from network 1ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 172076 new_block.id(): 0002a02c211ed6b4ab4ab 41989d9f0007ad02fef witness_node: /home/clayop/graphene/libraries /chain/db_maint.cpp:333: void graphene::chain ::database::process_budget(): Assertion `time _to_maint > 0' failed. Aborted (core dumped)

Good catch... https://github.com/cryptonomex/graphene/issues/313
Title: Re: Test Net for Advanced Users
Post by: puppies on September 14, 2015, 01:26:37 am: My witness node died as well. Not sure if its the same error. I did manually delete the logs before I noticed my witness was not producing blocks anymore.
Code: [Select]
2539393ms th_a application.cpp:422 handle_transaction ] Got transaction from network 2539533ms th_a application.cpp:691 get_blockchain_synop ] synopsis: ["0002e05380b9755fa598eaebeb6891efa2e7414c","0002e0656d75d264c5df9bbb87a2734af7a05997","0002e06e437036d12b42b0a1fec25ff02ab73d3f","0002e0736b5f6526008a20e525a419614d794da4","0002e075dfb2ef879b32010a09c482f7d68e5181","0002e076f489de970f945b052badedc7028c58c0"] 2539559ms th_a application.cpp:422 handle_transaction ] Got transaction from network witness_node: /home/user/src/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Program received signal SIGABRT, Aborted. 0x00007ffff6c01cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ffff6c01cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007ffff6c050d8 in __GI_abort () at abort.c:89 #2 0x00007ffff6bfab86 in __assert_fail_base (fmt=0x7ffff6d4b830 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x2b72788 "std::current_exception() == std::exception_ptr()", file=file@entry=0x2b72668 "/home/user/src/graphene/libraries/fc/src/thread/thread_d.hpp", line=line@entry=370, function=function@entry=0x2b73440 <fc::thread_d::start_next_fiber(bool)::__PRETTY_FUNCTION__> "bool fc::thread_d::start_next_fiber(bool)") at assert.c:92 #3 0x00007ffff6bfac32 in __GI___assert_fail (assertion=0x2b72788 "std::current_exception() == std::exception_ptr()", file=0x2b72668 "/home/user/src/graphene/libraries/fc/src/thread/thread_d.hpp", line=370, function=0x2b73440 <fc::thread_d::start_next_fiber(bool)::__PRETTY_FUNCTION__> "bool fc::thread_d::start_next_fiber(bool)") at assert.c:101 #4 0x000000000261c867 in fc::thread_d::start_next_fiber (this=0x3349b50, reschedule=true) at /home/user/src/graphene/libraries/fc/src/thread/thread_d.hpp:370 #5 0x00000000026164d5 in fc::thread::yield (this=0x32f8cd0, reschedule=true) at /home/user/src/graphene/libraries/fc/src/thread/thread.cpp:268 #6 0x0000000002617142 in fc::yield () at /home/user/src/graphene/libraries/fc/src/thread/thread.cpp:353 #7 0x0000000002629c95 in fc::spin_yield_lock::lock (this=0x7fffdcb6f43c) at /home/user/src/graphene/libraries/fc/src/thread/spin_yield_lock.cpp:41 #8 0x000000000262861c in fc::unique_lock<fc::spin_yield_lock&>::lock (this=0x7ffff6100c50) at /home/user/src/graphene/libraries/fc/include/fc/thread/unique_lock.hpp:21 #9 0x0000000002628537 in fc::unique_lock<fc::spin_yield_lock&>::unique_lock (this=0x7ffff6100c50, l=...) at /home/user/src/graphene/libraries/fc/include/fc/thread/unique_lock.hpp:17 #10 0x000000000262833e in fc::promise_base::_set_value (this=0x7fffdcb6f430, s=0x0) at /home/user/src/graphene/libraries/fc/src/thread/future.cpp:115 #11 0x0000000002627c08 in fc::promise_base::set_exception (this=0x7fffdcb6f430, e=...) at /home/user/src/graphene/libraries/fc/src/thread/future.cpp:47 #12 0x0000000002628ecf in fc::task_base::run_impl (this=0x7fffdcb6f3d0) at /home/user/src/graphene/libraries/fc/src/thread/task.cpp:55 #13 0x00000000026289bc in fc::task_base::run (this=0x7fffdcb6f3d0) at /home/user/src/graphene/libraries/fc/src/thread/task.cpp:32 #14 0x000000000261d3dc in fc::thread_d::run_next_task (this=0x3349b50) at /home/user/src/graphene/libraries/fc/src/thread/thread_d.hpp:498 #15 0x000000000261d880 in fc::thread_d::process_tasks (this=0x3349b50) at /home/user/src/graphene/libraries/fc/src/thread/thread_d.hpp:547 #16 0x000000000261cef3 in fc::thread_d::start_process_tasks (my=53779280) at /home/user/src/graphene/libraries/fc/src/thread/thread_d.hpp:475 #17 0x0000000002975a31 in make_fcontext () at libs/context/src/asm/make_x86_64_sysv_elf_gas.S:64 #18 0x0000000000000000 in ?? () (gdb)
Title: Re: Test Net for Advanced Users
Post by: abit on September 14, 2015, 04:36:56 am: Quote from: clayop on September 13, 2015, 10:50:22 pm
witness node stopped with the following error

Code: [Select]
3599870ms th_a application.cpp:422 handle_transaction ] Got transaction from network 1ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 172076 new_block.id(): 0002a02c211ed6b4ab4ab 41989d9f0007ad02fef witness_node: /home/clayop/graphene/libraries /chain/db_maint.cpp:333: void graphene::chain ::database::process_budget(): Assertion `time _to_maint > 0' failed. Aborted (core dumped)
Which commit were you running with? My nodes are unable to go over block 172075, but haven't crash. Looks like your issue is related to block 172076.
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 14, 2015, 05:41:41 am: The compilation from Saturday was running smoothly over the weekend. This morning I found the witness crashed:

Code: [Select]
973361ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"","data":{"trx":{"ref_block_num":57237,"ref_block_prefix":141629248,"expiration":"2015-09-13T23:16:57","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["206f76beb28d9a139bbb8f061d787a83aa3d0565040be653ae2330a802eafbfe0f780f4ec86c269c278eb81d6458d53ea8c0d7bfe78eadae56e124a529d6ffa6bc"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"","data":{"trx":{"ref_block_num":57237,"ref_block_prefix":141629248,"expiration":"2015-09-13T23:16:57","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["206f76beb28d9a139bbb8f061d787a83aa3d0565040be653ae2330a802eafbfe0f780f4ec86c269c278eb81d6458d53ea8c0d7bfe78eadae56e124a529d6ffa6bc"]}}}]} 973391ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973392ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973493ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973558ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973682ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973756ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973823ms th_a application.cpp:421 handle_transaction ] Got transaction from network witness_node: /home/calabiyau/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Aborted (core dumped)
Title: Re: Test Net for Advanced Users
Post by: betax on September 14, 2015, 05:54:19 am: Quote from: CalabiYau on September 14, 2015, 05:41:41 am
The compilation from Saturday was running smoothly over the weekend. This morning I found the witness crashed:

Code: [Select]
973361ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"","data":{"trx":{"ref_block_num":57237,"ref_block_prefix":141629248,"expiration":"2015-09-13T23:16:57","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["206f76beb28d9a139bbb8f061d787a83aa3d0565040be653ae2330a802eafbfe0f780f4ec86c269c278eb81d6458d53ea8c0d7bfe78eadae56e124a529d6ffa6bc"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"","data":{"trx":{"ref_block_num":57237,"ref_block_prefix":141629248,"expiration":"2015-09-13T23:16:57","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["206f76beb28d9a139bbb8f061d787a83aa3d0565040be653ae2330a802eafbfe0f780f4ec86c269c278eb81d6458d53ea8c0d7bfe78eadae56e124a529d6ffa6bc"]}}}]} 973391ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973392ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973493ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973558ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973682ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973756ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973823ms th_a application.cpp:421 handle_transaction ] Got transaction from network witness_node: /home/calabiyau/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Aborted (core dumped)

Woke up to this too

Code: [Select]
3169758ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"","data":{"trx":{"ref_block_num":60494,"ref_block_prefix":2734476150,"expiration":"2015-09-14T05:56:32","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["205c4049776969e7b3fa9ad3ee401a46b757a6b0821dcf2c0c2f4e79c9beac8bf60c37d51f490092708be2348d11228ea6ad225db2d884a96b26c5b990e6746ada"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"","data":{"trx":{"ref_block_num":60494,"ref_block_prefix":2734476150,"expiration":"2015-09-14T05:56:32","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["205c4049776969e7b3fa9ad3ee401a46b757a6b0821dcf2c0c2f4e79c9beac8bf60c37d51f490092708be2348d11228ea6ad225db2d884a96b26c5b990e6746ada"]}}}]}
Title: Re: Test Net for Advanced Users
Post by: betax on September 14, 2015, 05:59:11 am: And https://graphene.bitshares.org/ is dead

Code: [Select]
app.js:38 !!! WebSocket Error wss://graphene.bitshares.org:8090 app.js:38 WebSocket connection to 'wss://graphene.bitshares.org:8090/' failed: Error during WebSocket handshake: Unexpected response code: 502
Edit: All good now
Title: Re: Test Net for Advanced Users
Post by: betax on September 14, 2015, 07:58:13 am: Quote from: betax on September 14, 2015, 05:54:19 am
Quote from: CalabiYau on September 14, 2015, 05:41:41 am
The compilation from Saturday was running smoothly over the weekend. This morning I found the witness crashed:

Code: [Select]
973361ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"","data":{"trx":{"ref_block_num":57237,"ref_block_prefix":141629248,"expiration":"2015-09-13T23:16:57","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["206f76beb28d9a139bbb8f061d787a83aa3d0565040be653ae2330a802eafbfe0f780f4ec86c269c278eb81d6458d53ea8c0d7bfe78eadae56e124a529d6ffa6bc"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"","data":{"trx":{"ref_block_num":57237,"ref_block_prefix":141629248,"expiration":"2015-09-13T23:16:57","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["206f76beb28d9a139bbb8f061d787a83aa3d0565040be653ae2330a802eafbfe0f780f4ec86c269c278eb81d6458d53ea8c0d7bfe78eadae56e124a529d6ffa6bc"]}}}]} 973391ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973392ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973493ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973558ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973682ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973756ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973823ms th_a application.cpp:421 handle_transaction ] Got transaction from network witness_node: /home/calabiyau/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Aborted (core dumped)

Woke up to this too

Code: [Select]
3169758ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"","data":{"trx":{"ref_block_num":60494,"ref_block_prefix":2734476150,"expiration":"2015-09-14T05:56:32","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["205c4049776969e7b3fa9ad3ee401a46b757a6b0821dcf2c0c2f4e79c9beac8bf60c37d51f490092708be2348d11228ea6ad225db2d884a96b26c5b990e6746ada"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"","data":{"trx":{"ref_block_num":60494,"ref_block_prefix":2734476150,"expiration":"2015-09-14T05:56:32","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["205c4049776969e7b3fa9ad3ee401a46b757a6b0821dcf2c0c2f4e79c9beac8bf60c37d51f490092708be2348d11228ea6ad225db2d884a96b26c5b990e6746ada"]}}}]}

This problem (if not just a warning) seems to have disappeared now.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 14, 2015, 11:55:23 am: I started getting this about six hours ago. I switched back to "Master" which had a pile of updates and am rebuilding my witness binary. We'll see if that fixes it.

Code: [Select]
2842000ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn 2842001ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1442231242001571 next_second: 2015-09-14T11:47:23 2842014ms th_a application.cpp:356 handle_block ] Got block #194679 from network 2842015ms th_a application.cpp:378 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num < _head->num + MAX_BLOCK_REORDERING: {} th_a fork_database.cpp:70 _push_block {"new_block":{"previous":"0002f876121cf55147d14b4c30a8aaf0877a38eb","timestamp":"2015-09-14T11:47:20","witness":"1.6.48","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f5b899e8a4e1a406629a6a98d1dc2f463bae6b60517435ffe68825184d0680f240a7ed917a916c5e1475f05191d67536f74f78bf76e5323537f0990eebd0adc21","transactions":[]}} th_a db_block.cpp:176 _push_block 2843000ms th_a witness.cpp:220 block_production_loo ] Not producing block because it isn't my turn 2843001ms th_a witness.cpp:187 schedule_production_ ] now.time_since_epoch().count(): 1442231243001656 next_second: 2015-09-14T11:47:24 2843787ms th_a main.cpp:169 main ] Exiting from signal 2 2843798ms th_a thread.cpp:115 ~thread ] calling quit() on ntp 2843799ms th_a thread.cpp:160 quit ] destroying boost thread 139689216190208 2843802ms ntp thread.cpp:246 exec ] thread canceled: 9 canceled_exception: Canceled cancellation reason: [none given] {"reason":"[none given]"} ntp thread_d.hpp:463 start_next_fiber 2843836ms th_a thread.cpp:115 ~thread ] calling quit() on p2p 2843836ms th_a thread.cpp:160 quit ] destroying boost thread 139689180436224 2843840ms p2p thread.cpp:246 exec ] thread canceled: 9 canceled_exception: Canceled cancellation reason: [none given] {"reason":"[none given]"}
Title: Re: Test Net for Advanced Users
Post by: puppies on September 14, 2015, 01:23:48 pm: I woke up to this on my home machine
Code: [Select]
770ms th_a application.cpp:422 handle_transaction ] Got transaction from network 2492315ms th_a application.cpp:383 handle_block ] Got block #191949 from network 2492315ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 191949 new_block.id(): 0002edcda9a6ead041565776fc44dabfbe2e1047 2493260ms th_a application.cpp:683 get_blockchain_synop ] synopsis: ["0002edb0f9f9f46a5131e683d7cdf03630d0b105","0002edbffba5cc2aee85c854c9690d8640766f70","0002edc70bac5a6448cb68f234642c829cac4352","0002edcb696c768b569ade47a988f9ad8bb34344","0002edcd10fc9e1db43fd6ffbc4895169c245915"] 2493714ms th_a application.cpp:683 get_blockchain_synop ] synopsis: ["0002edb0f9f9f46a5131e683d7cdf03630d0b105","0002edbffba5cc2aee85c854c9690d8640766f70","0002edc70bac5a6448cb68f234642c829cac4352","0002edcb696c768b569ade47a988f9ad8bb34344","0002edcd10fc9e1db43fd6ffbc4895169c245915"] witness_node: /home/user/src/graphene/libraries/chain/db_block.cpp:82: std::vector<fc::ripemd160> graphene::chain::database::get_block_ids_on_fork(graphene::chain::block_id_type) const: Assertion `branches.first.back()->id == branches.second.back()->id' failed. Program received signal SIGABRT, Aborted. 0x00007ffff6c01cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ffff6c01cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007ffff6c050d8 in __GI_abort () at abort.c:89 #2 0x00007ffff6bfab86 in __assert_fail_base ( fmt=0x7ffff6d4b830 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x2ac0c40 "branches.first.back()->id == branches.second.back()->id", file=file@entry=0x2ac0be0 "/home/user/src/graphene/libraries/chain/db_block.cpp", line=line@entry=82, function=function@entry=0x2acb220 <graphene::chain::database::get_block_ids_on_fork(fc::ripemd160) const::__PRETTY_FUNCTION__> "std::vector<fc::ripemd160> graphene::chain::database::get_block_ids_on_fork(graphene::chain::block_id_type) const") at assert.c:92 #3 0x00007ffff6bfac32 in __GI___assert_fail ( assertion=0x2ac0c40 "branches.first.back()->id == branches.second.back()->id", file=0x2ac0be0 "/home/user/src/graphene/libraries/chain/db_block.cpp", line=82, function=0x2acb220 <graphene::chain::database::get_block_ids_on_fork(fc::ripemd160) const::__PRETTY_FUNCTION__> "std::vector<fc::ripemd160> graphene::chain::database::get_block_ids_on_fork(graphene::chain::block_id_type) const") at assert.c:101 #4 0x0000000002302824 in graphene::chain::database::get_block_ids_on_fork(fc::ripemd160) const () ---Type <return> to continue, or q <return> to quit--- #5 0x0000000001f99e28 in graphene::app::detail::application_impl::get_blockchain_synopsis(fc::ripemd160 const&, unsigned int) () #6 0x000000000281686f in graphene::net::detail::statistics_gathering_node_delegate_wrapper::get_blockchain_synopsis(fc::ripemd160 const&, unsigned int)::{lambda()#1}::operator()() const () #7 0x0000000002826910 in fc::detail::functor_run<graphene::net::detail::statistics_gathering_node_delegate_wrapper::get_blockchain_synopsis(fc::ripemd160 const&, unsigned int)::{lambda()#1}>::run(void*, fc::detail::functor_run<graphene::net::detail::statistics_gathering_node_delegate_wrapper::get_blockchain_synopsis(fc::ripemd160 const&, unsigned int)::{lambda()#1}>) () #8 0x00000000025f2011 in fc::task_base::run_impl() () #9 0x00000000025f1fa2 in fc::task_base::run() () #10 0x00000000025e69c2 in fc::thread_d::run_next_task() () #11 0x00000000025e6e66 in fc::thread_d::process_tasks() () #12 0x00000000025e64d9 in fc::thread_d::start_process_tasks(long) () #13 0x0000000002943a81 in make_fcontext () #14 0x0000000000000000 in ?? () (gdb)this is running on commit 30ae8e4f3433d4ee500f0b98e30f05e1ebe806ea.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 14, 2015, 01:41:08 pm: Also got this when I re-cloned graphene-ui. If there's another thread for the UI I'll move this post there.

Code: [Select]
> webgui@0.0.1 start /home/james/github/graphene-ui/web > node server.js Using DEV options 70.00% 1/1 build modules events.js:72 throw er; // Unhandled 'error' event ^ Error: listen EADDRINUSE at errnoException (net.js:901:11) at Server._listen2 (net.js:1039:14) at listen (net.js:1061:10) at net.js:1143:9 at dns.js:72:18 at process._tickCallback (node.js:415:13) at Function.Module.runMain (module.js:499:11) at startup (node.js:119:16) at node.js:902:3 npm ERR! webgui@0.0.1 start: `node server.js` npm ERR! Exit status 8 npm ERR! npm ERR! Failed at the webgui@0.0.1 start script. npm ERR! This is most likely a problem with the webgui package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node server.js npm ERR! You can get their info via: npm ERR! npm owner ls webgui npm ERR! There is likely additional logging output above. npm ERR! System Linux 3.19.0-28-generic npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "start" npm ERR! cwd /home/james/github/graphene-ui/web npm ERR! node -v v0.10.25 npm ERR! npm -v 1.4.21 npm ERR! code ELIFECYCLE npm WARN This failure might be due to the use of legacy binary "node" npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/james/github/graphene-ui/web/npm-debug.log npm ERR! not ok code 0 james@james-desktop:~/github/graphene-ui$
Title: Re: Test Net for Advanced Users
Post by: puppies on September 14, 2015, 01:58:07 pm: graphene ui is working for me on commit 25b7c4db6816684ae11f731aab522630cbeda66a. The Dashboard page wont load, and the blockexplorer eats up massive resources (enough to where it locks up firefox) while spamming though.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 14, 2015, 03:09:40 pm: Quote from: betax on September 14, 2015, 07:58:13 am
Quote from: betax on September 14, 2015, 05:54:19 am
Quote from: CalabiYau on September 14, 2015, 05:41:41 am
The compilation from Saturday was running smoothly over the weekend. This morning I found the witness crashed:

Code: [Select]
973361ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"","data":{"trx":{"ref_block_num":57237,"ref_block_prefix":141629248,"expiration":"2015-09-13T23:16:57","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["206f76beb28d9a139bbb8f061d787a83aa3d0565040be653ae2330a802eafbfe0f780f4ec86c269c278eb81d6458d53ea8c0d7bfe78eadae56e124a529d6ffa6bc"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"","data":{"trx":{"ref_block_num":57237,"ref_block_prefix":141629248,"expiration":"2015-09-13T23:16:57","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["206f76beb28d9a139bbb8f061d787a83aa3d0565040be653ae2330a802eafbfe0f780f4ec86c269c278eb81d6458d53ea8c0d7bfe78eadae56e124a529d6ffa6bc"]}}}]} 973391ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973392ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973493ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973558ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973682ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973756ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973823ms th_a application.cpp:421 handle_transaction ] Got transaction from network witness_node: /home/calabiyau/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Aborted (core dumped)

Woke up to this too

Code: [Select]
3169758ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"","data":{"trx":{"ref_block_num":60494,"ref_block_prefix":2734476150,"expiration":"2015-09-14T05:56:32","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["205c4049776969e7b3fa9ad3ee401a46b757a6b0821dcf2c0c2f4e79c9beac8bf60c37d51f490092708be2348d11228ea6ad225db2d884a96b26c5b990e6746ada"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"","data":{"trx":{"ref_block_num":60494,"ref_block_prefix":2734476150,"expiration":"2015-09-14T05:56:32","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["205c4049776969e7b3fa9ad3ee401a46b757a6b0821dcf2c0c2f4e79c9beac8bf60c37d51f490092708be2348d11228ea6ad225db2d884a96b26c5b990e6746ada"]}}}]}

This problem (if not just a warning) seems to have disappeared now.

I think I have identified the cause of this problem. Can you confirm that it occurred while you were using the RPC interface?
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 14, 2015, 03:24:14 pm: My stats.bitshares.eu node died with
Code: [Select]
3498879ms th_a application.cpp:422 handle_transaction ] Got transaction from network 3498880ms th_a application.cpp:422 handle_transaction ] Got transaction from network witness_node: /home/delegate/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Aborted
Title: Re: Test Net for Advanced Users
Post by: puppies on September 14, 2015, 03:33:43 pm: My witness producing node is no longer losing sync during stress tests, but it does stop producing blocks. I can't find anything in logs that sheds any light on it.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 14, 2015, 03:34:24 pm: Quote from: xeroc on September 14, 2015, 03:24:14 pm
My stats.bitshares.eu node died with
Code: [Select]
3498879ms th_a application.cpp:422 handle_transaction ] Got transaction from network 3498880ms th_a application.cpp:422 handle_transaction ] Got transaction from network witness_node: /home/delegate/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Aborted

The latest push to *fc* should fix it. Fetch the latest graphene and be sure to update submodules.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 14, 2015, 03:36:19 pm: Quote from: puppies on September 14, 2015, 03:33:43 pm
My witness producing node is no longer losing sync during stress tests, but it does stop producing blocks. I can't find anything in logs that sheds any light on it.

How are you determining that it stopped producing blocks? Perhaps the absence of logs is a clue :)
Title: Re: Test Net for Advanced Users
Post by: svk on September 14, 2015, 03:39:41 pm: Quote from: Riverhead on September 14, 2015, 01:41:08 pm

Also got this when I re-cloned graphene-ui. If there's another thread for the UI I'll move this post there.

Code: [Select]
> webgui@0.0.1 start /home/james/github/graphene-ui/web > node server.js Using DEV options 70.00% 1/1 build modules events.js:72 throw er; // Unhandled 'error' event ^ Error: listen EADDRINUSE at errnoException (net.js:901:11) at Server._listen2 (net.js:1039:14) at listen (net.js:1061:10) at net.js:1143:9 at dns.js:72:18 at process._tickCallback (node.js:415:13) at Function.Module.runMain (module.js:499:11) at startup (node.js:119:16) at node.js:902:3 npm ERR! webgui@0.0.1 start: `node server.js` npm ERR! Exit status 8 npm ERR! npm ERR! Failed at the webgui@0.0.1 start script. npm ERR! This is most likely a problem with the webgui package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node server.js npm ERR! You can get their info via: npm ERR! npm owner ls webgui npm ERR! There is likely additional logging output above. npm ERR! System Linux 3.19.0-28-generic npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "start" npm ERR! cwd /home/james/github/graphene-ui/web npm ERR! node -v v0.10.25 npm ERR! npm -v 1.4.21 npm ERR! code ELIFECYCLE npm WARN This failure might be due to the use of legacy binary "node" npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/james/github/graphene-ui/web/npm-debug.log npm ERR! not ok code 0 james@james-desktop:~/github/graphene-ui$
You already have a server running on port 8080, either something else or another copy of the gui.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 14, 2015, 03:45:06 pm: Quote from: bytemaster on September 14, 2015, 03:36:19 pm
Quote from: puppies on September 14, 2015, 03:33:43 pm
My witness producing node is no longer losing sync during stress tests, but it does stop producing blocks. I can't find anything in logs that sheds any light on it.

How are you determining that it stopped producing blocks? Perhaps the absence of logs is a clue :)

I am just watching the witness vesting pay 1.13.163. The witness is still voted in. Info shows a recent block time. At this point, I am rebuilding, and ill verify the issue remains. Then I was thinking I would run it on a more powerful machine and see if that helped. I'll also keep digging in the logs to see if I can find anything.

Is there a way to see the scheduled witness order? Some way to tell which witness was scheduled when a block isn't produced?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 14, 2015, 03:47:22 pm: Quote from: puppies on September 14, 2015, 03:45:06 pm
Quote from: bytemaster on September 14, 2015, 03:36:19 pm
Quote from: puppies on September 14, 2015, 03:33:43 pm
My witness producing node is no longer losing sync during stress tests, but it does stop producing blocks. I can't find anything in logs that sheds any light on it.

How are you determining that it stopped producing blocks? Perhaps the absence of logs is a clue :)

I am just watching the witness vesting pay 1.13.163. The witness is still voted in. Info shows a recent block time. At this point, I am rebuilding, and ill verify the issue remains. Then I was thinking I would run it on a more powerful machine and see if that helped. I'll also keep digging in the logs to see if I can find anything.

Is there a way to see the scheduled witness order? Some way to tell which witness was scheduled when a block isn't produced?

Does restarting the witness fix the production issue?
Title: Re: Test Net for Advanced Users
Post by: puppies on September 14, 2015, 03:48:53 pm: Quote from: bytemaster on September 14, 2015, 03:47:22 pm
Quote from: puppies on September 14, 2015, 03:45:06 pm
Quote from: bytemaster on September 14, 2015, 03:36:19 pm
Quote from: puppies on September 14, 2015, 03:33:43 pm
My witness producing node is no longer losing sync during stress tests, but it does stop producing blocks. I can't find anything in logs that sheds any light on it.

How are you determining that it stopped producing blocks? Perhaps the absence of logs is a clue :)

I am just watching the witness vesting pay 1.13.163. The witness is still voted in. Info shows a recent block time. At this point, I am rebuilding, and ill verify the issue remains. Then I was thinking I would run it on a more powerful machine and see if that helped. I'll also keep digging in the logs to see if I can find anything.

Is there a way to see the scheduled witness order? Some way to tell which witness was scheduled when a block isn't produced?

Does restarting the witness fix the production issue?
Yes.
In fact it just started producing again after I stopped stress testing. Without a restart
Title: Re: Test Net for Advanced Users
Post by: Akado on September 14, 2015, 03:55:50 pm: Glad the testing thread has more pages than the price discussion one, it's a good sign, keep it up guys! +5%
Title: Re: Test Net for Advanced Users
Post by: spartako on September 14, 2015, 04:10:37 pm: It seems the stress test has genereted a big block (> 100tx/sec):

blockNum IdWitness nameWitness nTx
196454 '1.6.3356' 'mr.agsexplorer' 507
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 14, 2015, 04:10:50 pm: Quote from: bytemaster on September 14, 2015, 03:09:40 pm
Quote from: betax on September 14, 2015, 07:58:13 am
Quote from: betax on September 14, 2015, 05:54:19 am
Quote from: CalabiYau on September 14, 2015, 05:41:41 am
The compilation from Saturday was running smoothly over the weekend. This morning I found the witness crashed:

Code: [Select]
973361ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"","data":{"trx":{"ref_block_num":57237,"ref_block_prefix":141629248,"expiration":"2015-09-13T23:16:57","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["206f76beb28d9a139bbb8f061d787a83aa3d0565040be653ae2330a802eafbfe0f780f4ec86c269c278eb81d6458d53ea8c0d7bfe78eadae56e124a529d6ffa6bc"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"","data":{"trx":{"ref_block_num":57237,"ref_block_prefix":141629248,"expiration":"2015-09-13T23:16:57","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["206f76beb28d9a139bbb8f061d787a83aa3d0565040be653ae2330a802eafbfe0f780f4ec86c269c278eb81d6458d53ea8c0d7bfe78eadae56e124a529d6ffa6bc"]}}}]} 973391ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973392ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973493ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973558ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973682ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973756ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973823ms th_a application.cpp:421 handle_transaction ] Got transaction from network witness_node: /home/calabiyau/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Aborted (core dumped)

Woke up to this too

Code: [Select]
3169758ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"","data":{"trx":{"ref_block_num":60494,"ref_block_prefix":2734476150,"expiration":"2015-09-14T05:56:32","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["205c4049776969e7b3fa9ad3ee401a46b757a6b0821dcf2c0c2f4e79c9beac8bf60c37d51f490092708be2348d11228ea6ad225db2d884a96b26c5b990e6746ada"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"","data":{"trx":{"ref_block_num":60494,"ref_block_prefix":2734476150,"expiration":"2015-09-14T05:56:32","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["205c4049776969e7b3fa9ad3ee401a46b757a6b0821dcf2c0c2f4e79c9beac8bf60c37d51f490092708be2348d11228ea6ad225db2d884a96b26c5b990e6746ada"]}}}]}

This problem (if not just a warning) seems to have disappeared now.

I think I have identified the cause of this problem. Can you confirm that it occurred while you were using the RPC interface?

cli_wallet was open but not actually used.

After witness restart it`s running o.k. since ~ 10 hours, will push some tx again within the next hour.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 14, 2015, 04:21:56 pm: Quote from: spartako on September 14, 2015, 04:10:37 pm
It seems the stress test has genereted a big block (> 100tx/sec):

blockNum IdWitness nameWitness nTx
196454 '1.6.3356' 'mr.agsexplorer' 507
+5%
Very nice progress so far.
Title: Re: Test Net for Advanced Users
Post by: abit on September 14, 2015, 04:59:07 pm: I don't know why my nodes were always stuck at block 172075.
Now trying with latest commit and --resync-blockchain.

//EDIT: it works with the latest commit and --resync.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 14, 2015, 06:24:40 pm: latest master crashed on me during stress test. I wasn't running in gdb
Code: [Select]
1051908ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 197873 new_block.id(): 000304f12cf6d6cf7636a0cd287f8ba8367c33a8 witness_node: /home/user/src/graphene/libraries/chain/db_block.cpp:82: std::vector<fc::ripemd160> graphene::chain::database::get_block_ids_on_fork(graphene::chain::block_id_type) const: Assertion `branches.first.back()->id == branches.second.back()->id' failed. Aborted (core dumped)
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 14, 2015, 07:35:38 pm: Quote from: svk on September 14, 2015, 03:39:41 pm
You already have a server running on port 8080, either something else or another copy of the gui.

Thanks. node server.js was still running.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 14, 2015, 07:44:29 pm: Quote from: puppies on September 14, 2015, 06:24:40 pm
latest master crashed on me during stress test. I wasn't running in gdb
Code: [Select]
1051908ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 197873 new_block.id(): 000304f12cf6d6cf7636a0cd287f8ba8367c33a8 witness_node: /home/user/src/graphene/libraries/chain/db_block.cpp:82: std::vector<fc::ripemd160> graphene::chain::database::get_block_ids_on_fork(graphene::chain::block_id_type) const: Assertion `branches.first.back()->id == branches.second.back()->id' failed. Aborted (core dumped)

Fixed: https://github.com/cryptonomex/graphene/commit/dd7d57c5ac89d8699f91eb6daee72b0854bfb860
Title: Re: Test Net for Advanced Users
Post by: puppies on September 14, 2015, 10:30:47 pm: very little of my spam is making it into blocks. I wrote a simple python script to tie into xerocs python-graphenelib which writes block producer and # of transactions to the console. While spamming there is quite a bit of variability.
Code: [Select]
block 199762 generated by init68 block 199762 contained 9 transactions block 199763 generated by init14 block 199763 contained 20 transactions block 199764 generated by init35 block 199764 contained 11 transactions block 199765 generated by init36 block 199765 contained 7 transactions block 199766 generated by init19 block 199766 contained 10 transactions block 199767 generated by init10 block 199767 contained 10 transactions block 199768 generated by init80 block 199768 contained 9 transactions block 199769 generated by init51 block 199769 contained 4 transactions block 199770 generated by init11 block 199770 contained 0 transactions block 199771 generated by init59 block 199771 contained 0 transactions block 199772 generated by init67 block 199772 contained 4 transactions block 199773 generated by init75 block 199773 contained 0 transactions block 199774 generated by init4 block 199774 contained 0 transactions block 199775 generated by init20 block 199775 contained 0 transactions
Title: Re: Test Net for Advanced Users
Post by: clout on September 15, 2015, 01:16:15 am: Quote from: puppies on September 14, 2015, 10:30:47 pm
very little of my spam is making it into blocks. I wrote a simple python script to tie into xerocs python-graphenelib which writes block producer and # of transactions to the console. While spamming there is quite a bit of variability.
Code: [Select]
block 199762 generated by init68 block 199762 contained 9 transactions block 199763 generated by init14 block 199763 contained 20 transactions block 199764 generated by init35 block 199764 contained 11 transactions block 199765 generated by init36 block 199765 contained 7 transactions block 199766 generated by init19 block 199766 contained 10 transactions block 199767 generated by init10 block 199767 contained 10 transactions block 199768 generated by init80 block 199768 contained 9 transactions block 199769 generated by init51 block 199769 contained 4 transactions block 199770 generated by init11 block 199770 contained 0 transactions block 199771 generated by init59 block 199771 contained 0 transactions block 199772 generated by init67 block 199772 contained 4 transactions block 199773 generated by init75 block 199773 contained 0 transactions block 199774 generated by init4 block 199774 contained 0 transactions block 199775 generated by init20 block 199775 contained 0 transactions

While you were spamming none of my transactions went through. Also can we spam the network from the js console in the web browser? I couldn't find any functions for making transactions.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 15, 2015, 03:16:15 am: Quote from: clout on September 15, 2015, 01:16:15 am

While you were spamming none of my transactions went through. Also can we spam the network from the js console in the web browser? I couldn't find any functions for making transactions.

Not exactly what you're looking for but it pushes the same buttons.

~/github/graphene-ui\README.md

Code: [Select]
A javascript CLI environment is also available in the ./cli folder. Some example commands: ``` // Transaction template: $g.wallet.template("account_upgrade") // Create a transaction: var tr = $g.wallet.new_transaction() tr.add_type_operation("account_upgrade", {"account_to_upgrade":"1.2.15","upgrade_to_lifetime_member":true}) $g.wallet.sign_and_broadcast(tr)
Title: Re: Test Net for Advanced Users
Post by: abit on September 15, 2015, 09:10:08 am: Crashed on commit f0f12076fa5d80e07758ae5104854efd1dcb748d
Code: [Select]
745500ms th_a application.cpp:383 handle_block ] Got block #199649 from network 745500ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 199649 new_block.id(): 00030be11aae3a4891869a7ad9aab215e93aee36747089ms th_a application.cpp:683 get_blockchain_synop ] synopsis: ["00030b6c048c2452ac552e476f913329d818074a","00030ba7eec13a91d97908a50549d874681ea35a","00030bc587cc15cfdf07f10a72804724cb51217d","00030bd4128e9547c6771b80e5ffff1fdeec37a4","00030bdba291f319d7f0f62ec67394ef613ca8a5","00030bdf303a78916851613360a845e22e0041d8","00030be11aae3a4891869a7ad9aab215e93aee36"] 749560ms th_a application.cpp:683 get_blockchain_synop ] synopsis: ["00030b6c048c2452ac552e476f913329d818074a","00030ba7eec13a91d97908a50549d874681ea35a","00030bc587cc15cfdf07f10a72804724cb51217d","00030bd4128e9547c6771b80e5ffff1fdeec37a4","00030bdba291f319d7f0f62ec67394ef613ca8a5","00030bdf303a78916851613360a845e22e0041d8","00030be11aae3a4891869a7ad9aab215e93aee36"] 752624ms th_a application.cpp:683 get_blockchain_synop ] synopsis: ["00030b6c048c2452ac552e476f913329d818074a","00030ba7eec13a91d97908a50549d874681ea35a","00030bc587cc15cfdf07f10a72804724cb51217d","00030bd4128e9547c6771b80e5ffff1fdeec37a4","00030bdba291f319d7f0f62ec67394ef613ca8a5","00030bdf303a78916851613360a845e22e0041d8","00030be11aae3a4891869a7ad9aab215e93aee36"] 752881ms th_a application.cpp:683 get_blockchain_synop ] synopsis: ["00030b6c048c2452ac552e476f913329d818074a","00030ba7eec13a91d97908a50549d874681ea35a","00030bc587cc15cfdf07f10a72804724cb51217d","00030bd4128e9547c6771b80e5ffff1fdeec37a4","00030bdba291f319d7f0f62ec67394ef613ca8a5","00030bdf303a78916851613360a845e22e0041d8","00030be11aae3a4891869a7ad9aab215e93aee36"] witness_node: /app/bts/graphene-test2b.7/libraries/app/application.cpp:624: virtual std::vector<fc::ripemd160> graphene::app::detail::application_impl::get_blockchain_synopsis(const item_hash_t&, uint32_t): Assertion `fork_history.back() == reference_point' failed. Program received signal SIGABRT, Aborted. 0x00007ffff6c01cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ffff6c01cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007ffff6c050d8 in __GI_abort () at abort.c:89 #2 0x00007ffff6bfab86 in __assert_fail_base (fmt=0x7ffff6d4b830 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x2aa0530 "fork_history.back() == reference_point", file=file@entry=0x2a9fd58 "/app/bts/graphene-test2b.7/libraries/app/application.cpp", line=line@entry=624, function=function@entry=0x2aa5f00 <graphene::app::detail::application_impl::get_blockchain_synopsis(fc::ripemd160 const&, unsigned int)::__PRETTY_FUNCTION__> "virtual std::vector<fc::ripemd160> graphene::app::detail::application_impl::get_blockchain_synopsis(const item_hash_t&, uint32_t)") at assert.c:92 #3 0x00007ffff6bfac32 in __GI___assert_fail (assertion=0x2aa0530 "fork_history.back() == reference_point", file=0x2a9fd58 "/app/bts/graphene-test2b.7/libraries/app/application.cpp", line=624, function=0x2aa5f00 <graphene::app::detail::application_impl::get_blockchain_synopsis(fc::ripemd160 const&, unsigned int)::__PRETTY_FUNCTION__> "virtual std::vector<fc::ripemd160> graphene::app::detail::application_impl::get_blockchain_synopsis(const item_hash_t&, uint32_t)") at assert.c:101 #4 0x0000000001fd088e in graphene::app::detail::application_impl::get_blockchain_synopsis (this=0x3318140, reference_point=..., number_of_blocks_after_reference_point=0) at /app/bts/graphene-test2b.7/libraries/app/application.cpp:624 #5 0x000000000284d3a3 in graphene::net::detail::statistics_gathering_node_delegate_wrapper::__lambda59::operator() ( __closure=0x7fffe411d868) at /app/bts/graphene-test2b.7/libraries/net/node.cpp:5296 #6 0x000000000285d444 in fc::detail::functor_run<graphene::net::detail::statistics_gathering_node_delegate_wrapper::get_blockchain_synopsis(const item_hash_t&, uint32_t)::__lambda59>::run(void *, void *) (functor=0x7fffe411d868, prom=0x7fffe411d950) at /app/bts/graphene-test2b.7/libraries/fc/include/fc/thread/task.hpp:77 #7 0x0000000002628a87 in fc::task_base::run_impl (this=0x7fffe411d888) at /app/bts/graphene-test2b.7/libraries/fc/src/thread/task.cpp:43 #8 0x0000000002628a18 in fc::task_base::run (this=0x7fffe411d888) at /app/bts/graphene-test2b.7/libraries/fc/src/thread/task.cpp:32 #9 0x000000000261d438 in fc::thread_d::run_next_task (this=0x334c040) at /app/bts/graphene-test2b.7/libraries/fc/src/thread/thread_d.hpp:498 #10 0x000000000261d8dc in fc::thread_d::process_tasks (this=0x334c040) at /app/bts/graphene-test2b.7/libraries/fc/src/thread/thread_d.hpp:547 #11 0x000000000261cf4f in fc::thread_d::start_process_tasks (my=53788736) at /app/bts/graphene-test2b.7/libraries/fc/src/thread/thread_d.hpp:475 #12 0x0000000002975b51 in make_fcontext () at libs/context/src/asm/make_x86_64_sysv_elf_gas.S:64 #13 0x0000000000000000 in ?? ()
Title: Re: Test Net for Advanced Users
Post by: abit on September 15, 2015, 09:37:53 am: The other of my nodes stopped syncing at block 199572
Code: [Select]
2015-09-14T22:02:15 th_a:Witness Block Production push_block ] new_block.block_num(): 199572 new_block.id(): 00030b940fbad34 0e39709083e5786d5e703bb33 db_block.cpp:98 2015-09-14T22:02:15 th_a:Witness Block Production _push_block ] Failed to push new block: 10 assert_exception: Assert Exception _pending_block.timestamp <= trx.expiration: {"pending.timestamp":"2015-09-14T22:02:15","trx.exp":"2015-09-14T22:02:10"} th_a db_block.cpp:534 _apply_transaction {"trx":{"ref_block_num":2945,"ref_block_prefix":4216103856,"expiration":"2015-09-14T22:02:10","operations":[[0,{"fee":{"amount":20 00000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.38483","amount":{"amount":100000,"asset_id":"1.3.0"},"extensions":[]}]],"extens ions":[],"signatures":["2014dd59f97199b1aaf2785e458284f5762cfc0a1f43bd560fb3058ea5dbd2d0291cc13da25a050f251ee300c573da2347e91fe2c30bc0 393e409eb067b871e4ac"]}} th_a db_block.cpp:564 _apply_transaction {"next_block.block_num()":199572} th_a db_block.cpp:469 _apply_block db_block.cpp:181
Code: [Select]
info { "head_block_num": 199572, "head_block_id": "00030b94089bb7f0949bb63189a506fdf13b6d54", ... }
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 15, 2015, 09:57:58 am: Build on ......5dc41a82 => o.k.

Witness crashed on downloading blocks:

Code: [Select]
1315751ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198066 new_block.id(): 000305b27cbf39adca86c5d4a086bc3febc56bc8 1315752ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198067 new_block.id(): 000305b3dc7d7e6d6ec1de714675167bb68d6844 1315753ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198068 new_block.id(): 000305b4cedbe47143d0ff393eef37113933ff6c 1315754ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198069 new_block.id(): 000305b5b4a47445460fbe4f570f6fcdd5640085 1315755ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198070 new_block.id(): 000305b6b7a20c14f5e1827af055a7bc4da82eb0 1315756ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198071 new_block.id(): 000305b748128bac176f75273a0023e892c52928 witness_node: /home/calabiyau/graphene/libraries/app/application.cpp:624: virtual std::vector<fc::ripemd160> graphene::app::detail::application_impl::get_blockchain_synopsis(const item_hash_t&, uint32_t): Assertion `fork_history.back() == reference_point' failed. Aborted (core dumped)
edit: second attempt => o.k., witness u&r
Title: Re: Test Net for Advanced Users
Post by: wackou on September 15, 2015, 10:11:46 am: Hi all, so I'm (finally) on the test net, witness wackou (already voted in). And I got a few crashes to report, too :D

one I had 2 days ago, just checked on github and it's fixed already (ahhh I missed the days of the first testnets when you had to update everyday to see the bugs from the day before fixed, and a whole new slew of fresh ones for today)

One I had today, same as abit in reply 876 of this thread, started a witness with a fresh download of the chain, log + stack trace follow (on commit 640d69aa05cdc629755edef9884444975dc41a82):

Code: [Select]
2735099ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198068 new_block.id(): 000305b4cedbe47143d0ff393eef37113933ff6c 2735100ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198069 new_block.id(): 000305b5b4a47445460fbe4f570f6fcdd5640085 2735100ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198070 new_block.id(): 000305b6b7a20c14f5e1827af055a7bc4da82eb0 2735101ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198071 new_block.id(): 000305b748128bac176f75273a0023e892c52928 2735101ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198072 new_block.id(): 000305b84a7b19f36c111e13ab8f4617f111e812 2735102ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198073 new_block.id(): 000305b904de6654a5450b597ecb0d2ec6217599 2735102ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198074 new_block.id(): 000305ba363cb379bdde904800269ed0e60a88b4 2735103ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198075 new_block.id(): 000305bb716d1936a8294d55215c5290f3254174 2735103ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 198076 new_block.id(): 000305bc3d4eba5a0e48b33c26b846070aa90161 witness_node: /home/admin/.BitShares2_build/libraries/app/application.cpp:624: virtual std::vector<fc::ripemd160> graphene::app::detail::application_impl::get_blockchain_synopsis(const item_hash_t&, uint32_t): Assertion `fork_history.back() == reference_point' failed. Program received signal SIGABRT, Aborted. 0x00007ffff6516107 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x00007ffff6516107 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff65174e8 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007ffff650f226 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #3 0x00007ffff650f2d2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x00000000020bd3c5 in graphene::app::detail::application_impl::get_blockchain_synopsis (this=0x356b030, reference_point=..., number_of_blocks_after_reference_point=0) at /home/admin/.BitShares2_build/libraries/app/application.cpp:624 #5 0x000000000297a705 in graphene::net::detail::statistics_gathering_node_delegate_wrapper::<lambda()>::operator()(void) const (__closure=0x7fffe0649698) at /home/admin/.BitShares2_build/libraries/net/node.cpp:5296 #6 0x000000000298a97b in fc::detail::functor_run<graphene::net::detail::statistics_gathering_node_delegate_wrapper::get_blockchain_synopsis(const item_hash_t&, uint32_t)::<lambda()> >::run(void *, void *) (functor=0x7fffe0649698, prom=0x7fffe0649780) at /home/admin/.BitShares2_build/libraries/fc/include/fc/thread/task.hpp:77 #7 0x00000000027519cd in fc::task_base::run_impl (this=0x7fffe06496b8) at /home/admin/.BitShares2_build/libraries/fc/src/thread/task.cpp:43 #8 0x000000000275195c in fc::task_base::run (this=0x7fffe06496b8) at /home/admin/.BitShares2_build/libraries/fc/src/thread/task.cpp:32 #9 0x00000000027459ba in fc::thread_d::run_next_task (this=0x359eab0) at /home/admin/.BitShares2_build/libraries/fc/src/thread/thread_d.hpp:498 #10 0x0000000002745e84 in fc::thread_d::process_tasks (this=0x359eab0) at /home/admin/.BitShares2_build/libraries/fc/src/thread/thread_d.hpp:547 #11 0x00000000027454ae in fc::thread_d::start_process_tasks (my=56224432) at /home/admin/.BitShares2_build/libraries/fc/src/thread/thread_d.hpp:475 #12 0x0000000002abf931 in make_fcontext () #13 0x00007fffe8000020 in ?? () #14 0x0000000000000000 in ?? ()
Title: Re: Test Net for Advanced Users
Post by: betax on September 15, 2015, 10:51:31 am: Quote from: bytemaster on September 14, 2015, 03:09:40 pm
Quote from: betax on September 14, 2015, 07:58:13 am
Quote from: betax on September 14, 2015, 05:54:19 am
Quote from: CalabiYau on September 14, 2015, 05:41:41 am
The compilation from Saturday was running smoothly over the weekend. This morning I found the witness crashed:

Code: [Select]
973361ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"","data":{"trx":{"ref_block_num":57237,"ref_block_prefix":141629248,"expiration":"2015-09-13T23:16:57","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["206f76beb28d9a139bbb8f061d787a83aa3d0565040be653ae2330a802eafbfe0f780f4ec86c269c278eb81d6458d53ea8c0d7bfe78eadae56e124a529d6ffa6bc"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-13T23:16:13"},"format":"","data":{"trx":{"ref_block_num":57237,"ref_block_prefix":141629248,"expiration":"2015-09-13T23:16:57","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["206f76beb28d9a139bbb8f061d787a83aa3d0565040be653ae2330a802eafbfe0f780f4ec86c269c278eb81d6458d53ea8c0d7bfe78eadae56e124a529d6ffa6bc"]}}}]} 973391ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973392ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973493ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973558ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973682ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973756ms th_a application.cpp:421 handle_transaction ] Got transaction from network 973823ms th_a application.cpp:421 handle_transaction ] Got transaction from network witness_node: /home/calabiyau/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Aborted (core dumped)

Woke up to this too

Code: [Select]
3169758ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":507,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"","data":{"trx":{"ref_block_num":60494,"ref_block_prefix":2734476150,"expiration":"2015-09-14T05:56:32","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["205c4049776969e7b3fa9ad3ee401a46b757a6b0821dcf2c0c2f4e79c9beac8bf60c37d51f490092708be2348d11228ea6ad225db2d884a96b26c5b990e6746ada"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-14T05:52:49"},"format":"","data":{"trx":{"ref_block_num":60494,"ref_block_prefix":2734476150,"expiration":"2015-09-14T05:56:32","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.63354","to":"1.2.17263","amount":{"amount":1,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["205c4049776969e7b3fa9ad3ee401a46b757a6b0821dcf2c0c2f4e79c9beac8bf60c37d51f490092708be2348d11228ea6ad225db2d884a96b26c5b990e6746ada"]}}}]}

This problem (if not just a warning) seems to have disappeared now.

I think I have identified the cause of this problem. Can you confirm that it occurred while you were using the RPC interface?

No, I was not using RPC.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 15, 2015, 12:08:34 pm: Thanks for the crash reports. We are looking into them.
Title: Re: Test Net for Advanced Users
Post by: spartako on September 15, 2015, 12:13:20 pm: In my witness log I see this error (anyway it is not crashed and continue to produce blocks):

Code: [Select]
635026ms th_a application.cpp:383 handle_block ] Got block #206473 from network 635027ms th_a db_block.cpp:98 push_block ] new_block.block_num(): 206473 new_block.id(): 00032689071a6235803359fc4b6a6ed6db088c10 635033ms th_a db_with.hpp:80 ~pending_transaction ] Pending transaction became invalid after switching to block 00032689071a6235803359fc4b6a6ed6db088c10 635034ms th_a db_with.hpp:81 ~pending_transaction ] The invalid pending transaction is {"ref_block_num":9862,"ref_block_prefix":2768671,"expiration":"2015-09-15T12:10:51","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":10,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["204130f6705ded8e60306341c81b97f967283c50e30d48c2296dc03ee61e19f30759452f4f89bc113a696f009144a8f0c29c46812300982819a7e194dd7d4aebd7"],"operation_results":[[0,{}]]} 635036ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":508,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:10:35"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":564,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:10:35"},"format":"","data":{"trx":{"ref_block_num":9862,"ref_block_prefix":2768671,"expiration":"2015-09-15T12:10:51","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":10,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["204130f6705ded8e60306341c81b97f967283c50e30d48c2296dc03ee61e19f30759452f4f89bc113a696f009144a8f0c29c46812300982819a7e194dd7d4aebd7"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":206,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:10:35"},"format":"","data":{"trx":{"ref_block_num":9862,"ref_block_prefix":2768671,"expiration":"2015-09-15T12:10:51","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":10,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["204130f6705ded8e60306341c81b97f967283c50e30d48c2296dc03ee61e19f30759452f4f89bc113a696f009144a8f0c29c46812300982819a7e194dd7d4aebd7"]}}}]}
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 15, 2015, 12:30:29 pm: Code: [Select]
1657120ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d56377e74af799db9b758a71c7e9163979 1667123ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1667123ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d59c6c160f7174fbfbba5e6b8c63ae1b95 1672747ms th_a application.cpp:383 handle_block ] Got block #206558 from network 1672747ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206558 new_block.id(): 000326dee3d9a84169d0bdf5f0b46a459a768795 1672870ms th_a db_with.hpp:80 ~pending_transaction ] Pending transaction became invalid after switching to block 000326dee3d9a84169d0bdf5f0b46a459a768795 1672871ms th_a db_with.hpp:81 ~pending_transaction ] The invalid pending transaction is {"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:00","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":100,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["2028d818a60cd6ab98b5ad892c3a2e84b44346c8489b6ceadef390e741c9392ffb510f0da09874b52239b76cad57586ad2bcafa4606092bc75314c7093aa39a32d"],"operation_results":[[0,{}]]} 1672871ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":533,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"_pending_block.timestamp <= trx.expiration: ","data":{"pending.timestamp":"2015-09-15T12:27:55","trx.exp":"2015-09-15T12:21:00"}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"","data":{"trx":{"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:00","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":100,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["2028d818a60cd6ab98b5ad892c3a2e84b44346c8489b6ceadef390e741c9392ffb510f0da09874b52239b76cad57586ad2bcafa4606092bc75314c7093aa39a32d"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"","data":{"trx":{"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:00","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":100,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["2028d818a60cd6ab98b5ad892c3a2e84b44346c8489b6ceadef390e741c9392ffb510f0da09874b52239b76cad57586ad2bcafa4606092bc75314c7093aa39a32d"]}}}]} 1672871ms th_a db_with.hpp:80 ~pending_transaction ] Pending transaction became invalid after switching to block 000326dee3d9a84169d0bdf5f0b46a459a768795 1672871ms th_a db_with.hpp:81 ~pending_transaction ] The invalid pending transaction is {"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:01","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":100,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["2006c75e648704e5b50bd596c2bb7f5bb34f5799559a1116d82c8d490f773bc611244773c9ea44b4546e72e25842662b97adc1158b5e1428403fede8eba885f22e"],"operation_results":[[0,{}]]} 1672872ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":533,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"_pending_block.timestamp <= trx.expiration: ","data":{"pending.timestamp":"2015-09-15T12:27:55","trx.exp":"2015-09-15T12:21:01"}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"","data":{"trx":{"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:01","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":100,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["2006c75e648704e5b50bd596c2bb7f5bb34f5799559a1116d82c8d490f773bc611244773c9ea44b4546e72e25842662b97adc1158b5e1428403fede8eba885f22e"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"","data":{"trx":{"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:01","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":100,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["2006c75e648704e5b50bd596c2bb7f5bb34f5799559a1116d82c8d490f773bc611244773c9ea44b4546e72e25842662b97adc1158b5e1428403fede8eba885f22e"]}}}]} 1672872ms th_a db_with.hpp:80 ~pending_transaction ] Pending transaction became invalid after switching to block 000326dee3d9a84169d0bdf5f0b46a459a768795 1672872ms th_a db_with.hpp:81 ~pending_transaction ] The invalid pending transaction is {"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:00","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":10,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["1f533969fa5a32713259232de97ab741958885d7e5f638d9cd8915cf416357c3c65c54365f2fce8aa89c44893fb30639bc623836ae93b13976a3906699fe581954"],"operation_results":[[0,{}]]} 1672872ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":533,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"_pending_block.timestamp <= trx.expiration: ","data":{"pending.timestamp":"2015-09-15T12:27:55","trx.exp":"2015-09-15T12:21:00"}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"","data":{"trx":{"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:00","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":10,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["1f533969fa5a32713259232de97ab741958885d7e5f638d9cd8915cf416357c3c65c54365f2fce8aa89c44893fb30639bc623836ae93b13976a3906699fe581954"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"","data":{"trx":{"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:00","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":10,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["1f533969fa5a32713259232de97ab741958885d7e5f638d9cd8915cf416357c3c65c54365f2fce8aa89c44893fb30639bc623836ae93b13976a3906699fe581954"]}}}]}
Not getting new blocks atm .. seems stuck
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 15, 2015, 12:31:21 pm: Code: [Select]
1732104ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1732104ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d54047d70832f0b643458cad10f121f661 1737105ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1737105ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d508b9036f52b63162bb2561d47b2988d9 1747107ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1747107ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d532008089670958f7496e38e4b2537e3e 1757103ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1757104ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d51bbe23a5c436dd55b2b4366a59d0906c 1762108ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1762109ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d56496799377d7f45fd9e367cc51ae72fb 1767104ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1767104ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d55790fa2d0fdcd09c02bbf0e8efa37e28 1777116ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1777116ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d5d595541d5c3e5691666fc52a9a72dbd1 1782104ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1782104ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d5c5706a78afd68b1bfc9624bca0082f73 1787106ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1787106ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d5173ef9325e7fe14bb657bdb8a5e38dce 1792105ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1792105ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d538b13494e6dfea6455ae8baa802ec509 1807107ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1807107ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d5da8d3ee1d5ae32ce20266bac1006794c 1812112ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1812113ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d5f1de54377d4aacbb540aa1240c55cdd6 1822106ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1822106ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d5990eb7c1330bde9dc37931367c4d47ff 1827107ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1827108ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d5c6d5ebf67c31a4cbdde664dc96d82d15 1832107ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1832107ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d5a25274db6aaeec31adc1717a6fe48767Do I get the same (different) block over and over?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 15, 2015, 12:39:00 pm: I have added additional debug messages around those assert crashes to give us better insight into the state at the time of the crash.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 15, 2015, 12:41:10 pm: Quote from: xeroc on September 15, 2015, 12:30:29 pm
Code: [Select]
1657120ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d56377e74af799db9b758a71c7e9163979 1667123ms th_a application.cpp:383 handle_block ] Got block #206549 from network 1667123ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d59c6c160f7174fbfbba5e6b8c63ae1b95 1672747ms th_a application.cpp:383 handle_block ] Got block #206558 from network 1672747ms th_a db_block.cpp:97 push_block ] new_block.block_num(): 206558 new_block.id(): 000326dee3d9a84169d0bdf5f0b46a459a768795 1672870ms th_a db_with.hpp:80 ~pending_transaction ] Pending transaction became invalid after switching to block 000326dee3d9a84169d0bdf5f0b46a459a768795 1672871ms th_a db_with.hpp:81 ~pending_transaction ] The invalid pending transaction is {"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:00","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":100,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["2028d818a60cd6ab98b5ad892c3a2e84b44346c8489b6ceadef390e741c9392ffb510f0da09874b52239b76cad57586ad2bcafa4606092bc75314c7093aa39a32d"],"operation_results":[[0,{}]]} 1672871ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":533,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"_pending_block.timestamp <= trx.expiration: ","data":{"pending.timestamp":"2015-09-15T12:27:55","trx.exp":"2015-09-15T12:21:00"}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"","data":{"trx":{"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:00","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":100,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["2028d818a60cd6ab98b5ad892c3a2e84b44346c8489b6ceadef390e741c9392ffb510f0da09874b52239b76cad57586ad2bcafa4606092bc75314c7093aa39a32d"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"","data":{"trx":{"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:00","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":100,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["2028d818a60cd6ab98b5ad892c3a2e84b44346c8489b6ceadef390e741c9392ffb510f0da09874b52239b76cad57586ad2bcafa4606092bc75314c7093aa39a32d"]}}}]} 1672871ms th_a db_with.hpp:80 ~pending_transaction ] Pending transaction became invalid after switching to block 000326dee3d9a84169d0bdf5f0b46a459a768795 1672871ms th_a db_with.hpp:81 ~pending_transaction ] The invalid pending transaction is {"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:01","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":100,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["2006c75e648704e5b50bd596c2bb7f5bb34f5799559a1116d82c8d490f773bc611244773c9ea44b4546e72e25842662b97adc1158b5e1428403fede8eba885f22e"],"operation_results":[[0,{}]]} 1672872ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":533,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"_pending_block.timestamp <= trx.expiration: ","data":{"pending.timestamp":"2015-09-15T12:27:55","trx.exp":"2015-09-15T12:21:01"}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"","data":{"trx":{"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:01","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":100,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["2006c75e648704e5b50bd596c2bb7f5bb34f5799559a1116d82c8d490f773bc611244773c9ea44b4546e72e25842662b97adc1158b5e1428403fede8eba885f22e"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"","data":{"trx":{"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:01","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":100,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["2006c75e648704e5b50bd596c2bb7f5bb34f5799559a1116d82c8d490f773bc611244773c9ea44b4546e72e25842662b97adc1158b5e1428403fede8eba885f22e"]}}}]} 1672872ms th_a db_with.hpp:80 ~pending_transaction ] Pending transaction became invalid after switching to block 000326dee3d9a84169d0bdf5f0b46a459a768795 1672872ms th_a db_with.hpp:81 ~pending_transaction ] The invalid pending transaction is {"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:00","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":10,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["1f533969fa5a32713259232de97ab741958885d7e5f638d9cd8915cf416357c3c65c54365f2fce8aa89c44893fb30639bc623836ae93b13976a3906699fe581954"],"operation_results":[[0,{}]]} 1672872ms th_a db_with.hpp:82 ~pending_transaction ] The invalid pending transaction caused exception {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":533,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"_pending_block.timestamp <= trx.expiration: ","data":{"pending.timestamp":"2015-09-15T12:27:55","trx.exp":"2015-09-15T12:21:00"}},{"context":{"level":"warn","file":"db_block.cpp","line":563,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"","data":{"trx":{"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:00","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":10,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["1f533969fa5a32713259232de97ab741958885d7e5f638d9cd8915cf416357c3c65c54365f2fce8aa89c44893fb30639bc623836ae93b13976a3906699fe581954"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":205,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-15T12:27:52"},"format":"","data":{"trx":{"ref_block_num":9949,"ref_block_prefix":2962347885,"expiration":"2015-09-15T12:21:00","operations":[[0,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"from":"1.2.28323","to":"1.2.69491","amount":{"amount":10,"asset_id":"1.3.0"},"extensions":[]}]],"extensions":[],"signatures":["1f533969fa5a32713259232de97ab741958885d7e5f638d9cd8915cf416357c3c65c54365f2fce8aa89c44893fb30639bc623836ae93b13976a3906699fe581954"]}}}]}
Not getting new blocks atm .. seems stuck

I am seeing the same thing on my node.

Except it appears that someone sent me block Got block #206566 from network in the middle of a stream of blocks at 206549..
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 15, 2015, 12:52:36 pm: Looks like the master node with the init witnesses is stuck (probably because Ben hasn't been around to update it with all the latest changes)

Code: [Select]
2931434ms th_a application.cpp:688 get_blockchain_synop ] synopsis: ["000326d238e7ae19d2c3835531c0ba5ae8024b78"] 2931786ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206547 new_block.id(): 000326d32d03860502c20f80cfba7188a58902cd new_block.witness: 1.6.28 new_block.timestamp: 2015-09-15T12:19:15 2931787ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206548 new_block.id(): 000326d418f9954d1a053be245d67abcc74fb333 new_block.witness: 1.6.42 new_block.timestamp: 2015-09-15T12:19:25 2931787ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d5b6eeec78e0cf9c0a6f4b7c495150568e new_block.witness: 1.6.24 new_block.timestamp: 2015-09-15T12:19:30 2931788ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206550 new_block.id(): 000326d66e59c5d4d44f3d7e24bc8202b8fc822d new_block.witness: 1.6.13 new_block.timestamp: 2015-09-15T12:19:35 2931788ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206551 new_block.id(): 000326d7acf81a715dc0d1f3ddd037ed54f36ab5 new_block.witness: 1.6.58 new_block.timestamp: 2015-09-15T12:19:40 2931789ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206552 new_block.id(): 000326d8568bc6fa597261862a7186dcd8a98667 new_block.witness: 1.6.69 new_block.timestamp: 2015-09-15T12:19:45 2931790ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206553 new_block.id(): 000326d9a89fbb94f98652b537b6858d3a07269d new_block.witness: 1.6.68 new_block.timestamp: 2015-09-15T12:19:50 2931790ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206554 new_block.id(): 000326da9c0f44e5ff5ea5ee4019a0a1ccdb3f66 new_block.witness: 1.6.39 new_block.timestamp: 2015-09-15T12:19:55 2931791ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206555 new_block.id(): 000326dbba7f985cd09b8b9b2492d14bc7e18ddb new_block.witness: 1.6.51 new_block.timestamp: 2015-09-15T12:20:00 2931847ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206556 new_block.id(): 000326dce6e9ebaf766cae6139a539a731893c9e new_block.witness: 1.6.5252 new_block.timestamp: 2015-09-15T12:20:25 2931847ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206557 new_block.id(): 000326dd6dd791b001061dff9002e71ad2e3a85f new_block.witness: 1.6.1063 new_block.timestamp: 2015-09-15T12:20:30 2931848ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206558 new_block.id(): 000326dee3d9a84169d0bdf5f0b46a459a768795 new_block.witness: 1.6.1538 new_block.timestamp: 2015-09-15T12:27:50 2931902ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206559 new_block.id(): 000326df5f1d8789b1d4be4fcc709f488736b3f0 new_block.witness: 1.6.1527 new_block.timestamp: 2015-09-15T12:30:45 2931958ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206560 new_block.id(): 000326e05ee43c32b52bd4924d9ef846da414ff3 new_block.witness: 1.6.4232 new_block.timestamp: 2015-09-15T12:32:15 2931959ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206561 new_block.id(): 000326e15aad53e16fae3eaeb3f904dccbeea335 new_block.witness: 1.6.3968 new_block.timestamp: 2015-09-15T12:32:25 2931959ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206562 new_block.id(): 000326e27314e948f62035d14f5dbcf9774bb2e7 new_block.witness: 1.6.1527 new_block.timestamp: 2015-09-15T12:36:25 2932021ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206563 new_block.id(): 000326e3b3a2f68bf1004ac6360033b34bdff358 new_block.witness: 1.6.1538 new_block.timestamp: 2015-09-15T12:37:15 2932021ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206564 new_block.id(): 000326e40425207efe4ef960af42e0e918fb77c5 new_block.witness: 1.6.1063 new_block.timestamp: 2015-09-15T12:37:35 2932022ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206565 new_block.id(): 000326e5289b7f016a6903f87bf36ea6adac931c new_block.witness: 1.6.4232 new_block.timestamp: 2015-09-15T12:37:45 2932022ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206566 new_block.id(): 000326e65b9d1cec3c728ac2ee653925da819a1d new_block.witness: 1.6.5247 new_block.timestamp: 2015-09-15T12:39:55 2932022ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206567 new_block.id(): 000326e79d32f42bb6d06efb780a4a15b9b946a4 new_block.witness: 1.6.3968 new_block.timestamp: 2015-09-15T12:40:25 2932081ms th_a application.cpp:688 get_blockchain_synop ] synopsis: ["000326d238e7ae19d2c3835531c0ba5ae8024b78","000326dd6dd791b001061dff9002e71ad2e3a85f","000326e3b3a2f68bf1004ac6360033b34bdff358","000326e65b9d1cec3c728ac2ee653925da819a1d","000326e79d32f42bb6d06efb780a4a15b9b946a4"]
It looks like everyone who has upgraded is still producing blocks when you get the chance.

When Ben gets in today I will have him update the main node.
Title: Re: Test Net for Advanced Users
Post by: abit on September 15, 2015, 07:14:00 pm: Quote from: bytemaster on September 15, 2015, 12:52:36 pm
Looks like the master node with the init witnesses is stuck (probably because Ben hasn't been around to update it with all the latest changes)

Code: [Select]
2931434ms th_a application.cpp:688 get_blockchain_synop ] synopsis: ["000326d238e7ae19d2c3835531c0ba5ae8024b78"] 2931786ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206547 new_block.id(): 000326d32d03860502c20f80cfba7188a58902cd new_block.witness: 1.6.28 new_block.timestamp: 2015-09-15T12:19:15 2931787ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206548 new_block.id(): 000326d418f9954d1a053be245d67abcc74fb333 new_block.witness: 1.6.42 new_block.timestamp: 2015-09-15T12:19:25 2931787ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206549 new_block.id(): 000326d5b6eeec78e0cf9c0a6f4b7c495150568e new_block.witness: 1.6.24 new_block.timestamp: 2015-09-15T12:19:30 2931788ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206550 new_block.id(): 000326d66e59c5d4d44f3d7e24bc8202b8fc822d new_block.witness: 1.6.13 new_block.timestamp: 2015-09-15T12:19:35 2931788ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206551 new_block.id(): 000326d7acf81a715dc0d1f3ddd037ed54f36ab5 new_block.witness: 1.6.58 new_block.timestamp: 2015-09-15T12:19:40 2931789ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206552 new_block.id(): 000326d8568bc6fa597261862a7186dcd8a98667 new_block.witness: 1.6.69 new_block.timestamp: 2015-09-15T12:19:45 2931790ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206553 new_block.id(): 000326d9a89fbb94f98652b537b6858d3a07269d new_block.witness: 1.6.68 new_block.timestamp: 2015-09-15T12:19:50 2931790ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206554 new_block.id(): 000326da9c0f44e5ff5ea5ee4019a0a1ccdb3f66 new_block.witness: 1.6.39 new_block.timestamp: 2015-09-15T12:19:55 2931791ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206555 new_block.id(): 000326dbba7f985cd09b8b9b2492d14bc7e18ddb new_block.witness: 1.6.51 new_block.timestamp: 2015-09-15T12:20:00 2931847ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206556 new_block.id(): 000326dce6e9ebaf766cae6139a539a731893c9e new_block.witness: 1.6.5252 new_block.timestamp: 2015-09-15T12:20:25 2931847ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206557 new_block.id(): 000326dd6dd791b001061dff9002e71ad2e3a85f new_block.witness: 1.6.1063 new_block.timestamp: 2015-09-15T12:20:30 2931848ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206558 new_block.id(): 000326dee3d9a84169d0bdf5f0b46a459a768795 new_block.witness: 1.6.1538 new_block.timestamp: 2015-09-15T12:27:50 2931902ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206559 new_block.id(): 000326df5f1d8789b1d4be4fcc709f488736b3f0 new_block.witness: 1.6.1527 new_block.timestamp: 2015-09-15T12:30:45 2931958ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206560 new_block.id(): 000326e05ee43c32b52bd4924d9ef846da414ff3 new_block.witness: 1.6.4232 new_block.timestamp: 2015-09-15T12:32:15 2931959ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206561 new_block.id(): 000326e15aad53e16fae3eaeb3f904dccbeea335 new_block.witness: 1.6.3968 new_block.timestamp: 2015-09-15T12:32:25 2931959ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206562 new_block.id(): 000326e27314e948f62035d14f5dbcf9774bb2e7 new_block.witness: 1.6.1527 new_block.timestamp: 2015-09-15T12:36:25 2932021ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206563 new_block.id(): 000326e3b3a2f68bf1004ac6360033b34bdff358 new_block.witness: 1.6.1538 new_block.timestamp: 2015-09-15T12:37:15 2932021ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206564 new_block.id(): 000326e40425207efe4ef960af42e0e918fb77c5 new_block.witness: 1.6.1063 new_block.timestamp: 2015-09-15T12:37:35 2932022ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206565 new_block.id(): 000326e5289b7f016a6903f87bf36ea6adac931c new_block.witness: 1.6.4232 new_block.timestamp: 2015-09-15T12:37:45 2932022ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206566 new_block.id(): 000326e65b9d1cec3c728ac2ee653925da819a1d new_block.witness: 1.6.5247 new_block.timestamp: 2015-09-15T12:39:55 2932022ms th_a db_block.cpp:105 push_block ] new_block.block_num(): 206567 new_block.id(): 000326e79d32f42bb6d06efb780a4a15b9b946a4 new_block.witness: 1.6.3968 new_block.timestamp: 2015-09-15T12:40:25 2932081ms th_a application.cpp:688 get_blockchain_synop ] synopsis: ["000326d238e7ae19d2c3835531c0ba5ae8024b78","000326dd6dd791b001061dff9002e71ad2e3a85f","000326e3b3a2f68bf1004ac6360033b34bdff358","000326e65b9d1cec3c728ac2ee653925da819a1d","000326e79d32f42bb6d06efb780a4a15b9b946a4"]
It looks like everyone who has upgraded is still producing blocks when you get the chance.

When Ben gets in today I will have him update the main node.

Code: [Select]
247300ms th_a db_block.cpp:181 _push_block ] Failed to push new block: 3070000 undo_database_exception: undo database exception The database does not have enough undo history to support a blockchain with so many missed blocks. Please add a checkpoint if you would like to continue applying blocks beyond this point. {"recently_missed":13547,"max_undo":1000} th_a db_update.cpp:72 update_global_dynamic_data {"next_block.block_num()":206568} th_a db_block.cpp:469 _apply_blockWe may need a new chain if the master node missed too many blocks.
Title: Re: Test Net for Advanced Users
Post by: Fox on September 16, 2015, 03:01:15 am: May I get an update on the current Testnet parameters/status?

known active seed node(s) :
chain_id :
head_block_id (at time) :
Title: Re: Test Net for Advanced Users
Post by: puppies on September 16, 2015, 06:19:45 am: Quote from: Fox on September 16, 2015, 03:01:15 am
May I get an update on the current Testnet parameters/status?

known active seed node(s) :
chain_id :
head_block_id (at time) :

At this point the test net is dead. We are waiting on a new one.
Code: [Select]
info { "head_block_num": 206567, "head_block_id": "000326e79d32f42bb6d06efb780a4a15b9b946a4", "head_block_age": "18 hours old", "next_maintenance_time": "18 hours ago", "chain_id": "ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3", "participation": "6.25000000000000000", "active_witnesses": [
Title: Re: Test Net for Advanced Users
Post by: monsterer on September 16, 2015, 07:26:34 am: Quote from: puppies on September 16, 2015, 06:19:45 am
At this point the test net is dead. We are waiting on a new one.

How do we have a live countdown to launch when the testnet doesn't even work? Am I missing something here?
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 16, 2015, 09:48:38 am: What is an easy way to compare performance of one of my VPS witnesses to my cubox (arm) witness?
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 16, 2015, 09:52:01 am: Quote from: iHashFury on September 16, 2015, 09:48:38 am
What is an easy way to compare performance of one of my VPS witnesses to my cubox (arm) witness?
--replay-blockchain
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 16, 2015, 09:52:23 am: Quote from: monsterer on September 16, 2015, 07:26:34 am
Quote from: puppies on September 16, 2015, 06:19:45 am
At this point the test net is dead. We are waiting on a new one.

How do we have a live countdown to launch when the testnet doesn't even work? Am I missing something here?
init witnesses are down for an upgrade
Title: Re: Test Net for Advanced Users
Post by: Fox on September 16, 2015, 04:53:48 pm: Quote from: xeroc on September 16, 2015, 09:52:23 am
init witnesses are down for an upgrade
Very well.

Do you expect a new genesis file will be used with the next testnet?
If yes, may I request the transfer fees be eliminated and the block interval decreased to 3 seconds to match the anticipated launch parameter?

Is anyone able to speak to an estimated time for launching the next testnet?

Thanks in advance,
Fox
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 16, 2015, 04:57:40 pm: Afaik next testnet within the day ... i recall bm talking about zero fees .. lets see what happens... we can reduce fees via committee .. worth testing anyways
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 16, 2015, 05:28:09 pm: We are preparing a new test network that will be a dry-run for the actual BTS 2.0 launch process. This means the following:

1. It will have 3 second blocks
2. It will have 1 real computer per witness (but we will control all initial witnesses)
3. There will only be 11 initial witnesses, and we will VOTE in more
4. We will have 1 hour maintenance intervals, this should increase reindexing time by a factor 12
5. We will have lower transfer fees for testing purposes
6. We will be producing price feeds for bitassets
7. We will be producing a Mac / Windows GUI distribution
8. There will be a new genesis file from a recent snapshot.

The GUI distributions will be available next week. This week we are focusing on our infrastructure.

Before we can launch this test network we are putting in some scheduled minor hard-forking changes that have built up over the past several weeks of the last test network.

Our goal for this network is to pretend it is the real launch and to have it go as smoothly as possible.
Title: Re: Test Net for Advanced Users
Post by: nomoreheroes7 on September 16, 2015, 05:40:51 pm: Quote from: bytemaster on September 16, 2015, 05:28:09 pm
We are preparing a new test network that will be a dry-run for the actual BTS 2.0 launch process. This means the following:

1. It will have 3 second blocks
2. It will have 1 real computer per witness (but we will control all initial witnesses)
3. There will only be 11 initial witnesses, and we will VOTE in more
4. We will have 1 hour maintenance intervals, this should increase reindexing time by a factor 12
5. We will have lower transfer fees for testing purposes
6. We will be producing price feeds for bitassets
7. We will be producing a Mac / Windows GUI distribution
8. There will be a new genesis file from a recent snapshot.

The GUI distributions will be available next week. This week we are focusing on our infrastructure.

Before we can launch this test network we are putting in some scheduled minor hard-forking changes that have built up over the past several weeks of the last test network.

Our goal for this network is to pretend it is the real launch and to have it go as smoothly as possible.

See now that's cool. Here's hoping for a smooth launch. +5%
Title: Re: Test Net for Advanced Users
Post by: Fox on September 16, 2015, 06:08:36 pm: Quote from: bytemaster on September 16, 2015, 05:28:09 pm
We are preparing a new test network that will be a dry-run [...] Our goal for this network is to pretend it is the real launch and to have it go as smoothly as possible.
Very much appreciate the confirmation.
Title: Re: Test Net for Advanced Users
Post by: BTSdac on September 16, 2015, 06:21:00 pm: Quote from: bytemaster on September 16, 2015, 05:28:09 pm
We are preparing a new test network that will be a dry-run for the actual BTS 2.0 launch process. This means the following:

1. It will have 3 second blocks
2. It will have 1 real computer per witness (but we will control all initial witnesses)
3. There will only be 11 initial witnesses, and we will VOTE in more
4. We will have 1 hour maintenance intervals, this should increase reindexing time by a factor 12
5. We will have lower transfer fees for testing purposes
6. We will be producing price feeds for bitassets
7. We will be producing a Mac / Windows GUI distribution
8. There will be a new genesis file from a recent snapshot.

The GUI distributions will be available next week. This week we are focusing on our infrastructure.

Before we can launch this test network we are putting in some scheduled minor hard-forking changes that have built up over the past several weeks of the last test network.

Our goal for this network is to pretend it is the real launch and to have it go as smoothly as possible.
happy to hear this +5%
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 16, 2015, 06:56:12 pm: +5% .. this means you will include all assets and open (short) orders?

Looking forward
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 16, 2015, 07:02:45 pm: +5%

engines idle.....
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 16, 2015, 07:16:34 pm: Quote from: CalabiYau on September 16, 2015, 07:02:45 pm
+5%

engines idle.....

(http://www.f1fanatic.co.uk/wp-content/uploads/2008/06/canadian-grandprix_start_2008.jpg)
Title: Re: Test Net for Advanced Users
Post by: lakerta06 on September 16, 2015, 07:30:32 pm: Quote from: bytemaster on September 16, 2015, 05:28:09 pm
We are preparing a new test network that will be a dry-run for the actual BTS 2.0 launch process. This means the following:

1. It will have 3 second blocks
2. It will have 1 real computer per witness (but we will control all initial witnesses)
3. There will only be 11 initial witnesses, and we will VOTE in more
4. We will have 1 hour maintenance intervals, this should increase reindexing time by a factor 12
5. We will have lower transfer fees for testing purposes
6. We will be producing price feeds for bitassets
7. We will be producing a Mac / Windows GUI distribution
8. There will be a new genesis file from a recent snapshot.

The GUI distributions will be available next week. This week we are focusing on our infrastructure.

Before we can launch this test network we are putting in some scheduled minor hard-forking changes that have built up over the past several weeks of the last test network.

Our goal for this network is to pretend it is the real launch and to have it go as smoothly as possible.
Is the 0.9.3 update coming, so that we can easily import keys?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 16, 2015, 09:22:36 pm: Quote from: lakerta06 on September 16, 2015, 07:30:32 pm
Quote from: bytemaster on September 16, 2015, 05:28:09 pm
We are preparing a new test network that will be a dry-run for the actual BTS 2.0 launch process. This means the following:

1. It will have 3 second blocks
2. It will have 1 real computer per witness (but we will control all initial witnesses)
3. There will only be 11 initial witnesses, and we will VOTE in more
4. We will have 1 hour maintenance intervals, this should increase reindexing time by a factor 12
5. We will have lower transfer fees for testing purposes
6. We will be producing price feeds for bitassets
7. We will be producing a Mac / Windows GUI distribution
8. There will be a new genesis file from a recent snapshot.

The GUI distributions will be available next week. This week we are focusing on our infrastructure.

Before we can launch this test network we are putting in some scheduled minor hard-forking changes that have built up over the past several weeks of the last test network.

Our goal for this network is to pretend it is the real launch and to have it go as smoothly as possible.
Is the 0.9.3 update coming, so that we can easily import keys?

Just released it. Windows build is in the works.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 17, 2015, 02:30:35 am: 0.9.3 has some issues?
Title: Re: Test Net for Advanced Users
Post by: Fox on September 17, 2015, 03:05:44 am: Quote from: clayop on September 17, 2015, 02:30:35 am
0.9.3 has some issues?
Source?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 17, 2015, 03:16:31 am: Quote from: Fox on September 17, 2015, 03:05:44 am
Quote from: clayop on September 17, 2015, 02:30:35 am
0.9.3 has some issues?
Source?

Mac binary was removed.
Title: Re: Test Net for Advanced Users
Post by: liondani on September 17, 2015, 03:04:26 pm: Quote from: bytemaster on September 16, 2015, 09:22:36 pm
Quote from: lakerta06 on September 16, 2015, 07:30:32 pm
Quote from: bytemaster on September 16, 2015, 05:28:09 pm
We are preparing a new test network that will be a dry-run for the actual BTS 2.0 launch process. This means the following:

1. It will have 3 second blocks
2. It will have 1 real computer per witness (but we will control all initial witnesses)
3. There will only be 11 initial witnesses, and we will VOTE in more
4. We will have 1 hour maintenance intervals, this should increase reindexing time by a factor 12
5. We will have lower transfer fees for testing purposes
6. We will be producing price feeds for bitassets
7. We will be producing a Mac / Windows GUI distribution
8. There will be a new genesis file from a recent snapshot.

The GUI distributions will be available next week. This week we are focusing on our infrastructure.

Before we can launch this test network we are putting in some scheduled minor hard-forking changes that have built up over the past several weeks of the last test network.

Our goal for this network is to pretend it is the real launch and to have it go as smoothly as possible.
Is the 0.9.3 update coming, so that we can easily import keys?

Just released it. Windows build is in the works.

will you release 0.9.3v for DevShares also?
Title: Re: Test Net for Advanced Users
Post by: sudo on September 17, 2015, 04:18:29 pm: Quote from: bytemaster on September 16, 2015, 05:28:09 pm
We are preparing a new test network that will be a dry-run for the actual BTS 2.0 launch process. This means the following:

1. It will have 3 second blocks
2. It will have 1 real computer per witness (but we will control all initial witnesses)
3. There will only be 11 initial witnesses, and we will VOTE in more
4. We will have 1 hour maintenance intervals, this should increase reindexing time by a factor 12
5. We will have lower transfer fees for testing purposes
6. We will be producing price feeds for bitassets
7. We will be producing a Mac / Windows GUI distribution
8. There will be a new genesis file from a recent snapshot.

The GUI distributions will be available next week. This week we are focusing on our infrastructure.

Before we can launch this test network we are putting in some scheduled minor hard-forking changes that have built up over the past several weeks of the last test network.

Our goal for this network is to pretend it is the real launch and to have it go as smoothly as possible.

Windows GUI distribution +5%
Title: Re: Test Net for Advanced Users
Post by: wuyanren on September 17, 2015, 05:41:05 pm: https://graphene.bitshares.org/#/explorer/blocks 。 Stop for a long time. Don't test it?
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 17, 2015, 05:44:33 pm: Testnet has stopped .. next one is close
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 17, 2015, 05:54:49 pm: We just pushed a significant set of updates designed to fix issues discovered during the prior test net.

1. Transactions from an orphaned block now get migrated (if possible) to the main chain to be included. This should fix a lot of missing transaction issues.
2. We fixed an issue where nodes could get in an inconsistent state.
3. We added unit tests to check for these conditions.

Perhaps the most significant change to the meaning of transactions is that they no longer reference the "new block's timestamp" and instead only reference chainstate from the
prior head block or the application of prior transactions in the current block. This decision was made to ensure that all state referenced by a transaction that exists at the
time the transaction was first received still exists at the time the block is eventually produced. This means that for the purposes of expiration all transactions occur as if
the time was the head block time and not as if the time was the time the block that included them was created. Implication: If you have a transaction that expires at 1:23:01 and
the head block time is 1:23:00 and the next block produced is 1:30:00 then the block at 1:30:00 can include the transaction that expired at 1:23:01.

Considering our goal of 1 second blocks and 99.9% participation this particular issue should not make any significant difference.
Title: Re: Test Net for Advanced Users
Post by: Fox on September 17, 2015, 08:57:18 pm: I see the recent commit, but do not see a new tag or release. Is there a new testnet up using master? What is the seed node(s) and where is the genesis.json file located?
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 17, 2015, 09:08:45 pm: I did a checkout of Master and got a pile of new stuff. Nothing in the submodules though.

Code: [Select]
Updating 81cc8e4..f0502ee Fast-forward libraries/app/database_api.cpp | 1 + libraries/app/impacted.cpp | 11 +++++++- libraries/chain/db_block.cpp | 174 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------------------------------------- libraries/chain/db_maint.cpp | 21 +++------------ libraries/chain/db_management.cpp | 44 +++++++++--------------------- libraries/chain/db_market.cpp | 11 ++++++-- libraries/chain/db_update.cpp | 6 ----- libraries/chain/fork_database.cpp | 2 ++ libraries/chain/include/graphene/chain/database.hpp | 10 ++++--- libraries/chain/include/graphene/chain/db_with.hpp | 30 ++++++++++++++++----- libraries/chain/include/graphene/chain/exceptions.hpp | 2 ++ libraries/chain/include/graphene/chain/protocol/asset_ops.hpp | 25 +++++++++++++++++ libraries/chain/include/graphene/chain/protocol/operations.hpp | 6 +++-- libraries/chain/proposal_evaluator.cpp | 2 +- libraries/chain/vesting_balance_evaluator.cpp | 2 +- tests/common/database_fixture.cpp | 14 +++++++--- tests/tests/authority_tests.cpp | 32 ++++++++++++---------- tests/tests/block_tests.cpp | 8 +++--- 18 files changed, 231 insertions(+), 170 deletions(-) james@james-desktop:~/github/graphene$ git submodule update --init --recursive james@james-desktop:~/github/graphene$
Title: Re: Test Net for Advanced Users
Post by: abit on September 17, 2015, 11:30:17 pm: Quote from: Fox on September 17, 2015, 08:57:18 pm
I see the recent commit, but do not see a new tag or release. Is there a new testnet up using master? What is the seed node(s) and where is the genesis.json file located?
I think there is no new test net right now. The last one is dead, so we need to wait for the new one.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 17, 2015, 11:46:58 pm: Quote from: abit on September 17, 2015, 11:30:17 pm
Quote from: Fox on September 17, 2015, 08:57:18 pm
I see the recent commit, but do not see a new tag or release. Is there a new testnet up using master? What is the seed node(s) and where is the genesis.json file located?
I think there is no new test net right now. The last one is dead, so we need to wait for the new one.

Yeah. I know I'm anxious for a new testnet. Nothing we can do but wait.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 18, 2015, 09:25:09 pm: https://github.com/cryptonomex/graphene/releases

New Testnet is Here!

Please post your witness name so I can vote them in and add them to the growing list of active witnesses.
Title: Re: Test Net for Advanced Users
Post by: CLains on September 18, 2015, 09:29:04 pm: We rollin' 8) +5%
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 18, 2015, 09:36:29 pm: Testers that want to flood the network, do not use your witness node as the RPC server.

Also please take note of the new logging to the console that includes latencies of blocks received. Those on a DigitalOcean machine in NYC3 should have around 0 MS latency for many blocks ;)

Also... to get your witness voted in you will have to vote for all 11 init witnesses PLUS your own witness.
Title: Re: Test Net for Advanced Users
Post by: abit on September 18, 2015, 09:47:17 pm: Quote from: bytemaster on September 18, 2015, 09:36:29 pm
Testers that want to flood the network, do not use your witness node as the RPC server.

Also please take note of the new logging to the console that includes latencies of blocks received. Those on a DigitalOcean machine in NYC3 should have around 0 MS latency for many blocks ;)

Also... to get your witness voted in you will have to vote for all 11 init witnesses PLUS your own witness.
Building..
Title: Re: Test Net for Advanced Users
Post by: abit on September 18, 2015, 10:05:45 pm: Quote from: bytemaster on September 18, 2015, 09:25:09 pm
https://github.com/cryptonomex/graphene/releases

New Testnet is Here!

Please post your witness name so I can vote them in and add them to the growing list of active witnesses.

Running.
Code: [Select]
get_witness in.abit { "id": "1.6.5247", "witness_account": "1.2.38993", "last_aslot": 0, "signing_key": "GPH65XNUxWdYGqGyW9NtXdRpNntumLYT1cJ7CNE7F78Pwxrnx6cbV", "vote_id": "1:5267", "total_votes": 0, "url": "https://github.com/abitmore", "total_missed": 0 }
Title: Re: Test Net for Advanced Users
Post by: clayop on September 18, 2015, 10:13:05 pm: @bytemaster
When are windows and Mac binaries of 0.9.3 available?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 18, 2015, 10:14:48 pm: Quote from: clayop on September 18, 2015, 10:13:05 pm
@bytemaster
When are windows and Mac binaries of 0.9.3 available?

https://github.com/bitshares/bitshares/releases
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 18, 2015, 10:16:06 pm: Quote from: abit on September 18, 2015, 10:05:45 pm
Quote from: bytemaster on September 18, 2015, 09:25:09 pm
https://github.com/cryptonomex/graphene/releases

New Testnet is Here!

Please post your witness name so I can vote them in and add them to the growing list of active witnesses.

Running.
Code: [Select]
get_witness in.abit { "id": "1.6.5247", "witness_account": "1.2.38993", "last_aslot": 0, "signing_key": "GPH65XNUxWdYGqGyW9NtXdRpNntumLYT1cJ7CNE7F78Pwxrnx6cbV", "vote_id": "1:5267", "total_votes": 0, "url": "https://github.com/abitmore", "total_missed": 0 }

Voted: "next_maintenance_time": "44 minutes in the future" is when you will be active.
Title: Re: Test Net for Advanced Users
Post by: abit on September 18, 2015, 10:26:10 pm: Quote from: bytemaster on September 18, 2015, 10:16:06 pm
Quote from: abit on September 18, 2015, 10:05:45 pm
Quote from: bytemaster on September 18, 2015, 09:25:09 pm
https://github.com/cryptonomex/graphene/releases

New Testnet is Here!

Please post your witness name so I can vote them in and add them to the growing list of active witnesses.

Running.
Code: [Select]
get_witness in.abit { "id": "1.6.5247", "witness_account": "1.2.38993", "last_aslot": 0, "signing_key": "GPH65XNUxWdYGqGyW9NtXdRpNntumLYT1cJ7CNE7F78Pwxrnx6cbV", "vote_id": "1:5267", "total_votes": 0, "url": "https://github.com/abitmore", "total_missed": 0 }

Voted: "next_maintenance_time": "44 minutes in the future" is when you will be active.
Thanks.
How to vote for multiple witnesses in cli_wallet?

//Update:
It seems that it's impossible to vote for multiple witnesses in cli_wallet https://github.com/cryptonomex/graphene/issues/323
Title: Re: Test Net for Advanced Users
Post by: abit on September 18, 2015, 10:28:16 pm: https://graphene.bitshares.org is still running in test2 network?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 18, 2015, 10:31:41 pm: Quote from: abit on September 18, 2015, 10:28:16 pm
https://graphene.bitshares.org is still running in test2 network?

Probably not updated. Valentine is working on it over the weekend to get it ready.

I have a Mac binary GUI built that works, but am still working on deployment issues. Will likely resolve monday.
Title: Re: Test Net for Advanced Users
Post by: Fox on September 18, 2015, 10:36:16 pm: Anyone willing to transfer a small CORE amount to "fox" on test3?
Title: Re: Test Net for Advanced Users
Post by: puppies on September 18, 2015, 10:46:38 pm: Please vote dele-puppy in. 1.6.1527.

I'm stuck at work and can't flood yet, but I'll keep an eye on the vps with my witness on it.
Title: Re: Test Net for Advanced Users
Post by: lafona on September 18, 2015, 11:04:36 pm: My witness is up and running. If someone could vote it in, that would be awesome. Thanks :)

delegate-1.lafona
(1.6.1531)
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 18, 2015, 11:24:56 pm: Witness is up and running. Appreciate some votes.

Edit: new name

Code: [Select]
get_witness xeldal { "id": "1.6.4949", "witness_account": "1.2.86459",
Title: Re: Test Net for Advanced Users
Post by: Fox on September 18, 2015, 11:40:39 pm: The Fox witness node is operational. Thanks in advance for your votes.
Code: [Select]
get_witness fox { "id": "1.6.2104", "witness_account": "1.2.30566",
Title: Re: Test Net for Advanced Users
Post by: wackou on September 18, 2015, 11:54:01 pm: wackou now up and running

Code: [Select]
get_witness wackou { "id": "1.6.5248", "witness_account": "1.2.83349", "last_aslot": 0, "signing_key": "GPH8C1Cz3LDu732VT74bYvNE2G25NLghV96zcMnFwLd4Z6aXWup9i", "vote_id": "1:5268", "total_votes": 0, "url": "http://digitalgaia.io", "total_missed": 0 }
Title: Re: Test Net for Advanced Users
Post by: clayop on September 19, 2015, 12:11:18 am: delegate-clayop 1.6.1538
Title: Re: Test Net for Advanced Users
Post by: puppies on September 19, 2015, 12:30:15 am:    dele-puppy
delegate-1.lafona
delegate-clayop
fox
in.abit
init0
init1
init10
init11
init2
init3
init4
init5
init6
init7
init8
init9
wackou
xeldal

I think I got everybody. I don't know if I will have enough funds to get you in, or to increase the witness average.

If you are having a hard time voting for multiple witnesses with the cli you can use me as your proxy by
Code: [Select]
set_voting_proxy your-account-name puppies true
Title: Re: Test Net for Advanced Users
Post by: Fox on September 19, 2015, 12:51:41 am: Remind me of the precision of CORE. 5 or 6? Do we need 8.5M or 850K votes to be elected as a witness?

Code: [Select]
get_witness init10 { "id": "1.6.11", "witness_account": "1.2.110", ... "total_votes": "857124062634", ... }
To be honest, I was not planning to bring that much stake to this chain at this time. Your votes are appreciated.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 19, 2015, 12:56:58 am: Quote from: Fox on September 19, 2015, 12:51:41 am
Remind me of the precision of CORE. 5 or 6? Do we need 8.5M or 850K votes to be elected as a witness?

Code: [Select]
get_witness init10 { "id": "1.6.11", "witness_account": "1.2.110", ... "total_votes": "857124062634", ... }
To be honest, I was not planning to bring that much stake to this chain at this time. Your votes are appreciated.

thats not me. I think that is BM. We aren't trying to outvote the init witnesses. We are trying to increase the average number of witnesses voted for by account. That is how the number of witnesses that are active is determined. Or at least thats the way it was a couple of weeks ago, and I don't think that changed.

Should know if it worked in about 2 minutes.

edit. damnit looks like all that happened is abit got voted out.
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 01:00:59 am: Quote from: puppies on September 19, 2015, 12:56:58 am
Quote from: Fox on September 19, 2015, 12:51:41 am
Remind me of the precision of CORE. 5 or 6? Do we need 8.5M or 850K votes to be elected as a witness?

Code: [Select]
get_witness init10 { "id": "1.6.11", "witness_account": "1.2.110", ... "total_votes": "857124062634", ... }
To be honest, I was not planning to bring that much stake to this chain at this time. Your votes are appreciated.

thats not me. I think that is BM. We aren't trying to outvote the init witnesses. We are trying to increase the average number of witnesses voted for by account. That is how the number of witnesses that are active is determined. Or at least thats the way it was a couple of weeks ago, and I don't think that changed.

Should know if it worked in about 2 minutes.
Looks like BM voted me in, but voted out 1.6.11 (or init10?)
Don't know why.

//Edit:
Ah, I know, because in.abit voted for in.abit only in last round.
Looks like currently the max number of witnesses is 11.
After set proxy to puppies, in.abit votes for all witnesses, so it got voted out..
Title: Re: Test Net for Advanced Users
Post by: puppies on September 19, 2015, 01:08:49 am: Quote from: abit on September 19, 2015, 01:00:59 am
Quote from: puppies on September 19, 2015, 12:56:58 am
Quote from: Fox on September 19, 2015, 12:51:41 am
Remind me of the precision of CORE. 5 or 6? Do we need 8.5M or 850K votes to be elected as a witness?

Code: [Select]
get_witness init10 { "id": "1.6.11", "witness_account": "1.2.110", ... "total_votes": "857124062634", ... }
To be honest, I was not planning to bring that much stake to this chain at this time. Your votes are appreciated.

thats not me. I think that is BM. We aren't trying to outvote the init witnesses. We are trying to increase the average number of witnesses voted for by account. That is how the number of witnesses that are active is determined. Or at least thats the way it was a couple of weeks ago, and I don't think that changed.

Should know if it worked in about 2 minutes.
Looks like BM voted me in, but voted out 1.6.11 (or init10?)
Don't know why.

//Edit:
Ah, I know, because in.abit voted for in.abit only in last round.
Looks like currently the max number of witnesses is 11.
After set proxy to puppies, in.abit votes for all witnesses, so it got voted out..
I'll remove init 10 from my vote. That will get you back in in an hour. I think we will have to wait for dan to vote for more tomorrow. Sorry about that abit. I was hoping we could increase the witness slots.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 19, 2015, 01:31:20 am: Oh please don't vote me in now. I have some problems but cannot solve them now
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 19, 2015, 04:22:16 am: Please vote witness: riverhead (1.6.3968)

voted for witnesses 1.6.1->1.6.10, 1.6.5247, riverhead, in.abit, fox

Code: [Select]
get_witness riverhead { "id": "1.6.3968", "witness_account": "1.2.67253", "last_aslot": 0, "signing_key": "GPH6BJYGHftujnbttFFKX6YacnvsMd4sbJrbucg682GiU4vmXHTik", "vote_id": "1:3967", "total_votes": 0, "url": "", "total_missed": 0
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 19, 2015, 05:02:44 am: cli_wallet core dumps on exit for me:

Code: [Select]
james@james-desktop:~/github/graphene/programs/cli_wallet$ ./cli_wallet -w test3 --chain-id 0f8b631d7a9dfebf16d6776fab96b629a14429762bf9c3eb95db1e4e4af637a4 -s ws://192.168.1.11:8090 Logging RPC to file: logs/rpc/rpc.log 109742ms th_a main.cpp:114 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W 109743ms th_a main.cpp:118 main ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV 109743ms th_a main.cpp:119 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3 109745ms th_a main.cpp:166 main ] wdata.ws_server: ws://192.168.1.11:8090 109750ms th_a main.cpp:171 main ] wdata.ws_user: wdata.ws_password: 109765ms th_a wallet.cpp:700 load_wallet_file ] Account 1.2.2331 : "aliya" updated on chain 109771ms th_a thread.cpp:95 thread ] name:getline tid:140217568634624 111105ms th_a wallet.cpp:723 save_wallet_file ] saving wallet to file test3 pure virtual method called terminate called without an active exception Aborted (core dumped) james@james-desktop:~/github/graphene/programs/cli_wallet$
Title: Re: Test Net for Advanced Users
Post by: puppies on September 19, 2015, 05:10:18 am: Added you riverhead, but it won't be enough to bring you in. Unfortunately I am not a whale. Not even a dolphin.

On a side note, is there a feed script yet? If not what is the syntax to publish a feed manually?
publish_asset_feed(string, string, graphene::chain::price_feed, bool)
I was guessing account_name asset_name price broadcast? but thats not working. Might be because I am not voted in yet. If someone figures it out please post.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 19, 2015, 09:26:31 am: Thanks Puppies :)

witness node crashed though. I'll run it again in gdb however here are the last few lines of the console and p2p.log respectively.

Code: [Select]
1758265ms th_a application.cpp:428 handle_transaction ] Got transaction from network 1758281ms th_a application.cpp:428 handle_transaction ] Got transaction from network 1758299ms th_a application.cpp:428 handle_transaction ] Got transaction from network 1758394ms th_a application.cpp:428 handle_transaction ] Got transaction from network 1758398ms th_a application.cpp:388 handle_block ] Got block #11840 with time 2015-09-19T05:29:18 from network with latency of 393 ms from init6 1758402ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["00002e364abd058627066531933247506f6702ef","00002e3b1016d465a146cbe56883f153dfd535ea","00002e3d21092a12f05a169774d0d212669d3bc4","00002e3ef9328450f51dd107276d69b6981afcc1"] 1758404ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["00002e364abd058627066531933247506f6702ef","00002e3c2cbd1af001bec13c5332c92ae130bdad","00002e3f3be98a54f20afd35a9dc43147def829b","00002e40a7bf3ed2a7cae24f26740b5af78d8627"] 1758404ms th_a application.cpp:428 handle_transaction ] Got transaction from network 1758405ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["00002e364abd058627066531933247506f6702ef","00002e3c2cbd1af001bec13c5332c92ae130bdad","00002e3f3be98a54f20afd35a9dc43147def829b","00002e40a7bf3ed2a7cae24f26740b5af78d8627"] witness_node: /home/james/github/graphene/libraries/net/node.cpp:2488: void graphene::net::detail::node_impl::on_blockchain_item_ids_inventory_message(graphene::net::peer_connection*, const graphene::net::blockchain_item_ids_inventory_message&): Assertion `originating_peer->last_block_number_delegate_has_seen == _delegate->get_block_number(originating_peer->last_block_delegate_has_seen)' failed. Aborted (core dumped)

Code: [Select]
2015-09-19T05:29:18 p2p:process_backlog_of_sync_blocks trigger_fetch_sync_i ] Triggering fetch sync items loop now node.cpp:1083 2015-09-19T05:29:18 p2p:fetch_sync_items_loop fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:1022 2015-09-19T05:29:18 p2p:fetch_sync_items_loop fetch_sync_items_loo ] no sync items to fetch right now, going to sleep node.cpp:1072 2015-09-19T05:29:18 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 192.241.198.6:58168's last block the delegate has seen is now 00002e40a7bf3ed2a7cae24f26740b5af78d8627 (actual block #11836, tracked block #11836) node.cpp:2487
Title: Re: Test Net for Advanced Users
Post by: cube on September 19, 2015, 09:50:22 am: I just got my witness up. Please vote.

get_witness bitcube
{
"id": "1.6.624",
"witness_account": "1.2.8206",
"last_aslot": 0,
"signing_key": "GPH7qbi1TEAFGjsCTNQoecnGkcMr3RV6ya5yc8GbXyXCV1adQtFsn",
"vote_id": "1:623",
"total_votes": 0,
"url": "",
"total_missed": 0
}
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 10:04:01 am: Quote from: puppies on September 19, 2015, 05:10:18 am
Added you riverhead, but it won't be enough to bring you in. Unfortunately I am not a whale. Not even a dolphin.

On a side note, is there a feed script yet? If not what is the syntax to publish a feed manually?
publish_asset_feed(string, string, graphene::chain::price_feed, bool)
I was guessing account_name asset_name price broadcast? but thats not working. Might be because I am not voted in yet. If someone figures it out please post.

Hi puppies, looks like there is a whale voting. We already have more voting power than BM.
If you remove some of the init witnesses from your list, other witnesses will be voted in.

Code: [Select]
get_witness init9 { "id": "1.6.10", "witness_account": "1.2.109", "last_aslot": 17927, "signing_key": "GPH6aRys1uA71La2EyA1sjLqGzZzwPXc9dm6NCcWARrsDn7Y6EPoc", "pay_vb": "1.13.6", "vote_id": "1:9", "total_votes": "2079167368873", "url": "", "total_missed": 65 } get_witness init10 { "id": "1.6.11", "witness_account": "1.2.110", "last_aslot": 8372, "signing_key": "GPH5uXNw7r167Dhuf4qMz1BTj74rAeicYCARTifpmrcfFhRZquU8B", "pay_vb": "1.13.5", "vote_id": "1:10", "total_votes": "872119491831", "url": "", "total_missed": 64 }
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 10:12:19 am: Quote from: puppies on September 19, 2015, 05:10:18 am
Added you riverhead, but it won't be enough to bring you in. Unfortunately I am not a whale. Not even a dolphin.

On a side note, is there a feed script yet? If not what is the syntax to publish a feed manually?
publish_asset_feed(string, string, graphene::chain::price_feed, bool)
I was guessing account_name asset_name price broadcast? but thats not working. Might be because I am not voted in yet. If someone figures it out please post.

See https://github.com/cryptonomex/graphene/blob/93c72b05951ad2fd0f1a07b702773e9a905d8adc/libraries/wallet/include/graphene/wallet/wallet.hpp#L916-L935

Code: [Select]
#define GRAPHENE_PRICE_FEED_FIELDS (settlement_price)(maintenance_collateral_ratio)(maximum_short_squeeze_ratio) \ (core_exchange_rate)
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 19, 2015, 11:29:57 am: Is it still cool to set-up a witness on a cubox at home?

Or would a fresh VPS be better. Or both?
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 19, 2015, 12:07:20 pm: witness ready:

"id": "1.6.1063",
"witness_account": "1.2.14634"

thank you for voting me in, some funds for "calabiyau" appreciated
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 12:09:01 pm: Quote from: abit on September 19, 2015, 10:12:19 am
Quote from: puppies on September 19, 2015, 05:10:18 am
Added you riverhead, but it won't be enough to bring you in. Unfortunately I am not a whale. Not even a dolphin.

On a side note, is there a feed script yet? If not what is the syntax to publish a feed manually?
publish_asset_feed(string, string, graphene::chain::price_feed, bool)
I was guessing account_name asset_name price broadcast? but thats not working. Might be because I am not voted in yet. If someone figures it out please post.

See https://github.com/cryptonomex/graphene/blob/93c72b05951ad2fd0f1a07b702773e9a905d8adc/libraries/wallet/include/graphene/wallet/wallet.hpp#L916-L935

Don't know the syntax of struct "price_feed" though..

Code: [Select]
#define GRAPHENE_PRICE_FEED_FIELDS (settlement_price)(maintenance_collateral_ratio)(maximum_short_squeeze_ratio) \ (core_exchange_rate)
I figured out the syntax of publishing a price feed, but the transaction got refused by the chain.
Looks like there is a bug. See https://github.com/cryptonomex/graphene/issues/328
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 12:09:29 pm: Quote from: iHashFury on September 19, 2015, 11:29:57 am
Is it still cool to set-up a witness on a cubox at home?

Or would a fresh VPS be better. Or both?
My witness is running at home.
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 19, 2015, 12:33:38 pm: I'll update the stats page when back at my computer on monday .. sorry for the delay
Title: Re: Test Net for Advanced Users
Post by: spartako on September 19, 2015, 12:45:17 pm: spartako (1.6.4232) now up and running.

I just voted for everyone....thanks for your votes in advance!

Code: [Select]
get_witness spartako { "id": "1.6.4232", "witness_account": "1.2.72822", .... }
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 19, 2015, 01:08:43 pm: I still have 0 votes.

I've changed my witness name to just xeldal ,thinking that may be why.

Please update your votes for this witness. Thankyou

Code: [Select]
get_witness xeldal { "id": "1.6.4949", "witness_account": "1.2.86459",
Title: Re: Test Net for Advanced Users
Post by: sittingduck on September 19, 2015, 01:16:19 pm: I believe bm didn't want the init witnesses being voted out but added to

Sent from my iPhone using Tapatalk
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 01:19:43 pm: Since it's unable to short bitUSD right now, welcome to trade on my private bitAsset "ABITUSDA".
Short is enabled here. Current settlement price is 1 BITUSDA = 1 CORE.
Anyone who wants to publish price feeds for the asset please leave a message here, so that I can add him/her to the authorized list.
The command for publishing price feed is like:
Code: [Select]
publish_asset_feed in.abit ABITUSDA {"settlement_price":{"base":{"amount":50000,"asset_id":"1.3.662"},"quote":{"amount":1000000000,"asset_id":"1.3.0"}},"core_exchange_rate":{"base":{"amount":100000,"asset_id":"1.3.0"},"quote":{"amount":10000,"asset_id":"1.3.662"}}} true
In which,
* in.abit is my account name, so replace with your name
* ABITUSDA is the name of asset
* "1.3.662" is ID of the asset, "1.3.0" is CORE
Fill the other numbers as you like.
Title: Re: Test Net for Advanced Users
Post by: spartako on September 19, 2015, 01:42:18 pm: Quote from: Xeldal on September 19, 2015, 01:08:43 pm
I still have 0 votes.

I've changed my witness name to just xeldal ,thinking that may be why.

Please update your votes for this witness. Thankyou

Code: [Select]
get_witness xeldal { "id": "1.6.4949", "witness_account": "1.2.86459",

Me too I have 0 votes and it is really strange, I try to understand how voting is working:

If I type:
Code: [Select]
vote_for_witness spartako init0 true trueI obtain:
Code: [Select]
.... "new_options": { "memo_key": "GPH5mgup8evDqMnT86L7scVebRYDC2fwAWmygPEUL43LjstQegYCC", "voting_account": "1.2.5", "num_witness": 0, "num_committee": 0, "votes": [ "1:0", "1:623" ], "extensions": [] ....
So if I understood well I voted for 1:0 and 1:623, the vote id correspond to init0 and bitcube:
Code: [Select]
get_witness init0 { "id": "1.6.1", "witness_account": "1.2.100", "last_aslot": 22268, "signing_key": "GPH6gBqcGKgkVQvt7XZtYN9z3QHdWFCGKB2oiNvpMkXQsMqZB1YWi", "pay_vb": "1.13.12", "vote_id": "1:0", "total_votes": "2074182939478", "url": "bitshares.org", "total_missed": 71 }
Code: [Select]
get_witness bitcube { "id": "1.6.624", "witness_account": "1.2.8206", "last_aslot": 0, "signing_key": "GPH7qbi1TEAFGjsCTNQoecnGkcMr3RV6ya5yc8GbXyXCV1adQtFsn", "vote_id": "1:623", "total_votes": 0, "url": "", "total_missed": 0 }
If then I give the command:
Code: [Select]
vote_for_witness spartako init1 true true
I obtain:
Code: [Select]
.... "new_options": { "memo_key": "GPH5mgup8evDqMnT86L7scVebRYDC2fwAWmygPEUL43LjstQegYCC", "voting_account": "1.2.5", "num_witness": 0, "num_committee": 0, "votes": [ "1:1", "1:623" ], ....
It seems that I continue to vote for bitcube but no more for init0, instead I vote for init1

And so on if I vote for init2 I obtain:
Code: [Select]
... "new_options": { "memo_key": "GPH5mgup8evDqMnT86L7scVebRYDC2fwAWmygPEUL43LjstQegYCC", "voting_account": "1.2.5", "num_witness": 0, "num_committee": 0, "votes": [ "1:2", "1:623" ], "extensions": [] }, ....
I am really confused ???
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 01:58:30 pm: Quote from: spartako on September 19, 2015, 01:42:18 pm
I am really confused ???
There is a bug with voting in cli-wallet. It's only possible to vote for one witness via "vote_for_witness" -- the last one.
You can try vote-proxy or try GUI if you want to vote for more witnesses.

The "total_votes: 0" is also buggy. It will show non-zero only if your witness have ever been voted in.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 19, 2015, 01:59:13 pm: please whitelist me for ABITUSDA.

In regards to voting, it seems as if votes are not showing up in get_witness until you are voted in. Even if you are voted in, they only update once an hour.

We need to vote for more witnesses than the 11 that are currently in. The number of active witnesses is determined by the average number that we are all voting for. I am assuming this is based upon stake voting.

I am voting in gui, so I cant help with the cli syntax, but you can always set me as a proxy. I am currently voting for
Code: [Select]
bitcube calabiyau dele-puppy delegate-1.lafona delegate-clayop fox in.abit init1 init2 init3 init4 init5 init6 init7 init8 init9 riverhead wackou xeldal
Title: Re: Test Net for Advanced Users
Post by: spartako on September 19, 2015, 02:04:21 pm: Quote from: abit on September 19, 2015, 01:58:30 pm
Quote from: spartako on September 19, 2015, 01:42:18 pm
I am really confused ???
There is a bug with voting in cli-wallet. It's only possible to vote for one witness via "vote_for_witness" -- the last one.
You can try vote-proxy or try GUI if you want to vote for more witnesses.

The "total_votes: 0" is also buggy. It will show non-zero only if your witness have ever been voted in.

Thanks! Now it is more clear
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 19, 2015, 02:06:25 pm: Thx spartako, funds arrived - votes not showing up till now.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 19, 2015, 02:07:08 pm: Please do not vote out init0 -> init11 these are our nodes for testing in this test network and they are on separate machines / processes and not all on one machine.

Please DO vote for init0->init11 AND everyone on this thread so we can increase the total number of witnesses.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 19, 2015, 02:07:40 pm: Votes are only calculated once per hour, so they will not show up until the next maintenance interval.
Title: Re: Test Net for Advanced Users
Post by: spartako on September 19, 2015, 02:08:41 pm: Quote from: puppies on September 19, 2015, 01:59:13 pm

We need to vote for more witnesses than the 11 that are currently in. The number of active witnesses is determined by the average number that we are all voting for. I am assuming this is based upon stake voting.

I am voting in gui, so I cant help with the cli syntax, but you can always set me as a proxy. I am currently voting for

I just set you as a proxy:
Code: [Select]
set_voting_proxy spartako dele-puppy true
Please add "spartako" (1.6.4232) to the list, thanks!
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 19, 2015, 02:18:18 pm: Voted:
Code: [Select]
bitcube calabiyau dele-puppy delegate-1.lafona delegate-clayop fox in.abit init0 init1 init2 init3 init4 init5 init6 init7 init8 init9 init10 init11 riverhead wackou xeldal spartako
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 02:25:49 pm: Quote from: bytemaster on September 19, 2015, 02:07:08 pm
Please do not vote out init0 -> init11 these are our nodes for testing in this test network and they are on separate machines / processes and not all on one machine.

Please DO vote for init0->init11 AND everyone on this thread so we can increase the total number of witnesses.
How to increase the total number of witnesses? Do we need a proposal?
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 19, 2015, 02:26:53 pm: Cant create a backup for whatever reason.
https://bitsharestalk.org/index.php/topic,18511.0.html

In the meantime can someone send me (xeldal) 11 - 20 CORE so I can "set_voting_proxy"

Thanks
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 02:27:35 pm: Quote from: puppies on September 19, 2015, 01:59:13 pm
please whitelist me for ABITUSDA.

Thanks. dele-puppy is whitelisted.
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 02:33:28 pm: Quote from: Xeldal on September 19, 2015, 02:26:53 pm
In the meantime can someone send me (xeldal) 11 - 20 CORE so I can "set_voting_proxy"

Thanks
Transferred.
Title: Re: Test Net for Advanced Users
Post by: spartako on September 19, 2015, 02:38:00 pm: Quote from: CalabiYau on September 19, 2015, 02:18:18 pm
Code: [Select]
... spartako

Thanks!
Title: Re: Test Net for Advanced Users
Post by: puppies on September 19, 2015, 02:41:55 pm: Quote from: spartako on September 19, 2015, 02:08:41 pm
Quote from: puppies on September 19, 2015, 01:59:13 pm

We need to vote for more witnesses than the 11 that are currently in. The number of active witnesses is determined by the average number that we are all voting for. I am assuming this is based upon stake voting.

I am voting in gui, so I cant help with the cli syntax, but you can always set me as a proxy. I am currently voting for

I just set you as a proxy:
Code: [Select]
set_voting_proxy spartako dele-puppy true
Please add "spartako" (1.6.4232) to the list, thanks!
sorry thought I had you in there. I'll add you now.
Title: Re: Test Net for Advanced Users
Post by: spartako on September 19, 2015, 02:43:47 pm: Quote from: puppies on September 19, 2015, 02:41:55 pm
sorry thought I had you in there. I'll add you now.

Thanks!
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 02:45:30 pm: Quote from: puppies on September 19, 2015, 02:41:55 pm
Quote from: spartako on September 19, 2015, 02:08:41 pm
Quote from: puppies on September 19, 2015, 01:59:13 pm

We need to vote for more witnesses than the 11 that are currently in. The number of active witnesses is determined by the average number that we are all voting for. I am assuming this is based upon stake voting.

I am voting in gui, so I cant help with the cli syntax, but you can always set me as a proxy. I am currently voting for

I just set you as a proxy:
Code: [Select]
set_voting_proxy spartako dele-puppy true
Please add "spartako" (1.6.4232) to the list, thanks!
sorry thought I had you in there. I'll add you now.
I thought it should be
Code: [Select]
set_voting_proxy spartako puppies true
Title: Re: Test Net for Advanced Users
Post by: clayop on September 19, 2015, 02:52:59 pm: My node is back. Please vote me in.

delegate-clayop
Title: Re: Test Net for Advanced Users
Post by: spartako on September 19, 2015, 03:00:12 pm: Quote from: abit on September 19, 2015, 02:45:30 pm
I thought it should be
Code: [Select]
set_voting_proxy spartako puppies true

Yes my fault. thanks, updated the proxy
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 04:18:15 pm: Quote from: abit on September 19, 2015, 02:25:49 pm
Quote from: bytemaster on September 19, 2015, 02:07:08 pm
Please do not vote out init0 -> init11 these are our nodes for testing in this test network and they are on separate machines / processes and not all on one machine.

Please DO vote for init0->init11 AND everyone on this thread so we can increase the total number of witnesses.
How to increase the total number of witnesses? Do we need a proposal?

I think there is a bug in the code.
BM is voting for 13 witnesses, puppies' proxy is voting for 20 witnesses, a whale 'dummy0' is voting for 17 witnesses, but we still only get active 11 witnesses voted in.

Code: [Select]
2015-09-19T16:00:00 th_a:invoke handle_block operator() ] stake_account 1.2.22404 voting_stake 2494583263 num_witness 20 db_maint.cpp:437 2015-09-19T16:00:00 th_a:invoke handle_block operator() ] stake_account 1.2.21605 voting_stake 857123053259 num_witness 13 db_maint.cpp:437 2015-09-19T16:00:02 th_a:invoke handle_block operator() ] stake_account 1.2.201 voting_stake 1217059886219 num_witness 17 db_maint.cpp:437 2015-09-19T16:00:06 th_a:invoke handle_block operator() ] stake_account 1.2.63448 voting_stake 4982408107 num_witness 20 db_maint.cpp:437 2015-09-19T16:00:07 th_a:invoke handle_block operator() ] stake_account 1.2.72822 voting_stake 63991967993 num_witness 20 db_maint.cpp:437 2015-09-19T16:00:09 th_a:invoke handle_block operator() ] stake_account 1.2.86459 voting_stake 8796602 num_witness 20 db_maint.cpp:437
So.. let us try to vote for at least 23 witnesses and see what will happen.

//Edit: more info here, maybe real "num_witness" is num_witness+1 (the ones voting for 0 witness are actually voting for 1 witness)
Code: [Select]
2015-09-19T16:00:00 th_a:invoke handle_block operator() ] stake_account 1.2.22404 voting_stake 2494583263 num_witness 20 db_maint.cpp:437 2015-09-19T16:00:00 th_a:invoke handle_block operator() ] stake_account 1.2.21605 voting_stake 857123053259 num_witness 13 db_maint.cpp:437 2015-09-19T16:00:01 th_a:invoke handle_block operator() ] stake_account 1.2.17357 voting_stake 4822 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:01 th_a:invoke handle_block operator() ] stake_account 1.2.14634 voting_stake 993180513 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:01 th_a:invoke handle_block operator() ] stake_account 1.2.13486 voting_stake 2000068356 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:02 th_a:invoke handle_block operator() ] stake_account 1.2.106 voting_stake 100000 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:02 th_a:invoke handle_block operator() ] stake_account 1.2.108 voting_stake 99800000 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:02 th_a:invoke handle_block operator() ] stake_account 1.2.109 voting_stake 99800000 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:02 th_a:invoke handle_block operator() ] stake_account 1.2.110 voting_stake 99800000 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:02 th_a:invoke handle_block operator() ] stake_account 1.2.100 voting_stake 69999800000 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:02 th_a:invoke handle_block operator() ] stake_account 1.2.101 voting_stake 109800000 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:02 th_a:invoke handle_block operator() ] stake_account 1.2.201 voting_stake 1217059886219 num_witness 17 db_maint.cpp:437 2015-09-19T16:00:02 th_a:invoke handle_block operator() ] stake_account 1.2.2331 voting_stake 6998869201 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:02 th_a:invoke handle_block operator() ] stake_account 1.2.3089 voting_stake 167071154666 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:03 th_a:invoke handle_block operator() ] stake_account 1.2.38993 voting_stake 8412165358 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:03 th_a:invoke handle_block operator() ] stake_account 1.2.41123 voting_stake 338984266 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:03 th_a:invoke handle_block operator() ] stake_account 1.2.47247 voting_stake 7309344543864 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:04 th_a:invoke handle_block operator() ] stake_account 1.2.30566 voting_stake 10000000 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:05 th_a:invoke handle_block operator() ] stake_account 1.2.53724 voting_stake 10000000 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:06 th_a:invoke handle_block operator() ] stake_account 1.2.63448 voting_stake 4982408107 num_witness 20 db_maint.cpp:437 2015-09-19T16:00:07 th_a:invoke handle_block operator() ] stake_account 1.2.72822 voting_stake 63991967993 num_witness 20 db_maint.cpp:437 2015-09-19T16:00:08 th_a:invoke handle_block operator() ] stake_account 1.2.83349 voting_stake 18122731729 num_witness 0 db_maint.cpp:437 2015-09-19T16:00:09 th_a:invoke handle_block operator() ] stake_account 1.2.86459 voting_stake 8796602 num_witness 20 db_maint.cpp:437 2015-09-19T16:00:09 th_a:invoke handle_block operator() ] stake_account 1.2.90134 voting_stake 29695789064 num_witness 0 db_maint.cpp:437
Title: Re: Test Net for Advanced Users
Post by: roadscape on September 19, 2015, 04:36:51 pm: Got my witness up and tried to set `puppies` as my voting proxy.

Code: [Select]
get_witness roadscape { "id": "1.6.5249", "witness_account": "1.2.67429", "last_aslot": 0, "signing_key": "GPH8LkpAcZX1wpzh69or1WG62PYvgSpuUjL3YShR9ChA5XDYVh3zW", "vote_id": "1:5270", "total_votes": 0, "url": "https://github.com/roadscape", "total_missed": 0 }
Unrelated: got this error message when first running the witness node. But it continued chugging along:
Code: [Select]
2666068ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000021f029ef1ca6c188b018a875452251581b15"] 2666483ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["00002282c22d98bcb469328a6520f8ea217cd6cd"] 2667707ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000025622acfbcb5f395ab8b83cf64c972a33307","00002568780f577938c1d6cef4a48518fdf91a0a","0000256ba7c4b4e1df57f66669a9b10c9a0e8fb5","0000256d10479bd4d2ea39820f5a448187e266f6"] 2667723ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000025622acfbcb5f395ab8b83cf64c972a33307","00002568780f577938c1d6cef4a48518fdf91a0a","0000256ba7c4b4e1df57f66669a9b10c9a0e8fb5","0000256d10479bd4d2ea39820f5a448187e266f6"] 2667781ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000025622acfbcb5f395ab8b83cf64c972a33307","00002568780f577938c1d6cef4a48518fdf91a0a","0000256ba7c4b4e1df57f66669a9b10c9a0e8fb5","0000256d10479bd4d2ea39820f5a448187e266f6"] 2668098ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["0000264aec280792e37cc3869300babc686c4ca5","000026500ea3aaf8c2a217199ff8cdf50be63c64","0000265313d7b3710423bd3512efd060a702c5dd","00002655bd9279f769d00e1859f3de4ccd64c9c2"] 2668401ms th_a application.cpp:388 handle_block ] Got block #10000 with time 2015-09-19T03:57:00 from network with latency of 42448404 ms from in.abit 2668594ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["00002737d801c5d34b19396459eac2f2fe7b9d4e","0000273d16d8bf5a9d8c2875db6f7ac9151e8623","000027401bd8cee3da35e4d3aacf2753724e2460","00002742cdb021792a5c60c529b416321b2c0e42"] 2669240ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["00002882f1df81160013ce49c97826e38bdfc267","0000288871ded5ef996932d1be1458f3a37c1219","0000288b99fae8170cd675e087c1388beb2bc3c6","0000288d7f0f59de985c3fe38881e435f90449ef"] 2670470ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000029ba24508e67e34e8e1c46bc20bfc0e2902f"] 2671314ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["00002a889920c1ff645878ec2e7296a20b765c8f"] 2681172ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["0000320133034eff6b2ecb099691fb1b87bfc27b","000032077334ed5905814efa490b5ee5148cc987","0000320af4e42828469a2a9d5fa1d611f588a911","0000320c2f0c947368d0e82fbaa1f724bdd3aac7"] 2681621ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["0000329aaf65eb6736c8970c945cce58f0f4b6be"] 2682480ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000033b6e9a19ad7990a791f7c140691b168410f","000033bc9dc6e3e6024adf03615577ce9b7f699f","000033bf21c91a136bea1ee3d96e062f77ac65aa","000033c16880f71ee9570af4ef46cd4cb932f0e0"] 2683239ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["00002119231e1df277239782c45f90259488fe4e"] 2687651ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["00003b30aa266b17cbb3a28be80f860914cafeb0","00003b367a77572e16e483ceb1da514bef3f24e6","00003b39842e23b90f94248fb3deff3143136f1e","00003b3b91b39257324e2a0963cc47f280891d72"] 2689399ms th_a application.cpp:415 handle_block ] Error when pushing block: 10 assert_exception: Assert Exception item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old {"item->num":15530,"head":15746,"max_size":14} th_a fork_database.cpp:71 _push_block {"new_block":{"previous":"00003ca9a64aaab511688859835d1012c60d3358","timestamp":"2015-09-19T08:34:42","witness":"1.6.9","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f183a56a6c97eec1dacdc22cbbcc6879d2e04869ac8371ba91b50bdcc3f6604b40b3b4c6b6377afa8b096167a7bf2747d41423302c71bba97d0d875399a07debe","transactions":[]}} th_a db_block.cpp:195 _push_block 2692265ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["00002d3cc0a9b72c6e182894336d43dd6ac9cda5"] 2693143ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["00002f11f0b8a623ce90e94de9c0983134ef378b"] 2694038ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["00002d3cc0a9b72c6e182894336d43dd6ac9cda5"]
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 04:48:23 pm: Is it a bug, or a feature?

With current implementation, the chain will take more than 11 witnesses only if more than 50% of voting stakes ALL vote for more than 11 witnesses.

Now most of voting stakes (from my log 76134065.91839 out of 97590672.87282) are voting for 1 witness, with current implementation, the chain take minimum number of witnesses, it's 11.

The biggest whale in the testnet, 1.2.47247, name 'llc', who owns 73M CORE, please help test voting -- don't vote for yourself only.
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 19, 2015, 05:09:06 pm: Quote from: abit on September 19, 2015, 04:48:23 pm
Is it a bug, or a feature?

With current implementation, the chain will take more than 11 witnesses only if more than 50% of voting stakes ALL vote for more than 11 witnesses.

Now most of voting stakes (from my log 76134065.91839 out of 97590672.87282) are voting for 1 witness, with current implementation, the chain take minimum number of witnesses, it's 11.

The biggest whale in the testnet, 1.2.47247, name 'llc', who owns 73M CORE, please help test voting -- don't vote for yourself only.
You need committee members voted into the active committe that want more witnesses ..

- create some committee accounts
- set their witness amount parameter to something higher than 11
- have them vote into active committee

afaik the amount of active witnesses will increase to the MEDIAN amount of what the (active) committee members want

Would lobe to help out but oli am mobile over the weekend ..

Good luck
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 19, 2015, 05:09:50 pm: Witmeas amount is just ONE out of MANY parameters that can be defined by committee .. also fees
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 05:22:22 pm: Quote from: xeroc on September 19, 2015, 05:09:06 pm

You need committee members voted into the active committe that want more witnesses ..

- create some committee accounts
- set their witness amount parameter to something higher than 11
- have them vote into active committee

afaik the amount of active witnesses will increase to the MEDIAN amount of what the (active) committee members want

Would lobe to help out but oli am mobile over the weekend ..

Good luck
I ever thought of this as well, but after check the global parameter is 1001 indeed. So it's another issue.
Code: [Select]
get_global_properties { ... "maximum_witness_count": 1001, ... }
//Edit:
I wrote 'current implementation', it means that current code told me this..
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 05:25:12 pm: Ok, this hour come in some different witnesses, but the number is still 11.
Code: [Select]
"active_witnesses": [ "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.6.5", "1.6.6", "1.6.7", "1.6.1538", "1.6.2104", "1.6.5247", "1.6.5248" ],
Title: Re: Test Net for Advanced Users
Post by: puppies on September 19, 2015, 05:36:13 pm: I'm updated to voting for 23 witnesses.
Code: [Select]
bitcube calabiyau dele-puppy delegate-1.lafona delegate-clayop fox in.abit init0 init1 init10 init2 init3 init4 init5 init6 init7 init8 init9 riverhead roadscape spartako wackou xeldal
I also upgraded dele-puppy to a committee member so we can see if that helps.
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 19, 2015, 05:47:35 pm: To clarify:

Should the proxy vote be on "puppies" or "dele-puppy"?

Above it lists both.
Title: Re: Test Net for Advanced Users
Post by: roadscape on September 19, 2015, 05:49:30 pm: My witness node just quit, lots of "unlinkable block" exceptions:

Code: [Select]
th_a fork_database.cpp:79 _push_block {"new_block":{"previous":"000063f6db1440c2b25130cd53dfb59ba393476c","timestamp":"2015-09-19T17:44:45","witness":"1.6.2","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f356d6f0f9cd1f5b0c3d42f52f6eb46df93af7518175018bc91a4dfe06a395b4541c65ddbc7ec81499868cb52508afd27c6d8348029fc910b7aa3537448464924","transactions":[]}} th_a db_block.cpp:195 _push_block 2687000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 2687510ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c177ee3dada43f55223bb18fdd7d9b30e7","000063c7f469f342f415e7dc947e7ab3f50bd335","000063ca5952fd63f7d343ae9243e48e80863d54","000063cc082deb3db5bf5face1691e24ba7f8460"] 2688000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 2688773ms th_a application.cpp:388 handle_block ] Got block #25592 with time 2015-09-19T17:44:48 from network with latency of 780 ms from delegate-clayop 2688773ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link: 000063f80322c81f8b12de9b5993c1c955d54a8c, 25592 2688773ms th_a fork_database.cpp:58 push_block ] Head: 25548, 000063cc082deb3db5bf5face1691e24ba7f8460 2688773ms th_a application.cpp:415 handle_block ] Error when pushing block: 3080000 unlinkable_block_exception: unlinkable block block does not link to known chain {} th_a fork_database.cpp:79 _push_block {"new_block":{"previous":"000063f77cfaaecfdd6756b2f5833ec19cc3fc20","timestamp":"2015-09-19T17:44:48","witness":"1.6.1538","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f34c399fc3bc711109d9412adb172f0258f1dd6612eb9c3e24a72bd87d8aecea54915fb219f1de70572b3b1abd13b5a6dc84191806bd98083ba59f42de76354b1","transactions":[]}} th_a db_block.cpp:195 _push_block 2689000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 2689111ms th_a application.cpp:388 handle_block ] Got block #25592 with time 2015-09-19T17:44:48 from network with latency of 1118 ms from delegate-clayop 2689111ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link: 000063f80322c81f8b12de9b5993c1c955d54a8c, 25592 2689111ms th_a fork_database.cpp:58 push_block ] Head: 25548, 000063cc082deb3db5bf5face1691e24ba7f8460 2689112ms th_a application.cpp:415 handle_block ] Error when pushing block: 3080000 unlinkable_block_exception: unlinkable block block does not link to known chain {} th_a fork_database.cpp:79 _push_block {"new_block":{"previous":"000063f77cfaaecfdd6756b2f5833ec19cc3fc20","timestamp":"2015-09-19T17:44:48","witness":"1.6.1538","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f34c399fc3bc711109d9412adb172f0258f1dd6612eb9c3e24a72bd87d8aecea54915fb219f1de70572b3b1abd13b5a6dc84191806bd98083ba59f42de76354b1","transactions":[]}} th_a db_block.cpp:195 _push_block 2689490ms th_a application.cpp:388 handle_block ] Got block #25592 with time 2015-09-19T17:44:48 from network with latency of 1497 ms from delegate-clayop 2689491ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link: 000063f80322c81f8b12de9b5993c1c955d54a8c, 25592 2689491ms th_a fork_database.cpp:58 push_block ] Head: 25548, 000063cc082deb3db5bf5face1691e24ba7f8460 2689491ms th_a application.cpp:415 handle_block ] Error when pushing block: 3080000 unlinkable_block_exception: unlinkable block block does not link to known chain {} th_a fork_database.cpp:79 _push_block {"new_block":{"previous":"000063f77cfaaecfdd6756b2f5833ec19cc3fc20","timestamp":"2015-09-19T17:44:48","witness":"1.6.1538","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f34c399fc3bc711109d9412adb172f0258f1dd6612eb9c3e24a72bd87d8aecea54915fb219f1de70572b3b1abd13b5a6dc84191806bd98083ba59f42de76354b1","transactions":[]}} th_a db_block.cpp:195 _push_block 2690000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 2690098ms th_a application.cpp:388 handle_block ] Got block #25592 with time 2015-09-19T17:44:48 from network with latency of 2104 ms from delegate-clayop 2690098ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link: 000063f80322c81f8b12de9b5993c1c955d54a8c, 25592 2690098ms th_a fork_database.cpp:58 push_block ] Head: 25548, 000063cc082deb3db5bf5face1691e24ba7f8460 2690098ms th_a application.cpp:415 handle_block ] Error when pushing block: 3080000 unlinkable_block_exception: unlinkable block block does not link to known chain {} th_a fork_database.cpp:79 _push_block {"new_block":{"previous":"000063f77cfaaecfdd6756b2f5833ec19cc3fc20","timestamp":"2015-09-19T17:44:48","witness":"1.6.1538","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f34c399fc3bc711109d9412adb172f0258f1dd6612eb9c3e24a72bd87d8aecea54915fb219f1de70572b3b1abd13b5a6dc84191806bd98083ba59f42de76354b1","transactions":[]}} th_a db_block.cpp:195 _push_block 2690209ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c26bf08ebafa5593807c31ba77bcc06b81","000063c8f3216b57009235878d541207b150c29a","000063cb4385c7f6965a107a22006874c09afef9","000063cdd010890862beaa64123e32edbdd73f14"] 2690217ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c26bf08ebafa5593807c31ba77bcc06b81","000063c8f3216b57009235878d541207b150c29a","000063cb4385c7f6965a107a22006874c09afef9","000063cdd010890862beaa64123e32edbdd73f14"] 2690223ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c26bf08ebafa5593807c31ba77bcc06b81","000063c8f3216b57009235878d541207b150c29a","000063cb4385c7f6965a107a22006874c09afef9","000063cdd010890862beaa64123e32edbdd73f14"] 2690232ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c39be97087c9ce5c8b343e059e809ba8ab","000063c9260aa4abe461ecdf1573b3025fcad188","000063cc082deb3db5bf5face1691e24ba7f8460","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85"] 2690290ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c4c1508ce08b8cd7f183b4dcea85777bb9","000063ca5952fd63f7d343ae9243e48e80863d54","000063cdd010890862beaa64123e32edbdd73f14","000063cf50a023252b8084621ace2cafa3d70886"] 2690291ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c4c1508ce08b8cd7f183b4dcea85777bb9","000063ca5952fd63f7d343ae9243e48e80863d54","000063cdd010890862beaa64123e32edbdd73f14","000063cf50a023252b8084621ace2cafa3d70886"] (57 repeating lines snipped) 2690471ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690471ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690474ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690474ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690474ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690478ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690478ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690478ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690479ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690479ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690479ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690480ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690480ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690480ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690481ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690481ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690481ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690482ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690482ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690482ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690483ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690483ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690483ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690484ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690484ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2690485ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063c5c82a119bcff707293aa756e7615e2840","000063cb4385c7f6965a107a22006874c09afef9","000063ce70a9e0e47eaaa80a44e9537fc4cdbc85","000063d037b5440a9c184de7169f50b4e2e395ac"] 2691000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 2691769ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063dfa50edb6fee62b24771504d3cb6efaa23"] 2691789ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063dfa50edb6fee62b24771504d3cb6efaa23"] 2691824ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063dfa50edb6fee62b24771504d3cb6efaa23"] 2691824ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063dfa50edb6fee62b24771504d3cb6efaa23"] 2691834ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063dfa50edb6fee62b24771504d3cb6efaa23"] 2691837ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063dfa50edb6fee62b24771504d3cb6efaa23"] 2691956ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063edc2e9e068f5f45ad848fe5f5c0fd82944","000063f37425282d452ecccbeda8ffdb82e1efbb","000063f6db1440c2b25130cd53dfb59ba393476c","000063f80322c81f8b12de9b5993c1c955d54a8c"] 2692000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 2692199ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063edc2e9e068f5f45ad848fe5f5c0fd82944","000063f37425282d452ecccbeda8ffdb82e1efbb","000063f6db1440c2b25130cd53dfb59ba393476c","000063f80322c81f8b12de9b5993c1c955d54a8c"] 2692315ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063edc2e9e068f5f45ad848fe5f5c0fd82944","000063f37425282d452ecccbeda8ffdb82e1efbb","000063f6db1440c2b25130cd53dfb59ba393476c","000063f80322c81f8b12de9b5993c1c955d54a8c"] 2692427ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063edc2e9e068f5f45ad848fe5f5c0fd82944","000063f37425282d452ecccbeda8ffdb82e1efbb","000063f6db1440c2b25130cd53dfb59ba393476c","000063f80322c81f8b12de9b5993c1c955d54a8c"] 2692762ms th_a application.cpp:388 handle_block ] Got block #25593 with time 2015-09-19T17:44:51 from network with latency of 1768 ms from init0 2692864ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["000063ee628e421e0ceb897f5f76ffb14122445e","000063f4e9ee967ffda64febd3ac53182cda02df","000063f77cfaaecfdd6756b2f5833ec19cc3fc20","000063f95be93182f33ef48c608556a4aa163303"] witness_node: /root/graphene/libraries/net/node.cpp:2488: void graphene::net::detail::node_impl::on_blockchain_item_ids_inventory_message(graphene::net::peer_connection*, const graphene::net::blockchain_item_ids_inventory_message&): Assertion `originating_peer->last_block_number_delegate_has_seen == _delegate->get_block_number(originating_peer->last_block_delegate_has_seen)' failed.
The last line: witness_node: /root/graphene/libraries/net/node.cpp:2488: void graphene::net::detail::node_impl::on_blockchain_item_ids_inventory_message(graphene::net::peer_connection*, const graphene::net::blockchain_item_ids_inventory_message&): Assertion `originating_peer->last_block_number_delegate_has_seen == _delegate->get_block_number(originating_peer->last_block_delegate_has_seen)' failed.

edit: I restarted witness_node, and after some similar looking errors, it's running smoothly for now:
Code: [Select]
3006446ms th_a application.cpp:514 get_item ] Serving up block #15625 3006446ms th_a application.cpp:514 get_item ] Serving up block #15626 3006446ms th_a application.cpp:514 get_item ] Serving up block #15627 3006447ms th_a application.cpp:514 get_item ] Serving up block #15628 3006447ms th_a application.cpp:514 get_item ] Serving up block #15629 3009000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 3009139ms th_a application.cpp:388 handle_block ] Got block #25699 with time 2015-09-19T17:50:09 from network with latency of 138 ms from fox 3012000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 3012205ms th_a application.cpp:388 handle_block ] Got block #25700 with time 2015-09-19T17:50:12 from network with latency of 205 ms from init4 3015000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 3015329ms th_a application.cpp:388 handle_block ] Got block #25701 with time 2015-09-19T17:50:15 from network with latency of 329 ms from init1 3018000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 3018282ms th_a application.cpp:388 handle_block ] Got block #25702 with time 2015-09-19T17:50:18 from network with latency of 282 ms from delegate-clayop 3021000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 3021155ms th_a application.cpp:388 handle_block ] Got block #25703 with time 2015-09-19T17:50:21 from network with latency of 155 ms from init6 3024000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 3024380ms th_a application.cpp:388 handle_block ] Got block #25704 with time 2015-09-19T17:50:24 from network with latency of 380 ms from in.abit 3027000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 3027137ms th_a application.cpp:388 handle_block ] Got block #25705 with time 2015-09-19T17:50:27 from network with latency of 137 ms from init5
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 19, 2015, 05:49:57 pm: Quote from: puppies on September 19, 2015, 05:36:13 pm
I'm updated to voting for 23 witnesses.
Code: [Select]
bitcube calabiyau dele-puppy delegate-1.lafona delegate-clayop fox in.abit init0 init1 init10 init2 init3 init4 init5 init6 init7 init8 init9 riverhead roadscape spartako wackou xeldal
I also upgraded dele-puppy to a committee member so we can see if that helps.
Committee members have to be voted for separately ..

The max delegate amount int the config is the absolut max allowed ever .. not the current amount to be used afaik
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 05:56:58 pm: Quote from: puppies on September 19, 2015, 05:36:13 pm
I'm updated to voting for 23 witnesses.

I also upgraded dele-puppy to a committee member so we can see if that helps.
No use with current code and that whale. See my post https://bitsharestalk.org/index.php/topic,17962.msg237551.html#msg237551 and this issue https://github.com/cryptonomex/graphene/issues/330.
Hope that devs will come and explain more.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 19, 2015, 06:01:13 pm: Quote from: Xeldal on September 19, 2015, 05:47:35 pm
To clarify:

Should the proxy vote be on "puppies" or "dele-puppy"?

Above it lists both.

puppies please
Title: Re: Test Net for Advanced Users
Post by: puppies on September 19, 2015, 07:01:46 pm: Quote from: abit on September 19, 2015, 05:56:58 pm
Quote from: puppies on September 19, 2015, 05:36:13 pm
I'm updated to voting for 23 witnesses.

I also upgraded dele-puppy to a committee member so we can see if that helps.
No use with current code and that whale. See my post https://bitsharestalk.org/index.php/topic,17962.msg237551.html#msg237551 and this issue https://github.com/cryptonomex/graphene/issues/330.
Hope that devs will come and explain more.

Yeah. Sadly I think you're right.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 19, 2015, 07:07:34 pm: Quote from: puppies on September 19, 2015, 06:01:13 pm
Quote from: Xeldal on September 19, 2015, 05:47:35 pm
To clarify:

Should the proxy vote be on "puppies" or "dele-puppy"?

Above it lists both.

puppies please

So I voted 70k CORE for riverhead and it appeared to work but I see no votes on the delegate account..

Code: [Select]
get_witness riverhead { "id": "1.6.3968", "witness_account": "1.2.67253", "last_aslot": 0, "signing_key": "GPH6BJYGHftujnbttFFKX6YacnvsMd4sbJrbucg682GiU4vmXHTik", "vote_id": "1:3967", "total_votes": 0, "url": "", "total_missed": 0 } unlocked >>>
I noticed bitcube is on puppies' list and also does not have any votes. Any ideas?
Title: Re: Test Net for Advanced Users
Post by: puppies on September 19, 2015, 07:13:25 pm: It looks like there is a bug that shows total votes as 0 until you have been voted into active status. dele-puppy is still showing 0 votes as well.
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 07:28:09 pm: Looks like all witnesses other than the init ones are voted out..

Here is a summary of all votes. Note: the number before 'total' is 'vote_id' but not 'witness_id', the number after 'total' is how many CORE's * 100000.
Code: [Select]
2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 0 total 2153652707602 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 1 total 2153652707602 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 2 total 2153652707602 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 3 total 2153652707602 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 4 total 2153652707602 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 5 total 2153652707602 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 6 total 2153652707602 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 7 total 2153652707602 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 8 total 2153652707602 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 9 total 2153652707602 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 10 total 2153652707602 2015-09-19T19:00:04 th_a:invoke handle_block operator() ] 11 total 2074182535280 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 623 total 1296529654343 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 1062 total 1296529654343 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 1526 total 1296529654343 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 1530 total 1296529654343 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 1537 total 1296529654343 2015-09-19T19:00:04 th_a:invoke handle_block operator() ] 1624 total 1217059482021 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 2103 total 1314652386072 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 3967 total 1296529654343 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 4231 total 1296529654343 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 4948 total 1296529654343 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 5267 total 2153652707602 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 5268 total 1314652386072 2015-09-19T19:00:02 th_a:invoke handle_block operator() ] 5269 total 8411563602 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 5270 total 92919771170 2015-09-19T19:00:09 th_a:invoke handle_block operator() ] 5271 total 79470172322
Another strange thing, the 73M CORE whale seems doesn't vote for anyone, but the stake is counted "voting".
Code: [Select]
2015-09-19T19:00:02 th_a:invoke handle_block operator() ] stake_account 1.2.47247 voting_stake 7309344543864 num_witness 0 db_maint.cpp:437 2015-09-19T19:00:02 th_a:invoke handle_block operator() ] d._witness_count_histogram_buffer[0] = 7309354543864 db_maint.cpp:458 2015-09-19T19:00:02 th_a:invoke handle_block operator() ] d._total_voting_stake = 7309354543864 db_maint.cpp:472not like this (although same num_witness=0)
Code: [Select]
2015-09-19T19:00:02 th_a:invoke handle_block operator() ] stake_account 1.2.38993 voting_stake 8411563602 num_witness 0 db_maint.cpp:437 2015-09-19T19:00:02 th_a:invoke handle_block operator() ] stake_account 1.2.38993 voting_stake 8411563602 vote_for 5269 total 8411563602 db_maint.cpp:444 2015-09-19T19:00:02 th_a:invoke handle_block operator() ] d._witness_count_histogram_buffer[0] = 7318105091732 db_maint.cpp:458 2015-09-19T19:00:02 th_a:invoke handle_block operator() ] d._total_voting_stake = 7318105091732 db_maint.cpp:472
Title: Re: Test Net for Advanced Users
Post by: lakerta06 on September 19, 2015, 07:34:33 pm: Maybe that whale is bm. Isnt he handling some whale's stake? Maybe he wants to run some tests with init delegates.

Just speculating though. Dont take me too serious
Title: Re: Test Net for Advanced Users
Post by: puppies on September 19, 2015, 07:39:16 pm: Where are you pulling all this vote info from abit?
Title: Re: Test Net for Advanced Users
Post by: abit on September 19, 2015, 08:32:42 pm: Quote from: puppies on September 19, 2015, 07:39:16 pm
Where are you pulling all this vote info from abit?
https://github.com/abitmore/graphene/tree/test3-patch1
I added some logs, and modified config.ini so that the program saves console output to a file.
Title: Re: Test Net for Advanced Users
Post by: cube on September 20, 2015, 01:07:39 am: Hi guys,

My witness_node was stuck and I had to replay the chain. But it is not replaying. I am getting zero head block and the console says:

Code: [Select]
291001ms th_a witness.cpp:179 block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production) 292001ms th_a witness.cpp:179 block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production) 293000ms th_a witness.cpp:179 block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production) 294001ms th_a witness.cpp:179 block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production) 295000ms th_a witness.cpp:179 block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production) 296000ms th_a witness.cpp:179 block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production) 297000ms th_a witness.cpp:179 block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production) 298001ms th_a witness.cpp:179 block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production) 299000ms th_a witness.cpp:179 block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production)

Is the seed node '104.236.118.105:1776' working?
Title: Re: Test Net for Advanced Users
Post by: puppies on September 20, 2015, 02:11:47 am: Quote from: cube on September 20, 2015, 01:07:39 am

Is the seed node '104.236.118.105:1776' working?

Looks like its down. you can use 188.165.233.53:1776
Title: Re: Test Net for Advanced Users
Post by: cube on September 20, 2015, 05:00:47 am: Yes the new seed is working. I am in sync. Thank you!

Can you help to vote bitcube in?

"id": "1.6.624",
"witness_account": "1.2.8206",
Title: Re: Test Net for Advanced Users
Post by: clayop on September 20, 2015, 12:32:30 pm: init8 witness node seems to be down.
Title: Re: Test Net for Advanced Users
Post by: abit on September 20, 2015, 01:12:01 pm: Quote from: clayop on September 20, 2015, 12:32:30 pm
init8 witness node seems to be down.
Yes. I think puppies can vote it out.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 20, 2015, 01:44:41 pm: witness ihashfury "id": "1.6.2562"

and

witness delegate.ihashfury "id": "1.6.1596"

are setup - if anyone would like to vote them in
Title: Re: Test Net for Advanced Users
Post by: puppies on September 20, 2015, 03:36:03 pm: Quote from: abit on September 20, 2015, 01:12:01 pm
Quote from: clayop on September 20, 2015, 12:32:30 pm
init8 witness node seems to be down.
Yes. I think puppies can vote it out.
Done. Thanks for the heads up.
Quote from: iHashFury on September 20, 2015, 01:44:41 pm
witness ihashfury "id": "1.6.2562"

and

witness delegate.ihashfury "id": "1.6.1596"

are setup - if anyone would like to vote them in

I'll add them. Not sure it will do much good though.
Title: Re: Test Net for Advanced Users
Post by: boombastic on September 20, 2015, 05:35:02 pm: delegates online, please help to vote in

mr.agsexplorer: 1.6.3356
mrs.agsexplorer: 1.6.3360
boombastic: 1.6.828
Title: Re: Test Net for Advanced Users
Post by: boombastic on September 20, 2015, 06:14:35 pm: Quote from: xeroc on August 23, 2015, 04:11:29 pm
Quote from: puppies on August 23, 2015, 03:28:49 pm
Quote from: Xeldal on August 23, 2015, 03:21:59 pm
Quote from: puppies on August 23, 2015, 02:34:43 pm
Quote from: Xeldal on August 23, 2015, 02:28:47 pm
Are existing 0.9.2 delegates automatically imported as a witness or is it required to upgrade and create witness object? I'm hoping to skip sorting through the hundreds of balance id's for a proper balance that also existed on the 20th.

Thank you betax, your guide was very helpful. +5%

All existing delegates are imported as witnesses. When you get your node set up let us know and we will vote you in.

I believe I'm up now. ID: 1.6.1624
seems I don't have my owner key imported into my vps. I won't be able to vote till after work. I'm sure someone else will vote you in.
Code: [Select]
0 exception: unspecified 3030001 tx_missing_active_auth: missing required active authority Missing Active Authority 1.2.63353
You may need to import the ACTIVE_KEY too!

I think it may be a good idea to put a note in the wiki file under the paragraph saying something like "if your active key is different from your owner key, you need to import active_key as well". It will be handy for people following the wiki instruction. @xeroc
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 20, 2015, 06:53:52 pm: Quote from: boombastic on September 20, 2015, 06:14:35 pm
Quote from: xeroc on August 23, 2015, 04:11:29 pm
Quote from: puppies on August 23, 2015, 03:28:49 pm
Quote from: Xeldal on August 23, 2015, 03:21:59 pm
Quote from: puppies on August 23, 2015, 02:34:43 pm
Quote from: Xeldal on August 23, 2015, 02:28:47 pm
Are existing 0.9.2 delegates automatically imported as a witness or is it required to upgrade and create witness object? I'm hoping to skip sorting through the hundreds of balance id's for a proper balance that also existed on the 20th.

Thank you betax, your guide was very helpful. +5%

All existing delegates are imported as witnesses. When you get your node set up let us know and we will vote you in.

I believe I'm up now. ID: 1.6.1624
seems I don't have my owner key imported into my vps. I won't be able to vote till after work. I'm sure someone else will vote you in.
Code: [Select]
0 exception: unspecified 3030001 tx_missing_active_auth: missing required active authority Missing Active Authority 1.2.63353
You may need to import the ACTIVE_KEY too!

I think it may be a good idea to put a note in the wiki file under the paragraph saying something like "if your active key is different from your owner key, you need to import active_key as well". It will be handy for people following the wiki instruction. @xeroc
Agreed .. do you have a github account and can just do it?
Title: Re: Test Net for Advanced Users
Post by: abit on September 20, 2015, 08:35:24 pm: Quote from: boombastic on September 20, 2015, 06:14:35 pm
Quote from: xeroc on August 23, 2015, 04:11:29 pm
Quote from: puppies on August 23, 2015, 03:28:49 pm
Quote from: Xeldal on August 23, 2015, 03:21:59 pm
Quote from: puppies on August 23, 2015, 02:34:43 pm
Quote from: Xeldal on August 23, 2015, 02:28:47 pm
Are existing 0.9.2 delegates automatically imported as a witness or is it required to upgrade and create witness object? I'm hoping to skip sorting through the hundreds of balance id's for a proper balance that also existed on the 20th.

Thank you betax, your guide was very helpful. +5%

All existing delegates are imported as witnesses. When you get your node set up let us know and we will vote you in.

I believe I'm up now. ID: 1.6.1624
seems I don't have my owner key imported into my vps. I won't be able to vote till after work. I'm sure someone else will vote you in.
Code: [Select]
0 exception: unspecified 3030001 tx_missing_active_auth: missing required active authority Missing Active Authority 1.2.63353
You may need to import the ACTIVE_KEY too!

I think it may be a good idea to put a note in the wiki file under the paragraph saying something like "if your active key is different from your owner key, you need to import active_key as well". It will be handy for people following the wiki instruction. @xeroc
I think owner_key is not required. Only need active_key.
Title: Re: Test Net for Advanced Users
Post by: abit on September 20, 2015, 09:30:09 pm: Quote from: lakerta06 on September 19, 2015, 07:34:33 pm
Maybe that whale is bm. Isnt he handling some whale's stake? Maybe he wants to run some tests with init delegates.

Just speculating though. Dont take me too serious
Yes, it's BM. And he's not voting. It causes the network to unable to have more than 11 witnesses.
Title: Re: Test Net for Advanced Users
Post by: abit on September 20, 2015, 09:31:33 pm: Web wallet of test network https://graphene.bitshares.org/ is live now.

Try market: https://graphene.bitshares.org/#/exchange/trade/ABITUSDA_CORE
Title: Re: Test Net for Advanced Users
Post by: mike623317 on September 21, 2015, 12:33:37 am: for me, when i click PAY the TO field is populated with my own address. Is this just for testing?
The current account should be in the FROM field, not the TO.
Title: Re: Test Net for Advanced Users
Post by: cube on September 21, 2015, 03:36:25 am: I have updated the system time via ntp. But I get this from the console:

<code>
1682280ms th_a application.cpp:428 handle_transaction ] Got transaction from network
1682436ms th_a application.cpp:428 handle_transaction ] Got transaction from network
1682473ms th_a application.cpp:388 handle_block ] Got block #63710 with time 2015-09-21T03:34:06 from network with latency of -40138 ms from init10
1682668ms th_a application.cpp:428 handle_transaction ] Got transaction from network
1682697ms th_a application.cpp:428 handle_transaction ] Got transaction from network
1
</code>

latency of -40138 ms? This looks strange. Is it a bug?
Title: Re: Test Net for Advanced Users
Post by: alt on September 21, 2015, 05:41:45 am: Quote from: abit on September 20, 2015, 09:31:33 pm
Web wallet of test network https://graphene.bitshares.org/ is live now.

Try market: https://graphene.bitshares.org/#/exchange/trade/ABITUSDA_CORE
can you give me some USD for test?
my account is altgo, thanks.
Title: Re: Test Net for Advanced Users
Post by: spartako on September 21, 2015, 07:26:21 am: I wake up this morning with the witness crashed, this is the error:

Code: [Select]
witness_node: /home/spartako/graphene/libraries/net/node.cpp:2488: void graphene::net::detail::node_impl::on_blockchain_item_ids_inventory_message(graphene::net::peer_connection*, const graphene::net::blockchain_item_ids_inventory_message&): Assertion `originating_peer->last_block_number_delegate_has_seen == _delegate->get_block_number(originating_peer->last_block_delegate_has_seen)' failed.
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 21, 2015, 07:33:13 am: Quote from: spartako on September 21, 2015, 07:26:21 am
I wake up this morning with the witness crashed with this error:

Code: [Select]
witness_node: /home/spartako/graphene/libraries/net/node.cpp:2488: void graphene::net::detail::node_impl::on_blockchain_item_ids_inventory_message(graphene::net::peer_connection*, const graphene::net::blockchain_item_ids_inventory_message&): Assertion `originating_peer->last_block_number_delegate_has_seen == _delegate->get_block_number(originating_peer->last_block_delegate_has_seen)' failed.

Same here:
Code: [Select]
13676d040372e2316","0000c1e66d1af92b560c6c632c9caade74c46d2d"] 2878300ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["0000c1dbab0c56a1818b4b96b7db480dde690c90","0000c1e1b20e19081ed1f7686732706fc60fba9a","0000c1e4adff2782c18a66e13676d040372e2316","0000c1e66d1af92b560c6c632c9caade74c46d2d"] 2878300ms th_a application.cpp:695 get_blockchain_synop ] synopsis: ["0000c1dbab0c56a1818b4b96b7db480dde690c90","0000c1e1b20e19081ed1f7686732706fc60fba9a","0000c1e4adff2782c18a66e13676d040372e2316","0000c1e66d1af92b560c6c632c9caade74c46d2d"] witness_node: /home/calabiyau/graphene/libraries/net/node.cpp:2488: void graphene::net::detail::node_impl::on_blockchain_item_ids_inventory_message(graphene::net::peer_connection*, const graphene::net::blockchain_item_ids_inventory_message&): Assertion `originating_peer->last_block_number_delegate_has_seen == _delegate->get_block_number(originating_peer->last_block_delegate_has_seen)' failed. Aborted (core dumped)
Title: Re: Test Net for Advanced Users
Post by: abit on September 21, 2015, 07:51:49 am: Quote from: alt on September 21, 2015, 05:41:45 am
Quote from: abit on September 20, 2015, 09:31:33 pm
Web wallet of test network https://graphene.bitshares.org/ is live now.

Try market: https://graphene.bitshares.org/#/exchange/trade/ABITUSDA_CORE
can you give me some USD for test?
my account is altgo, thanks.
Do you have some CORE? Try borrow some USD from the bond market.
It's not a UIA, but a pegged asset.
Title: Re: Test Net for Advanced Users
Post by: abit on September 21, 2015, 07:57:32 am: Looks like witness init0 is down.
Title: Re: Test Net for Advanced Users
Post by: betax on September 21, 2015, 09:02:33 am: Hi what chain / snapshot are we using? **confused***
Title: Re: Test Net for Advanced Users
Post by: spartako on September 21, 2015, 09:09:36 am: Quote from: betax on September 21, 2015, 09:02:33 am
Hi what chain / snapshot are we using? **confused***

This is the chain:
https://github.com/cryptonomex/graphene/releases/tag/test3
Title: Re: Test Net for Advanced Users
Post by: betax on September 21, 2015, 09:13:31 am: Quote from: spartako on September 21, 2015, 09:09:36 am
Quote from: betax on September 21, 2015, 09:02:33 am
Hi what chain / snapshot are we using? **confused***

This is the chain:
https://github.com/cryptonomex/graphene/releases/tag/test3

Thanks, that is what I thought. ;)

Edit: I had spun 3 witnesses for testing, hence my cli client was connecting to an old one, I had not killed from test_net 2. FYI if any on the same situation, although very unlikely.
Title: Re: Test Net for Advanced Users
Post by: abit on September 21, 2015, 09:49:06 am: Quote from: betax on September 21, 2015, 09:13:31 am
Quote from: spartako on September 21, 2015, 09:09:36 am
Quote from: betax on September 21, 2015, 09:02:33 am
Hi what chain / snapshot are we using? **confused***

This is the chain:
https://github.com/cryptonomex/graphene/releases/tag/test3

Thanks, that is what I thought. ;)

Edit: I had spun 3 witnesses for testing, hence my cli client was connecting to an old one, I had not killed from test_net 2. FYI if any on the same situation, although very unlikely.
If the seed node is not working, use this seed node: 188.165.233.53:1776
Title: Re: Test Net for Advanced Users
Post by: betax on September 21, 2015, 09:59:03 am: Thanks ! That was the other issue.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 01:39:39 pm: It looks like there are now 23 active witnesses voted in and 77.3% witness participation.

I have pushed an update to the P2P code that might fix some nodes that (such as my init node) that got stuck on an orphan branch.
Title: Re: Test Net for Advanced Users
Post by: spartako on September 21, 2015, 01:50:49 pm: Quote from: bytemaster on September 21, 2015, 01:39:39 pm
It looks like there are now 23 active witnesses voted in and 77.3% witness participation.

I have pushed an update to the P2P code that might fix some nodes that (such as my init node) that got stuck on an orphan branch.

I tried to compile the master but I have this error:

Code: [Select]
/home/spartako/graphene/libraries/chain/account_object.cpp:71:54: error: ‘props’ was not declared in this scope share_type reserveed = cut_fee(network_cut, props.parameters.reserve_percent_of_fee); ^ libraries/chain/CMakeFiles/graphene_chain.dir/build.make:997: recipe for target 'libraries/chain/CMakeFiles/graphene_chain.dir/account_object.cpp.o' failed make[2]: *** [libraries/chain/CMakeFiles/graphene_chain.dir/account_object.cpp.o] Error 1 CMakeFiles/Makefile2:787: recipe for target 'libraries/chain/CMakeFiles/graphene_chain.dir/all' failed make[1]: *** [libraries/chain/CMakeFiles/graphene_chain.dir/all] Error 2 Makefile:113: recipe for target 'all' failed make: *** [all] Error 2
Title: Re: Test Net for Advanced Users
Post by: betax on September 21, 2015, 02:26:20 pm: Quote from: bytemaster on September 21, 2015, 01:39:39 pm
It looks like there are now 23 active witnesses voted in and 77.3% witness participation.

I have pushed an update to the P2P code that might fix some nodes that (such as my init node) that got stuck on an orphan branch.

Hi can anybody vote me in? my votes don't seem to appear. Thanks!

Forgot: betaxtrade and 1.6.5252
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 02:29:46 pm: Quote from: betax on September 21, 2015, 02:26:20 pm
Quote from: bytemaster on September 21, 2015, 01:39:39 pm
It looks like there are now 23 active witnesses voted in and 77.3% witness participation.

I have pushed an update to the P2P code that might fix some nodes that (such as my init node) that got stuck on an orphan branch.

Hi can anybody vote me in? my votes don't seem to appear. Thanks!

Forgot: betaxtrade and 1.6.5252

Added you to the slate, you should be in at the next maintenance interval (est 30 min)
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 21, 2015, 02:30:53 pm: Quote from: betax on September 21, 2015, 02:26:20 pm
Quote from: bytemaster on September 21, 2015, 01:39:39 pm
It looks like there are now 23 active witnesses voted in and 77.3% witness participation.

I have pushed an update to the P2P code that might fix some nodes that (such as my init node) that got stuck on an orphan branch.

Hi can anybody vote me in? my votes don't seem to appear. Thanks!

Forgot: betaxtrade and 1.6.5252

same here, I still have 0 votes

Code: [Select]
get_witness xeldal { "id": "1.6.4949", "witness_account": "1.2.86459", "last_aslot": 0, "signing_key": "G......M", "vote_id": "1:4948", "total_votes": 0, "url": "", "total_missed": 0 }
Title: Re: Test Net for Advanced Users
Post by: spartako on September 21, 2015, 02:31:34 pm: Please vote for spartako (1.6.4232), I am ready but out of the current witness set.

Thanks!
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 02:48:13 pm: Spart and xeldal you should be in
Title: Re: Test Net for Advanced Users
Post by: clayop on September 21, 2015, 02:52:48 pm: Please vote me in: delegate-clayop 1.6.1538
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 02:55:46 pm: Quote from: clayop on September 21, 2015, 02:52:48 pm
Please vote me in: delegate-clayop 1.6.1538

Done
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 03:00:21 pm: There are now 27 active witnesses.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 21, 2015, 03:13:50 pm: Quote from: iHashFury on September 20, 2015, 01:44:41 pm
witness ihashfury "id": "1.6.2562"

and

witness delegate.ihashfury "id": "1.6.1596"

are setup - if anyone would like to vote them in

is there room for more?
Title: Re: Test Net for Advanced Users
Post by: puppies on September 21, 2015, 03:14:27 pm: I removed my votes from those witnesses missing blocks. bitcube and riverhead. I added the one btsnow delegate that seems to be up. delegate-dev3.btsnow. My current slate is
Code: [Select]
betaxtrade boombastic calabiyau dele-puppy delegate-1.lafona delegate-clayop delegate-dev3.btsnow delegate.ihashfury fox ihashfury in.abit init0 init1 init10 init2 init3 init4 init5 init6 init7 init8 init9 mr.agsexplorer mrs.agsexplorer roadscape spartako wackou xeldalLet me know when your node is up and ready, and I'll throw my vote your way. Last I checked I had about 12M bts proxied through puppies.
Title: Re: Test Net for Advanced Users
Post by: wackou on September 21, 2015, 03:15:57 pm: please also vote for wackou (1.6.5248), witness running and ready to produce blocks! :)
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 21, 2015, 03:20:02 pm: Since are are only brave members in this thread, I'll just drop this here and ask those that run an active witness to publish feeds if possible:
https://github.com/xeroc/python-graphenelib/blob/develop/scripts/pricefeeds.py
Run this script once every hour or 30 minutes .. I will improve it over time ..

If you run into trouble you can post here or in the other thread: https://bitsharestalk.org/index.php/topic,18382.new.html#new

Good luck :)

PS. IIRC it only publishes feeds for USD EUR and CNY if I am not mistaken .. if you want to pimp it on your own, please send a pull request ..
Title: Re: Test Net for Advanced Users
Post by: spartako on September 21, 2015, 03:21:03 pm: I tried to spam the network and the results are quite impressive! Spamming alone I reached 242 tx per block (80 tx/sec) we can reach bigger number in this test net

Code: [Select]
76079 '1.6.4' 'init3' 81 76078 '1.6.7' 'init6' 242 76077 '1.6.828' 'boombastic' 116 76076 '1.6.12' 'init11' 98 76075 '1.6.1538' 'delegate-clayop' 11 76074 '1.6.11' 'init10' 47 76073 '1.6.5252' 'betaxtrade' 5 76072 '1.6.4232' 'spartako' 0 76071 '1.6.4949' 'xeldal' 0 76070 '1.6.2' 'init1' 0 76069 '1.6.3360' 'mrs.agsexplorer' 0 76068 '1.6.3356' 'mr.agsexplorer' 12 76067 '1.6.9' 'init8' 147 76066 '1.6.1543' 'delegate-dev3.btsnow' 77 76065 '1.6.3' 'init2' 89 76064 '1.6.5247' 'in.abit' 27 76063 '1.6.10' 'init9' 52 76062 '1.6.5' 'init4' 50 76061 '1.6.6' 'init5' 43 76060 '1.6.8' 'init7' 0
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 03:22:30 pm: bitcube and riverhead are not producing blocks... any particular reason?
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 21, 2015, 03:24:10 pm: Quote from: spartako on September 21, 2015, 03:21:03 pm
I tried to spam the network and the results are quite impressive! Spamming alone I reached 242 tx per block (80 tx/sec) we can reach bigger number in this test net

Code: [Select]
76079 '1.6.4' 'init3' 81 76078 '1.6.7' 'init6' 242 76077 '1.6.828' 'boombastic' 116 76076 '1.6.12' 'init11' 98 76075 '1.6.1538' 'delegate-clayop' 11 76074 '1.6.11' 'init10' 47 76073 '1.6.5252' 'betaxtrade' 5 76072 '1.6.4232' 'spartako' 0 76071 '1.6.4949' 'xeldal' 0 76070 '1.6.2' 'init1' 0 76069 '1.6.3360' 'mrs.agsexplorer' 0 76068 '1.6.3356' 'mr.agsexplorer' 12 76067 '1.6.9' 'init8' 147 76066 '1.6.1543' 'delegate-dev3.btsnow' 77 76065 '1.6.3' 'init2' 89 76064 '1.6.5247' 'in.abit' 27 76063 '1.6.10' 'init9' 52 76062 '1.6.5' 'init4' 50 76061 '1.6.6' 'init5' 43 76060 '1.6.8' 'init7' 0
Seems I need to tune the max value of the gauge quite soon ..
I intend to work more on the stats page once I find the time ..
Title: Re: Test Net for Advanced Users
Post by: spartako on September 21, 2015, 03:27:52 pm: My delegate just crashed :(
Code: [Select]
witness_node: /home/spartako/graphene/libraries/net/node.cpp:2319: std::vector<fc::ripemd160> graphene::net::detail::node_impl::create_blockchain_synopsis_for_peer(const graphene::net::peer_connection*): Assertion `synopsis.back() == original_ids_of_items_to_get->back()' failed.
I'm syncing...
Title: Re: Test Net for Advanced Users
Post by: mindphlux on September 21, 2015, 03:30:00 pm: Hello all,

Can you please give me instructions how to spam the network with transactions, do I need to install a CLI version?

Thank you
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 03:53:36 pm: Quote from: wackou on September 21, 2015, 03:15:57 pm
please also vote for wackou (1.6.5248), witness running and ready to produce blocks! :)

You have been voted for.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 03:58:59 pm: Quote from: spartako on September 21, 2015, 03:27:52 pm
My delegate just crashed :(
Code: [Select]
witness_node: /home/spartako/graphene/libraries/net/node.cpp:2319: std::vector<fc::ripemd160> graphene::net::detail::node_impl::create_blockchain_synopsis_for_peer(const graphene::net::peer_connection*): Assertion `synopsis.back() == original_ids_of_items_to_get->back()' failed.
I'm syncing...

That appears to only happen in debug builds. We will look into that issue closer.
Title: Re: Test Net for Advanced Users
Post by: jtme on September 21, 2015, 04:00:53 pm: If more witnesses needed, please vote me in.
( runs in vps with latencies around 150ms )

get_witness jtm1
{
"id": "1.6.5251",
"witness_account": "1.2.92002"
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 04:12:09 pm: Quote from: jtme on September 21, 2015, 04:00:53 pm
If more witnesses needed, please vote me in.
( runs in vps with latencies around 150ms )

get_witness jtm1
{
"id": "1.6.5251",
"witness_account": "1.2.92002"

Voted.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 04:12:58 pm: Participation Rate: 96.875%

With 27 witnesses! Only bitcube is not producing and I am not voting for him :)
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 21, 2015, 04:34:16 pm: Code: [Select]
get_witness ihashfury { "id": "1.6.2562", "witness_account": "1.2.38577", "last_aslot": 0, "signing_key": "GPH5yzrzYt3VLaN8ksyv6ypXZpZ22k2mJA4xMvv5eznskuMbNQ8Mj", "vote_id": "1:2561", "total_votes": 0, "url": "", "total_missed": 0 } unlocked >>> get_witness delegate.ihashfury get_witness delegate.ihashfury { "id": "1.6.1596", "witness_account": "1.2.22473", "last_aslot": 0, "signing_key": "GPH53CQ3wX2jt9bmJTY2cFpcKoouauB16QdqSfe6fVCCezSGRkhvT", "vote_id": "1:1595", "total_votes": 0, "url": "", "total_missed": 0 } unlocked >>>
subtlety is not my strong point!
Title: Re: Test Net for Advanced Users
Post by: roadscape on September 21, 2015, 04:46:19 pm: Please vote for roadscape!

Code: [Select]
get_witness roadscape { "id": "1.6.5249", "witness_account": "1.2.67429"
Title: Re: Test Net for Advanced Users
Post by: abit on September 21, 2015, 05:09:41 pm: Quote from: xeroc on September 21, 2015, 03:20:02 pm
Since are are only brave members in this thread, I'll just drop this here and ask those that run an active witness to publish feeds if possible:
https://github.com/xeroc/python-graphenelib/blob/develop/scripts/pricefeeds.py
Run this script once every hour or 30 minutes .. I will improve it over time ..

If you run into trouble you can post here or in the other thread: https://bitsharestalk.org/index.php/topic,18382.new.html#new

Good luck :)

PS. IIRC it only publishes feeds for USD EUR and CNY if I am not mistaken .. if you want to pimp it on your own, please send a pull request ..
Great work +5%
I believe there was a bug which prevents prices be feed into USD and other pre-defined bitAssets, but it's possible with user-issued pegged assets, for example ABITUSDA.
See https://github.com/cryptonomex/graphene/issues/328
Title: Re: Test Net for Advanced Users
Post by: lafona on September 21, 2015, 05:10:59 pm: Also seem to be having the same issue as ihashfury.
Code: [Select]
get_witness delegate-1.lafona { "id": "1.6.1531", "witness_account": "1.2.22396", "last_aslot": 0, "signing_key": "GPH5DCL5nbhL13sXBh1mwQp5pUBSw7rmwjWeiiy5b2Z2UxuYf8spU", "vote_id": "1:1530", "total_votes": 0, "url": "", "total_missed": 0 }
I even voted for myself, so it should show some votes.

Code: [Select]
vote_for_witness delegate-1.lafona delegate-1.lafona true true { "ref_block_num": 12218, "ref_block_prefix": 4139592174, "expiration": "2015-09-21T16:48:51", "operations": [[ 6,{ "fee": { "amount": 1002929, "asset_id": "1.3.0" }, "account": "1.2.22396", "new_options": { "memo_key": "GPH5DCL5nbhL13sXBh1mwQp5pUBSw7rmwjWeiiy5b2Z2UxuYf8spU", "voting_account": "1.2.5", "num_witness": 0, "num_committee": 0, "votes": [ "1:1530" ], "extensions": [] }, "extensions": [] } ] ], "extensions": [], "signatures": [ "1f7e93d12f8eea0d4844aa4a804fd41b387cecad8344224e7f8d46acda96880f2b372027a57468750770e909eedf7fda3f4af14c59e66cafd38f76589241999396" ] }
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 21, 2015, 05:12:10 pm: calabiyau still up & running, waiting for some votes:

"id": "1.6.1063",
"witness_account": "1.2.14634"
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 21, 2015, 05:36:19 pm: Quote from: lafona on September 21, 2015, 05:10:59 pm
Also seem to be having the same issue as ihashfury.
Code: [Select]
get_witness delegate-1.lafona { "id": "1.6.1531", "witness_account": "1.2.22396", "last_aslot": 0, "signing_key": "GPH5DCL5nbhL13sXBh1mwQp5pUBSw7rmwjWeiiy5b2Z2UxuYf8spU", "vote_id": "1:1530", "total_votes": 0, "url": "", "total_missed": 0 }
I even voted for myself, so it should show some votes.

Code: [Select]
vote_for_witness delegate-1.lafona delegate-1.lafona true true { "ref_block_num": 12218, "ref_block_prefix": 4139592174, "expiration": "2015-09-21T16:48:51", "operations": [[ 6,{ "fee": { "amount": 1002929, "asset_id": "1.3.0" }, "account": "1.2.22396", "new_options": { "memo_key": "GPH5DCL5nbhL13sXBh1mwQp5pUBSw7rmwjWeiiy5b2Z2UxuYf8spU", "voting_account": "1.2.5", "num_witness": 0, "num_committee": 0, "votes": [ "1:1530" ], "extensions": [] }, "extensions": [] } ] ], "extensions": [], "signatures": [ "1f7e93d12f8eea0d4844aa4a804fd41b387cecad8344224e7f8d46acda96880f2b372027a57468750770e909eedf7fda3f4af14c59e66cafd38f76589241999396" ] }

I'm up-dating to latest master to see if it helps
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 21, 2015, 05:43:11 pm: Quote from: bytemaster on September 21, 2015, 03:22:30 pm
bitcube and riverhead are not producing blocks... any particular reason?

Must have gotten on a fork. Rebuilding with your most recent submit and should be back online in a few minutes.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 05:50:10 pm: Quote from: iHashFury on September 21, 2015, 05:36:19 pm
Quote from: lafona on September 21, 2015, 05:10:59 pm
Also seem to be having the same issue as ihashfury.
Code: [Select]
get_witness delegate-1.lafona { "id": "1.6.1531", "witness_account": "1.2.22396", "last_aslot": 0, "signing_key": "GPH5DCL5nbhL13sXBh1mwQp5pUBSw7rmwjWeiiy5b2Z2UxuYf8spU", "vote_id": "1:1530", "total_votes": 0, "url": "", "total_missed": 0 }
I even voted for myself, so it should show some votes.

Code: [Select]
vote_for_witness delegate-1.lafona delegate-1.lafona true true { "ref_block_num": 12218, "ref_block_prefix": 4139592174, "expiration": "2015-09-21T16:48:51", "operations": [[ 6,{ "fee": { "amount": 1002929, "asset_id": "1.3.0" }, "account": "1.2.22396", "new_options": { "memo_key": "GPH5DCL5nbhL13sXBh1mwQp5pUBSw7rmwjWeiiy5b2Z2UxuYf8spU", "voting_account": "1.2.5", "num_witness": 0, "num_committee": 0, "votes": [ "1:1530" ], "extensions": [] }, "extensions": [] } ] ], "extensions": [], "signatures": [ "1f7e93d12f8eea0d4844aa4a804fd41b387cecad8344224e7f8d46acda96880f2b372027a57468750770e909eedf7fda3f4af14c59e66cafd38f76589241999396" ] }

I'm up-dating to latest master to see if it helps

Votes are only updated once every hour. Wait 11 minutes and you should see your votes.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 21, 2015, 05:54:22 pm: New witness_node crashed shortly after startup.

Code: [Select]
(gdb) run --rpc-endpoint "127.192.168.1.11:8090" -d test_net_3 -s "104.236.118.105:1776" --genesis-json sep-18-testnet-genesis.json --resync-blockchain Starting program: /home/james/github/graphene/programs/witness_node/witness_node --rpc-endpoint "127.192.168.1.11:8090" -d test_net_3 -s "104.236.118.105:1776" --genesis-json sep-18-testnet-genesis.json --resync-blockchain [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 3104986ms th_a witness.cpp:83 plugin_initialize ] witness plugin: plugin_initialize() begin 3104987ms th_a witness.cpp:93 plugin_initialize ] key_id_to_wif_pair: ["GPH6BJYGH.....","5....."] 3104987ms th_a witness.cpp:111 plugin_initialize ] witness plugin: plugin_initialize() end 3104987ms th_a db_management.cpp:95 wipe ] Wiping database 3104990ms th_a object_database.cpp:82 wipe ] Wiping object_database. 3104991ms th_a application.cpp:301 startup ] Detected unclean shutdown. Replaying blockchain... 3104992ms th_a application.cpp:242 operator() ] Initializing database... 3131559ms th_a db_management.cpp:42 reindex ] reindexing blockchain 3131560ms th_a db_management.cpp:95 wipe ] Wiping database 3131562ms th_a object_database.cpp:82 wipe ] Wiping object_database. 3144646ms th_a db_management.cpp:49 reindex ] !no last block 3144647ms th_a db_management.cpp:50 reindex ] last_block: 3144682ms th_a thread.cpp:95 thread ] name:ntp tid:140737315571456 3144682ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] [New Thread 0x7ffff4135700 (LWP 13774)] [New Thread 0x7ffff4936700 (LWP 13773)] [New Thread 0x7ffff5137700 (LWP 13772)] [New Thread 0x7ffff5b38700 (LWP 13771)] 3144691ms th_a thread.cpp:95 thread ] name:p2p tid:140737296688896 3144723ms ntp ntp.cpp:81 request_now ] sending request to 76.191.88.3:123 3144728ms th_a application.cpp:122 reset_p2p_node ] Adding seed node 104.236.118.105:1776 3144732ms th_a application.cpp:134 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:60399 3144733ms th_a application.cpp:184 reset_websocket_serv ] Configured websocket rpc to listen on 127.192.168.1.11:8090 3144735ms th_a main.cpp:176 main ] Exiting with error: 13 N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE: Invalid argument Invalid argument: error converting string to IP endpoint {"what":"Invalid argument"} th_a ip.cpp:84 from_string {} th_a application.cpp:187 reset_websocket_server {} th_a application.cpp:337 startup 3144808ms ntp ntp.cpp:147 read_loop ] received ntp reply from 76.191.88.3:123 3144808ms ntp ntp.cpp:161 read_loop ] ntp offset: -2899, round_trip_delay 80013 3144808ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to -2899 witness_node: /home/james/github/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Program received signal SIGABRT, Aborted. 0x00007ffff6979267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 55 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) trace Tracepoint 1 at 0x7ffff6979267: file ../sysdeps/unix/sysv/linux/raise.c, line 55. (gdb)
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 05:56:15 pm: Congrats on 100% participation rate with the current 27 witnesses most of which are on separate / unique machines :)
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 05:57:15 pm: Quote from: Riverhead on September 21, 2015, 05:54:22 pm

New witness_node crashed shortly after startup.

Code: [Select]
(gdb) run --rpc-endpoint "127.192.168.1.11:8090" -d test_net_3 -s "104.236.118.105:1776" --genesis-json sep-18-testnet-genesis.json --resync-blockchain Starting program: /home/james/github/graphene/programs/witness_node/witness_node --rpc-endpoint "127.192.168.1.11:8090" -d test_net_3 -s "104.236.118.105:1776" --genesis-json sep-18-testnet-genesis.json --resync-blockchain [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 3104986ms th_a witness.cpp:83 plugin_initialize ] witness plugin: plugin_initialize() begin 3104987ms th_a witness.cpp:93 plugin_initialize ] key_id_to_wif_pair: ["GPH6BJYGH.....","5....."] 3104987ms th_a witness.cpp:111 plugin_initialize ] witness plugin: plugin_initialize() end 3104987ms th_a db_management.cpp:95 wipe ] Wiping database 3104990ms th_a object_database.cpp:82 wipe ] Wiping object_database. 3104991ms th_a application.cpp:301 startup ] Detected unclean shutdown. Replaying blockchain... 3104992ms th_a application.cpp:242 operator() ] Initializing database... 3131559ms th_a db_management.cpp:42 reindex ] reindexing blockchain 3131560ms th_a db_management.cpp:95 wipe ] Wiping database 3131562ms th_a object_database.cpp:82 wipe ] Wiping object_database. 3144646ms th_a db_management.cpp:49 reindex ] !no last block 3144647ms th_a db_management.cpp:50 reindex ] last_block: 3144682ms th_a thread.cpp:95 thread ] name:ntp tid:140737315571456 3144682ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123] [New Thread 0x7ffff4135700 (LWP 13774)] [New Thread 0x7ffff4936700 (LWP 13773)] [New Thread 0x7ffff5137700 (LWP 13772)] [New Thread 0x7ffff5b38700 (LWP 13771)] 3144691ms th_a thread.cpp:95 thread ] name:p2p tid:140737296688896 3144723ms ntp ntp.cpp:81 request_now ] sending request to 76.191.88.3:123 3144728ms th_a application.cpp:122 reset_p2p_node ] Adding seed node 104.236.118.105:1776 3144732ms th_a application.cpp:134 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:60399 3144733ms th_a application.cpp:184 reset_websocket_serv ] Configured websocket rpc to listen on 127.192.168.1.11:8090 3144735ms th_a main.cpp:176 main ] Exiting with error: 13 N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE: Invalid argument Invalid argument: error converting string to IP endpoint {"what":"Invalid argument"} th_a ip.cpp:84 from_string {} th_a application.cpp:187 reset_websocket_server {} th_a application.cpp:337 startup 3144808ms ntp ntp.cpp:147 read_loop ] received ntp reply from 76.191.88.3:123 3144808ms ntp ntp.cpp:161 read_loop ] ntp offset: -2899, round_trip_delay 80013 3144808ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to -2899 witness_node: /home/james/github/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Program received signal SIGABRT, Aborted. 0x00007ffff6979267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 55 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) trace Tracepoint 1 at 0x7ffff6979267: file ../sysdeps/unix/sysv/linux/raise.c, line 55. (gdb)

Looks like a configuration error on the websocket server.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 06:04:41 pm: riverhead, ihashfury, and bitcube are currently misbehaving (missing blocks) on the test network.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 21, 2015, 06:06:20 pm: witness delegate.ihashfury is on the latest master branch.

Thank you for the votes

I need to update ihashfury to the latest branch
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 21, 2015, 06:06:40 pm: Quote from: bytemaster on September 21, 2015, 06:04:41 pm
riverhead, ihashfury, and bitcube are currently misbehaving (missing blocks) on the test network.

I screwed up one of the parameters. 127.192.168.1.11 is not a real IP address. Fixed and syncing fine.

Update: All good now :D
Title: Re: Test Net for Advanced Users
Post by: puppies on September 21, 2015, 08:01:13 pm: I am getting a different return for get_object 1.13.46 depending upon what box I pull it from. from my local box I get
Code: [Select]
get_object 1.13.46 [{ "id": "1.13.46", "owner": "1.2.22388", "balance": { "amount": 255000000, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 86400, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "3100167000000", "coin_seconds_earned_last_update": "2015-09-21T19:57:21" } ] } ]but my witness node shows amount as 311000000. Everything else is the same except for coin seconds earned. Both nodes show as being synced. What would cause this device to show up differently on different boxes?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 08:19:55 pm: Mac users now have a test full node with gui available: https://github.com/cryptonomex/graphene/releases/download/test3/Graphene-Sept18-Testnet.dmg

Note that the web GUI included is in progress and has known issues (such as exchange tab missing and menu bar display issues).

This is really more of a proof of concept full node release.
Title: Re: Test Net for Advanced Users
Post by: fav on September 21, 2015, 08:29:23 pm: @bytemaster can we test the affiliate system, or is this still in development?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 08:30:39 pm: Quote from: fav on September 21, 2015, 08:29:23 pm
@bytemaster can we test the affiliate system, or is this still in development?

Affiliate system is still TBD.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 21, 2015, 08:49:40 pm: witness ihashfury is now on latest master branch
Title: Re: Test Net for Advanced Users
Post by: Fox on September 21, 2015, 10:04:55 pm: Quote from: Fox on September 18, 2015, 11:40:39 pm
The Fox witness node is operational. Thanks in advance for your votes.
Code: [Select]
get_witness fox { "id": "1.6.2104", ... "total_votes": "1306663376502", ... }

How may I determine the threshold number of for votes required to be a witness at this time? I have votes, and watched a maintenance interval pass, but do not see my witness ID included in the active witnesses:
Code: [Select]
>>get_global_properties ], "active_witnesses": [ "1.6.1", ... "1.6.5252" ]
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 10:18:20 pm: All witnesses please upgrade to the latest master. We have checked in a few "hard-forking" fixes for publishing price feeds. This hardfork was required due to a misconfigured genesis state for bitassets preventing us from publishing feeds. Please do not attempt to publish price feeds for at least 24 hours to give all testers a chance to upgrade to the latest.

Fox I voted you in. The least approved witness is bitcube which as 13M votes...
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 10:26:49 pm: 31 active witnesses with 100% participation. I couldn't ask for a better set of testers!
Title: Re: Test Net for Advanced Users
Post by: clout on September 21, 2015, 10:47:03 pm: do delegates or witnesses produce feeds?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 21, 2015, 10:49:11 pm: Quote from: clout on September 21, 2015, 10:47:03 pm
do delegates or witnesses produce feeds?

Witnesses do (starting Wednesday)
Title: Re: Test Net for Advanced Users
Post by: spartako on September 21, 2015, 11:10:52 pm: Upgraded to the master, during the update I missed 2 blocks.

What is the best practice for not missing any block during an update?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 21, 2015, 11:15:18 pm: Quote from: bytemaster on September 21, 2015, 10:18:20 pm
All witnesses please upgrade to the latest master. We have checked in a few "hard-forking" fixes for publishing price feeds. This hardfork was required due to a misconfigured genesis state for bitassets preventing us from publishing feeds. Please do not attempt to publish price feeds for at least 24 hours to give all testers a chance to upgrade to the latest.

Fox I voted you in. The least approved witness is bitcube which as 13M votes...

delegate-clayop has upgraded.
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 21, 2015, 11:38:38 pm: Quote from: bytemaster on September 21, 2015, 10:18:20 pm
All witnesses please upgrade to the latest master. We have checked in a few "hard-forking" fixes for publishing price feeds. This hardfork was required due to a misconfigured genesis state for bitassets preventing us from publishing feeds. Please do not attempt to publish price feeds for at least 24 hours to give all testers a chance to upgrade to the latest.

Fox I voted you in. The least approved witness is bitcube which as 13M votes...

Forgive my ignorance.

How to "upgrade to latest master"?

Is this just "git pull master" and restart witness?, or does this require a complete rebuild and "git checkout master" ??

I assume "git checkout test3" would just be the same thing I'm already running.
Title: Re: Test Net for Advanced Users
Post by: abit on September 21, 2015, 11:43:02 pm: Quote from: bytemaster on September 21, 2015, 10:18:20 pm
All witnesses please upgrade to the latest master. We have checked in a few "hard-forking" fixes for publishing price feeds. This hardfork was required due to a misconfigured genesis state for bitassets preventing us from publishing feeds. Please do not attempt to publish price feeds for at least 24 hours to give all testers a chance to upgrade to the latest.

Fox I voted you in. The least approved witness is bitcube which as 13M votes...
in.abit is upgraded to latest commit.
Title: Re: Test Net for Advanced Users
Post by: abit on September 21, 2015, 11:50:35 pm: Quote from: Xeldal on September 21, 2015, 11:38:38 pm
Quote from: bytemaster on September 21, 2015, 10:18:20 pm
All witnesses please upgrade to the latest master. We have checked in a few "hard-forking" fixes for publishing price feeds. This hardfork was required due to a misconfigured genesis state for bitassets preventing us from publishing feeds. Please do not attempt to publish price feeds for at least 24 hours to give all testers a chance to upgrade to the latest.

Fox I voted you in. The least approved witness is bitcube which as 13M votes...

Forgive my ignorance.

How to "upgrade to latest master"?

Is this just "git pull master" and restart witness?, or does this require a complete rebuild and "git checkout master" ??

I assume "git checkout test3" would just be the same thing I'm already running.

Code: [Select]
git checkout master git pull git submodule update --init --recursive cmake . make
However make will fail if your witness_node is already running. So what I did is clone the repository to a new directory and run make there. With this trick it will achieve minimum down time. @spartako

Quote from: spartako on September 21, 2015, 11:10:52 pm
Upgraded to the master, during the update I missed 2 blocks.

What is the best practice for not missing any block during an update?
Title: Re: Test Net for Advanced Users
Post by: Fox on September 21, 2015, 11:52:01 pm: Quote from: spartako on September 21, 2015, 11:10:52 pm
What is the best practice for not missing any block during an update?

Run multiple nodes synced to the network; only producing blocks on a single node. Watch the github repository for updates. Upgrade a non-block producing node, then migrate block production to the upgraded node. Always ensure you have only a single node producing blocks so as not to introduce a fork.
Title: Re: Test Net for Advanced Users
Post by: alt on September 22, 2015, 12:06:40 am: need some vote, thanks.
Code: [Select]
get_witness delegate.baozi { "id": "1.6.1569", "witness_account": "1.2.22439",
Title: Re: Test Net for Advanced Users
Post by: puppies on September 22, 2015, 12:28:36 am: dele-puppy is updated. A means of turning block production on and off within the witness node would be really useful for upgrading.
Title: Re: Test Net for Advanced Users
Post by: muse-umum on September 22, 2015, 01:21:19 am: What is the minimum hardware requirement to participate in the testnet?
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 22, 2015, 01:32:01 am: riverhead is updated.
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 22, 2015, 02:01:21 am: xeldal is updated
Title: Re: Test Net for Advanced Users
Post by: roadscape on September 22, 2015, 03:44:52 am: roadscape is updated, but seems to have been voted out.
Title: Re: Test Net for Advanced Users
Post by: Fox on September 22, 2015, 04:24:16 am: Quote from: heyD on September 22, 2015, 01:21:19 am
What is the minimum hardware requirement to participate in the testnet?
Seed node (stable): Shared CPU, 768MB RAM
Witness node (stable): 2 Cores, 3.5GB RAM

I attempted to run the witness node on the lower specs VPS, but the node would not reliably produce blocks, so I returned to Witness node (stable) specs above.
Title: Re: Test Net for Advanced Users
Post by: theoretical on September 22, 2015, 05:19:45 am: Quote from: spartako on September 21, 2015, 11:10:52 pm
What is the best practice for not missing any block during an update?

The update_witness command in CLI wallet allows you to change your witness's block signing key. This architecture allows several different downtime-free update procedures according to your specific hosting situation:

(1) Create new witness on new server with new block signing key (you can use suggest_brain_key in CLI wallet, or the get_dev_key binary, to generate a new key). When the new witness is synced, run update_witness to change your key, shutdown old witness and delete old server. Good method if you use a pay-by-the-hour hosting provider that lets you quickly create and destroy servers (e.g. DigitalOcean).

(2) Create new witness on the same server with new block signing key in different datadir. When new witness is synced, update_witness to change your block signing key and shut down old witness. Good method if you have a large server capable of running two witnesses at once (e.g. dedicated host).

(3) Create temporary witness on your own personal machine. When it is synced, update_witness to change your block signing key and cause the temporary witness to start producing. Then shut down the old witness and spin up the new witness on the same server; it is okay if it takes some time, because your temporary witness is still signing blocks. Then when new witness is ready, run update_witness again to change your block signing key back (or create another new key). Good method if you have a decent personal machine you can occasionally put on witness duty for a few blocks when you're doing an upgrade, and don't want to mess with multiple VPS's as in (1) or pay for a large server as in (2).

Also note that the block signing key can be different from the active and owner keys which control account funds. The only key which needs to live unencrypted on a machine with 24/7 internet connectivity is the block signing key; if an attacker compromises the server, the only thing they can do with the block signing key is sign blocks.

I designed this system, and my goal was to give witnesses better options for dealing with the various IT headaches of signing blocks in DPOS.

I just gave update_witness quite a real-world test on this testnet -- I initially ran all of the init witnesses in a single process on the cloud server that I used to create the testnet, then bytemaster and I migrated a bunch of them to different machines within the first day. In prepping them for the hardfork, I've had to shut down and re-create the witnesses, and also migrated them to better balance them between the multiple machines. I used the update_witness command for all of this and achieved it with minimal downtime. In particular for today's hardfork upgrade, I had no downtime on block signing during the upgrade / migration, even though I had to upgrade 8 witnesses on multiple machines, and I also migrated some of those witnesses to better balance them between machines. The update_witness code and its supporting logic in the block production loop are rock solid!

Some of my init witnesses have been down, but that's mostly due to issues in the p2p layer, the worst of which are resolved in the latest code.

I think I'll write this up in a wiki article sometime this week
Title: Re: Test Net for Advanced Users
Post by: puppies on September 22, 2015, 05:42:38 am: Very very nice work theoretical. Thank you for explaining. I really like this method of turning block production on and off. Allows me to run two witness nodes and switch back and forth without having to worry about double signing.
Title: Re: Test Net for Advanced Users
Post by: boombastic on September 22, 2015, 06:04:23 am: thanks @theoretical, it's very useful.
Title: Re: Test Net for Advanced Users
Post by: boombastic on September 22, 2015, 06:19:46 am: Therefore, in the witness server, I should only use the witness signing key to boot up the witness node, but to publish price feed, still need to import owner key/active key to cli_wallet and keep wallet unlock. Are there any suggestions to make this more secure in case server is compromised?
Title: Re: Test Net for Advanced Users
Post by: cube on September 22, 2015, 09:04:39 am: Quote from: bytemaster on September 21, 2015, 10:18:20 pm
All witnesses please upgrade to the latest master. We have checked in a few "hard-forking" fixes for publishing price feeds. This hardfork was required due to a misconfigured genesis state for bitassets preventing us from publishing feeds. Please do not attempt to publish price feeds for at least 24 hours to give all testers a chance to upgrade to the latest.

Fox I voted you in. The least approved witness is bitcube which as 13M votes...

My witness node was having problem with negative latency values which I suspect my computer's system clock was not working properly. I sent my PC for repair and just got it back. I will get the witness node up soon. Please give bitcube a chance.

I am compiling the latest master and the node should be up soon.

Edit: bitcube witness is updated with the latest master and fully re-synced. Please vote for bitcube.

p.s.: Latency values are back to positive.

Code: [Select]
634472ms th_a application.cpp:388 handle_block ] Got block #97888 with time 2015-09-22T10:10:33 from network with latency of 25101 ms from init8 636002ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 636526ms th_a application.cpp:388 handle_block ] Got block #97889 with time 2015-09-22T10:10:36 from network with latency of 24155 ms from init6 637996ms th_a application.cpp:518 get_item ] Serving up block #97889 639429ms th_a application.cpp:388 handle_block ] Got block #97890 with time 2015-09-22T10:10:39 from network with latency of 24059 ms from init3
Title: Re: Test Net for Advanced Users
Post by: spartako on September 22, 2015, 09:14:11 am: Quote from: theoretical on September 22, 2015, 05:19:45 am
Quote from: spartako on September 21, 2015, 11:10:52 pm
What is the best practice for not missing any block during an update?

The update_witness command in CLI wallet allows you to change your witness's block signing key. This architecture allows several different downtime-free update procedures according to your specific hosting situation:
...

Thanks theoretical! Great work!
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 22, 2015, 09:29:28 am: Quote from: spartako on September 22, 2015, 09:14:11 am
Quote from: theoretical on September 22, 2015, 05:19:45 am
Quote from: spartako on September 21, 2015, 11:10:52 pm
What is the best practice for not missing any block during an update?

The update_witness command in CLI wallet allows you to change your witness's block signing key. This architecture allows several different downtime-free update procedures according to your specific hosting situation:
...

Thanks theoretical! Great work!

+5% Very useful information.
Title: Re: Test Net for Advanced Users
Post by: cube on September 22, 2015, 09:34:12 am: Quote from: theoretical on September 22, 2015, 05:19:45 am
Quote from: spartako on September 21, 2015, 11:10:52 pm
What is the best practice for not missing any block during an update?

The update_witness command in CLI wallet allows you to change your witness's block signing key. This architecture allows several different downtime-free update procedures according to your specific hosting situation:

(1) Create new witness on new server with new block signing key (you can use suggest_brain_key in CLI wallet, or the get_dev_key binary, to generate a new key). When the new witness is synced, run update_witness to change your key, shutdown old witness and delete old server. Good method if you use a pay-by-the-hour hosting provider that lets you quickly create and destroy servers (e.g. DigitalOcean).

...

I think I'll write this up in a wiki article sometime this week

Thanks for the nice writeup and good planning!

Between the time the new witness just took over signing block and the old witness is still active, is there something to look out for to prevent double signing (ie both old and new witnesses signing block?)
Title: Re: Test Net for Advanced Users
Post by: boombastic on September 22, 2015, 10:17:58 am: After you update new signing key to witness account, the old witness node won't produce blocks 'cause it doesn't have correct key to sign blocks.
Title: Re: Test Net for Advanced Users
Post by: cube on September 22, 2015, 10:22:19 am: Quote from: boombastic on September 22, 2015, 10:17:58 am
After you update new signing key to witness account, the old witness node won't produce blocks 'cause it doesn't have correct key to sign blocks.

This is cool! It makes upgrading witness safer to execute. +5%
Title: Re: Test Net for Advanced Users
Post by: jtme on September 22, 2015, 10:48:50 am: jtm1 updated to the latest master
Title: Re: Test Net for Advanced Users
Post by: abit on September 22, 2015, 11:36:12 am: My witnesses got out of sync 2 hours ago. Restart didn't fix it. Resyncing.
Will check the logs.

//Update:
1. resync worked.
2. issue submitted https://github.com/cryptonomex/graphene/issues/336
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 22, 2015, 12:03:57 pm: Botched an update migrating to a dedicated hosted server. ~~Should be back up in a minute.~~ Producing again.
Title: Re: Test Net for Advanced Users
Post by: betax on September 22, 2015, 12:27:19 pm: Quote from: theoretical on September 22, 2015, 05:19:45 am
Quote from: spartako on September 21, 2015, 11:10:52 pm
What is the best practice for not missing any block during an update?

The update_witness command in CLI wallet allows you to change your witness's block signing key. This architecture allows several different downtime-free update procedures according to your specific hosting situation:

(1) Create new witness on new server with new block signing key (you can use suggest_brain_key in CLI wallet, or the get_dev_key binary, to generate a new key). When the new witness is synced, run update_witness to change your key, shutdown old witness and delete old server. Good method if you use a pay-by-the-hour hosting provider that lets you quickly create and destroy servers (e.g. DigitalOcean).

(2) Create new witness on the same server with new block signing key in different datadir. When new witness is synced, update_witness to change your block signing key and shut down old witness. Good method if you have a large server capable of running two witnesses at once (e.g. dedicated host).

(3) Create temporary witness on your own personal machine. When it is synced, update_witness to change your block signing key and cause the temporary witness to start producing. Then shut down the old witness and spin up the new witness on the same server; it is okay if it takes some time, because your temporary witness is still signing blocks. Then when new witness is ready, run update_witness again to change your block signing key back (or create another new key). Good method if you have a decent personal machine you can occasionally put on witness duty for a few blocks when you're doing an upgrade, and don't want to mess with multiple VPS's as in (1) or pay for a large server as in (2).

Also note that the block signing key can be different from the active and owner keys which control account funds. The only key which needs to live unencrypted on a machine with 24/7 internet connectivity is the block signing key; if an attacker compromises the server, the only thing they can do with the block signing key is sign blocks.

I designed this system, and my goal was to give witnesses better options for dealing with the various IT headaches of signing blocks in DPOS.

I just gave update_witness quite a real-world test on this testnet -- I initially ran all of the init witnesses in a single process on the cloud server that I used to create the testnet, then bytemaster and I migrated a bunch of them to different machines within the first day. In prepping them for the hardfork, I've had to shut down and re-create the witnesses, and also migrated them to better balance them between the multiple machines. I used the update_witness command for all of this and achieved it with minimal downtime. In particular for today's hardfork upgrade, I had no downtime on block signing during the upgrade / migration, even though I had to upgrade 8 witnesses on multiple machines, and I also migrated some of those witnesses to better balance them between machines. The update_witness code and its supporting logic in the block production loop are rock solid!

Some of my init witnesses have been down, but that's mostly due to issues in the p2p layer, the worst of which are resolved in the latest code.

I think I'll write this up in a wiki article sometime this week

Very good procedure, one question how do you get the WIF key for the blockchain signing key?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 22, 2015, 12:30:20 pm: This morning I came in to find all 3 of the nodes I run having issues. I am looking into the cause. After the successful run yesterday I am confident we are very close to eliminating all of the edge cases.

Will update things soon.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 22, 2015, 12:40:43 pm: Quote from: bytemaster on September 22, 2015, 12:30:20 pm
This morning I came in to find all 3 of the nodes I run having issues. I am looking into the cause. After the successful run yesterday I am confident we are very close to eliminating all of the edge cases.

Will update things soon.

It looks like all of my nodes went down because they got into an inconsistent blockchain state regarding a vesting balance object. A replay of the blockchain fixed it.

(Anyone notice how much faster replaying the blockchain is with 1 hour maitenance intervals??!! )
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 22, 2015, 12:44:48 pm: Quote from: betax on September 22, 2015, 12:27:19 pm
Very good procedure, one question how do you get the WIF key for the blockchain signing key?

You can create with a command in the cli_wallet: suggest_brain_key

Import that private key and update your config.ini on the new witness. Fire up the new witness and once sync'd update_witness <name> <public key from above> true

I missed the update to the config.ini which is why I was down for a few minutes.
Title: Re: Test Net for Advanced Users
Post by: abit on September 22, 2015, 01:23:00 pm: Quote from: bytemaster on September 22, 2015, 12:40:43 pm
Quote from: bytemaster on September 22, 2015, 12:30:20 pm
This morning I came in to find all 3 of the nodes I run having issues. I am looking into the cause. After the successful run yesterday I am confident we are very close to eliminating all of the edge cases.

Will update things soon.

It looks like all of my nodes went down because they got into an inconsistent blockchain state regarding a vesting balance object. A replay of the blockchain fixed it.

(Anyone notice how much faster replaying the blockchain is with 1 hour maitenance intervals??!! )
Maybe same issue as my nodes encountered. I did resync. Will try replay next time (if happen again).
Title: Re: Test Net for Advanced Users
Post by: maqifrnswa on September 22, 2015, 02:12:19 pm: If you're looking for more witnesses
maqifrnswa is online
witness id 1.6.3184
Title: Re: Test Net for Advanced Users
Post by: betax on September 22, 2015, 02:34:34 pm: Quote from: Riverhead on September 22, 2015, 12:44:48 pm
Quote from: betax on September 22, 2015, 12:27:19 pm
Very good procedure, one question how do you get the WIF key for the blockchain signing key?

You can create with a command in the cli_wallet: suggest_brain_key

Import that private key and update your config.ini on the new witness. Fire up the new witness and once sync'd update_witness <name> <public key from above> true

I missed the update to the config.ini which is why I was down for a few minutes.

Thanks, @Riverhead all clear now.
Title: Re: Test Net for Advanced Users
Post by: clout on September 22, 2015, 05:26:41 pm: do you have to enable stale block production to produce blocks?
Title: Re: Test Net for Advanced Users
Post by: abit on September 22, 2015, 05:30:27 pm: Quote from: clout on September 22, 2015, 05:26:41 pm
do you have to enable stale block production to produce blocks?
Don't enable that
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 22, 2015, 05:32:40 pm: Quote from: abit on September 22, 2015, 05:30:27 pm
Quote from: clout on September 22, 2015, 05:26:41 pm
do you have to enable stale block production to produce blocks?
Don't enable that

Stale production is only required to bootstrap a dead chain, but should never be used with a live chain.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 22, 2015, 06:16:38 pm: Stupid question: How do I create an account in the GUI? I've tried importing a .json and creating an account with the "Create Account" button. Does it need to be done via the Javascript CLI? I feel like I'm missing something obvious - hopefully not as bad as my IP address typo but....

Update: Seems this is a Firefox issue (at least my copy). Chrome displayed the two password fields as expected but still returns the same error.

(http://i.imgur.com/eLwdqd2.png)
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 22, 2015, 07:15:58 pm: Quote from: Riverhead on September 22, 2015, 06:16:38 pm

Stupid question: How do I create an account in the GUI? I've tried importing a .json and creating an account with the "Create Account" button. Does it need to be done via the Javascript CLI? I feel like I'm missing something obvious - hopefully not as bad as my IP address typo but....

Update: Seems this is a Firefox issue (at least my copy). Chrome displayed the two password fields as expected but still returns the same error.

(http://i.imgur.com/eLwdqd2.png)

Assuming you are on the welcome page, the problem is that it is configured for use with a faucet backend that isn't running on your computer.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 22, 2015, 08:08:22 pm: Quote from: bytemaster on September 22, 2015, 07:15:58 pm
Assuming you are on the welcome page, the problem is that it is configured for use with a faucet backend that isn't running on your computer.

That would be it. Thanks BM.
Title: Re: Test Net for Advanced Users
Post by: cube on September 22, 2015, 10:31:00 pm: Quote from: abit on September 22, 2015, 11:36:12 am
My witnesses got out of sync 2 hours ago. Restart didn't fix it. Resyncing.
Will check the logs.

//Update:
1. resync worked.
2. issue submitted https://github.com/cryptonomex/graphene/issues/336

I had the same issue. My witness was out of sync again and I could not fix it by restarting too. I have to resyn it. It is now resynced.

Please vote for bitcube.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 22, 2015, 10:38:15 pm: Quote from: bytemaster on September 22, 2015, 07:15:58 pm
Quote from: Riverhead on September 22, 2015, 06:16:38 pm

Stupid question: How do I create an account in the GUI? I've tried importing a .json and creating an account with the "Create Account" button. Does it need to be done via the Javascript CLI? I feel like I'm missing something obvious - hopefully not as bad as my IP address typo but....

Update: Seems this is a Firefox issue (at least my copy). Chrome displayed the two password fields as expected but still returns the same error.

(http://i.imgur.com/eLwdqd2.png)

Assuming you are on the welcome page, the problem is that it is configured for use with a faucet backend that isn't running on your computer.

We have just pushed an update that will allow you to register your account this way fixing this issue.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 22, 2015, 10:41:51 pm: I just observed some nice flooding of the network with a single block containing 192 transactions and during the flooding there were no missed blocks.

There are currently 33 active witnesses most of which are on unique nodes with 100% participation.

It looks like things have really stabilized with this test network which is a really good sign that 3 weeks from now the upgrade will go smoothly.

Great work everyone, keep up the testing!
Title: Re: Test Net for Advanced Users
Post by: spartako on September 22, 2015, 11:11:05 pm: Quote from: bytemaster on September 22, 2015, 10:41:51 pm
I just observed some nice flooding of the network with a single block containing 192 transactions and during the flooding there were no missed blocks.

There are currently 33 active witnesses most of which are on unique nodes with 100% participation.

It looks like things have really stabilized with this test network which is a really good sign that 3 weeks from now the upgrade will go smoothly.

Great work everyone, keep up the testing!

I was spamming the network alone with this simple code:

https://github.com/spartako82/node-graphene

Code: [Select]
node bin/flood.js spartako spartako1 ws://127.0.0.1:8099 200
If more people join the spam I think we can reach great results
Title: Re: Test Net for Advanced Users
Post by: clayop on September 23, 2015, 03:34:17 am: Quote from: spartako on September 22, 2015, 11:11:05 pm
I was spamming the network alone with this simple code:

https://github.com/spartako82/node-graphene

Code: [Select]
node bin/flood.js spartako spartako1 ws://127.0.0.1:8099 200
If more people join the spam I think we can reach great results

I got error messages.

Code: [Select]
module.js:340 throw err; ^ Error: Cannot find module 'lib/' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.<anonymous> (/home/clayop/node-graphene/bin/flood.js:4:8) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10)
Title: Re: Test Net for Advanced Users
Post by: spartako on September 23, 2015, 05:09:30 am: Quote from: clayop on September 23, 2015, 03:34:17 am
Quote from: spartako on September 22, 2015, 11:11:05 pm
I was spamming the network alone with this simple code:

https://github.com/spartako82/node-graphene

Code: [Select]
node bin/flood.js spartako spartako1 ws://127.0.0.1:8099 200
If more people join the spam I think we can reach great results

I got error messages.

Code: [Select]
module.js:340 throw err; ^ Error: Cannot find module 'lib/' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.<anonymous> (/home/clayop/node-graphene/bin/flood.js:4:8) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10)

Updated the master, should be fixed now
Title: Re: Test Net for Advanced Users
Post by: boombastic on September 23, 2015, 05:27:34 am: What will happen if two witness node signing using same key due to any reason. I understand that will cause fork, but if the witness is not voted down in a timely manner and keep doing that, what will that cause? Will the network auto "kickoff" this witness?
Title: Re: Test Net for Advanced Users
Post by: cube on September 23, 2015, 06:30:48 am: I think I am producing blocks. I am delighted!

Thank you all for your support!

Code: [Select]
1584002ms th_a witness.cpp:176 block_production_loo ] Generated block #121017 with timestamp 2015-09-23T06:26:24 at time 2015-09-23T06:26:24
Quote from: spartako on September 23, 2015, 05:09:30 am
Updated the master, should be fixed now

Code: [Select]
~/node-graphene# nodejs bin/flood.js bitcube bitcube ws://127.0.0.1:8090 200 ******* 0******* ERROR 10 assert_exception: Assert Exception itr != _by_name.end(): no method with name 'transfer' {"name":"transfer","api":[["cancel_all_subscriptions",4],["get_account_balances",21],["get_account_by_name",16],["get_account_count",20],["get_account_references",17],["get_accounts",14],["get_assets",26],["get_balance_objects",23],["get_blinded_balances",52],["get_block",6],["get_block_header",5],["get_call_orders",30],["get_chain_id",11],["get_chain_properties",8],["get_committee_member_by_account",40],["get_committee_members",39],["get_config",10],["get_dynamic_global_properties",12],["get_full_accounts",15],["get_global_properties",9],["get_key_references",13],["get_limit_orders",29],["get_margin_positions",32],["get_named_account_balances",22],["get_objects",0],["get_potential_signatures",46],["get_proposed_transactions",51],["get_required_fees",50],["get_required_signatures",45],["get_settle_orders",31],["get_transaction",7],["get_transaction_hex",44],["get_vested_balances",24],["get_vesting_balances",25],["get_witness_by_account",36],["get_witness_count",38],["get_witnesses",35],["get_workers_by_account",42],["list_assets",27],["lookup_account_names",18],["lookup_accounts",19],["lookup_asset_symbols",28],["lookup_committee_member_accounts",41],["lookup_vote_ids",43],["lookup_witness_accounts",37],["set_block_applied_callback",3],["set_pending_transaction_callback",2],["set_subscribe_callback",1],["subscribe_to_market",33],["unsubscribe_from_market",34],["validate_transaction",49],["verify_account_authority",48],["verify_authority",47]]} th_a api_connection.hpp:84 call
Any idea?
Title: Re: Test Net for Advanced Users
Post by: spartako on September 23, 2015, 07:15:47 am: Quote from: cube on September 23, 2015, 06:30:48 am

Quote from: spartako on September 23, 2015, 05:09:30 am
Updated the master, should be fixed now

Code: [Select]
~/node-graphene# nodejs bin/flood.js bitcube bitcube ws://127.0.0.1:8090 200 ******* 0******* ERROR 10 assert_exception: Assert Exception itr != _by_name.end(): no method with name 'transfer' {"name":"transfer","api":[["cancel_all_subscriptions",4],["get_account_balances",21],["get_account_by_name",16],["get_account_count",20],["get_account_references",17],["get_accounts",14],["get_assets",26],["get_balance_objects",23],["get_blinded_balances",52],["get_block",6],["get_block_header",5],["get_call_orders",30],["get_chain_id",11],["get_chain_properties",8],["get_committee_member_by_account",40],["get_committee_members",39],["get_config",10],["get_dynamic_global_properties",12],["get_full_accounts",15],["get_global_properties",9],["get_key_references",13],["get_limit_orders",29],["get_margin_positions",32],["get_named_account_balances",22],["get_objects",0],["get_potential_signatures",46],["get_proposed_transactions",51],["get_required_fees",50],["get_required_signatures",45],["get_settle_orders",31],["get_transaction",7],["get_transaction_hex",44],["get_vested_balances",24],["get_vesting_balances",25],["get_witness_by_account",36],["get_witness_count",38],["get_witnesses",35],["get_workers_by_account",42],["list_assets",27],["lookup_account_names",18],["lookup_accounts",19],["lookup_asset_symbols",28],["lookup_committee_member_accounts",41],["lookup_vote_ids",43],["lookup_witness_accounts",37],["set_block_applied_callback",3],["set_pending_transaction_callback",2],["set_subscribe_callback",1],["subscribe_to_market",33],["unsubscribe_from_market",34],["validate_transaction",49],["verify_account_authority",48],["verify_authority",47]]} th_a api_connection.hpp:84 call
Any idea?

You have to point to the wallet-url and not the witness url.
You can do that in this way for example:
Code: [Select]
./cli_wallet -w wallet.json --chain-id 0f8b631d7a9dfebf16d6776fab96b629a14429762bf9c3eb95db1e4e4af637a4 -s ws://127.0.0.1:8090 -r 127.0.0.1:8099
Moreover the accounts must be different because transfer doesn't work if you transfer to yourself. So create an other account (like bitcube1)
Unlock your wallet and use this command:
Code: [Select]
~/node-graphene# nodejs bin/flood.js bitcube bitcube1 ws://127.0.0.1:8099 200
Edit: at the beginning test with only 10 tx X block so you don't spend too much:

Code: [Select]
~/node-graphene# nodejs bin/flood.js bitcube bitcube1 ws://127.0.0.1:8099 10
You can see your results with:
Code: [Select]
~/node-graphene# nodejs bin/lastBlocks.js ws://127.0.0.1:8090 30
Title: Re: Test Net for Advanced Users
Post by: mindphlux on September 23, 2015, 07:23:05 am: Quote from: spartako on September 23, 2015, 07:15:47 am
Quote from: cube on September 23, 2015, 06:30:48 am

Quote from: spartako on September 23, 2015, 05:09:30 am
Updated the master, should be fixed now

Code: [Select]
~/node-graphene# nodejs bin/flood.js bitcube bitcube ws://127.0.0.1:8090 200 ******* 0******* ERROR 10 assert_exception: Assert Exception itr != _by_name.end(): no method with name 'transfer' {"name":"transfer","api":[["cancel_all_subscriptions",4],["get_account_balances",21],["get_account_by_name",16],["get_account_count",20],["get_account_references",17],["get_accounts",14],["get_assets",26],["get_balance_objects",23],["get_blinded_balances",52],["get_block",6],["get_block_header",5],["get_call_orders",30],["get_chain_id",11],["get_chain_properties",8],["get_committee_member_by_account",40],["get_committee_members",39],["get_config",10],["get_dynamic_global_properties",12],["get_full_accounts",15],["get_global_properties",9],["get_key_references",13],["get_limit_orders",29],["get_margin_positions",32],["get_named_account_balances",22],["get_objects",0],["get_potential_signatures",46],["get_proposed_transactions",51],["get_required_fees",50],["get_required_signatures",45],["get_settle_orders",31],["get_transaction",7],["get_transaction_hex",44],["get_vested_balances",24],["get_vesting_balances",25],["get_witness_by_account",36],["get_witness_count",38],["get_witnesses",35],["get_workers_by_account",42],["list_assets",27],["lookup_account_names",18],["lookup_accounts",19],["lookup_asset_symbols",28],["lookup_committee_member_accounts",41],["lookup_vote_ids",43],["lookup_witness_accounts",37],["set_block_applied_callback",3],["set_pending_transaction_callback",2],["set_subscribe_callback",1],["subscribe_to_market",33],["unsubscribe_from_market",34],["validate_transaction",49],["verify_account_authority",48],["verify_authority",47]]} th_a api_connection.hpp:84 call
Any idea?

You have to point to the wallet-url and not the witness url.
You can do that in this way for example:
Code: [Select]
./cli_wallet -w wallet.json --chain-id 0f8b631d7a9dfebf16d6776fab96b629a14429762bf9c3eb95db1e4e4af637a4 -s ws://127.0.0.1:8090 -r 127.0.0.1:8099
Moreover the accounts must be different because transfer doesn't work if you transfer to yourself. So create an other account (like bitcube1)
Unlock your wallet and use this command:
Code: [Select]
~/node-graphene# nodejs bin/flood.js bitcube bitcube1 ws://127.0.0.1:8099 200

Can you please post a link to node-graphene.. can't find it on github.

Thanks.

Newbie question - do I need to run a witness in order to run the flood script?
Title: Re: Test Net for Advanced Users
Post by: spartako on September 23, 2015, 07:28:10 am: Quote from: mindphlux on September 23, 2015, 07:23:05 am

Can you please post a link to node-graphene.. can't find it on github.

Thanks.

Newbie question - do I need to run a witness in order to run the flood script?

This is the github link:
https://github.com/spartako82/node-graphene (https://github.com/spartako82/node-graphene)

Yes, you need to run a standard witness (without producing blocks) and also run the cli_wallet command
Here you can see how to run a witness:
https://github.com/cryptonomex/graphene/wiki/CLI-Wallet-Cookbook
Title: Re: Test Net for Advanced Users
Post by: mindphlux on September 23, 2015, 07:39:06 am: Thank you, I understand this.

The documentation talks about a local testnet. How do I connect my newly default witness node to the real testnet, are there seed node ips I need to specifically connect to?

EDIT: Do I need to connect the CLI wallet to the real testnet too, including to the setup faucet server, so I can create accounts? How do I do that?
Title: Re: Test Net for Advanced Users
Post by: spartako on September 23, 2015, 07:46:03 am: Quote from: mindphlux on September 23, 2015, 07:39:06 am
Thank you, I understand this.

The documentation talks about a local testnet. How do I connect my newly default witness node to the real testnet, are there seed node ips I need to specifically connect to?

The current testnet is this one:

https://github.com/cryptonomex/graphene/releases/tag/test3
(https://github.com/cryptonomex/graphene/releases/tag/test3)

You need to download the genesis file: sep-18-testnet-genesis.json
and launch your witness in this way:

Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090" --genesis-json sep-18-testnet-genesis.json -d witness_dir/ -s 104.236.118.105:1776
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 23, 2015, 10:33:17 am: Nice to see these scripts surfacing :).

I'm getting the following error. I can correct on my side but was wondering if perhaps a commit is missing?

Code: [Select]
node bin/flood.js riverhead james ws://192.168.1.11:8090 10 ERROR 10 assert_exception: Assert Exception itr != _by_name.end(): no method with name 'transfer'
Title: Re: Test Net for Advanced Users
Post by: spartako on September 23, 2015, 10:40:51 am: Quote from: Riverhead on September 23, 2015, 10:33:17 am

Nice to see these scripts surfacing :).

I'm getting the following error. I can correct on my side but was wondering if perhaps a commit is missing?

Code: [Select]
node bin/flood.js riverhead james ws://192.168.1.11:8090 10 ERROR 10 assert_exception: Assert Exception itr != _by_name.end(): no method with name 'transfer'

You have to point to the wallet-url and not the witness url.
You can do that in this way for example:
Code: [Select]
./cli_wallet -w wallet.json --chain-id 0f8b631d7a9dfebf16d6776fab96b629a14429762bf9c3eb95db1e4e4af637a4 -s ws://192.168.1.11:8090 -r 192.168.1.11:8099
Then unlock the wallet and use in this way

Code: [Select]
node bin/flood.js riverhead james ws://192.168.1.11:8099 10
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 23, 2015, 10:43:56 am: Quote from: spartako on September 23, 2015, 10:40:51 am
You have to point to the wallet-url and not the witness url.

/facepalm of course. Still on my first cup of coffee :P.
Title: Re: Test Net for Advanced Users
Post by: spartako on September 23, 2015, 10:47:20 am: Quote from: Riverhead on September 23, 2015, 10:43:56 am
Quote from: spartako on September 23, 2015, 10:40:51 am
You have to point to the wallet-url and not the witness url.

/facepalm of course. Still on my first cup of coffee :P.

I am already at the second one :P
Tell me if you are able to spam
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 23, 2015, 10:49:02 am: Quote from: spartako on September 23, 2015, 10:47:20 am

I am already at the second one :P
Tell me if you are able to spam

Works great!!

(http://i.imgur.com/b3Rilrc.png)
Title: Re: Test Net for Advanced Users
Post by: spartako on September 23, 2015, 10:50:34 am: Quote from: Riverhead on September 23, 2015, 10:49:02 am
Quote from: spartako on September 23, 2015, 10:47:20 am

I am already at the second one :P
Tell me if you are able to spam

Works great!!
+5%
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 23, 2015, 10:53:01 am: Quote from: spartako on September 23, 2015, 10:50:34 am
Quote from: Riverhead on September 23, 2015, 10:49:02 am
Quote from: spartako on September 23, 2015, 10:47:20 am

I am already at the second one :P
Tell me if you are able to spam

Works great!!
+5%

Can it be expanded to do a transaction mix? Maybe transfer, market order, order cancel, etc?
Title: Re: Test Net for Advanced Users
Post by: spartako on September 23, 2015, 11:04:55 am: Quote from: Riverhead on September 23, 2015, 10:53:01 am

Can it be expanded to do a transaction mix? Maybe transfer, market order, order cancel, etc?

Sure, I finish the api binding and I will be able to do that.
You can see in the code I started spamming using create account because cost less but it is slower.
Title: Re: Test Net for Advanced Users
Post by: mindphlux on September 23, 2015, 11:05:59 am: I got the default witness to run and the cli wallet runs too, and I created a password.. however, I'm not able to create/register an account.

Can you please give instructions how to register an account on the blockchain to get the 1000 CORE in the cli wallet?
Title: Re: Test Net for Advanced Users
Post by: spartako on September 23, 2015, 11:22:15 am: Quote from: mindphlux on September 23, 2015, 11:05:59 am
I got the default witness to run and the cli wallet runs too, and I created a password.. however, I'm not able to create/register an account.

Can you please give instructions how to register an account on the blockchain to get the 1000 CORE in the cli wallet?

Type suggest_brain_key in the wallet, give me your public key: GPH...
I will try to register for you and I will send you 1000 CORE

Edit: also the account name
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 23, 2015, 11:28:51 am: Changes to graphene-ui work great :)

(http://i.imgur.com/xJmOHlE.png)
Title: Re: Test Net for Advanced Users
Post by: clayop on September 23, 2015, 11:31:17 am: Spamming now.... but curious why only part of transactions are accepted.
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 23, 2015, 11:32:57 am: (http://i.imgur.com/b5YwYQ0.png)
missed the top with my screenshot .. was > 12 :)
Title: Re: Test Net for Advanced Users
Post by: jakub on September 23, 2015, 11:36:37 am: What I've noticed is that the GUI becomes totally unresponsive when these transaction spamming events happen.
Especially this page:
https://graphene.bitshares.org/#/explorer/blocks

It referrers to both Firefox and Chrome (on Windows 7).
Has anyone noticed similar effect?
Title: Re: Test Net for Advanced Users
Post by: spartako on September 23, 2015, 11:39:32 am: Quote from: jakub on September 23, 2015, 11:36:37 am
What I've noticed is that the GUI becomes totally unresponsive when these transaction spamming events happen.
Especially this page:
https://graphene.bitshares.org/#/explorer/blocks

It referrers to both Firefox and Chrome (on Windows 7).
Has anyone noticed similar effect?

Yes me too (chrome on mac)
Title: Re: Test Net for Advanced Users
Post by: clayop on September 23, 2015, 11:40:00 am: (http://i.imgur.com/ogyEzvK.png)

Edited ;)
Title: Re: Test Net for Advanced Users
Post by: clayop on September 23, 2015, 11:40:26 am: Quote from: jakub on September 23, 2015, 11:36:37 am
What I've noticed is that the GUI becomes totally unresponsive when these transaction spamming events happen.
Especially this page:
https://graphene.bitshares.org/#/explorer/blocks

It referrers to both Firefox and Chrome (on Windows 7).
Has anyone noticed similar effect?

Me too
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 23, 2015, 11:41:44 am: (http://i.imgur.com/pvZ2Wjz.png)
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 23, 2015, 11:55:33 am: Quote from: clayop on September 23, 2015, 11:40:26 am
Quote from: jakub on September 23, 2015, 11:36:37 am
What I've noticed is that the GUI becomes totally unresponsive when these transaction spamming events happen.
Especially this page:
https://graphene.bitshares.org/#/explorer/blocks

It referrers to both Firefox and Chrome (on Windows 7).
Has anyone noticed similar effect?

Me too

I have noticed that it drags a bit. I have some ideas on improving performance.
Title: Re: Test Net for Advanced Users
Post by: betax on September 23, 2015, 12:05:06 pm: Yes, my UI is frozen on explorer blocks (Chrome), I'm currently sending 20 at a time.
Title: Re: Test Net for Advanced Users
Post by: wackou on September 23, 2015, 12:05:44 pm: Quote from: spartako on September 22, 2015, 09:14:11 am
Quote from: theoretical on September 22, 2015, 05:19:45 am
Quote from: spartako on September 21, 2015, 11:10:52 pm
What is the best practice for not missing any block during an update?

The update_witness command in CLI wallet allows you to change your witness's block signing key. This architecture allows several different downtime-free update procedures according to your specific hosting situation:
...

Thanks theoretical! Great work!

+5% indeed, very useful and sounds like a fool-proof way to do it with no risk of signing double blocks.

One question: how long does it take for the signing key to be updated after you call the update_witness command? As soon as the transaction is processed by the network? After the next maintenance interval? Sth else?

I seem to recall that in BitShares 0.9.x changing the signing key did take a bit of time to go into effect, so that set_block_production true/false was the preferred way. If in graphene the call to changing the signing key takes effect immediately, then that's really nice as it's a much better way of doing it.
Title: Re: Test Net for Advanced Users
Post by: betax on September 23, 2015, 12:09:31 pm: Before I raise an issue, on the UI spamming to myself supertest1 the transactions appear as 1 hour ago. Is this a known feature?
It also appears the last block was produced 1 hour ago.

Note: I have move from hotel network this morning, to using a mobile hot spot to check graphene. Will this in anyway affect the datetime ?
Title: Re: Test Net for Advanced Users
Post by: jakub on September 23, 2015, 12:22:29 pm: Quote from: bytemaster on September 23, 2015, 11:55:33 am
Quote from: clayop on September 23, 2015, 11:40:26 am
Quote from: jakub on September 23, 2015, 11:36:37 am
What I've noticed is that the GUI becomes totally unresponsive when these transaction spamming events happen.
Especially this page:
https://graphene.bitshares.org/#/explorer/blocks

It referrers to both Firefox and Chrome (on Windows 7).
Has anyone noticed similar effect?

Me too

I have noticed that it drags a bit. I have some ideas on improving performance.

I think it's more serious than that - the whole thing becomes totally unresponsive. In case of Firefox it slows down the entire browser.
I'd guess it's an issue with the "Recent Activity" list.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 23, 2015, 12:38:17 pm: Quote from: betax on September 23, 2015, 12:09:31 pm
Before I raise an issue, on the UI spamming to myself supertest1 the transactions appear as 1 hour ago. Is this a known feature?
It also appears the last block was produced 1 hour ago.

Note: I have move from hotel network this morning, to using a mobile hot spot to check graphene. Will this in anyway affect the datetime ?

Depending upon which version of the code you had it may or may not be factoring in timezone.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 23, 2015, 12:41:02 pm: jtml - what kind of difficulties are you having at the moment, you have missed quite a few blocks recently.
Title: Re: Test Net for Advanced Users
Post by: svk on September 23, 2015, 12:44:41 pm: Quote from: betax on September 23, 2015, 12:05:06 pm
Yes, my UI is frozen on explorer blocks (Chrome), I'm currently sending 20 at a time.

Yea I've noticed this too today while you guys were spamming :) I managed to get it a little better but haven't pushed those changes yet, I'll have to look into it in more detail once I get the time, maybe later today or if not tomorrow.
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 23, 2015, 01:09:47 pm: I will be 'off-grid' for the next day or two.

If my witness runs off and misbehaves, or needs updates, I will likely not be available to fix it until I return.

Happy testing! : )
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 23, 2015, 01:57:18 pm: Quote from: svk on September 23, 2015, 12:44:41 pm
Quote from: betax on September 23, 2015, 12:05:06 pm
Yes, my UI is frozen on explorer blocks (Chrome), I'm currently sending 20 at a time.

Yea I've noticed this too today while you guys were spamming :) I managed to get it a little better but haven't pushed those changes yet, I'll have to look into it in more detail once I get the time, maybe later today or if not tomorrow.

I was able to significantly improve the performance by only showing the most recent 15 operations in Recent Activity and have committed my changes.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 23, 2015, 02:12:24 pm: I used the command save_wallet_file test3.json in the cli_wallet and tried to restore it in the UI but it says invalid format. Is there a different command I should be using in the CLI or is restore not implemented yet?

Just want to make sure it's not PEBKAC before I log an issue.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 23, 2015, 02:37:45 pm: Quote from: Riverhead on September 23, 2015, 02:12:24 pm
I used the command save_wallet_file test3.json in the cli_wallet and tried to restore it in the UI but it says invalid format. Is there a different command I should be using in the CLI or is restore not implemented yet?

Just want to make sure it's not PEBKAC before I log an issue.

PEBKAC?

The CLI wallet format is not compatible with the GUI import format. There is not currently an easy way to migrate from one wallet to the other.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 23, 2015, 02:52:16 pm: Quote from: bytemaster on September 23, 2015, 02:37:45 pm
PEBKAC?

Problem Exists Between Keyboard and Chair - the usual source of my bugs.

Quote from: bytemaster on September 23, 2015, 02:37:45 pm
The CLI wallet format is not compatible with the GUI import format. There is not currently an easy way to migrate from one wallet to the other.

Understood, thank you.
Title: Re: Test Net for Advanced Users
Post by: ElMato on September 23, 2015, 03:25:30 pm: I have my witness node running.
Need some votes.

elmato
Title: Re: Test Net for Advanced Users
Post by: abit on September 23, 2015, 04:03:58 pm: USD/CORE market is active now. https://graphene.bitshares.org/#/exchange/trade/USD_CORE

It's strange that lowest price is on the top but highest price at bottom.
Title: Re: Test Net for Advanced Users
Post by: mindphlux on September 23, 2015, 05:09:48 pm: I cannot register a new account in the GUI, it's always hanging at this screen after entering username+password:

I deleted all cookie and local storage before..

What to do? Is something crashed?

http://imgur.com/HtDO4bA

Also the webserver seems kind of slow, looks overloaded to me..
Title: Re: Test Net for Advanced Users
Post by: fav on September 23, 2015, 05:16:21 pm: Quote from: mindphlux on September 23, 2015, 05:09:48 pm
I cannot register a new account in the GUI, it's always hanging at this screen after entering username+password:

I deleted all cookie and local storage before..

What to do? Is something crashed?

http://imgur.com/HtDO4bA

Also the webserver seems kind of slow, looks overloaded to me..

lagging for me too at the moment
Title: Re: Test Net for Advanced Users
Post by: boombastic on September 23, 2015, 05:40:16 pm: Double Signing attack test

Since I can't find more information about how double signing will harm the network and what defensive mechanism network will have against double signing, I am going to perform a 30 minutes double signing attack on test net. Double signing could happen due to honest witness mis-configuring node, witness server compromised by evil third party or corrupted witness.

I have 3 witness accounts voted in that I can coordinate, I am going to try double signing from 1, 2, 3 witnesses using 2 separate servers (US, Asia).

Here is the plan:

The attack will last for 30 minutes, 3 phases, each will last for 10 minutes.

phase I (0-10min): 1 double signing witness (boombastic)
phase II (10-20min): 2 double signing witness (boombastic and mr.agsexplorer)
phase III (20-30min): 3 double signing witness (boombastic and mr.agsexplorer and mrs.agsexplorer)
end (30min): stop double signing

Double signing will cause fork, I want to see after all this mess, if network can recover, and I will do some transactions during the attack and see how it's gonna affect normal user operations. If you are here, you can perform normal operation and report back after the attack is finished.

bytemaster, if you see this, please do not vote out these double signing witness just yet. In real world, if some witness starts double signing, voters might not react that quickly, network should survive on its own for at least 30 minutes.

The attack will start at today 2015-09-23 18:00 (UTC), which is 20 mintues from now
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 23, 2015, 05:48:12 pm: delegate-1.lafona what happened to your node?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 23, 2015, 05:59:30 pm: Quote from: boombastic on September 23, 2015, 05:40:16 pm
Double Signing attack test

Since I can't find more information about how double signing will harm the network and what defensive mechanism network will have against double signing, I am going to perform a 30 minutes double signing attack on test net. Double signing could happen due to honest witness mis-configuring node, witness server compromised by evil third party or corrupted witness.

I have 3 witness accounts voted in that I can coordinate, I am going to try double signing from 1, 2, 3 witnesses using 2 separate servers (US, Asia).

Here is the plan:

The attack will last for 30 minutes, 3 phases, each will last for 10 minutes.

phase I (0-10min): 1 double signing witness (boombastic)
phase II (10-20min): 2 double signing witness (boombastic and mr.agsexplorer)
phase III (20-30min): 3 double signing witness (boombastic and mr.agsexplorer and mrs.agsexplorer)
end (30min): stop double signing

Double signing will cause fork, I want to see after all this mess, if network can recover, and I will do some transactions during the attack and see how it's gonna affect normal user operations. If you are here, you can perform normal operation and report back after the attack is finished.

bytemaster, if you see this, please do not vote out these double signing witness just yet. In real world, if some witness starts double signing, voters might not react that quickly, network should survive on its own for at least 30 minutes.

The attack will start at today 2015-09-23 18:00 (UTC), which is 20 mintues from now

In the spirt of the scientific method I will submit the hypothesis on what should happen:

Phase 1:
The next witness will receive one of your blocks first and then save (but not switch to the other block)
The next witness will pick one of the blocks to build off of
All of the other nodes will switch as soon as the next witness produces a block and everything will be in sync.

Phase 2:
WIll be identical to Phase 1 except in the case that both witnesses are scheduled back to back. If they are scheduled back to back then it may take two blocks to resolve any forks.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 23, 2015, 06:18:16 pm: I found no difference with my node during the double signing attack :)
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 23, 2015, 06:20:22 pm: Quote from: clayop on September 23, 2015, 06:18:16 pm
I found no difference with my node during the double signing attack :)
100% participation during the attack :)
Title: Re: Test Net for Advanced Users
Post by: boombastic on September 23, 2015, 06:34:03 pm: All right, I stopped the double signing attack just now. First of all, I did do that. :) But it feels that didn't happen. I sent various transactions to account hoping to see some balance missing, etc, but in vain. The network seems totally immune to double signing.

Is that safe to say that 'evil' double signing in BTS1 era now goes into witness's toolbox. We can use two machines as redundancy to prevent accident server shutdown?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 23, 2015, 06:50:39 pm: Quote from: boombastic on September 23, 2015, 06:34:03 pm
All right, I stopped the double signing attack just now. First of all, I did do that. :) But it feels that didn't happen. I sent various transactions to account hoping to see some balance missing, etc, but in vain. The network seems totally immune to double signing.

Is that safe to say that 'evil' double signing in BTS1 era now goes into witness's toolbox. We can use two machines as redundancy to prevent accident server shutdown?

Please don't do that.
Title: Re: Test Net for Advanced Users
Post by: lakerta06 on September 23, 2015, 06:54:51 pm: Quote from: boombastic on September 23, 2015, 06:34:03 pm
All right, I stopped the double signing attack just now. First of all, I did do that. :) But it feels that didn't happen. I sent various transactions to account hoping to see some balance missing, etc, but in vain. The network seems totally immune to double signing.

Is that safe to say that 'evil' double signing in BTS1 era now goes into witness's toolbox. We can use two machines as redundancy to prevent accident server shutdown?
If each witness double signs, fork never gets resolved i guess?
Title: Re: Test Net for Advanced Users
Post by: puppies on September 23, 2015, 07:02:28 pm: For redundancy I think I will run multiple nodes with different signing keys. I will then set up a single node to switch signing keys when my witness misses a block.
Title: Re: Test Net for Advanced Users
Post by: lafona on September 23, 2015, 07:03:01 pm: Quote from: bytemaster on September 23, 2015, 05:48:12 pm
delegate-1.lafona what happened to your node?

It looks like I am on a fork.
Code: [Select]
2813283ms th_a fork_database.cpp:57 push_block ] Pushing block to fork database that failed to link: 00020081f8a1dd2c575919181724f39ca247d8a1, 131201 2813283ms th_a fork_database.cpp:58 push_block ] Head: 131108, 00020024713817f57183d045cdecaf3303acbf0d 2813283ms th_a application.cpp:415 handle_block ] Error when pushing block: 3080000 unlinkable_block_exception: unlinkable block block does not link to known chain {} th_a fork_database.cpp:79 _push_block {"new_block":{"previous":"00020080759ee5c5fc93983b99af426e9d3fcf36","timestamp":"2015-09-23T15:02:12","witness":"1.6.7","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f65d50fe53a1c376657599d29910bf650086d48a4642b43f5b654d083ef6052a30997ecdac3dab252a2e0e83f9294363a9faacccec6f2852e94643ce22143a689","transactions":[]}} th_a db_block.cpp:195 _push_block
I won't have much time to go through the logs until tonight, but if it helps I will send you a link to the log files.
Title: Re: Test Net for Advanced Users
Post by: abit on September 23, 2015, 07:08:59 pm: For those brave witnesses, I made a patch based on xeroc's price feed script. Enjoy it!

https://github.com/abitmore/python-graphenelib
https://github.com/abitmore/python-graphenelib/blob/master/scripts/pricefeeds.py
Title: Re: Test Net for Advanced Users
Post by: jtme on September 23, 2015, 07:16:14 pm: Quote from: bytemaster on September 23, 2015, 12:41:02 pm
jtml - what kind of difficulties are you having at the moment, you have missed quite a few blocks recently.

witness crashed

Code: [Select]
witness_node: /mon/g/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed.
auto start did not work , there was an error when replaying blockchain

Code: [Select]
Unable to create directories object_database/0 {"path":"object_database/0","inner":"Dynamic exception type: boost::filesystem::filesystem_error\nstd::exception::what: boost::filesystem::create_directories: Permission denied: \"object_database\"\n"}
After some investigation, I've realized that the problem was in using an absolute path
for --data-dir. All is written under the given absolute path except object_database, which
is written relative to the current dir (and the proccess did not have write access to that dir)
And it seems that the object_database is not needed and writen during the initial sync,
so the witness was running fine without the need to write to object_database for a while.

Not sure if this could cause the initial crash

The witness is now up and running again.
Title: Re: Test Net for Advanced Users
Post by: wackou on September 23, 2015, 08:02:44 pm: Quote from: puppies on September 23, 2015, 07:02:28 pm
For redundancy I think I will run multiple nodes with different signing keys. I will then set up a single node to switch signing keys when my witness misses a block.

I feel like that's the way to go in order to have a backup node ready to pop up in case the main witness goes down for some reason. I will do the same, and encourage other witnesses to get familiarized with this way of doing it.
Title: Re: Test Net for Advanced Users
Post by: wackou on September 23, 2015, 08:04:09 pm: Quote from: wackou on September 23, 2015, 12:05:44 pm
Quote from: spartako on September 22, 2015, 09:14:11 am
Quote from: theoretical on September 22, 2015, 05:19:45 am
Quote from: spartako on September 21, 2015, 11:10:52 pm
What is the best practice for not missing any block during an update?

The update_witness command in CLI wallet allows you to change your witness's block signing key. This architecture allows several different downtime-free update procedures according to your specific hosting situation:
...

Thanks theoretical! Great work!

+5% indeed, very useful and sounds like a fool-proof way to do it with no risk of signing double blocks.

One question: how long does it take for the signing key to be updated after you call the update_witness command? As soon as the transaction is processed by the network? After the next maintenance interval? Sth else?

I seem to recall that in BitShares 0.9.x changing the signing key did take a bit of time to go into effect, so that set_block_production true/false was the preferred way. If in graphene the call to changing the signing key takes effect immediately, then that's really nice as it's a much better way of doing it.

bump question @theoretical @bytemaster
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 23, 2015, 08:20:21 pm: Quote from: wackou on September 23, 2015, 08:04:09 pm
Quote from: wackou on September 23, 2015, 12:05:44 pm
Quote from: spartako on September 22, 2015, 09:14:11 am
Quote from: theoretical on September 22, 2015, 05:19:45 am
Quote from: spartako on September 21, 2015, 11:10:52 pm
What is the best practice for not missing any block during an update?

The update_witness command in CLI wallet allows you to change your witness's block signing key. This architecture allows several different downtime-free update procedures according to your specific hosting situation:
...

Thanks theoretical! Great work!

+5% indeed, very useful and sounds like a fool-proof way to do it with no risk of signing double blocks.

One question: how long does it take for the signing key to be updated after you call the update_witness command? As soon as the transaction is processed by the network? After the next maintenance interval? Sth else?

I seem to recall that in BitShares 0.9.x changing the signing key did take a bit of time to go into effect, so that set_block_production true/false was the preferred way. If in graphene the call to changing the signing key takes effect immediately, then that's really nice as it's a much better way of doing it.

bump question @theoretical @bytemaster

Instantly
Title: Re: Test Net for Advanced Users
Post by: jakub on September 23, 2015, 08:20:34 pm: Where is the best place to report bugs in the GUI?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 23, 2015, 08:53:37 pm: Quote from: jakub on September 23, 2015, 08:20:34 pm
Where is the best place to report bugs in the GUI?

https://github.com/cryptonomex/graphene-ui/issues

Create "New Issue"
Title: Re: Test Net for Advanced Users
Post by: abit on September 23, 2015, 10:20:11 pm: Quote from: abit on September 23, 2015, 07:08:59 pm
For those brave witnesses, I made a patch based on xeroc's price feed script. Enjoy it!

https://github.com/abitmore/python-graphenelib
https://github.com/abitmore/python-graphenelib/blob/master/scripts/pricefeeds.py
Script updated. Fixed BTC precision issue.
Title: Re: Test Net for Advanced Users
Post by: jakub on September 24, 2015, 11:12:13 am: For the last 12 hours I've been unable to access the GUI on https://graphene.bitshares.org (https://graphene.bitshares.org)
The browser constantly shows the message "waiting for graphene.bitshares.org".
Title: Re: Test Net for Advanced Users
Post by: wuyanren on September 24, 2015, 12:27:39 pm: Quote from: jakub on September 24, 2015, 11:12:13 am
For the last 12 hours I've been unable to access the GUI on https://graphene.bitshares.org (https://graphene.bitshares.org)
The browser constantly shows the message "waiting for graphene.bitshares.org".
mee too
Title: Re: Test Net for Advanced Users
Post by: svk on September 24, 2015, 01:35:12 pm: Quote from: wuyanren on September 24, 2015, 12:27:39 pm
Quote from: jakub on September 24, 2015, 11:12:13 am
For the last 12 hours I've been unable to access the GUI on https://graphene.bitshares.org (https://graphene.bitshares.org)
The browser constantly shows the message "waiting for graphene.bitshares.org".
mee too

I just told Valentine, he'll look into it.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 24, 2015, 02:18:52 pm: I was just testing claiming of genesis collateral positions (those who were short at the time of the snapshot) and discovered a bug that prevented the authority checks from passing.

I have fixed the bug, but it will require all testing witnesses to upgrade or the test network will fork as soon as someone does something with a usd-collateral-holder-# account.

Please upgrade your test node as soon possible so I can continue testing this feature without disruption.
Title: Re: Test Net for Advanced Users
Post by: lafona on September 24, 2015, 02:45:07 pm: delegate-1.lafona updated.

On a side note, the delegate seems to be out of the list of active witnesses, but has enough votes to be middle of the pack. Any thoughts?

Code: [Select]
{ "id": "1.6.1531", "witness_account": "1.2.22396", "last_aslot": 138787, "signing_key": "GPH5DCL5nbhL13sXBh1mwQp5pUBSw7rmwjWeiiy5b2Z2UxuYf8spU", "pay_vb": "1.13.57", "vote_id": "1:1530", "total_votes": "9524676529409", "url": "" }
Title: Re: Test Net for Advanced Users
Post by: abit on September 24, 2015, 03:01:51 pm: Quote from: lafona on September 24, 2015, 02:45:07 pm

On a side note, the delegate seems to be out of the list of active witnesses, but has enough votes to be middle of the pack. Any thoughts?

Code: [Select]
{ "id": "1.6.1531", "witness_account": "1.2.22396", "last_aslot": 138787, "signing_key": "GPH5DCL5nbhL13sXBh1mwQp5pUBSw7rmwjWeiiy5b2Z2UxuYf8spU", "pay_vb": "1.13.57", "vote_id": "1:1530", "total_votes": "9524676529409", "url": "" }
Every hour, only votes of (new) active witnesses will be updated.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 24, 2015, 03:17:26 pm: delegate-clayop is updated.
Title: Re: Test Net for Advanced Users
Post by: jakub on September 24, 2015, 03:19:57 pm: Quote from: svk on September 24, 2015, 01:35:12 pm
Quote from: wuyanren on September 24, 2015, 12:27:39 pm
Quote from: jakub on September 24, 2015, 11:12:13 am
For the last 12 hours I've been unable to access the GUI on https://graphene.bitshares.org (https://graphene.bitshares.org)
The browser constantly shows the message "waiting for graphene.bitshares.org".
mee too

I just told Valentine, he'll look into it.

Could we have a separate thread similar to this one but dedicated to the GUI available on https://graphene.bitshares.org (https://graphene.bitshares.org) ?
I guess there will be more and more strictly GUI-related issues.
Title: Re: Test Net for Advanced Users
Post by: alt on September 24, 2015, 03:29:30 pm: delegate.baozi is updated
Title: Re: Test Net for Advanced Users
Post by: svk on September 24, 2015, 03:37:12 pm: Quote from: jakub on September 24, 2015, 03:19:57 pm
Quote from: svk on September 24, 2015, 01:35:12 pm
Quote from: wuyanren on September 24, 2015, 12:27:39 pm
Quote from: jakub on September 24, 2015, 11:12:13 am
For the last 12 hours I've been unable to access the GUI on https://graphene.bitshares.org (https://graphene.bitshares.org)
The browser constantly shows the message "waiting for graphene.bitshares.org".
mee too

I just told Valentine, he'll look into it.

Could we have a separate thread similar to this one but dedicated to the GUI available on https://graphene.bitshares.org (https://graphene.bitshares.org) ?
I guess there will be more and more strictly GUI-related issues.

Sure: https://bitsharestalk.org/index.php/topic,18614.0.html
Title: Re: Test Net for Advanced Users
Post by: spartako on September 24, 2015, 03:42:12 pm: spartako updated
Title: Re: Test Net for Advanced Users
Post by: abit on September 24, 2015, 04:17:14 pm: in.abit updated.
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 24, 2015, 04:24:03 pm: calabiyau updated
Title: Re: Test Net for Advanced Users
Post by: lafona on September 24, 2015, 04:29:17 pm: Quote from: abit on September 24, 2015, 03:01:51 pm
Quote from: lafona on September 24, 2015, 02:45:07 pm

On a side note, the delegate seems to be out of the list of active witnesses, but has enough votes to be middle of the pack. Any thoughts?

Code: [Select]
{ "id": "1.6.1531", "witness_account": "1.2.22396", "last_aslot": 138787, "signing_key": "GPH5DCL5nbhL13sXBh1mwQp5pUBSw7rmwjWeiiy5b2Z2UxuYf8spU", "pay_vb": "1.13.57", "vote_id": "1:1530", "total_votes": "9524676529409", "url": "" }
Every hour, only votes of (new) active witnesses will be updated.

I think I might be confused. Is the total_votes object listed above the correct one I should be looking at to asses the state of my witness(active or standby)? Or is there another object which closer reflects the state of current votes? When I compared this to other witnesses, it seemed like the right metric to look at. Or maybe I might be missing some other factor which would allow the witness to become active again. Thanks
Title: Re: Test Net for Advanced Users
Post by: abit on September 24, 2015, 04:57:49 pm: Quote from: lafona on September 24, 2015, 04:29:17 pm
Is the total_votes object listed above the correct one I should be looking at to asses the state of my witness(active or standby)?
If your witness is already listed in the active witnesses list, yes, the total_votes object for your witness shows a correct number (which is calculated at last maintenance point); else, no, the number may or may not be correct (which is calculated at the time when your witness was still in active witnesses list, or 0 if it's never in the list).
I don't know if there is an API to get correct 'total_votes' of standby witnesses.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 24, 2015, 05:51:23 pm: Quote from: abit on September 24, 2015, 04:57:49 pm
Quote from: lafona on September 24, 2015, 04:29:17 pm
Is the total_votes object listed above the correct one I should be looking at to asses the state of my witness(active or standby)?
If your witness is already listed in the active witnesses list, yes, the total_votes object for your witness shows a correct number (which is calculated at last maintenance point); else, no, the number may or may not be correct (which is calculated at the time when your witness was still in active witnesses list, or 0 if it's never in the list).
I don't know if there is an API to get correct 'total_votes' of standby witnesses.

We don't store vote totals at this point in time.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 24, 2015, 06:24:09 pm: Can anyone explain why vesting balance objects would show up differently on different nodes? On my main active witness node (with no keys loaded into the cli_wallet I get
Code: [Select]
get_object 1.13.46 [{ "id": "1.13.46", "owner": "1.2.22388", "balance": { "amount": 2926266575, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 86400, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "252743032080000", "coin_seconds_earned_last_update": "2015-09-24T18:21:15" } ] } ]On my laptop (which does have my owner keys imported into the cli_wallet) I get
Code: [Select]
get_object 1.13.46 [{ "id": "1.13.46", "owner": "1.2.22388", "balance": { "amount": 2850282029, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 86400, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "246177967305600", "coin_seconds_earned_last_update": "2015-09-24T18:21:15" } ] } ]Am I missing something?

Also witness node is updated to latest source.
Title: Re: Test Net for Advanced Users
Post by: mindphlux on September 24, 2015, 06:26:43 pm: Is it possible to access the CLI console from the WebClient, ie the same commands as seen in the CLI Version.

Using the chrome developer tools/console does not work.
Title: Re: Test Net for Advanced Users
Post by: wackou on September 24, 2015, 07:31:44 pm: wackou updated to latest master
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 24, 2015, 07:35:28 pm: riverhead updated.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 24, 2015, 07:44:00 pm: I thought we witnesses weren't going to be able to produce back to back blocks.
Code: [Select]
2547247ms th_a application.cpp:388 handle_block ] Got block #165363 with time 2015-09-24T19:42:27 from network with latency of 250 ms from dele-puppy 2550252ms th_a application.cpp:388 handle_block ] Got block #165364 with time 2015-09-24T19:42:30 from network with latency of 255 ms from dele-puppy
Title: Re: Test Net for Advanced Users
Post by: Fox on September 24, 2015, 08:21:02 pm: Are we on git checkout master or test3c?
Title: Re: Test Net for Advanced Users
Post by: puppies on September 24, 2015, 08:23:51 pm: Quote from: Fox on September 24, 2015, 08:21:02 pm
Are we on git checkout master or test3c?
I'm on master
Title: Re: Test Net for Advanced Users
Post by: ElMato on September 24, 2015, 08:30:56 pm: elmato updated
Title: Re: Test Net for Advanced Users
Post by: Fox on September 24, 2015, 08:35:51 pm: Quote from: puppies on September 24, 2015, 08:23:51 pm
Quote from: Fox on September 24, 2015, 08:21:02 pm
Are we on git checkout master or test3c?
I'm on master
Witness updated to master
Title: Re: Test Net for Advanced Users
Post by: theoretical on September 24, 2015, 08:39:14 pm: Quote from: puppies on September 24, 2015, 06:24:09 pm
Can anyone explain why vesting balance objects would show up differently on different nodes? On my main active witness node (with no keys loaded into the cli_wallet I get...

This definitely shouldn't be. It's a known bug that we're trying to track down. Thanks for this data -- it may allow me to rule out a hypothesis about what's happening.
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 24, 2015, 09:04:24 pm: Missing some blocks - playing around with update_witness command and using past, present, and new keys.
Title: Re: Test Net for Advanced Users
Post by: lafona on September 24, 2015, 09:05:36 pm: Quote from: bytemaster on September 24, 2015, 05:51:23 pm
Quote from: abit on September 24, 2015, 04:57:49 pm
Quote from: lafona on September 24, 2015, 04:29:17 pm
Is the total_votes object listed above the correct one I should be looking at to asses the state of my witness(active or standby)?
If your witness is already listed in the active witnesses list, yes, the total_votes object for your witness shows a correct number (which is calculated at last maintenance point); else, no, the number may or may not be correct (which is calculated at the time when your witness was still in active witnesses list, or 0 if it's never in the list).
I don't know if there is an API to get correct 'total_votes' of standby witnesses.

We don't store vote totals at this point in time.

Thanks. So the witness was voted out, and once it was no longer active, that value was not updated. Makes sense. Would someone be willing to vote my witness back in? :)

delegate-1.lafona
Title: Re: Test Net for Advanced Users
Post by: Fox on September 24, 2015, 09:44:43 pm: Is it best practice to git install ntp on the witness node, or does Graphene have a built in time syncing protocol?
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 24, 2015, 10:06:57 pm: Quote from: Riverhead on September 24, 2015, 09:04:24 pm

Missing some blocks - playing around with update_witness command and using past, present, and new keys.
1) On 1st server blocks are being signed.
1) On 2nd server I launched the witness_node with new keys.
2) On 2nd server I started a client with a new wallet
4) On 2nd server I import_key "riverhead" "privatekeyhere" and it returns "false"
5) On 2nd server if I type "list_my_accounts" I see riverhead but it has the key from server 1 (the active witness key)
6) On 2nd server if I type "dump_private_keys" I see the pub/priv key pair from step 4
7) On 2nd server type: update_witness "riverhead" "publickeyfromstep 4" which returns:

Code: [Select]
update_witness riverhead "" "GPH5AB42MtMGrcnjtgSjwSp7T6u79Te3FnGKC5gj7vdUKNQ9hU1AL" true 10 assert_exception: Assert Exception it != _keys.end(): {} th_a wallet.cpp:602 get_private_key {"witness_name":"riverhead","url":"","block_signing_key":"GPH5AB42MtMGrcnjtgSjwSp7T6u79Te3FnGKC5gj7vdUKNQ9hU1AL","broadcast":true} th_a wallet.cpp:1401 update_witness unlocked >>>
Dumping private keys on the 2nd server returns the pub/priv key for the U1AL pair.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 24, 2015, 10:27:05 pm: Quote from: Fox on September 24, 2015, 09:44:43 pm
Is it best practice to git install ntp on the witness node, or does Graphene have a built in time syncing protocol?

It is best practice to have NTP or PTP installed... to get to 1 second blocks we will need PTP installed on all witness nodes using a single source.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 24, 2015, 10:27:45 pm: Quote from: lafona on September 24, 2015, 09:05:36 pm
Quote from: bytemaster on September 24, 2015, 05:51:23 pm
Quote from: abit on September 24, 2015, 04:57:49 pm
Quote from: lafona on September 24, 2015, 04:29:17 pm
Is the total_votes object listed above the correct one I should be looking at to asses the state of my witness(active or standby)?
If your witness is already listed in the active witnesses list, yes, the total_votes object for your witness shows a correct number (which is calculated at last maintenance point); else, no, the number may or may not be correct (which is calculated at the time when your witness was still in active witnesses list, or 0 if it's never in the list).
I don't know if there is an API to get correct 'total_votes' of standby witnesses.

We don't store vote totals at this point in time.

Thanks. So the witness was voted out, and once it was no longer active, that value was not updated. Makes sense. Would someone be willing to vote my witness back in? :)

delegate-1.lafona

Done
Title: Re: Test Net for Advanced Users
Post by: roadscape on September 24, 2015, 10:30:03 pm: witness roadscape updated
Title: Re: Test Net for Advanced Users
Post by: betax on September 25, 2015, 12:26:01 am: Quote from: Riverhead on September 24, 2015, 10:06:57 pm
Quote from: Riverhead on September 24, 2015, 09:04:24 pm

Missing some blocks - playing around with update_witness command and using past, present, and new keys.
1) On 1st server blocks are being signed.
1) On 2nd server I launched the witness_node with new keys.
2) On 2nd server I started a client with a new wallet
4) On 2nd server I import_key "riverhead" "privatekeyhere" and it returns "false"
5) On 2nd server if I type "list_my_accounts" I see riverhead but it has the key from server 1 (the active witness key)
6) On 2nd server if I type "dump_private_keys" I see the pub/priv key pair from step 4
7) On 2nd server type: update_witness "riverhead" "publickeyfromstep 4" which returns:

Code: [Select]
update_witness riverhead "" "GPH5AB42MtMGrcnjtgSjwSp7T6u79Te3FnGKC5gj7vdUKNQ9hU1AL" true 10 assert_exception: Assert Exception it != _keys.end(): {} th_a wallet.cpp:602 get_private_key {"witness_name":"riverhead","url":"","block_signing_key":"GPH5AB42MtMGrcnjtgSjwSp7T6u79Te3FnGKC5gj7vdUKNQ9hU1AL","broadcast":true} th_a wallet.cpp:1401 update_witness unlocked >>>
Dumping private keys on the 2nd server returns the pub/priv key for the U1AL pair.

Hi,

Similar steps, but in the same server.

1. Update / compile previous installation in another directory.
2. Run witness / not producing blocks to sync
3. Open client pointing to original witness
4. suggest_brain_key
5. Close new witness and restart with new port for rpc, and new key pair.
6. Back to client (still running) and update_witness betaxtrade "" "PUBLIC KEY" true
7. Get witness, and signing key is the new one
8. Run a few times get witness to see i am producing blocks

9. Confusing part.. dump_private_keys has the old one.

10. Stop other witness
11. Start cli with new port
Title: Re: Test Net for Advanced Users
Post by: cube on September 25, 2015, 06:43:46 am: Witness bitcube updated to latest master.

Quote from: Riverhead on September 23, 2015, 10:43:56 am
Quote from: spartako on September 23, 2015, 10:40:51 am
You have to point to the wallet-url and not the witness url.

/facepalm of course. Still on my first cup of coffee :P.

facepalm indeed. It now makes sense to me. Thank you.
Title: Re: Test Net for Advanced Users
Post by: jtme on September 25, 2015, 07:05:21 am: jtm1 is also updated and needs some votes to get back.
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 25, 2015, 11:17:18 am: Getting up to speed with
Code: [Select]
update_witness and changing and updating servers.
I missed a few blocks ( due to lack of coffee and CORE :P )

Code: [Select]
### change/update witness server and signing key ### # on synced node with open wallet suggest_brain_key { "brain_priv_key": "brain priv key brain priv key brain priv key brain priv key brain priv key brain priv key brain priv key brain priv key", "wif_priv_key": "wif_priv_keywif_priv_keywif_priv_keywif_priv_key", "pub_key": "pub_keypub_keypub_keypub_keypub_keypub_keypub_key" } import_key "delegate.ihashfury" "wif_priv_keywif_priv_keywif_priv_keywif_priv_key" true # check new keys dump_private_keys # build and setup new witness server # edit config.ini in data folder - add keys witness_node -d testNet3 --resync-blockchain #--replay-blockchain # wait untill new server is synced #on synced node with open wallet # update_witness(string witness_name, string url, string block_signing_key, bool broadcast) update_witness delegate.ihashfury "http://bit.ly/ihashfury" "pub_keypub_keypub_keypub_keypub_keypub_keypub_key" trueI strip and copy cli_wallet and witness_node to ~/bin (easy to use different data folders)

0.9.3 wallet_export_keys and import into graphene worked without issues.

Will try a get a new Ubuntu server up today with feeds

A few noob questions using https://graphene.bitshares.org (https://graphene.bitshares.org)

Can you change the wallet password?
Where can you delete say the default wallet to create a new one?
Title: Re: Test Net for Advanced Users
Post by: betax on September 25, 2015, 11:32:52 am: so that is the step missing !

Code: [Select]
import_key "delegate.ihashfury" "wif_priv_keywif_priv_keywif_priv_keywif_priv_key" true
Title: Re: Test Net for Advanced Users
Post by: liondani on September 25, 2015, 11:54:18 am: Quote from: bytemaster on September 24, 2015, 10:27:05 pm
Quote from: Fox on September 24, 2015, 09:44:43 pm
Is it best practice to git install ntp on the witness node, or does Graphene have a built in time syncing protocol?

It is best practice to have NTP or PTP installed... to get to 1 second blocks we will need PTP installed on all witness nodes using a single source.

what if this source get screwed/manipulated in future?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 25, 2015, 12:52:07 pm: Quote from: liondani on September 25, 2015, 11:54:18 am
Quote from: bytemaster on September 24, 2015, 10:27:05 pm
Quote from: Fox on September 24, 2015, 09:44:43 pm
Is it best practice to git install ntp on the witness node, or does Graphene have a built in time syncing protocol?

It is best practice to have NTP or PTP installed... to get to 1 second blocks we will need PTP installed on all witness nodes using a single source.

what if this source get screwed/manipulated in future?

There are more complex algorithms that do not depend upon a central source that would use a phase-locked loop. An example of how this could work:

1. Each machine is assumed broadcast their blocks at multiples of the block interval (1 second)
2. Each machine receives blocks from the other machine with some random latency added on to the time signal.
3. The receiver "KNOWS" the blocks were sent 1 second apart even if they were received .95 or 1.05 seconds apart.
4. The receiver can used this input stream to find the time that minimizes the error for all of the samples.
5. The receiver can then adjust his own clock (slowly) to get closer to his estimate of the sender's clock

So long as the adjustments made are very small relative to the noise in the signal, then both parties can lock to each other at the same time. Under this system the two machines may drift from real time, but they will drift together and maintain an average of 1 second blocks.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 25, 2015, 02:18:11 pm: 155 tps! Good job spartako.

https://graphene.bitshares.org/#/block/187317

(http://imgur.com/7sEd2K9.png)
Title: Re: Test Net for Advanced Users
Post by: spartako on September 25, 2015, 02:37:22 pm: Quote from: clayop on September 25, 2015, 02:18:11 pm
155 tps! Good job spartako.

https://graphene.bitshares.org/#/block/187317

Thanks your help spamming with me! +5%
Title: Re: Test Net for Advanced Users
Post by: clayop on September 25, 2015, 07:53:18 pm: Quote from: spartako on September 25, 2015, 02:37:22 pm
Quote from: clayop on September 25, 2015, 02:18:11 pm
155 tps! Good job spartako.

https://graphene.bitshares.org/#/block/187317

Thanks your help spamming with me! +5%

Btw, my spamming performance is too low; about 10 tps only. Because of I'm using virtual machine in my laptop? is there any tips for well-performed spamming?
Title: Re: Test Net for Advanced Users
Post by: spartako on September 25, 2015, 08:56:02 pm: Quote from: clayop on September 25, 2015, 07:53:18 pm
Quote from: spartako on September 25, 2015, 02:37:22 pm
Quote from: clayop on September 25, 2015, 02:18:11 pm
155 tps! Good job spartako.

https://graphene.bitshares.org/#/block/187317

Thanks your help spamming with me! +5%

Btw, my spamming performance is too low; about 10 tps only. Because of I'm using virtual machine in my laptop? is there any tips for well-performed spamming?

I don't know why, probably depend on power of machine, I'm on digital ocean with 16G, 8 core (anyway is a virtual machine).
What I see if I try to push too many transaction I see that transactions are not broadcasted so I start a command like this
Code: [Select]
node bin/flood.js spartako spartako1 ws://127.0.0.1:8099 400
But after 1000/1200 tx I kill the program (C-c) and usually I have spikes similar when I obtained 155 tps.

If I continue to spam at this rate it seems that transactions are not broadcasted.
The balance goes down and after a while goes up, example:

Code: [Select]
list_account_balances spartako 725729.97991 CORE unlocked >>> list_account_balances spartako list_account_balances spartako 718831.99894 CORE unlocked >>> list_account_balances spartako list_account_balances spartako 715724.23278 CORE unlocked >>> list_account_balances spartako list_account_balances spartako 710737.10803 CORE unlocked >>> list_account_balances spartako list_account_balances spartako 705602.99434 CORE unlocked >>> list_account_balances spartako list_account_balances spartako 724512.07155 CORE
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 25, 2015, 09:14:30 pm: witness 'xeldal' is updated to master
Title: Re: Test Net for Advanced Users
Post by: clayop on September 25, 2015, 09:59:46 pm: Quote from: spartako on September 25, 2015, 08:56:02 pm
Quote from: clayop on September 25, 2015, 07:53:18 pm
Quote from: spartako on September 25, 2015, 02:37:22 pm
Quote from: clayop on September 25, 2015, 02:18:11 pm
155 tps! Good job spartako.

https://graphene.bitshares.org/#/block/187317

Thanks your help spamming with me! +5%

Btw, my spamming performance is too low; about 10 tps only. Because of I'm using virtual machine in my laptop? is there any tips for well-performed spamming?

I don't know why, probably depend on power of machine, I'm on digital ocean with 16G, 8 core (anyway is a virtual machine).
What I see if I try to push too many transaction I see that transactions are not broadcasted so I start a command like this
Code: [Select]
node bin/flood.js spartako spartako1 ws://127.0.0.1:8099 400
But after 1000/1200 tx I kill the program (C-c) and usually I have spikes similar when I obtained 155 tps.

If I continue to spam at this rate it seems that transactions are not broadcasted.
The balance goes down and after a while goes up, example:

Code: [Select]
list_account_balances spartako 725729.97991 CORE unlocked >>> list_account_balances spartako list_account_balances spartako 718831.99894 CORE unlocked >>> list_account_balances spartako list_account_balances spartako 715724.23278 CORE unlocked >>> list_account_balances spartako list_account_balances spartako 710737.10803 CORE unlocked >>> list_account_balances spartako list_account_balances spartako 705602.99434 CORE unlocked >>> list_account_balances spartako list_account_balances spartako 724512.07155 CORE

Can it be an issue or considered just as node performance problem?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 25, 2015, 10:18:09 pm: I suspect what is happening is the other peers are forgetting about the inventory notification and it is never being rebroadcast so it sits in the local node's cache until it expires.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 25, 2015, 10:21:52 pm: http://127.0.0.1:8080/#/block/197175 had 660 transactions which is enough to choke the web GUI :)

Don't try to load that block.
Title: Re: Test Net for Advanced Users
Post by: spartako on September 25, 2015, 10:24:58 pm: Quote from: clayop on September 25, 2015, 09:59:46 pm

Can it be an issue or considered just as node performance problem?

Actually I don't know whats going on, if the wallet has problem to broadcast or it try and the transactions are refused by peers...

Meanwile new record: 225.6 tx/sec!:

https://graphene.bitshares.org/#/block/197175

I was able to do it launching 10 cli_wallet pointing to a single witness and flooding 10 tx per block each cli_wallet
Title: Re: Test Net for Advanced Users
Post by: clayop on September 25, 2015, 11:24:11 pm: Quote from: bytemaster on September 25, 2015, 10:18:09 pm
I suspect what is happening is the other peers are forgetting about the inventory notification and it is never being rebroadcast so it sits in the local node's cache until it expires.

Is it problematic or natural?
Title: Re: Test Net for Advanced Users
Post by: sittingduck on September 25, 2015, 11:35:14 pm: Only an issue during spamming

Sent from my iPhone using Tapatalk
Title: Re: Test Net for Advanced Users
Post by: puppies on September 26, 2015, 01:03:43 am: I was seeing average latency times around 1500ms on all three of my nodes during the spam test this morning. I usually see around 100-300.
Title: Re: Test Net for Advanced Users
Post by: roadscape on September 26, 2015, 03:27:08 am: Can I get some more votes for roadscape (1.6.5249)? Dropped out again.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 26, 2015, 05:44:55 am: For spamming, I found that issuing asset is more efficient than transfer.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 26, 2015, 06:22:48 am: Quote from: sittingduck on September 25, 2015, 11:35:14 pm
Only an issue during spamming

Sent from my iPhone using Tapatalk

IMO, it can be a potential problem in the future. What if a very successful exchange based on BitShares process 100 txs per second on average? (now with 36 core / 120G memory VPS can input about 40 txs per second on average). What happens about one third of transactions of the exchange are not broadcast and are expired?
Title: Re: Test Net for Advanced Users
Post by: Thom on September 26, 2015, 03:23:40 pm: I'm writing a VPS install script for graphene nodes and I'm not sure of the best way to handle the boost libs. I need some input about boost from a dev who has used it. It is one humongus library! I looked at the boost website but couldn't find anything about deployment there.

I don't plan to build any of the binaries on the VPS. I compile boost on a dev system from source, then afterwards compress the entire boost source hierarchy into a tarball (it's big, yeah I know) and run the "b2 install" after decompressing on it the VPS which installs the shared libs. From what I can tell, that approach still does some compiling and / or linking for configuration at install time, but it doesn't take nearly as long as starting from scratch. Still it's minutes not seconds.

The script installs all of the same packages required to compile graphene from scratch, even if they're all not needed (tho I think most if not all are).

Once boost is built from source and "b2 install" is run on the target VPS can the boost/boost_1_57_0 folder hierarchy be removed?

Does the witness_node and cli_wallet binaries require anything from the boost tree or only from the shared libraries (/usr/local/lib/libboost*.so.1.57.0)? What about the gui out of curiosity?

Of course all this wouldn't be necessary if a binary package for the version graphene requires were available via apt-get, or I knew how to produce a .deb file from the boost build tree.

The idea of this effort is to start with a brand new VPS, copy a script and a big tarball to it and when it is done executing it will be a configured, secured node for a witness, seed or backbone node. It installs monitoring, packages, users, tools, optimizes inode caching, swaping etc. So far the script is 125 lines long and it's 95% complete.

Today I hope to add built graphene binaries to the tarball so that will be the iron test. I just hope I can gather all the info I need to run a graphene witness in the testnet from this thread. It's been a few weeks and I see many others have joined in, but don't see much recent info on the process now or if it has changed.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 26, 2015, 04:56:29 pm: Can I have some more CORE for spamming? Thanks in advance.

Id: clayop
Title: Re: Test Net for Advanced Users
Post by: jtme on September 26, 2015, 06:41:26 pm: Quote from: Thom on September 26, 2015, 03:23:40 pm

Once boost is built from source and "b2 install" is run on the target VPS can the boost/boost_1_57_0 folder hierarchy be removed?

Does the witness_node and cli_wallet binaries require anything from the boost tree or only from the shared libraries (/usr/local/lib/libboost*.so.1.57.0)? What about the gui out of curiosity?

ldd witness_node shows
Code: [Select]
linux-vdso.so.1 => (0x00007ffe627f7000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f00b79ad000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f00b77a8000) librt.so.1 => /lib64/librt.so.1 (0x00007f00b75a0000) libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f00b7291000) libm.so.6 => /lib64/libm.so.6 (0x00007f00b6f88000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f00b6d71000) libc.so.6 => /lib64/libc.so.6 (0x00007f00b69b4000) /lib64/ld-linux-x86-64.so.2 (0x000055d7ecbf4000)
that witness_node is statically linked. Shared boost libs are not needed on the production host.
I would asume for the build it would be only needed to have the cpp headers and static *.a
boost libs from install dir to bulid a witness.
Title: Re: Test Net for Advanced Users
Post by: Thom on September 26, 2015, 07:03:46 pm: Quote from: jtme on September 26, 2015, 06:41:26 pm
Quote from: Thom on September 26, 2015, 03:23:40 pm

Once boost is built from source and "b2 install" is run on the target VPS can the boost/boost_1_57_0 folder hierarchy be removed?

Does the witness_node and cli_wallet binaries require anything from the boost tree or only from the shared libraries (/usr/local/lib/libboost*.so.1.57.0)? What about the gui out of curiosity?

ldd witness_node shows
Code: [Select]
linux-vdso.so.1 => (0x00007ffe627f7000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f00b79ad000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f00b77a8000) librt.so.1 => /lib64/librt.so.1 (0x00007f00b75a0000) libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f00b7291000) libm.so.6 => /lib64/libm.so.6 (0x00007f00b6f88000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f00b6d71000) libc.so.6 => /lib64/libc.so.6 (0x00007f00b69b4000) /lib64/ld-linux-x86-64.so.2 (0x000055d7ecbf4000)
that witness_node is statically linked. Shared boost libs are not needed on the production host.
I would asume for the build it would be only needed to have the cpp headers and static *.a
boost libs from install dir to bulid a witness.

Thanks for the reply jtme, I'm a bit rusty with my unix dev skills. Is that list definitive in terms of the boost libs required by graphene, and what tool did you use to get that list?

From what I can see boost is so big almost nobody uses it all so it gets chopped up and pulled apart to make use of various elements, if they want a static build. Static builds are great for removing external dependencies, which really makes sense for building blockchain apps & tools, but it can make for some mighty big executable images.

One last but important question, this may only be known by cryptonomex devs: can boost 1.57.0 libs be installed on a host running the 0.9.x code without any collisions? If 0.9.x was also built with static linking I presume the answer to that is yes, they can coexist without an issue. I'd like a solid confirmation tho before I run my graphene VPS setup script on my production delegate VPS.
Title: Re: Test Net for Advanced Users
Post by: jtme on September 26, 2015, 08:09:04 pm: Quote from: Thom on September 26, 2015, 07:03:46 pm
Quote from: jtme on September 26, 2015, 06:41:26 pm
Quote from: Thom on September 26, 2015, 03:23:40 pm

Once boost is built from source and "b2 install" is run on the target VPS can the boost/boost_1_57_0 folder hierarchy be removed?

Does the witness_node and cli_wallet binaries require anything from the boost tree or only from the shared libraries (/usr/local/lib/libboost*.so.1.57.0)? What about the gui out of curiosity?

ldd witness_node shows
Code: [Select]
linux-vdso.so.1 => (0x00007ffe627f7000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f00b79ad000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f00b77a8000) librt.so.1 => /lib64/librt.so.1 (0x00007f00b75a0000) libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f00b7291000) libm.so.6 => /lib64/libm.so.6 (0x00007f00b6f88000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f00b6d71000) libc.so.6 => /lib64/libc.so.6 (0x00007f00b69b4000) /lib64/ld-linux-x86-64.so.2 (0x000055d7ecbf4000)
that witness_node is statically linked. Shared boost libs are not needed on the production host.
I would asume for the build it would be only needed to have the cpp headers and static *.a
boost libs from install dir to bulid a witness.

Thanks for the reply jtme, I'm a bit rusty with my unix dev skills. Is that list definitive in terms of the boost libs required by graphene, and what tool did you use to get that list?

From what I can see boost is so big almost nobody uses it all so it gets chopped up and pulled apart to make use of various elements, if they want a static build. Static builds are great for removing external dependencies, which really makes sense for building blockchain apps & tools, but it can make for some mighty big executable images.

One last but important question, this may only be known by cryptonomex devs: can boost 1.57.0 libs be installed on a host running the 0.9.x code without any collisions? If 0.9.x was also built with static linking I presume the answer to that is yes, they can coexist without an issue. I'd like a solid confirmation tho before I run my graphene VPS setup script on my production delegate VPS.

ldd is the unix cmd that will show which shared libs the binarry needs to be linked with at runtime.
As for your last q. I would think there should be no problem. Your 1.57.0 boost shared libs should
have different versions if their api or behaviour changed, so your 0.9 client wont link with them.
Plus you can install boost into some other dir like /usr/grapheneboost , then 0.9 clients
cannot link them for sure unles you will point them to the dir using LD_LIBRARY_PATH
env. variable
Title: Re: Test Net for Advanced Users
Post by: mindphlux on September 27, 2015, 06:22:59 pm: Hello all,

I've been lurking here since mid-2014 and I've decided to become more active.

Please vote for my new witness node: mindphlux-witness on testnet.

I've already talked to bytemaster, I will learn ReactJS and help out the frontend development team. Web development is my main job, very experienced in plain JS, so it should be an easy task.

Thank you

Best Regards
mindphlux
Title: Re: Test Net for Advanced Users
Post by: svk on September 27, 2015, 08:48:04 pm: Quote from: mindphlux on September 27, 2015, 06:22:59 pm
Hello all,

I've been lurking here since mid-2014 and I've decided to become more active.

Please vote for my new witness node: mindphlux-witness on testnet.

I've already talked to bytemaster, I will learn ReactJS and help out the frontend development team. Web development is my main job, very experienced in plain JS, so it should be an easy task.

Thank you

Best Regards
mindphlux

Awesome, welcome! :)
Title: Re: Test Net for Advanced Users
Post by: cass on September 27, 2015, 11:23:30 pm: Quote from: svk on September 27, 2015, 08:48:04 pm
Quote from: mindphlux on September 27, 2015, 06:22:59 pm
Hello all,

I've been lurking here since mid-2014 and I've decided to become more active.

Please vote for my new witness node: mindphlux-witness on testnet.

I've already talked to bytemaster, I will learn ReactJS and help out the frontend development team. Web development is my main job, very experienced in plain JS, so it should be an easy task.

Thank you

Best Regards
mindphlux

Awesome, welcome! :)

Yep!!! Welcome, great to have you aboard!
Title: Re: Test Net for Advanced Users
Post by: clayop on September 27, 2015, 11:57:47 pm: Quote from: mindphlux on September 27, 2015, 06:22:59 pm
Hello all,

I've been lurking here since mid-2014 and I've decided to become more active.

Please vote for my new witness node: mindphlux-witness on testnet.

I've already talked to bytemaster, I will learn ReactJS and help out the frontend development team. Web development is my main job, very experienced in plain JS, so it should be an easy task.

Thank you

Best Regards
mindphlux

+5% +5% +5%
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 05:39:48 am: I set up 51 VPSs from three different regions around the world. If I did correctly, they will spam the network at the same time at 2015/9/28 0:02 AM PST (7:02 UTC)
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 28, 2015, 06:00:32 am: Quote from: clayop on September 28, 2015, 05:39:48 am
I set up 51 VPSs from three different regions around the world. If I did correctly, they will spam the network at the same time at 2015/9/28 0:02 AM PST (7:02 UTC)
wow ..
Title: Re: Test Net for Advanced Users
Post by: alt on September 28, 2015, 06:05:48 am: Quote from: clayop on September 28, 2015, 05:39:48 am
I set up 51 VPSs from three different regions around the world. If I did correctly, they will spam the network at the same time at 2015/9/28 0:02 AM PST (7:02 UTC)
unbeliveable, how could you manage so many VPS?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 06:17:00 am: Quote from: alt on September 28, 2015, 06:05:48 am
Quote from: clayop on September 28, 2015, 05:39:48 am
I set up 51 VPSs from three different regions around the world. If I did correctly, they will spam the network at the same time at 2015/9/28 0:02 AM PST (7:02 UTC)
unbeliveable, how could you manage so many VPS?

I am just running them for about 2 hours or so. Probably they just cost under $5 in total.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 06:38:50 am: Operation test is successfully done. 25 minutes left.
Title: Re: Test Net for Advanced Users
Post by: sudo on September 28, 2015, 06:56:41 am: Quote from: clayop on September 28, 2015, 05:39:48 am
I set up 51 VPSs from three different regions around the world. If I did correctly, they will spam the network at the same time at 2015/9/28 0:02 AM PST (7:02 UTC)

awesome +5% +5%
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 07:16:15 am: Many witnesses are down now... please fix your vps :(
Title: Re: Test Net for Advanced Users
Post by: alt on September 28, 2015, 07:21:08 am: block 262244: 1715 txs
thread p2p have 100% CPU usage, can we improve it more?
Code: [Select]
top - 07:20:31 up 208 days, 10:26, 1 user, load average: 1.23, 1.21, 0.96 Threads: 205 total, 3 running, 198 sleeping, 4 stopped, 0 zombie %Cpu(s): 76.4 us, 20.2 sy, 0.0 ni, 1.0 id, 1.5 wa, 0.0 hi, 1.0 si, 0.0 st KiB Mem: 2042528 total, 2022388 used, 20140 free, 1756 buffers KiB Swap: 4227064 total, 1671884 used, 2555180 free. 1253948 cached Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 20771 alt 20 0 988692 190716 6656 S 0.0 9.3 8:44.70 witness_node 20774 alt 20 0 988692 190716 6656 S 0.0 9.3 0:00.35 ntp 20775 alt 20 0 988692 190716 6656 S 0.0 9.3 7:36.21 asio 20776 alt 20 0 988692 190716 6656 S 0.0 9.3 0:00.08 ntp 20777 alt 20 0 988692 190716 6656 R 99.1 9.3 358:36.98 p2p
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 07:23:45 am: https://graphene.bitshares.org/#/block/262215

1307 txs = 435.7 tps
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 07:25:34 am: Should I stop here?
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 07:27:10 am: Quote from: alt on September 28, 2015, 07:21:08 am
block 262244: 1715 txs
thread p2p have 100% CPU usage, can we improve it more?
Code: [Select]
top - 07:20:31 up 208 days, 10:26, 1 user, load average: 1.23, 1.21, 0.96 Threads: 205 total, 3 running, 198 sleeping, 4 stopped, 0 zombie %Cpu(s): 76.4 us, 20.2 sy, 0.0 ni, 1.0 id, 1.5 wa, 0.0 hi, 1.0 si, 0.0 st KiB Mem: 2042528 total, 2022388 used, 20140 free, 1756 buffers KiB Swap: 4227064 total, 1671884 used, 2555180 free. 1253948 cached Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 20771 alt 20 0 988692 190716 6656 S 0.0 9.3 8:44.70 witness_node 20774 alt 20 0 988692 190716 6656 S 0.0 9.3 0:00.35 ntp 20775 alt 20 0 988692 190716 6656 S 0.0 9.3 7:36.21 asio 20776 alt 20 0 988692 190716 6656 S 0.0 9.3 0:00.08 ntp 20777 alt 20 0 988692 190716 6656 R 99.1 9.3 358:36.98 p2p

Mine is around 30%.

Machine type
n1-standard-1 (1 vCPU, 3.75 GB memory)
CPU platform
Intel Ivy Bridge
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 07:38:36 am: Test is done

Duration: 30 min
Total Transactions: approximately 40,000 txs
Max TPS: 435.7 (block #262215)

Participation rate before testing: 94%
Participation rate after testing: 79%
Title: Re: Test Net for Advanced Users
Post by: lakerta06 on September 28, 2015, 07:44:22 am: Quote from: clayop on September 28, 2015, 07:38:36 am
Test is done

Duration: 30 min
Total Transactions: approximately 40,000 txs
Max TPS: 435.7 (block #262215)

Participation rate before testing: 97%
Participation rate after testing: 79%

Assuming similar delegate configuration at launch, cost of getting 1/5 of delegates down is ~5.2k $
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 07:51:52 am: Quote from: lakerta06 on September 28, 2015, 07:44:22 am
Quote from: clayop on September 28, 2015, 07:38:36 am
Test is done

Duration: 30 min
Total Transactions: approximately 40,000 txs
Max TPS: 435.7 (block #262215)

Participation rate before testing: 97%
Participation rate after testing: 79%

Assuming similar delegate configuration at launch, cost of getting 1/5 of delegates down is ~5.2k $

I spent 100k CORE. (But will withdraw 75k of them as a vesting)
Title: Re: Test Net for Advanced Users
Post by: spartako on September 28, 2015, 07:59:51 am: Quote from: clayop on September 28, 2015, 07:23:45 am
https://graphene.bitshares.org/#/block/262215

1307 txs = 435.7 tps

Wow!! Great work!!
Title: Re: Test Net for Advanced Users
Post by: betax on September 28, 2015, 08:04:00 am: im back up now...

Very good job!!!
Title: Re: Test Net for Advanced Users
Post by: fav on September 28, 2015, 08:04:34 am: Quote from: spartako on September 28, 2015, 07:59:51 am
Quote from: clayop on September 28, 2015, 07:23:45 am
https://graphene.bitshares.org/#/block/262215

1307 txs = 435.7 tps

Wow!! Great work!!

+5% really amazing!
Title: Re: Test Net for Advanced Users
Post by: liondani on September 28, 2015, 08:13:07 am: clayop spammed poloniex troll-box about the news also successfully ! ;) (in real time!)

+5%
Title: Re: Test Net for Advanced Users
Post by: clout on September 28, 2015, 08:13:59 am: Quote from: clayop on September 28, 2015, 07:38:36 am
Test is done

Duration: 30 min
Total Transactions: approximately 40,000 txs
Max TPS: 435.7 (block #262215)

Participation rate before testing: 94%
Participation rate after testing: 79%

Actually the max tps was 571 from block 262244. And the participation rate during the test was about 50%
Title: Re: Test Net for Advanced Users
Post by: betax on September 28, 2015, 08:16:31 am: A word of warning, make sure you sync before you start producing blocks, OR you will miss a huge amount of blocks. ~500 blocks missed whilst syncing. Either that or I got all the blocks missed by everyone ;)

Code: [Select]
"id": "1.6.5252", "witness_account": "1.2.7109", "last_aslot": 214677, "signing_key": "GPH6saDVJCEaHreyMhp4yumANMyyr73b8cYg3PCyWxrnufop2NwXs", "pay_vb": "1.13.50", "vote_id": "1:5275", "total_votes": "9563612188418", "url": "", "total_missed": 1379 } unlocked >>> get_witness betaxtrade get_witness betaxtrade { "id": "1.6.5252", "witness_account": "1.2.7109", "last_aslot": 214677, "signing_key": "GPH6saDVJCEaHreyMhp4yumANMyyr73b8cYg3PCyWxrnufop2NwXs", "pay_vb": "1.13.50", "vote_id": "1:5275", "total_votes": "9563612188418", "url": "", "total_missed": 1388 } unlocked >>> get_witness betaxtrade get_witness betaxtrade { "id": "1.6.5252", "witness_account": "1.2.7109", "last_aslot": 214677, "signing_key": "GPH6saDVJCEaHreyMhp4yumANMyyr73b8cYg3PCyWxrnufop2NwXs", "pay_vb": "1.13.50", "vote_id": "1:5275", "total_votes": "9563612188418", "url": "", "total_missed": 1388 } unlocked >>> get_witness betaxtrade get_witness betaxtrade { "id": "1.6.5252", "witness_account": "1.2.7109", "last_aslot": 214677, "signing_key": "GPH6saDVJCEaHreyMhp4yumANMyyr73b8cYg3PCyWxrnufop2NwXs", "pay_vb": "1.13.50", "vote_id": "1:5275", "total_votes": "9563612188418", "url": "", "total_missed": 1397 } unlocked >>> get_witness betaxtrade get_witness betaxtrade { "id": "1.6.5252", "witness_account": "1.2.7109", "last_aslot": 274302, "signing_key": "GPH6saDVJCEaHreyMhp4yumANMyyr73b8cYg3PCyWxrnufop2NwXs", "pay_vb": "1.13.50", "vote_id": "1:5275", "total_votes": "9524011927872", "url": "", "total_missed": 1806 }
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 28, 2015, 09:13:36 am: Code: [Select]
15:48 from network with latency of 320 ms from init2 951317ms th_a application.cpp:388 handle_block ] Got block #248796 with time 2015-09-27T19:15:51 from network with latency of 318 ms from init3 954311ms th_a application.cpp:388 handle_block ] Got block #248797 with time 2015-09-27T19:15:54 from network with latency of 312 ms from init6 957353ms th_a application.cpp:388 handle_block ] Got block #248798 with time 2015-09-27T19:15:57 from network with latency of 354 ms from maqifrnswa 960544ms th_a application.cpp:388 handle_block ] Got block #248799 with time 2015-09-27T19:16:00 from network with latency of 546 ms from delegate-dev2.btsnow 960869ms th_a application.cpp:518 get_item ] Serving up block #248799 961012ms th_a application.cpp:432 handle_transaction ] Got transaction from network 961232ms th_a application.cpp:432 handle_transaction ] Got transaction from network witness_node: /home/calabiyau/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed. Aborted (core dumped)after running stable for days, witness didn`t survive the storm :(
Title: Re: Test Net for Advanced Users
Post by: Fernandez on September 28, 2015, 09:59:00 am: The 3 second blocks going to be the standard or is there a planned change later with a hard fork?
Title: Re: Test Net for Advanced Users
Post by: spartako on September 28, 2015, 10:22:27 am: I tried to spam the network using my delegate spartako as witness to broadcast txs, I obtain a good result with a single machine:

https://graphene.bitshares.org/#/block/264951
tx: 876
tx/s: 292

But when I try to push more, my delegate start to miss blocks....
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 28, 2015, 10:22:34 am: (http://i.imgur.com/2fKiIB6.png)

wow....
Title: Re: Test Net for Advanced Users
Post by: spartako on September 28, 2015, 10:27:12 am: Quote from: CalabiYau on September 28, 2015, 10:22:34 am
(http://i.imgur.com/2fKiIB6.png)

wow....

You can see the two spikes is my delegate spartako producing blocks, in the second "storm" my delegate started to miss blocks and so no spikes.
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 28, 2015, 10:35:57 am: Quote from: Fernandez on September 28, 2015, 09:59:00 am
The 3 second blocks going to be the standard or is there a planned change later with a hard fork?
3 secs initially .. then reducing it if shareholders approve
Title: Re: Test Net for Advanced Users
Post by: lakerta06 on September 28, 2015, 11:15:43 am: Quote from: clayop on September 28, 2015, 07:51:52 am
Quote from: lakerta06 on September 28, 2015, 07:44:22 am
Quote from: clayop on September 28, 2015, 07:38:36 am
Test is done

Duration: 30 min
Total Transactions: approximately 40,000 txs
Max TPS: 435.7 (block #262215)

Participation rate before testing: 97%
Participation rate after testing: 79%

Assuming similar delegate configuration at launch, cost of getting 1/5 of delegates down is ~5.2k $

I spent 100k CORE. (But will withdraw 75k of them as a vesting)
AFAIK cost per transaction will be 20 BTS at the beginning. So in the real network, transaction cost will be 20 x 40k = 800k BTS
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 28, 2015, 12:21:43 pm: Quote from: CalabiYau on September 28, 2015, 10:22:34 am
(http://i.imgur.com/2fKiIB6.png)

wow....

This is a clear indication that the network isn't efficiently propagating transactions.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 28, 2015, 12:24:21 pm: Any chance that we could get an estimate of the number of broadcast transactions that expire before being included in the blockchain?
Title: Re: Test Net for Advanced Users
Post by: BunkerChainLabs-DataSecurityNode on September 28, 2015, 12:47:49 pm: Quote from: clayop on September 28, 2015, 07:23:45 am
https://graphene.bitshares.org/#/block/262215

1307 txs = 435.7 tps

Fantastic work!
Title: Re: Test Net for Advanced Users
Post by: spartako on September 28, 2015, 01:38:07 pm: Quote from: bytemaster on September 28, 2015, 12:24:21 pm
Any chance that we could get an estimate of the number of broadcast transactions that expire before being included in the blockchain?

I just tried to send 1500 tx (at 500 per block) and I got 235 tx in blockchain so 15.6% included:
Code: [Select]
268186 '1.6.4' 'init3' 15 268185 '1.6.11' 'init10' 9 268184 '1.6.1527' 'dele-puppy' 5 268183 '1.6.2' 'init1' 82 268182 '1.6.2104' 'fox' 7 268181 '1.6.3' 'init2' 1 268180 '1.6.5252' 'betaxtrade' 53 268179 '1.6.7' 'init6' 0 268178 '1.6.1' 'init0' 52 268177 '1.6.9' 'init8' 11
Spamming a 300 tx/block I obtained: 441/600 (73.5%)
Code: [Select]
268326 '1.6.1' 'init0' 67 268325 '1.6.1531' 'delegate-1.lafona' 52 268324 '1.6.11' 'init10' 11 268323 '1.6.1531' 'delegate-1.lafona' 32 268322 '1.6.12' 'init11' 3 268321 '1.6.3356' 'mr.agsexplorer' 51 268320 '1.6.3360' 'mrs.agsexplorer' 119 268319 '1.6.4949' 'xeldal' 65

Spamming at 200 tx /block I lost no transactions 600/600 (100%)
Code: [Select]
268375 '1.6.3360' 'mrs.agsexplorer' 110 268374 '1.6.11' 'init10' 3 268373 '1.6.3356' 'mr.agsexplorer' 201 268372 '1.6.6' 'init5' 36 268371 '1.6.1569' 'delegate.baozi' 5 268370 '1.6.3184' 'maqifrnswa' 75 268369 '1.6.7' 'init6' 0 268368 '1.6.3968' 'riverhead' 121 268367 '1.6.5' 'init4' 24 268366 '1.6.4' 'init3' 10 268365 '1.6.5252' 'betaxtrade' 15
Title: Re: Test Net for Advanced Users
Post by: Stan on September 28, 2015, 02:11:26 pm: Quote from: Fernandez on September 28, 2015, 09:59:00 am
The 3 second blocks going to be the standard or is there a planned change later with a hard fork?

No hard fork needed. Speed is an adjustable parameter as networking code is optimized over the next few months.
Expectation is to ramp up to 1 second blocks in 2 or 3 steps if shareholders approve.
Title: Re: Test Net for Advanced Users
Post by: Fox on September 28, 2015, 03:18:21 pm: I have added additional resources to my block producing node(s) in an attempt to meet the peak TPS spam testing. Please continue these tests and I will adjust node resources to match peak demand.
Title: Re: Test Net for Advanced Users
Post by: puppies on September 28, 2015, 03:39:50 pm: What were the average latencies looking like during the stress test?
Title: Re: Test Net for Advanced Users
Post by: abit on September 28, 2015, 03:55:38 pm: My block-producing node got killed during the test, but my observer node is still alive.
~~Will see what happened.~~

//Edit:
Last block received is:
Code: [Select]
2015-09-28T07:05:33 th_a:invoke handle_block handle_block ] Got block #262123 with time 2015-09-28T07:05:30 from network withlatency of 3618 ms from init11 application.cpp:388
Last transaction received is:
Code: [Select]
2015-09-28T07:05:38 th_a:invoke handle_transaction handle_transaction ] Got transaction from network application.cpp:432After that the witness node received nothing from network, but recursively trying to generate block by itself.
Will see what happened in p2p.log.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 04:00:41 pm: Quote from: lakerta06 on September 28, 2015, 11:15:43 am
Quote from: clayop on September 28, 2015, 07:51:52 am
Quote from: lakerta06 on September 28, 2015, 07:44:22 am
Quote from: clayop on September 28, 2015, 07:38:36 am
Test is done

Duration: 30 min
Total Transactions: approximately 40,000 txs
Max TPS: 435.7 (block #262215)

Participation rate before testing: 97%
Participation rate after testing: 79%

Assuming similar delegate configuration at launch, cost of getting 1/5 of delegates down is ~5.2k $

I spent 100k CORE. (But will withdraw 75k of them as a vesting)
AFAIK cost per transaction will be 20 BTS at the beginning. So in the real network, transaction cost will be 20 x 40k = 800k BTS

Selling asaet fee is only 2.5 CORE.
Title: Re: Test Net for Advanced Users
Post by: lakerta06 on September 28, 2015, 04:14:45 pm: Quote from: clayop on September 28, 2015, 04:00:41 pm
Quote from: lakerta06 on September 28, 2015, 11:15:43 am
Quote from: clayop on September 28, 2015, 07:51:52 am
Quote from: lakerta06 on September 28, 2015, 07:44:22 am
Quote from: clayop on September 28, 2015, 07:38:36 am
Test is done

Duration: 30 min
Total Transactions: approximately 40,000 txs
Max TPS: 435.7 (block #262215)

Participation rate before testing: 97%
Participation rate after testing: 79%

Assuming similar delegate configuration at launch, cost of getting 1/5 of delegates down is ~5.2k $

I spent 100k CORE. (But will withdraw 75k of them as a vesting)
AFAIK cost per transaction will be 20 BTS at the beginning. So in the real network, transaction cost will be 20 x 40k = 800k BTS

Selling asaet fee is only 2.5 CORE.

So you can basically hang the network with a couple thousand dollars for a couple hours maybe? I am trying to understand if this is a valid attack vector.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 04:58:07 pm: Quote from: lakerta06 on September 28, 2015, 04:14:45 pm
Quote from: clayop on September 28, 2015, 04:00:41 pm
Quote from: lakerta06 on September 28, 2015, 11:15:43 am
Quote from: clayop on September 28, 2015, 07:51:52 am
Quote from: lakerta06 on September 28, 2015, 07:44:22 am
Quote from: clayop on September 28, 2015, 07:38:36 am
Test is done

Duration: 30 min
Total Transactions: approximately 40,000 txs
Max TPS: 435.7 (block #262215)

Participation rate before testing: 97%
Participation rate after testing: 79%

Assuming similar delegate configuration at launch, cost of getting 1/5 of delegates down is ~5.2k $

I spent 100k CORE. (But will withdraw 75k of them as a vesting)
AFAIK cost per transaction will be 20 BTS at the beginning. So in the real network, transaction cost will be 20 x 40k = 800k BTS

Selling asaet fee is only 2.5 CORE.

So you can basically hang the network with a couple thousand dollars for a couple hours maybe? I am trying to understand if this is a valid attack vector.

If price of CORE equals to current BTS, I spent under $1,000 for the stress test.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 06:31:32 pm: Quote from: clout on September 28, 2015, 08:13:59 am
Actually the max tps was 571 from block 262244. And the participation rate during the test was about 50%

Since the block interval is 6 second between 262243 and 262244, its actual tps is 286.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 07:43:40 pm: I'm planning second stress test with 101 VPSs 10 txs per second each.
But should I wait for a network protocol fix (which can handle spam transactions more effectively)?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 28, 2015, 08:46:58 pm: Quote from: clayop on September 28, 2015, 07:43:40 pm
I'm planning second stress test with 101 VPSs 10 txs per second each.
But should I wait for a network protocol fix (which can handle spam transactions more effectively)?

Probably.
Title: Re: Test Net for Advanced Users
Post by: maqifrnswa on September 28, 2015, 08:49:32 pm: so far my $10 DO vps witness has been stable through this testing; in case someone wants a point of comparison for hardware specs.
1GB ram, 1 CPU
Ubuntu 15.04, using the daily build packages
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 28, 2015, 09:16:33 pm: Quote from: bytemaster on September 28, 2015, 08:46:58 pm
Quote from: clayop on September 28, 2015, 07:43:40 pm
I'm planning second stress test with 101 VPSs 10 txs per second each.
But should I wait for a network protocol fix (which can handle spam transactions more effectively)?

Probably.

I just got off a call with Eric regarding the P2P code and propagation of transactions. Currently it fetches at most 1 trx per peer at a time. This means that if you have a 50 ms ping time to most of your peers, the fastest a single node can broadcast transactions is 20 trx per second.

Tomorrow Eric is going to modify the P2P code to fetch several many transactions at once which should dramatically increase the ability of a single peer to broadcast.

We are also going to add a small modification to the protocol where the "inventory/request" method only applies to "rebroadcasting" of transactions/blocks. If your node is the SOURCE of the transaction or block then it will simply send it to you because it knows in advance that you do not have it and there is no one else who can give it to you. This should shave a round trip time from the block propagation delay which should reduce average propagation times (latency) by 25% or more.

If you are attempting to flood with 101 VPSs then the current P2P code should propagate just fine so long as you verify that each of your VPSs are connected to 8 peers before attempting to flood.
Title: Re: Test Net for Advanced Users
Post by: alt on September 28, 2015, 11:19:26 pm: forked, have to resync.
can we add the block number for parameter --resync-blockchain?
so we only need to resync from the given block number.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 11:27:57 pm: I will flood the testnet at 9/29 0:10 UTC with 101 VPSs. Tips for VPS costs are more than welcome. ;)

BTS ID: clayop

Due to the limit of numbers per region, I can only manage about 70 VPSs.
Title: Re: Test Net for Advanced Users
Post by: onceuponatime on September 28, 2015, 11:51:22 pm: Quote from: clayop on September 28, 2015, 11:27:57 pm
I will flood the testnet at 9/29 0:10 UTC with 101 VPSs. Tips for VPS costs are more than welcome. ;)

BTS ID: clayop

Due to the limit of numbers per region, I can only manage about 60 VPSs.

Sent you 500BTS for to help with your costs ;D
Title: Re: Test Net for Advanced Users
Post by: clayop on September 28, 2015, 11:52:17 pm: Quote from: onceuponatime on September 28, 2015, 11:51:22 pm
Quote from: clayop on September 28, 2015, 11:27:57 pm
I will flood the testnet at 9/29 0:10 UTC with 101 VPSs. Tips for VPS costs are more than welcome. ;)

BTS ID: clayop

Due to the limit of numbers per region, I can only manage about 60 VPSs.

Sent you 500BTS for to help with your costs ;D

Thank you!!!
Title: Re: Test Net for Advanced Users
Post by: alt on September 29, 2015, 12:09:45 am: here is a piece from the log when it forked:
Code: [Select]
2015-09-28T20:08:30 p2p:message read_loop process_block_during ] received a block from peer 216.252.204.69:54183, passing it to client node.cpp:3232 2015-09-28T20:08:30 p2p:message read_loop process_block_during ] Successfully pushed block 275994 (id:0004361a7b4321512a38bc112c8c8ecd84d3e59c) node.cpp:3254 .................... 2015-09-28T20:08:36 p2p:message read_loop process_block_during ] received a block from peer 114.92.254.159:62015, passing it to client node.cpp:3232 ......................... 2015-09-28T20:08:36 p2p:message read_loop process_block_during ] Failed to push block 275996 (id:0004361c004527fceb33c4dfe9062a92a6421508), client rejected block sent by peer node.cpp:3346 2015-09-28T20:08:36 p2p:message read_loop process_block_during ] disconnecting client 114.92.254.159:62015 because it offered us the rejected block node.cpp:3368 ............... 2015-09-28T20:08:37 p2p:message read_loop process_block_during ] received a block from peer 185.42.242.124:40060, passing it to client node.cpp:3232 2015-09-28T20:08:37 p2p:message read_loop process_block_during ] Failed to push block 275996 (id:0004361c004527fceb33c4dfe9062a92a6421508), client rejected block sent by peer node.cpp:3346 2015-09-28T20:08:37 p2p:message read_loop process_block_during ] disconnecting client 185.42.242.124:40060 because it offered us the rejected block node.cpp:3368 .............. 2015-09-28T20:08:39 p2p:message read_loop process_block_during ] received a block from peer 178.62.88.151:46944, passing it to client node.cpp:3232 2015-09-28T20:08:39 p2p:message read_loop process_block_during ] Successfully pushed block 275996 (id:0004361c4c4b8410260663693fd59b7ca1977b86) node.cpp:3254 2015-09-28T20:08:39 p2p:message read_loop process_block_during ] client validated the block, advertising it to other peers node.cpp:3278 .............. 2015-09-28T20:08:42 p2p:message read_loop process_block_during ] received a block from peer 178.62.88.151:46944, passing it to client node.cpp:3232 2015-09-28T20:08:42 p2p:message read_loop process_block_during ] Peer 178.62.88.151:46944 sent me a block that didn't link to our blockchain. Restarting sync mode wi th them to get the missing block. Error pushing block was: {"code":90006,"name":"unlinkable_block_exception","message":"unlinkable block","stack":[{"context":{"level" :"error","file":"application.cpp","line":417,"method":"handle_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:42"},"format":"Error when pushin g block:\n${e}","data":{"e":"3080000 unlinkable_block_exception: unlinkable block\nblock does not link to known chain\n {}\n th_a fork_database.cpp:79 _push_bl ock\n\n {\"new_block\":{\"previous\":\"0004361c004527fceb33c4dfe9062a92a6421508\",\"timestamp\":\"2015-09-28T20:08:42\",\"witness\":\"1.6.5248\",\"transaction_merk le_root\":\"0000000000000000000000000000000000000000\",\"extensions\":[],\"witness_signature\":\"1f051e73526e48fd46a4359daaede6e5e5a8b6f451194c24caad9a1287506ef0cd026 c0ecdadb5ea35b9843dc0bd68faee59053278a7ce6e571f838a2d870bebc9\",\"transactions\":[]}}\n th_a db_block.cpp:195 _push_block"}},{"context":{"level":"warn","file":"ap plication.cpp","line":428,"method":"handle_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:42"},"format":"","data":{"blk_msg":{"block":{"previ ous":"0004361c004527fceb33c4dfe9062a92a6421508","timestamp":"2015-09-28T20:08:42","witness":"1.6.5248","transaction_merkle_root":"000000000000000000000000000000000000 0000","extensions":[],"witness_signature":"1f051e73526e48fd46a4359daaede6e5e5a8b6f451194c24caad9a1287506ef0cd026c0ecdadb5ea35b9843dc0bd68faee59053278a7ce6e571f838a2d8 70bebc9","transactions":[]},"block_id":"0004361d1c4d414512a8ae8e99ecf2026627d08e"},"sync_mode":false}}]} node.cpp:3362 d>2015-09-28T20:08:42 p2p:message read_loop fetch_next_batch_of_ ] sync: sending a request for the next items after 0004361c4c4b8410260663693fd59b7ca1977b86 to peer 178 .62.88.151:46944, (full request is ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184c26912df003d6ac2","0004361a7b4321512a38bc112c8c8ecd84d3e59c"," 0004361c4c4b8410260663693fd59b7ca1977b86"]) node.cpp:2354 ............................ 2015-09-28T20:08:42 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 178.62.88.151:46944's last block the delegat e has seen is now 0004361a7b4321512a38bc112c8c8ecd84d3e59c (actual block #275994) node.cpp:2511 2015-09-28T20:08:42 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 178.62.88.151:46944's last block the delegat e has seen is now 0004361bd4f6fdf618a74290b09a8a018ab7867b (actual block #275995) node.cpp:2511 2015-09-28T20:08:42 p2p:message read_loop on_blockchain_item_i ] after removing all items we have already seen, item_hashes_received.size() = 2 node.cpp:2515 2015-09-28T20:08:42 p2p:message read_loop trigger_fetch_sync_i ] Triggering fetch sync items loop now node.cpp:1083 2015-09-28T20:08:42 p2p:fetch_sync_items_loop fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:1022 2015-09-28T20:08:42 p2p:fetch_sync_items_loop request_sync_items_f ] requesting 2 item(s) ["0004361c004527fceb33c4dfe9062a92a6421508","0004361d1c4d414512a8ae8e99ecf20 26627d08e"] from peer 178.62.88.151:46944 node.cpp:1006 2015-09-28T20:08:42 p2p:fetch_sync_items_loop fetch_sync_items_loo ] no sync items to fetch right now, going to sleep node.cpp:1072 2015-09-28T20:08:42 p2p:message read_loop on_message ] handling message fetch_blockchain_item_ids_message_type f9797929aee8529c183c2a43787da7a9b3d24e14 size 85 from peer 23.102.65.247:1984 node.cpp:1684 2015-09-28T20:08:42 p2p:message read_loop on_fetch_blockchain_ ] sync: received a request for item ids after 0004361c4c4b8410260663693fd59b7ca1977b86 from peer 23.102 .65.247:1984 (full request: ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184c26912df003d6ac2","0004361a7b4321512a38bc112c8c8ecd84d3e59c","0004361 c4c4b8410260663693fd59b7ca1977b86"]) node.cpp:2171 2015-09-28T20:08:42 p2p:message read_loop on_fetch_blockchain_ ] reply_message: {"total_remaining_item_count":0,"item_type":1001,"item_hashes_available":["0004361c4c4 b8410260663693fd59b7ca1977b86"]} fetch_blockchain_item_ids_message_received.blockchain_synopsis: ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184 c26912df003d6ac2","0004361a7b4321512a38bc112c8c8ecd84d3e59c","0004361c4c4b8410260663693fd59b7ca1977b86"] node.cpp:2194 2015-09-28T20:08:42 p2p:message read_loop on_fetch_blockchain_ ] sync: peer is already in sync with us node.cpp:2213 2015-09-28T20:08:43 p2p:message read_loop on_message ] handling message fetch_blockchain_item_ids_message_type f9797929aee8529c183c2a43787da7a9b3d24e14 size 85 from peer 207.46.141.218:1344 node.cpp:1684 2015-09-28T20:08:43 p2p:message read_loop on_fetch_blockchain_ ] sync: received a request for item ids after 0004361c4c4b8410260663693fd59b7ca1977b86 from peer 207.46 .141.218:1344 (full request: ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184c26912df003d6ac2","0004361a7b4321512a38bc112c8c8ecd84d3e59c","000436 1c4c4b8410260663693fd59b7ca1977b86"]) node.cpp:2171 2015-09-28T20:08:43 p2p:message read_loop on_fetch_blockchain_ ] reply_message: {"total_remaining_item_count":0,"item_type":1001,"item_hashes_available":["0004361c4c4 b8410260663693fd59b7ca1977b86"]} fetch_blockchain_item_ids_message_received.blockchain_synopsis: ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184 c26912df003d6ac2","0004361a7b4321512a38bc112c8c8ecd84d3e59c","0004361c4c4b8410260663693fd59b7ca1977b86"] node.cpp:2194 2015-09-28T20:08:43 p2p:message read_loop on_fetch_blockchain_ ] sync: peer is already in sync with us node.cpp:2213 2015-09-28T20:08:43 p2p:message read_loop on_message ] handling message block_message_type 1003c4eca3a31fd0e4933c919f37b072876911dc size 133 from peer 71.19 7.2.119:1776 node.cpp:1684 2015-09-28T20:08:43 p2p:message read_loop process_block_during ] received a block from peer 71.197.2.119:1776, passing it to client node.cpp:3232 2015-09-28T20:08:43 p2p:message read_loop process_block_during ] Peer 71.197.2.119:1776 sent me a block that didn't link to our blockchain. Restarting sync mode with them to get the missing block. Error pushing block was: {"code":90006,"name":"unlinkable_block_exception","message":"unlinkable block","stack":[{"context":{"level":" error","file":"application.cpp","line":417,"method":"handle_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"Error when pushing block:\n${e}","data":{"e":"3080000 unlinkable_block_exception: unlinkable block\nblock does not link to known chain\n {}\n th_a fork_database.cpp:79 _push_bloc k\n\n {\"new_block\":{\"previous\":\"0004361c004527fceb33c4dfe9062a92a6421508\",\"timestamp\":\"2015-09-28T20:08:42\",\"witness\":\"1.6.5248\",\"transaction_merkle _root\":\"0000000000000000000000000000000000000000\",\"extensions\":[],\"witness_signature\":\"1f051e73526e48fd46a4359daaede6e5e5a8b6f451194c24caad9a1287506ef0cd026c0 ecdadb5ea35b9843dc0bd68faee59053278a7ce6e571f838a2d870bebc9\",\"transactions\":[]}}\n th_a db_block.cpp:195 _push_block"}},{"context":{"level":"warn","file":"appl ication.cpp","line":428,"method":"handle_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"","data":{"blk_msg":{"block":{"previou s":"0004361c004527fceb33c4dfe9062a92a6421508","timestamp":"2015-09-28T20:08:42","witness":"1.6.5248","transaction_merkle_root":"00000000000000000000000000000000000000 00","extensions":[],"witness_signature":"1f051e73526e48fd46a4359daaede6e5e5a8b6f451194c24caad9a1287506ef0cd026c0ecdadb5ea35b9843dc0bd68faee59053278a7ce6e571f838a2d870 bebc9","transactions":[]},"block_id":"0004361d1c4d414512a8ae8e99ecf2026627d08e"},"sync_mode":false}}]} node.cpp:3362 2015-09-28T20:08:43 p2p:message read_loop fetch_next_batch_of_ ] sync: sending a request for the next items after 0004361c4c4b8410260663693fd59b7ca1977b86 to peer 71. 197.2.119:1776, (full request is ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184c26912df003d6ac2","0004361a7b4321512a38bc112c8c8ecd84d3e59c","00 04361c4c4b8410260663693fd59b7ca1977b86"]) node.cpp:2354 .............. 2015-09-28T20:08:43 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] Successfully pushed sync block 275996 (id:0004361c004527fceb33c4dfe9062a92a6421508) node.cpp:2935 .............. 2015-09-28T20:08:43 p2p:send_sync_block_to_node_delegate fetch_next_batch_of_ ] sync: sending a request for the next items after 0004361c4c4b8410260663693fd59b7ca1977 b86 to peer 71.197.2.119:61371, (full request is ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184c26912df003d6ac2","0004361a7b4321512a38bc112c8c8 ecd84d3e59c","0004361c4c4b8410260663693fd59b7ca1977b86"]) node.cpp:2354 ............... 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 109.73.172.144:43494's last block the delega te has seen is now 0004361a7b4321512a38bc112c8c8ecd84d3e59c (actual block #275994) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 109.73.172.144:43494's last block the delega te has seen is now 0004361bd4f6fdf618a74290b09a8a018ab7867b (actual block #275995) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 109.73.172.144:43494's last block the delega te has seen is now 0004361c004527fceb33c4dfe9062a92a6421508 (actual block #275996) node.cpp:2511 ................... 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 188.138.122.20:60328's last block the delega te has seen is now 0004361a7b4321512a38bc112c8c8ecd84d3e59c (actual block #275994) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 188.165.233.53:1776's last block the delegat e has seen is now 0004361a7b4321512a38bc112c8c8ecd84d3e59c (actual block #275994) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 188.138.122.20:60328's last block the delega te has seen is now 0004361bd4f6fdf618a74290b09a8a018ab7867b (actual block #275995) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 188.165.233.53:1776's last block the delegat e has seen is now 0004361bd4f6fdf618a74290b09a8a018ab7867b (actual block #275995) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 188.138.122.20:60328's last block the delega te has seen is now 0004361c004527fceb33c4dfe9062a92a6421508 (actual block #275996) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] after removing all items we have already seen, item_hashes_received.size() = 1 node.cpp:2515 2015-09-28T20:08:43 p2p:message read_loop trigger_fetch_sync_i ] Triggering fetch sync items loop now node.cpp:1083 2015-09-28T20:08:43 p2p:fetch_sync_items_loop fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:1022 2015-09-28T20:08:43 p2p:fetch_sync_items_loop fetch_sync_items_loo ] no sync items to fetch right now, going to sleep node.cpp:1072 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 188.165.233.53:1776's last block the delegat e has seen is now 0004361c004527fceb33c4dfe9062a92a6421508 (actual block #275996) node.cpp:2511 ....................... 2015-09-28T20:08:43 p2p:fetch_sync_items_loop fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:1022 2015-09-28T20:08:43 p2p:fetch_sync_items_loop fetch_sync_items_loo ] no sync items to fetch right now, going to sleep node.cpp:1072 f>2015-09-28T20:08:43 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] Failed to push sync block 275997 (id:0004361d1c4d414512a8ae8e99ecf2026627d08e): client rejected sync block sent by peer: {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"vesting_balance_eval uator.cpp","line":103,"method":"do_evaluate","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"vbo.is_withdraw_allowed( now, op.amount ) : ","data":{"now":"2015-09-28T20:08:33","op":{"fee":{"amount":50000,"asset_id":"1.3.0"},"vesting_balance":"1.13.30","owner":"1.2.22404","amount":{"amount":"6400000000 ","asset_id":"1.3.0"}},"vbo":{"id":"1.13.30","owner":"1.2.22404","balance":{"amount":"6392481409","asset_id":"1.3.0"},"policy":[1,{"vesting_seconds":86400,"start_clai m":"1970-01-01T00:00:00","coin_seconds_earned":"552223993737600","coin_seconds_earned_last_update":"2015-09-28T20:07:51"}]}}},{"context":{"level":"warn","file":"vesti ng_balance_evaluator.cpp","line":109,"method":"do_evaluate","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"","data":{"op":{"fee":{"am ount":50000,"asset_id":"1.3.0"},"vesting_balance":"1.13.30","owner":"1.2.22404","amount":{"amount":"6400000000","asset_id":"1.3.0"}}}},{"context":{"level":"warn","fil e":"evaluator.cpp","line":42,"method":"start_evaluate","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"","data":{}},{"context":{"level ":"warn","file":"db_block.cpp","line":609,"method":"apply_operation","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"","data":{}},{"co ntext":{"level":"warn","file":"db_block.cpp","line":592,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":" ","data":{"trx":{"ref_block_num":13848,"ref_block_prefix":996090894,"expiration":"2015-09-28T20:08:54","operations":[[33,{"fee":{"amount":50000,"asset_id":"1.3.0"},"v esting_balance":"1.13.30","owner":"1.2.22404","amount":{"amount":"6400000000","asset_id":"1.3.0"}}]],"extensions":[],"signatures":["202c842047ea693db88068f8a5cb2e289d 372a8ab1226655695e7db2a2a427c7d41ff6887c12e5769aebc2e4e70953c17b95fd423b44ac03696cd413fd67c55aef"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":495,"met hod":"_apply_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"","data":{"next_block.block_num()":275996}},{"context":{"level":"w arn","file":"db_block.cpp","line":195,"method":"_push_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"","data":{"new_block":{"p revious":"0004361c004527fceb33c4dfe9062a92a6421508","timestamp":"2015-09-28T20:08:42","witness":"1.6.5248","transaction_merkle_root":"00000000000000000000000000000000 00000000","extensions":[],"witness_signature":"1f051e73526e48fd46a4359daaede6e5e5a8b6f451194c24caad9a1287506ef0cd026c0ecdadb5ea35b9843dc0bd68faee59053278a7ce6e571f838 a2d870bebc9","transactions":[]}}},{"context":{"level":"warn","file":"application.cpp","line":428,"method":"handle_block","hostname":"","thread_name":"th_a","timestamp ":"2015-09-28T20:08:43"},"format":"","data":{"blk_msg":{"block":{"previous":"0004361c004527fceb33c4dfe9062a92a6421508","timestamp":"2015-09-28T20:08:42","witness":"1. 6.5248","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f051e73526e48fd46a4359daaede6e5e5a8b6f451194c24caad 9a1287506ef0cd026c0ecdadb5ea35b9843dc0bd68faee59053278a7ce6e571f838a2d870bebc9","transactions":[]},"block_id":"0004361d1c4d414512a8ae8e99ecf2026627d08e"},"sync_mode": true}}]} node.cpp:2959 2015-09-28T20:08:43 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] disconnecting client 104.155.223.175:32832 because it offered us the rejected block node.cpp:3073 .................... 2015-09-28T20:08:56 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] Successfully pushed sync block 275997 (id:0004361d7bf5aecfd85eac9e45b1d1e84287a640) node.cpp:2935 ................... 2015-09-28T20:09:09 p2p:message read_loop process_block_during ] Successfully pushed block 275998 (id:0004361e9fceb5c9825c54df7adb585bc4976602) node.cpp:3254 .................... 2015-09-28T20:09:15 p2p:message read_loop process_block_during ] Successfully pushed block 275999 (id:0004361f189606417518259ba750f34aff126187) node.cpp:3254 ..................... ................. ............... b>2015-09-28T20:26:24 p2p:message read_loop process_block_during ] Successfully pushed block 276099 (id:000436831df20b58af1fda3d1439dd6c1423ec24) node.cpp:3254 ...............forked at block 275997.
from the log, it have received the correct block 275997:0004361d1c4d414512a8ae8e99ecf2026627d08e
but it denied it.
then switch to the wrong block: 0004361d7bf5aecfd85eac9e45b1d1e84287a640
Title: Re: Test Net for Advanced Users
Post by: alt on September 29, 2015, 12:17:26 am: maybe need to notice, before block 275997, already met a fork switch at block 275996, and it switch to the correct chain.

Quote from: alt on September 29, 2015, 12:09:45 am
here is a piece from the log when it forked:
Code: [Select]
2015-09-28T20:08:30 p2p:message read_loop process_block_during ] received a block from peer 216.252.204.69:54183, passing it to client node.cpp:3232 2015-09-28T20:08:30 p2p:message read_loop process_block_during ] Successfully pushed block 275994 (id:0004361a7b4321512a38bc112c8c8ecd84d3e59c) node.cpp:3254 .................... 2015-09-28T20:08:36 p2p:message read_loop process_block_during ] received a block from peer 114.92.254.159:62015, passing it to client node.cpp:3232 ......................... 2015-09-28T20:08:36 p2p:message read_loop process_block_during ] Failed to push block 275996 (id:0004361c004527fceb33c4dfe9062a92a6421508), client rejected block sent by peer node.cpp:3346 2015-09-28T20:08:36 p2p:message read_loop process_block_during ] disconnecting client 114.92.254.159:62015 because it offered us the rejected block node.cpp:3368 ............... 2015-09-28T20:08:37 p2p:message read_loop process_block_during ] received a block from peer 185.42.242.124:40060, passing it to client node.cpp:3232 2015-09-28T20:08:37 p2p:message read_loop process_block_during ] Failed to push block 275996 (id:0004361c004527fceb33c4dfe9062a92a6421508), client rejected block sent by peer node.cpp:3346 2015-09-28T20:08:37 p2p:message read_loop process_block_during ] disconnecting client 185.42.242.124:40060 because it offered us the rejected block node.cpp:3368 .............. 2015-09-28T20:08:39 p2p:message read_loop process_block_during ] received a block from peer 178.62.88.151:46944, passing it to client node.cpp:3232 2015-09-28T20:08:39 p2p:message read_loop process_block_during ] Successfully pushed block 275996 (id:0004361c4c4b8410260663693fd59b7ca1977b86) node.cpp:3254 2015-09-28T20:08:39 p2p:message read_loop process_block_during ] client validated the block, advertising it to other peers node.cpp:3278 .............. 2015-09-28T20:08:42 p2p:message read_loop process_block_during ] received a block from peer 178.62.88.151:46944, passing it to client node.cpp:3232 2015-09-28T20:08:42 p2p:message read_loop process_block_during ] Peer 178.62.88.151:46944 sent me a block that didn't link to our blockchain. Restarting sync mode wi th them to get the missing block. Error pushing block was: {"code":90006,"name":"unlinkable_block_exception","message":"unlinkable block","stack":[{"context":{"level" :"error","file":"application.cpp","line":417,"method":"handle_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:42"},"format":"Error when pushin g block:\n${e}","data":{"e":"3080000 unlinkable_block_exception: unlinkable block\nblock does not link to known chain\n {}\n th_a fork_database.cpp:79 _push_bl ock\n\n {\"new_block\":{\"previous\":\"0004361c004527fceb33c4dfe9062a92a6421508\",\"timestamp\":\"2015-09-28T20:08:42\",\"witness\":\"1.6.5248\",\"transaction_merk le_root\":\"0000000000000000000000000000000000000000\",\"extensions\":[],\"witness_signature\":\"1f051e73526e48fd46a4359daaede6e5e5a8b6f451194c24caad9a1287506ef0cd026 c0ecdadb5ea35b9843dc0bd68faee59053278a7ce6e571f838a2d870bebc9\",\"transactions\":[]}}\n th_a db_block.cpp:195 _push_block"}},{"context":{"level":"warn","file":"ap plication.cpp","line":428,"method":"handle_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:42"},"format":"","data":{"blk_msg":{"block":{"previ ous":"0004361c004527fceb33c4dfe9062a92a6421508","timestamp":"2015-09-28T20:08:42","witness":"1.6.5248","transaction_merkle_root":"000000000000000000000000000000000000 0000","extensions":[],"witness_signature":"1f051e73526e48fd46a4359daaede6e5e5a8b6f451194c24caad9a1287506ef0cd026c0ecdadb5ea35b9843dc0bd68faee59053278a7ce6e571f838a2d8 70bebc9","transactions":[]},"block_id":"0004361d1c4d414512a8ae8e99ecf2026627d08e"},"sync_mode":false}}]} node.cpp:3362 d>2015-09-28T20:08:42 p2p:message read_loop fetch_next_batch_of_ ] sync: sending a request for the next items after 0004361c4c4b8410260663693fd59b7ca1977b86 to peer 178 .62.88.151:46944, (full request is ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184c26912df003d6ac2","0004361a7b4321512a38bc112c8c8ecd84d3e59c"," 0004361c4c4b8410260663693fd59b7ca1977b86"]) node.cpp:2354 ............................ 2015-09-28T20:08:42 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 178.62.88.151:46944's last block the delegat e has seen is now 0004361a7b4321512a38bc112c8c8ecd84d3e59c (actual block #275994) node.cpp:2511 2015-09-28T20:08:42 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 178.62.88.151:46944's last block the delegat e has seen is now 0004361bd4f6fdf618a74290b09a8a018ab7867b (actual block #275995) node.cpp:2511 2015-09-28T20:08:42 p2p:message read_loop on_blockchain_item_i ] after removing all items we have already seen, item_hashes_received.size() = 2 node.cpp:2515 2015-09-28T20:08:42 p2p:message read_loop trigger_fetch_sync_i ] Triggering fetch sync items loop now node.cpp:1083 2015-09-28T20:08:42 p2p:fetch_sync_items_loop fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:1022 2015-09-28T20:08:42 p2p:fetch_sync_items_loop request_sync_items_f ] requesting 2 item(s) ["0004361c004527fceb33c4dfe9062a92a6421508","0004361d1c4d414512a8ae8e99ecf20 26627d08e"] from peer 178.62.88.151:46944 node.cpp:1006 2015-09-28T20:08:42 p2p:fetch_sync_items_loop fetch_sync_items_loo ] no sync items to fetch right now, going to sleep node.cpp:1072 2015-09-28T20:08:42 p2p:message read_loop on_message ] handling message fetch_blockchain_item_ids_message_type f9797929aee8529c183c2a43787da7a9b3d24e14 size 85 from peer 23.102.65.247:1984 node.cpp:1684 2015-09-28T20:08:42 p2p:message read_loop on_fetch_blockchain_ ] sync: received a request for item ids after 0004361c4c4b8410260663693fd59b7ca1977b86 from peer 23.102 .65.247:1984 (full request: ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184c26912df003d6ac2","0004361a7b4321512a38bc112c8c8ecd84d3e59c","0004361 c4c4b8410260663693fd59b7ca1977b86"]) node.cpp:2171 2015-09-28T20:08:42 p2p:message read_loop on_fetch_blockchain_ ] reply_message: {"total_remaining_item_count":0,"item_type":1001,"item_hashes_available":["0004361c4c4 b8410260663693fd59b7ca1977b86"]} fetch_blockchain_item_ids_message_received.blockchain_synopsis: ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184 c26912df003d6ac2","0004361a7b4321512a38bc112c8c8ecd84d3e59c","0004361c4c4b8410260663693fd59b7ca1977b86"] node.cpp:2194 2015-09-28T20:08:42 p2p:message read_loop on_fetch_blockchain_ ] sync: peer is already in sync with us node.cpp:2213 2015-09-28T20:08:43 p2p:message read_loop on_message ] handling message fetch_blockchain_item_ids_message_type f9797929aee8529c183c2a43787da7a9b3d24e14 size 85 from peer 207.46.141.218:1344 node.cpp:1684 2015-09-28T20:08:43 p2p:message read_loop on_fetch_blockchain_ ] sync: received a request for item ids after 0004361c4c4b8410260663693fd59b7ca1977b86 from peer 207.46 .141.218:1344 (full request: ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184c26912df003d6ac2","0004361a7b4321512a38bc112c8c8ecd84d3e59c","000436 1c4c4b8410260663693fd59b7ca1977b86"]) node.cpp:2171 2015-09-28T20:08:43 p2p:message read_loop on_fetch_blockchain_ ] reply_message: {"total_remaining_item_count":0,"item_type":1001,"item_hashes_available":["0004361c4c4 b8410260663693fd59b7ca1977b86"]} fetch_blockchain_item_ids_message_received.blockchain_synopsis: ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184 c26912df003d6ac2","0004361a7b4321512a38bc112c8c8ecd84d3e59c","0004361c4c4b8410260663693fd59b7ca1977b86"] node.cpp:2194 2015-09-28T20:08:43 p2p:message read_loop on_fetch_blockchain_ ] sync: peer is already in sync with us node.cpp:2213 2015-09-28T20:08:43 p2p:message read_loop on_message ] handling message block_message_type 1003c4eca3a31fd0e4933c919f37b072876911dc size 133 from peer 71.19 7.2.119:1776 node.cpp:1684 2015-09-28T20:08:43 p2p:message read_loop process_block_during ] received a block from peer 71.197.2.119:1776, passing it to client node.cpp:3232 2015-09-28T20:08:43 p2p:message read_loop process_block_during ] Peer 71.197.2.119:1776 sent me a block that didn't link to our blockchain. Restarting sync mode with them to get the missing block. Error pushing block was: {"code":90006,"name":"unlinkable_block_exception","message":"unlinkable block","stack":[{"context":{"level":" error","file":"application.cpp","line":417,"method":"handle_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"Error when pushing block:\n${e}","data":{"e":"3080000 unlinkable_block_exception: unlinkable block\nblock does not link to known chain\n {}\n th_a fork_database.cpp:79 _push_bloc k\n\n {\"new_block\":{\"previous\":\"0004361c004527fceb33c4dfe9062a92a6421508\",\"timestamp\":\"2015-09-28T20:08:42\",\"witness\":\"1.6.5248\",\"transaction_merkle _root\":\"0000000000000000000000000000000000000000\",\"extensions\":[],\"witness_signature\":\"1f051e73526e48fd46a4359daaede6e5e5a8b6f451194c24caad9a1287506ef0cd026c0 ecdadb5ea35b9843dc0bd68faee59053278a7ce6e571f838a2d870bebc9\",\"transactions\":[]}}\n th_a db_block.cpp:195 _push_block"}},{"context":{"level":"warn","file":"appl ication.cpp","line":428,"method":"handle_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"","data":{"blk_msg":{"block":{"previou s":"0004361c004527fceb33c4dfe9062a92a6421508","timestamp":"2015-09-28T20:08:42","witness":"1.6.5248","transaction_merkle_root":"00000000000000000000000000000000000000 00","extensions":[],"witness_signature":"1f051e73526e48fd46a4359daaede6e5e5a8b6f451194c24caad9a1287506ef0cd026c0ecdadb5ea35b9843dc0bd68faee59053278a7ce6e571f838a2d870 bebc9","transactions":[]},"block_id":"0004361d1c4d414512a8ae8e99ecf2026627d08e"},"sync_mode":false}}]} node.cpp:3362 2015-09-28T20:08:43 p2p:message read_loop fetch_next_batch_of_ ] sync: sending a request for the next items after 0004361c4c4b8410260663693fd59b7ca1977b86 to peer 71. 197.2.119:1776, (full request is ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184c26912df003d6ac2","0004361a7b4321512a38bc112c8c8ecd84d3e59c","00 04361c4c4b8410260663693fd59b7ca1977b86"]) node.cpp:2354 .............. 2015-09-28T20:08:43 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] Successfully pushed sync block 275996 (id:0004361c004527fceb33c4dfe9062a92a6421508) node.cpp:2935 .............. 2015-09-28T20:08:43 p2p:send_sync_block_to_node_delegate fetch_next_batch_of_ ] sync: sending a request for the next items after 0004361c4c4b8410260663693fd59b7ca1977 b86 to peer 71.197.2.119:61371, (full request is ["0004361158e0898268252af7afa90b1d59ffa354","0004361707141c5119a53184c26912df003d6ac2","0004361a7b4321512a38bc112c8c8 ecd84d3e59c","0004361c4c4b8410260663693fd59b7ca1977b86"]) node.cpp:2354 ............... 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 109.73.172.144:43494's last block the delega te has seen is now 0004361a7b4321512a38bc112c8c8ecd84d3e59c (actual block #275994) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 109.73.172.144:43494's last block the delega te has seen is now 0004361bd4f6fdf618a74290b09a8a018ab7867b (actual block #275995) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 109.73.172.144:43494's last block the delega te has seen is now 0004361c004527fceb33c4dfe9062a92a6421508 (actual block #275996) node.cpp:2511 ................... 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 188.138.122.20:60328's last block the delega te has seen is now 0004361a7b4321512a38bc112c8c8ecd84d3e59c (actual block #275994) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 188.165.233.53:1776's last block the delegat e has seen is now 0004361a7b4321512a38bc112c8c8ecd84d3e59c (actual block #275994) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 188.138.122.20:60328's last block the delega te has seen is now 0004361bd4f6fdf618a74290b09a8a018ab7867b (actual block #275995) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 188.165.233.53:1776's last block the delegat e has seen is now 0004361bd4f6fdf618a74290b09a8a018ab7867b (actual block #275995) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 188.138.122.20:60328's last block the delega te has seen is now 0004361c004527fceb33c4dfe9062a92a6421508 (actual block #275996) node.cpp:2511 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] after removing all items we have already seen, item_hashes_received.size() = 1 node.cpp:2515 2015-09-28T20:08:43 p2p:message read_loop trigger_fetch_sync_i ] Triggering fetch sync items loop now node.cpp:1083 2015-09-28T20:08:43 p2p:fetch_sync_items_loop fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:1022 2015-09-28T20:08:43 p2p:fetch_sync_items_loop fetch_sync_items_loo ] no sync items to fetch right now, going to sleep node.cpp:1072 2015-09-28T20:08:43 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 188.165.233.53:1776's last block the delegat e has seen is now 0004361c004527fceb33c4dfe9062a92a6421508 (actual block #275996) node.cpp:2511 ....................... 2015-09-28T20:08:43 p2p:fetch_sync_items_loop fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:1022 2015-09-28T20:08:43 p2p:fetch_sync_items_loop fetch_sync_items_loo ] no sync items to fetch right now, going to sleep node.cpp:1072 f>2015-09-28T20:08:43 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] Failed to push sync block 275997 (id:0004361d1c4d414512a8ae8e99ecf2026627d08e): client rejected sync block sent by peer: {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"vesting_balance_eval uator.cpp","line":103,"method":"do_evaluate","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"vbo.is_withdraw_allowed( now, op.amount ) : ","data":{"now":"2015-09-28T20:08:33","op":{"fee":{"amount":50000,"asset_id":"1.3.0"},"vesting_balance":"1.13.30","owner":"1.2.22404","amount":{"amount":"6400000000 ","asset_id":"1.3.0"}},"vbo":{"id":"1.13.30","owner":"1.2.22404","balance":{"amount":"6392481409","asset_id":"1.3.0"},"policy":[1,{"vesting_seconds":86400,"start_clai m":"1970-01-01T00:00:00","coin_seconds_earned":"552223993737600","coin_seconds_earned_last_update":"2015-09-28T20:07:51"}]}}},{"context":{"level":"warn","file":"vesti ng_balance_evaluator.cpp","line":109,"method":"do_evaluate","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"","data":{"op":{"fee":{"am ount":50000,"asset_id":"1.3.0"},"vesting_balance":"1.13.30","owner":"1.2.22404","amount":{"amount":"6400000000","asset_id":"1.3.0"}}}},{"context":{"level":"warn","fil e":"evaluator.cpp","line":42,"method":"start_evaluate","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"","data":{}},{"context":{"level ":"warn","file":"db_block.cpp","line":609,"method":"apply_operation","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"","data":{}},{"co ntext":{"level":"warn","file":"db_block.cpp","line":592,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":" ","data":{"trx":{"ref_block_num":13848,"ref_block_prefix":996090894,"expiration":"2015-09-28T20:08:54","operations":[[33,{"fee":{"amount":50000,"asset_id":"1.3.0"},"v esting_balance":"1.13.30","owner":"1.2.22404","amount":{"amount":"6400000000","asset_id":"1.3.0"}}]],"extensions":[],"signatures":["202c842047ea693db88068f8a5cb2e289d 372a8ab1226655695e7db2a2a427c7d41ff6887c12e5769aebc2e4e70953c17b95fd423b44ac03696cd413fd67c55aef"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":495,"met hod":"_apply_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"","data":{"next_block.block_num()":275996}},{"context":{"level":"w arn","file":"db_block.cpp","line":195,"method":"_push_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T20:08:43"},"format":"","data":{"new_block":{"p revious":"0004361c004527fceb33c4dfe9062a92a6421508","timestamp":"2015-09-28T20:08:42","witness":"1.6.5248","transaction_merkle_root":"00000000000000000000000000000000 00000000","extensions":[],"witness_signature":"1f051e73526e48fd46a4359daaede6e5e5a8b6f451194c24caad9a1287506ef0cd026c0ecdadb5ea35b9843dc0bd68faee59053278a7ce6e571f838 a2d870bebc9","transactions":[]}}},{"context":{"level":"warn","file":"application.cpp","line":428,"method":"handle_block","hostname":"","thread_name":"th_a","timestamp ":"2015-09-28T20:08:43"},"format":"","data":{"blk_msg":{"block":{"previous":"0004361c004527fceb33c4dfe9062a92a6421508","timestamp":"2015-09-28T20:08:42","witness":"1. 6.5248","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f051e73526e48fd46a4359daaede6e5e5a8b6f451194c24caad 9a1287506ef0cd026c0ecdadb5ea35b9843dc0bd68faee59053278a7ce6e571f838a2d870bebc9","transactions":[]},"block_id":"0004361d1c4d414512a8ae8e99ecf2026627d08e"},"sync_mode": true}}]} node.cpp:2959 2015-09-28T20:08:43 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] disconnecting client 104.155.223.175:32832 because it offered us the rejected block node.cpp:3073 .................... 2015-09-28T20:08:56 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] Successfully pushed sync block 275997 (id:0004361d7bf5aecfd85eac9e45b1d1e84287a640) node.cpp:2935 ................... 2015-09-28T20:09:09 p2p:message read_loop process_block_during ] Successfully pushed block 275998 (id:0004361e9fceb5c9825c54df7adb585bc4976602) node.cpp:3254 .................... 2015-09-28T20:09:15 p2p:message read_loop process_block_during ] Successfully pushed block 275999 (id:0004361f189606417518259ba750f34aff126187) node.cpp:3254 ..................... ................. ............... b>2015-09-28T20:26:24 p2p:message read_loop process_block_during ] Successfully pushed block 276099 (id:000436831df20b58af1fda3d1439dd6c1423ec24) node.cpp:3254 ...............forked at block 275997.
from the log, it have received the correct block 275997:0004361d1c4d414512a8ae8e99ecf2026627d08e
but it denied it.
then switch to the wrong block: 0004361d7bf5aecfd85eac9e45b1d1e84287a640
Title: Re: Test Net for Advanced Users
Post by: clayop on September 29, 2015, 12:19:29 am: Quote from: clayop on September 28, 2015, 11:27:57 pm
I will flood the testnet at 9/29 0:10 UTC with 101 VPSs.

I changed some parameter and will do it again at 0:40 UTC
Title: Re: Test Net for Advanced Users
Post by: clayop on September 29, 2015, 01:24:34 am: During the spam, I can observe a high latency

Code: [Select]
1410962ms th_a application.cpp:388 handle_block ] Got block #281678 with time 2015-09-29T01:23:27 from network with latency of 3975 ms from spartako
Title: Re: Test Net for Advanced Users
Post by: abit on September 29, 2015, 01:26:32 am: Here are some of the tons of errors found in p2p.logs while spamming.

At first:
Code: [Select]
2015-09-28T07:02:09 p2p:message read_loop process_ordinary_mes ] client rejected message sent by peer 127.0.0.1:62015, {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":534,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:02:09"}, "format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":592,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:02:09"},"format":"","data":{"trx":{"ref_block_num":65467,"ref_block_prefix":2922805723,"expiration":"2015-09-28T07:02:48","operations":[[1,{"fee":{"amount":250000,"asset_id":"1.3.0"},"seller":"1.2.17357","amount_to_sell":{"amount":1,"asset_id":"1.3.664"},"min_to_receive":{"amount":100000,"asset_id":"1.3.0"},"expiration":"2015-09-28T07:03:43","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["1f17bdb09411ca7eeaf6c7e28b81222ae240c68dddd71d4ce6a68049c38b9429420e5ab73e01ca705fa52ced97a1b723069eac4c8fb3683df09ae6e168d8ce5a87"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":214,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:02:09"},"format":"","data":{"trx":{"ref_block_num":65467,"ref_block_prefix":2922805723,"expiration":"2015-09-28T07:02:48","operations":[[1,{"fee":{"amount":250000,"asset_id":"1.3.0"},"seller":"1.2.17357","amount_to_sell":{"amount":1,"asset_id":"1.3.664"},"min_to_receive":{"amount":100000,"asset_id":"1.3.0"},"expiration":"2015-09-28T07:03:43","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["1f17bdb09411ca7eeaf6c7e28b81222ae240c68dddd71d4ce6a68049c38b9429420e5ab73e01ca705fa52ced97a1b723069eac4c8fb3683df09ae6e168d8ce5a87"]}}},{"context":{"level":"warn","file":"application.cpp","line":434,"method":"handle_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:02:09"},"format":"","data":{"transaction_message":{"trx":{"ref_block_num":65467,"ref_block_prefix":2922805723,"expiration":"2015-09-28T07:02:48","operations":[[1,{"fee":{"amount":250000,"asset_id":"1.3.0"},"seller":"1.2.17357","amount_to_sell":{"amount":1,"asset_id":"1.3.664"},"min_to_receive":{"amount":100000,"asset_id":"1.3.0"},"expiration":"2015-09-28T07:03:43","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["1f17bdb09411ca7eeaf6c7e28b81222ae240c68dddd71d4ce6a68049c38b9429420e5ab73e01ca705fa52ced97a1b723069eac4c8fb3683df09ae6e168d8ce5a87"]}}}}]} node.cpp:3759
Code: [Select]
2015-09-28T07:03:13 p2p:message read_loop process_ordinary_mes ] client rejected message sent by peer 104.236.11.171:48991, {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":562,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:03:13"}, "format":"now <= trx.expiration: ","data":{"now":"2015-09-28T07:03:09","trx.exp":"2015-09-28T07:03:00"}},{"context":{"level":"warn","file":"db_block.cpp","line":592,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:03:13"},"format":"","data":{"trx":{"ref_block_num":65475,"ref_block_prefix":3967048843,"expiration":"2015-09-28T07:03:00","operations":[[1,{"fee":{"amount":250000,"asset_id":"1.3.0"},"seller":"1.2.17357","amount_to_sell":{"amount":1,"asset_id":"1.3.664"},"min_to_receive":{"amount":100000,"asset_id":"1.3.0"},"expiration":"2015-09-28T07:04:19","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["1f51cc04c73f2236caa7da4ce80eb8134b5065c632fae74f8f16e839a819f511822a5d375a3457be4fe8028686b6766bcd7c3d77fce19ef35c609c0a15f80fb76f"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":214,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:03:13"},"format":"","data":{"trx":{"ref_block_num":65475,"ref_block_prefix":3967048843,"expiration":"2015-09-28T07:03:00","operations":[[1,{"fee":{"amount":250000,"asset_id":"1.3.0"},"seller":"1.2.17357","amount_to_sell":{"amount":1,"asset_id":"1.3.664"},"min_to_receive":{"amount":100000,"asset_id":"1.3.0"},"expiration":"2015-09-28T07:04:19","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["1f51cc04c73f2236caa7da4ce80eb8134b5065c632fae74f8f16e839a819f511822a5d375a3457be4fe8028686b6766bcd7c3d77fce19ef35c609c0a15f80fb76f"]}}},{"context":{"level":"warn","file":"application.cpp","line":434,"method":"handle_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:03:13"},"format":"","data":{"transaction_message":{"trx":{"ref_block_num":65475,"ref_block_prefix":3967048843,"expiration":"2015-09-28T07:03:00","operations":[[1,{"fee":{"amount":250000,"asset_id":"1.3.0"},"seller":"1.2.17357","amount_to_sell":{"amount":1,"asset_id":"1.3.664"},"min_to_receive":{"amount":100000,"asset_id":"1.3.0"},"expiration":"2015-09-28T07:04:19","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["1f51cc04c73f2236caa7da4ce80eb8134b5065c632fae74f8f16e839a819f511822a5d375a3457be4fe8028686b6766bcd7c3d77fce19ef35c609c0a15f80fb76f"]}}}}]} node.cpp:3759
Code: [Select]
2015-09-28T07:04:23 p2p:message read_loop process_ordinary_mes ] client rejected message sent by peer 127.0.0.1:62015, {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":555,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:04:23"}, "format":"trx.ref_block_prefix == tapos_block_summary.block_id._hash[1]: ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":592,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:04:23"},"format":"","data":{"trx":{"ref_block_num":65498,"ref_block_prefix":3583879970,"expiration":"2015-09-28T07:04:43","operations":[[1,{"fee":{"amount":250000,"asset_id":"1.3.0"},"seller":"1.2.17357","amount_to_sell":{"amount":1,"asset_id":"1.3.664"},"min_to_receive":{"amount":100000,"asset_id":"1.3.0"},"expiration":"2015-09-28T07:05:58","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["20332b3cbc6e337b00ae7b5ebc2e4cf2903fdbd4046558fb51496aee33e45ece6032386c5b3979c85ff1035e6561bb823198fb47f52e2dec224ba48452dd572c53"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":214,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:04:23"},"format":"","data":{"trx":{"ref_block_num":65498,"ref_block_prefix":3583879970,"expiration":"2015-09-28T07:04:43","operations":[[1,{"fee":{"amount":250000,"asset_id":"1.3.0"},"seller":"1.2.17357","amount_to_sell":{"amount":1,"asset_id":"1.3.664"},"min_to_receive":{"amount":100000,"asset_id":"1.3.0"},"expiration":"2015-09-28T07:05:58","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["20332b3cbc6e337b00ae7b5ebc2e4cf2903fdbd4046558fb51496aee33e45ece6032386c5b3979c85ff1035e6561bb823198fb47f52e2dec224ba48452dd572c53"]}}},{"context":{"level":"warn","file":"application.cpp","line":434,"method":"handle_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:04:23"},"format":"","data":{"transaction_message":{"trx":{"ref_block_num":65498,"ref_block_prefix":3583879970,"expiration":"2015-09-28T07:04:43","operations":[[1,{"fee":{"amount":250000,"asset_id":"1.3.0"},"seller":"1.2.17357","amount_to_sell":{"amount":1,"asset_id":"1.3.664"},"min_to_receive":{"amount":100000,"asset_id":"1.3.0"},"expiration":"2015-09-28T07:05:58","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["20332b3cbc6e337b00ae7b5ebc2e4cf2903fdbd4046558fb51496aee33e45ece6032386c5b3979c85ff1035e6561bb823198fb47f52e2dec224ba48452dd572c53"]}}}}]} node.cpp:3759
My witness node got out of sync here after some seconds.

Later:
Code: [Select]
2015-09-28T07:22:20 p2p:send_sync_block_to_node_delegate send_sync_block_to_n ] Failed to push sync block 262132 (id:0003fff4f020495812404736ce0e866d4801c01b): client rejected sync block sent by peer: {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":613,"method":"validate_block_header","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:22:20"}, "format":"head_block_id() == next_block.previous: ","data":{"head_block_id":"0003fff3004e3e0a5eed50770023bf74e4c246f1","next.prev":"0003fff36a9b0c61dd3922f19fe1f4a040ff1ae2"}},{"context":{"level":"warn","file":"db_block.cpp","line":495,"method":"_apply_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:22:20"},"format":"","data":{"next_block.block_num()":262132}},{"context":{"level":"warn","file":"db_block.cpp","line":195,"method":"_push_block","hostname":"","thread_name":"th_a","timestamp":"2015-09-28T07:22:20"},"format":"","data":{"new_block":{"previous":"0003fff36a9b0c61dd3922f19fe1f4a040ff1ae2","timestamp":"2015-09-28T07:06:12","witness":"1.6.2","transaction_merkle_root":"93a42a8d8c1db93d55ce90defea956544834b5e0","extensions":[],"witness_signature":"20045fae9169b63f0d2f764cfbacf9be2ab7d7044192158b6cf9eca676079b3e302c0f04fa6dd99913c3ef53f7f8423d9809932d3457747dd96fcf920cc920ebbf","transactions":[.....]}
Title: Re: Test Net for Advanced Users
Post by: abit on September 29, 2015, 01:34:22 am: Quote from: clayop on September 29, 2015, 01:24:34 am
During the spam, I can observe a high latency

Code: [Select]
1410962ms th_a application.cpp:388 handle_block ] Got block #281678 with time 2015-09-29T01:23:27 from network with latency of 3975 ms from spartako
My block producing node is dead.
Observer node's CPU is 100% but alive.
Title: Re: Test Net for Advanced Users
Post by: abit on September 29, 2015, 01:39:15 am: Quote from: alt on September 28, 2015, 11:19:26 pm
forked, have to resync.
can we add the block number for parameter --resync-blockchain?
so we only need to resync from the given block number.
Make a backup of the blockchain directory when you're in sync.
After forked, restore with the backup.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 29, 2015, 01:44:31 am: (http://imgur.com/zlLShUA.png)
Title: Re: Test Net for Advanced Users
Post by: abit on September 29, 2015, 02:00:32 am: It took 75 seconds to replay the 280k-blocks chain.
Title: Re: Test Net for Advanced Users
Post by: cube on September 29, 2015, 03:32:07 am: My witness node passed through the spam with 20 missed blocks. So far it has managed to survive all the spam attempts with about 20 missed blocks.
Title: Re: Test Net for Advanced Users
Post by: Fox on September 29, 2015, 04:08:21 am: Quote from: onceuponatime on September 28, 2015, 11:51:22 pm
Quote from: clayop on September 28, 2015, 11:27:57 pm
I will flood the testnet at 9/29 0:10 UTC with 101 VPSs. Tips for VPS costs are more than welcome. ;)

BTS ID: clayop

Due to the limit of numbers per region, I can only manage about 60 VPSs.

Sent you 500BTS for to help with your costs ;D

Matching funds sent.

I will match up to 50,000 BTS thru 23:59 UTC 29 SEP 2015 to support Clayop with his VPS needs. Please do not spam this thread.

Please PM me your Transaction ID and I will match it.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 29, 2015, 04:20:25 am: Quote from: Fox on September 29, 2015, 04:08:21 am
Quote from: onceuponatime on September 28, 2015, 11:51:22 pm
Quote from: clayop on September 28, 2015, 11:27:57 pm
I will flood the testnet at 9/29 0:10 UTC with 101 VPSs. Tips for VPS costs are more than welcome. ;)

BTS ID: clayop

Due to the limit of numbers per region, I can only manage about 60 VPSs.

Sent you 500BTS for to help with your costs ;D

Matching funds sent.

I will match up to 50,000 BTS thru 23:59 UTC 29 SEP 2015 to support Clayop with his VPS needs. Please do not spam this thread.

Please PM me your Transaction ID and I will match it.

Thank you fox! Fund received.
Title: Re: Test Net for Advanced Users
Post by: alt on September 29, 2015, 06:43:16 am: I think it's more reasonable to copy those blocks which is not fork from the database directoly than resync from the network.

Quote from: abit on September 29, 2015, 01:39:15 am
Quote from: alt on September 28, 2015, 11:19:26 pm
forked, have to resync.
can we add the block number for parameter --resync-blockchain?
so we only need to resync from the given block number.
Make a backup of the blockchain directory when you're in sync.
After forked, restore with the backup.
Title: Re: Test Net for Advanced Users
Post by: mindphlux on September 29, 2015, 07:41:59 am: I'm thinking of writing a functional test for the UI frontend. One that makes sure that every function still works as designed after modyfing/adding a new feature.

For example, also market order creation could be automated, including a stress test of market orders on multiple instances of the functional test.

Can you please give me examples of other items that are worth testing, UI-wise and network wise? It will automatically report when something doesn't work as expected, and it can be also be integrated into jenkins if that is used yet.

I tried using phantomjs, but it does not support IndexedDB, so I'll use selenium and chrome as a real browser.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 29, 2015, 12:55:18 pm: Quote from: abit on September 29, 2015, 02:00:32 am
It took 75 seconds to replay the 280k-blocks chain.

Maybe on a SLOW vps, but on my machine it takes a mere 11 seconds.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 29, 2015, 02:46:26 pm: Quote from: bytemaster on September 29, 2015, 12:55:18 pm
Quote from: abit on September 29, 2015, 02:00:32 am
It took 75 seconds to replay the 280k-blocks chain.

Maybe on a SLOW vps, but on my machine it takes a mere 11 8.79 seconds.

In Debug build it took me 59 seconds to reindex.
In Release build it took me 8.79 seconds to reindex.

There were a total of 444758 operations in the blockchain which means we are averaging over 50K TPS.
The average maintenance calculation time is: 7 ms
1.5 seconds were spent doing maintenance calculations (on the hour, instead of every day) leaving us at 62K TPS average
The vast majority of blocks have been empty which means our TPS average is being diluted by block processing overhead.

It looks like in Debug mode we process closer to 10K TPS.
Title: Re: Test Net for Advanced Users
Post by: emailtooaj on September 29, 2015, 03:07:46 pm: @clayop just sent u some bts for VPS donation
Title: Re: Test Net for Advanced Users
Post by: clayop on September 29, 2015, 04:05:36 pm: Quote from: emailtooaj on September 29, 2015, 03:07:46 pm
@clayop just sent u some bts for VPS donation
Thanks my friend!
Title: Re: Test Net for Advanced Users
Post by: emailtooaj on September 29, 2015, 04:53:53 pm: Quote from: clayop on September 29, 2015, 04:05:36 pm
Quote from: emailtooaj on September 29, 2015, 03:07:46 pm
@clayop just sent u some bts for VPS donation
Thanks my friend!
Np. Thanks for helping. I'll send u some more in next day or two
Title: Re: Test Net for Advanced Users
Post by: theoretical on September 29, 2015, 07:34:01 pm: You may have recently noticed a 20% decrease in fees, and witness pay being lowered to 5 BTS per block. This is our testing of the parameter change functionality described at https://bitshares.org/technology/delegated-proof-of-stake-consensus/#parameter-changes-by-elected-delegates (https://bitshares.org/technology/delegated-proof-of-stake-consensus/#parameter-changes-by-elected-delegates)

Unfortunately the witness pay change was inadvertently reverted due to certain technicalities of how proposals work, but I re-applied it in another proposal which will take effect fairly soon. So here are the new parameters:

Code: [Select]
propose_parameter_change init2 "2015-09-29T19:45:00" { "maintenance_skip_slots": 4, "maintenance_interval" : 1800, "maximum_transaction_size": 65536, "cashback_vesting_period_seconds": 7776000, "witness_pay_per_block": 500000, "committee_proposal_review_period" : 300 } true approve_proposal init2 1.10.4 {"active_approvals_to_add" : ["init2", "init3", "init4", "init5", "init6", "init7", "init8", "init9", "init10"]} true get_block 299579 get_block 299596
As you might guess from these commands, the change will take effect at (the next maintenance interval after) 19:45:00 UTC today (2015-09-29).

In the live network, changes to parameters will require approval of committee members elected by the community and require a two-week waiting period during which no new approvals can be added. To better enable us to test the system, we turned the waiting period way down for the testnet (and this parameter change will lower it even further to 300 seconds), and voted the init witnesses as committee members.

We've also traced why the total witness budget wasn't a round number. Due to the lower block interval and extra CORE balances we added to the testnet genesis, the requested witness pay was being capped by the hard-coded limit on the rate of creating CORE. As stated in https://bitshares.org/technology/stakeholder-approved-project-funding/ (https://bitshares.org/technology/stakeholder-approved-project-funding/) the maximum rate at which CORE can be created to pay witnesses / workers is approximately 5 BTS per second (the actual number is reserve * 17 / 2^32). But there are 500M+ extra test CORE in the testnet genesis which will not exist in the real genesis, and this depleted the reserve down to about 3 BTS per second -- so witness funding at 10 BTS every 3 seconds was a little over the limit.

I don't know if we'll have the GUI for creating and inspecting parameters and proposals ready for the launch. But this test proves the blockchain and command line interface for it is working, so if the community has a desire to change parameters soon after the launch, it should be possible for the committee members elected by the community to enact any desired changes.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 29, 2015, 09:58:58 pm: New code has been checked in to improve propagation of transactions during flooding by requesting multiple transactions at once.

All nodes will have to upgrade to get the full benefit so please post once you have upgraded. Once enough nodes have updated then we can try the flooding tests again.

https://github.com/cryptonomex/graphene/commit/74bbde785b3d9c492007aced389df597b16cf124
Title: Re: Test Net for Advanced Users
Post by: clayop on September 29, 2015, 10:50:21 pm: delegate-clayop updated
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 29, 2015, 10:57:51 pm: First try crashed. Second is replaying blockchain but seems OK.

Code: [Select]
riverhead@dedi3890:~/github/graphene/programs/witness_node$ ./witness_node --rpc-endpoint "127.0.0.1:8090" -d test_net_3 -s "104.236.118.105:1776" --genesis-json sep-18-testnet-genesis.json 3284321ms th_a witness.cpp:83 plugin_initialize ] witness plugin: plugin_initialize() begin 3284321ms th_a witness.cpp:93 plugin_initialize ] key_id_to_wif_pair: ["G-------","5-------"] 3284321ms th_a witness.cpp:111 plugin_initialize ] witness plugin: plugin_initialize() end 3284321ms th_a db_management.cpp:131 open ] Old database version detected, reindex is required 3284321ms th_a db_management.cpp:98 wipe ] Wiping database 3284328ms th_a object_database.cpp:81 wipe ] Wiping object_database. 3284375ms th_a application.cpp:242 operator() ] Initializing database... 3320089ms th_a db_management.cpp:147 open ] last_block->id(): 0004a4f61b6d4898f6311bae5fb8a960ffc0a3de last_block->block_num(): 304374 3320120ms th_a thread.cpp:95 thread ] name:ntp tid:140230048286464 3320122ms th_a thread.cpp:95 thread ] name:p2p tid:140230029403904 3320127ms th_a application.cpp:122 reset_p2p_node ] Adding seed node 104.236.118.105:1776 3320128ms th_a application.cpp:134 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:51599 3320129ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 646 us 3320130ms th_a application.cpp:184 reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090 3320130ms th_a witness.cpp:116 plugin_startup ] witness plugin: plugin_startup() begin 3320130ms th_a witness.cpp:123 plugin_startup ] Launching block production for 1 witnesses. 3320130ms th_a witness.cpp:134 plugin_startup ] witness plugin: plugin_startup() end 3320130ms th_a main.cpp:167 main ] Started witness node on a chain with 0 blocks. 3320130ms th_a main.cpp:168 main ] Chain ID is 0f8b631d7a9dfebf16d6776fab96b629a14429762bf9c3eb95db1e4e4af637a4 3321000ms th_a witness.cpp:179 block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production) witness_node: /home/riverhead/github/graphene/libraries/chain/block_database.cpp:128: graphene::chain::block_id_type graphene::chain::block_database::fetch_block_id(uint32_t) const: Assertion `block_num != 0' failed. Aborted riverhead@dedi3890:~/github/graphene/programs/witness_node$
Blocks are producing again. Updated.
Title: Re: Test Net for Advanced Users
Post by: alt on September 29, 2015, 11:30:40 pm: delegate.baozi updated
And I got the same problem as you.
Quote from: Riverhead on September 29, 2015, 10:57:51 pm

First try crashed. Second is replaying blockchain but seems OK.

Code: [Select]
riverhead@dedi3890:~/github/graphene/programs/witness_node$ ./witness_node --rpc-endpoint "127.0.0.1:8090" -d test_net_3 -s "104.236.118.105:1776" --genesis-json sep-18-testnet-genesis.json 3284321ms th_a witness.cpp:83 plugin_initialize ] witness plugin: plugin_initialize() begin 3284321ms th_a witness.cpp:93 plugin_initialize ] key_id_to_wif_pair: ["G-------","5-------"] 3284321ms th_a witness.cpp:111 plugin_initialize ] witness plugin: plugin_initialize() end 3284321ms th_a db_management.cpp:131 open ] Old database version detected, reindex is required 3284321ms th_a db_management.cpp:98 wipe ] Wiping database 3284328ms th_a object_database.cpp:81 wipe ] Wiping object_database. 3284375ms th_a application.cpp:242 operator() ] Initializing database... 3320089ms th_a db_management.cpp:147 open ] last_block->id(): 0004a4f61b6d4898f6311bae5fb8a960ffc0a3de last_block->block_num(): 304374 3320120ms th_a thread.cpp:95 thread ] name:ntp tid:140230048286464 3320122ms th_a thread.cpp:95 thread ] name:p2p tid:140230029403904 3320127ms th_a application.cpp:122 reset_p2p_node ] Adding seed node 104.236.118.105:1776 3320128ms th_a application.cpp:134 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:51599 3320129ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 646 us 3320130ms th_a application.cpp:184 reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090 3320130ms th_a witness.cpp:116 plugin_startup ] witness plugin: plugin_startup() begin 3320130ms th_a witness.cpp:123 plugin_startup ] Launching block production for 1 witnesses. 3320130ms th_a witness.cpp:134 plugin_startup ] witness plugin: plugin_startup() end 3320130ms th_a main.cpp:167 main ] Started witness node on a chain with 0 blocks. 3320130ms th_a main.cpp:168 main ] Chain ID is 0f8b631d7a9dfebf16d6776fab96b629a14429762bf9c3eb95db1e4e4af637a4 3321000ms th_a witness.cpp:179 block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production) witness_node: /home/riverhead/github/graphene/libraries/chain/block_database.cpp:128: graphene::chain::block_id_type graphene::chain::block_database::fetch_block_id(uint32_t) const: Assertion `block_num != 0' failed. Aborted riverhead@dedi3890:~/github/graphene/programs/witness_node$
Blocks are producing again. Updated.
Title: Re: Test Net for Advanced Users
Post by: alt on September 29, 2015, 11:45:09 pm: here is the bt
Code: [Select]
(gdb) bt #0 0x00007ffff6b88cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007ffff6b8c0d8 in __GI_abort () at abort.c:89 #2 0x00007ffff6b81b86 in __assert_fail_base (fmt=0x7ffff6cd2830 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x2cf35f4 "block_num != 0", file=file@entry=0x2cf3518 "/home/alt/workspace/dac/graphene/libraries/chain/block_database.cpp", line=line@entry=128, function=function@entry=0x2cf4e00 <graphene::chain::block_database::fetch_block_id(unsigned int) const::__PRETTY_FUNCTION__> "graphene::chain::block_id_type graphene::chain::block_database::fetch_block_id(uint32_t) const") at assert.c:92 #3 0x00007ffff6b81c32 in __GI___assert_fail (assertion=0x2cf35f4 "block_num != 0", file=0x2cf3518 "/home/alt/workspace/dac/graphene/libraries/chain/block_database.cpp", line=128, function=0x2cf4e00 <graphene::chain::block_database::fetch_block_id(unsigned int) const::__PRETTY_FUNCTION__> "graphene::chain::block_id_type graphene::chain::block_database::fetch_block_id(uint32_t) const") at assert.c:101 #4 0x00000000026eeaa2 in graphene::chain::block_database::fetch_block_id (this=0x34fe120, block_num=0) at /home/alt/workspace/dac/graphene/libraries/chain/block_database.cpp:128 #5 0x00000000024356dd in graphene::chain::database::get_block_id_for_num (this=0x34fde60, block_num=0) at /home/alt/workspace/dac/graphene/libraries/chain/db_block.cpp:50 #6 0x00000000020b5798 in graphene::app::detail::application_impl::get_blockchain_synopsis (this=0x34fdd30, reference_point=..., number_of_blocks_after_reference_point=0) at /home/alt/workspace/dac/graphene/libraries/app/application.cpp:692 #7 0x00000000029754fb in graphene::net::detail::statistics_gathering_node_delegate_wrapper::<lambda()>::operator()(void) const (__closure=0x7fffdc0660a8) at /home/alt/workspace/dac/graphene/libraries/net/node.cpp:5394 #8 0x0000000002986118 in fc::detail::functor_run<graphene::net::detail::statistics_gathering_node_delegate_wrapper::get_blockchain_synopsis(const item_hash_t&, uint32_t)::<lambda()> >::run(void *, void *) (functor=0x7fffdc0660a8, prom=0x7fffdc066190) at /home/alt/workspace/dac/graphene/libraries/fc/include/fc/thread/task.hpp:77 #9 0x000000000274ae45 in fc::task_base::run_impl (this=0x7fffdc0660c8) at /home/alt/workspace/dac/graphene/libraries/fc/src/thread/task.cpp:43 #10 0x000000000274add6 in fc::task_base::run (this=0x7fffdc0660c8) at /home/alt/workspace/dac/graphene/libraries/fc/src/thread/task.cpp:32 #11 0x000000000273ec50 in fc::thread_d::run_next_task (this=0x3538ff0) at /home/alt/workspace/dac/graphene/libraries/fc/src/thread/thread_d.hpp:498 #12 0x000000000273f0f4 in fc::thread_d::process_tasks (this=0x3538ff0) at /home/alt/workspace/dac/graphene/libraries/fc/src/thread/thread_d.hpp:547 #13 0x000000000273e765 in fc::thread_d::start_process_tasks (my=55807984) at /home/alt/workspace/dac/graphene/libraries/fc/src/thread/thread_d.hpp:475 #14 0x0000000002aa7351 in make_fcontext () #15 0x0000000000000000 in ?? ()
Title: Re: Test Net for Advanced Users
Post by: maqifrnswa on September 30, 2015, 12:11:48 am: maqifrnswa upgraded
PPA upgraded
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 30, 2015, 12:14:48 am: xeldal updated
Title: Re: Test Net for Advanced Users
Post by: puppies on September 30, 2015, 12:32:00 am: dele-puppy is updated
Title: Re: Test Net for Advanced Users
Post by: cube on September 30, 2015, 01:52:19 am: bitcube is updated to latest master.
Title: Re: Test Net for Advanced Users
Post by: Fox on September 30, 2015, 02:53:45 am: Special thanks to the five (5) community members taking part in the fund matching offer to support Clayop's efforts with spamming the network from a global VPS entourage. These individuals combined to contribute 9500 BTS. I kicked in an extra 500 BTS extra, making it a 5-digit match.

Again, thanks to the community and Clayop.

Best,
Fox
Title: Re: Test Net for Advanced Users
Post by: Fox on September 30, 2015, 04:17:32 am: All nodes are now up to date with master.

FYI - I did encounter unclean database shutdown detected >> resync blockchain on about 1/3 of the nodes. All were previously the prior day's build.
Title: Re: Test Net for Advanced Users
Post by: roadscape on September 30, 2015, 04:38:35 am: roadscape (1.6.5249) is up to date but I need more votes!
Title: Re: Test Net for Advanced Users
Post by: clayop on September 30, 2015, 05:55:59 am: Quote from: Fox on September 30, 2015, 02:53:45 am
Special thanks to the five (5) community members taking part in the fund matching offer to support Clayop's efforts with spamming the network from a global VPS entourage. These individuals combined to contribute 9500 BTS. I kicked in an extra 500 BTS extra, making it a 5-digit match.

Again, thanks to the community and Clayop.

Best,
Fox

Many thanks to all community members with invaluable support for BitShares.
Title: Re: Test Net for Advanced Users
Post by: clayop on September 30, 2015, 06:00:28 am: I tested new network code with preliminary spam transactions, say 1500 txs. The network processed all the transactions very successfully.

I will run the third stress test tomorrow at around 0:00 UTC (the schedule is subject to be changed with further announcement)

All testnet witnesses, please update your witness node before then.

Add: a drill will take place in 20 min (23:45 PST) for 3 min.
Title: Re: Test Net for Advanced Users
Post by: spartako on September 30, 2015, 08:00:04 am: I wake up this morning and my witness for all night was not able to sync the correct fork.
I have a while [ True ] in my bash script so if it crash, it start again but every times gives me this error and started again to try to resync (without success):

Code: [Select]
93.3428% 284000 of 304255 1818515ms th_a undo_database.hpp:62 ~session ] 10 assert_exception: Assert Exception !_disabled: {} th_a undo_database.cpp:88 undo {} th_a undo_database.cpp:116 undo terminate called after throwing an instance of 'fc::assert_exception' Aborted (core dumped)
Now the witness if updated to the new master.
Title: Re: Test Net for Advanced Users
Post by: spartako on September 30, 2015, 08:40:42 am: I am no more able to run my witness, every time I get this error:

Code: [Select]
witness_node: /home/spartako/graphene/libraries/chain/db_market.cpp:290: bool graphene::chain::database::fill_order(const graphene::chain::call_order_object&, const graphene::chain::asset&, const graphene::chain::asset&): Assertion `order.get_collateral() >= pays' failed. Aborted (core dumped)
Also https://graphene.bitshares.org/ seems down
Title: Re: Test Net for Advanced Users
Post by: clayop on September 30, 2015, 08:49:56 am: It seems that the network has some serious problem. My cli_client says that the head block age is 30 min old.
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on September 30, 2015, 09:22:14 am: calabiyau updated
Code: [Select]
witness_node: /home/calabiyau/graphene/libraries/chain/db_market.cpp:290: bool graphene::chain::database::fill_order(const graphene::chain::call_order_object&, const graphene::chain::asset&, const graphene::chain::asset&): Assertion `order.get_collateral() >= pays' failed. Aborted (core dumped)
seems to sync now after rm blockchain again

uumm - no:
Code: [Select]
witness_node: /home/calabiyau/graphene/libraries/chain/db_market.cpp:290: bool graphene::chain::database::fill_order(const graphene::chain::call_order_object&, const graphene::chain::asset&, const graphene::chain::asset&): Assertion `order.get_collateral() >= pays' failed. Aborted (core dumped)
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 30, 2015, 09:49:20 am: Ditto. I'll restart in gdb.

Code: [Select]
witness_node: /home/riverhead/github/graphene/libraries/chain/db_market.cpp:290: bool graphene::chain::database::fill_order(const graphene::chain::call_order_object&, const graphene::chain::asset&, const graphene::chain::asset&): Assertion `order.get_collateral() >= pays' failed. Aborted
Title: Re: Test Net for Advanced Users
Post by: wackou on September 30, 2015, 10:18:13 am: had this crash too:

Code: [Select]
1294000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn 1295000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn witness_node: /home/admin/.BitShares2_build/libraries/chain/db_market.cpp:290: bool graphene::chain::database::fill_order(const graphene::chain::call_order_object&, const graphene::chain::asset&, const graphene::chain::asset&): Assertion `order.get_collateral() >= pays' failed. Program received signal SIGABRT, Aborted. 0x00007ffff6516107 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x00007ffff6516107 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff65174e8 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007ffff650f226 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #3 0x00007ffff650f2d2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x00000000024ec8a3 in graphene::chain::database::fill_order (this=0x360f160, order=..., pays=..., receives=...) at /home/admin/.BitShares2_build/libraries/chain/db_market.cpp:290 #5 0x00000000024ec173 in graphene::chain::database::match (this=0x360f160, call=..., settle=..., match_price=..., max_settlement=...) at /home/admin/.BitShares2_build/libraries/chain/db_market.cpp:239 #6 0x00000000024f1f82 in graphene::chain::database::clear_expired_orders (this=0x360f160) at /home/admin/.BitShares2_build/libraries/chain/db_update.cpp:237 #7 0x00000000024d4b90 in graphene::chain::database::_apply_block (this=0x360f160, next_block=...) at /home/admin/.BitShares2_build/libraries/chain/db_block.cpp:478 #8 0x00000000024d4088 in graphene::chain::database::<lambda()>::operator()(void) const (__closure=0x7fffe7df1330) at /home/admin/.BitShares2_build/libraries/chain/db_block.cpp:436 #9 0x00000000024f2f55 in graphene::chain::detail::with_skip_flags<graphene::chain::database::apply_block(const graphene::chain::signed_block&, uint32_t)::<lambda()> >(graphene::chain::database &, uint32_t, graphene::chain::database::<lambda()>) (db=..., skip_flags=0, callback=...) at /home/admin/.BitShares2_build/libraries/chain/include/graphene/chain/db_with.hpp:123 #10 0x00000000024d44ad in graphene::chain::database::apply_block (this=0x360f160, next_block=..., skip=0) at /home/admin/.BitShares2_build/libraries/chain/db_block.cpp:437 #11 0x00000000024ce648 in graphene::chain::database::_push_block (this=0x360f160, new_block=...) at /home/admin/.BitShares2_build/libraries/chain/db_block.cpp:185 #12 0x00000000024cdc21 in graphene::chain::database::<lambda()>::<lambda()>::operator()(void) const (__closure=0x7fffe7df1e20) at /home/admin/.BitShares2_build/libraries/chain/db_block.cpp:112 #13 0x00000000024f2d5e in graphene::chain::detail::without_pending_transactions<graphene::chain::database::push_block(const graphene::chain::signed_block&, uint32_t)::<lambda()>::<lambda()> >(graphene::chain::database &, <unknown type in /home/admin/.BitShares2_bin/witness_node_2015-09-24_test3c-1-gd01fc0a, CU 0xfa3feb, DIE 0x11f4221>, graphene::chain::database::<lambda()>::<lambda()>) (db=..., pending_transactions=<unknown type in /home/admin/.BitShares2_bin/witness_node_2015-09-24_test3c-1-gd01fc0a, CU 0xfa3feb, DIE 0x11f4221>, callback=...) at /home/admin/.BitShares2_build/libraries/chain/include/graphene/chain/db_with.hpp:140 #14 0x00000000024cdc92 in graphene::chain::database::<lambda()>::operator()(void) const (__closure=0x7fffe7df1ed0) at /home/admin/.BitShares2_build/libraries/chain/db_block.cpp:113 #15 0x00000000024f2dd9 in graphene::chain::detail::with_skip_flags<graphene::chain::database::push_block(const graphene::chain::signed_block&, uint32_t)::<lambda()> >(graphene::chain::database &, uint32_t, graphene::chain::database::<lambda()>) (db=..., skip_flags=0, callback=...) at /home/admin/.BitShares2_build/libraries/chain/include/graphene/chain/db_with.hpp:123 #16 0x00000000024cdce3 in graphene::chain::database::push_block (this=0x360f160, new_block=..., skip=0) at /home/admin/.BitShares2_build/libraries/chain/db_block.cpp:114 ---Type <return> to continue, or q <return> to quit--- #17 0x00000000024d158b in graphene::chain::database::_generate_block (this=0x360f160, when=..., witness_id=..., block_signing_private_key=..., retry_on_failure=true) at /home/admin/.BitShares2_build/libraries/chain/db_block.cpp:368 #18 0x00000000024d07d3 in graphene::chain::database::<lambda()>::operator()(void) const (__closure=0x7fffe7df2c40) at /home/admin/.BitShares2_build/libraries/chain/db_block.cpp:276 #19 0x00000000024f2ecf in graphene::chain::detail::with_skip_flags<graphene::chain::database::generate_block(fc::time_point_sec, graphene::chain::witness_id_type, const fc::ecc::private_key&, uint32_t)::<lambda()> >(graphene::chain::database &, uint32_t, graphene::chain::database::<lambda()>) (db=..., skip_flags=0, callback=...) at /home/admin/.BitShares2_build/libraries/chain/include/graphene/chain/db_with.hpp:123 #20 0x00000000024d089f in graphene::chain::database::generate_block (this=0x360f160, when=..., witness_id=..., block_signing_private_key=..., skip=0) at /home/admin/.BitShares2_build/libraries/chain/db_block.cpp:277 #21 0x00000000024c218f in graphene::witness_plugin::witness_plugin::maybe_produce_block (this=0x3618410, capture=...) at /home/admin/.BitShares2_build/libraries/plugins/witness/witness.cpp:276 #22 0x00000000024bff51 in graphene::witness_plugin::witness_plugin::block_production_loop (this=0x3618410) at /home/admin/.BitShares2_build/libraries/plugins/witness/witness.cpp:160 #23 0x00000000024bfe19 in graphene::witness_plugin::witness_plugin::<lambda()>::operator()(void) const (__closure=0x1639d188) at /home/admin/.BitShares2_build/libraries/plugins/witness/witness.cpp:150 #24 0x00000000024c3288 in fc::detail::void_functor_run<graphene::witness_plugin::witness_plugin::schedule_production_loop()::<lambda()> >::run(void *, void *) (functor=0x1639d188, prom=0x1639d180) at /home/admin/.BitShares2_build/libraries/fc/include/fc/thread/task.hpp:83 #25 0x00000000027e209d in fc::task_base::run_impl (this=0x1639d190) at /home/admin/.BitShares2_build/libraries/fc/src/thread/task.cpp:43 #26 0x00000000027e202c in fc::task_base::run (this=0x1639d190) at /home/admin/.BitShares2_build/libraries/fc/src/thread/task.cpp:32 #27 0x00000000027d608a in fc::thread_d::run_next_task (this=0x364d2f0) at /home/admin/.BitShares2_build/libraries/fc/src/thread/thread_d.hpp:498 #28 0x00000000027d6554 in fc::thread_d::process_tasks (this=0x364d2f0) at /home/admin/.BitShares2_build/libraries/fc/src/thread/thread_d.hpp:547 #29 0x00000000027d5b7e in fc::thread_d::start_process_tasks (my=56939248) at /home/admin/.BitShares2_build/libraries/fc/src/thread/thread_d.hpp:475 #30 0x0000000002b50711 in make_fcontext () #31 0x00010102464c457f in ?? () #32 0x0000000000000000 in ?? () (gdb)
Note that I hadn't upgraded to the latest master yet, will do so now.
Title: Re: Test Net for Advanced Users
Post by: wackou on September 30, 2015, 10:25:25 am: not sure if that's helpful, but I tried to get some more info out of it, and I could retrieve this:

the block in push_block (in stack frame #16) has a header that starts like this:

Code: [Select]
{<graphene::chain::block_header> = {previous = {_hash = {3201106944, 1397224070, 591270816, 3178160838, 2663318844}}, timestamp = {utc_seconds = 1443601296} [...]
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 30, 2015, 11:01:25 am: Crashed on witness and one of my nodes at the same block

# witness crash
Code: [Select]
1244000ms th_a witness.cpp:182 block_production_loo ] Not producing block because it isn't my turn witness_node: /home/ihashfury/tmp/graphene/libraries/chain/db_market.cpp:290: bool graphene::chain::database::fill_order(const graphene: :chain::call_order_object&, const graphene::chain::asset&, const graphene::chain::asset&): Assertion `order.get_collateral() >= pays' fa iled. Aborted (core dumped)
# node crash
Code: [Select]
1272262ms th_a application.cpp:388 handle_block ] Got block #314815 with time 2015-09-30T08:21:12 from network with latency of 263 ms from init0 witness_node: /home/ihashfury/tmp/graphene/libraries/chain/db_market.cpp:290: bool graphene::chain::database::fill_order(const graphene::chain::call_order_object&, const graphene::chain::asset&, const graphene::chain::asset&): Assertion `order.get_collateral() >= pays' failed. Aborted
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 30, 2015, 12:17:14 pm: Quote from: spartako on September 30, 2015, 08:00:04 am
I wake up this morning and my witness for all night was not able to sync the correct fork.
I have a while [ True ] in my bash script so if it crash, it start again but every times gives me this error and started again to try to resync (without success):

Code: [Select]
93.3428% 284000 of 304255 1818515ms th_a undo_database.hpp:62 ~session ] 10 assert_exception: Assert Exception !_disabled: {} th_a undo_database.cpp:88 undo {} th_a undo_database.cpp:116 undo terminate called after throwing an instance of 'fc::assert_exception' Aborted (core dumped)
Now the witness if updated to the new master.

This issue was fixed yesterday.
Title: Re: Test Net for Advanced Users
Post by: Fox on September 30, 2015, 12:22:22 pm: All of my updated nodes also crashed. I am now unable to --resync-blockchain. I only have a single seed node listed in my startup script, but it is not responding.

Please post your peers so that I may sync.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 30, 2015, 12:27:41 pm: All of my nodes were hung when I came in this morning. Looks like a major issue was discovered and we are looking into the cause.

Based upon the crash reports it looks like someone attempted a force settle.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 30, 2015, 12:28:49 pm: Quote from: Fox on September 30, 2015, 12:22:22 pm
All of my updated nodes also crashed. I am now unable to --resync-blockchain. I only have a single seed node listed in my startup script, but it is not responding.

Please post your peers so that I may sync.

The network is effectively dead at this point. It will require a checkpoint to revive.

Could everyone post their head block number and hash?
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 30, 2015, 12:29:20 pm: "head_block_num": 314836,
"head_block_id": "0004cdd471f6d83da5ddcfc8d93b65262538643a",
"head_block_age": "4 hours old"
Title: Re: Test Net for Advanced Users
Post by: Riverhead on September 30, 2015, 12:37:19 pm: No useful info here I'm afraid. I tried to reload with a new chain but the network was already dead.

Code: [Select]
"head_block_num": 0, "head_block_id": "0000000000000000000000000000000000000000", "head_block_age": "12 days old", "next_maintenance_time": "45 years ago", "chain_id": "0f8b631d7a9dfebf16d6776fab96b629a14429762bf9c3eb95db1e4e4af637a4", "participation": "100.00000000000000000",
Title: Re: Test Net for Advanced Users
Post by: Xeldal on September 30, 2015, 12:40:23 pm: "head_block_num": 314814,
"head_block_id": "0004cdbe86f24753a0133e23c6e26ebd3c05bf9e",
"head_block_age": "4 hours old",
Title: Re: Test Net for Advanced Users
Post by: Troglodactyl on September 30, 2015, 12:42:38 pm: Here's how my observer node ended:

Code: [Select]
1179254ms th_a application.cpp:388 handle_block ] Got block #314806 with time 2015-09-30T08:19:39 from network with latency of 255 ms from delegate-dev3.btsnow 1179486ms th_a application.cpp:518 get_item ] Serving up block #314806 1182227ms th_a application.cpp:388 handle_block ] Got block #314807 with time 2015-09-30T08:19:42 from network with latency of 227 ms from init6 1182462ms th_a application.cpp:518 get_item ] Serving up block #314807 1185107ms th_a application.cpp:388 handle_block ] Got block #314808 with time 2015-09-30T08:19:45 from network with latency of 108 ms from init11 1185338ms th_a application.cpp:518 get_item ] Serving up block #314808 1188176ms th_a application.cpp:388 handle_block ] Got block #314809 with time 2015-09-30T08:19:48 from network with latency of 177 ms from init1 1188411ms th_a application.cpp:518 get_item ] Serving up block #314809 1191249ms th_a application.cpp:388 handle_block ] Got block #314810 with time 2015-09-30T08:19:51 from network with latency of 250 ms from init2 1194378ms th_a application.cpp:388 handle_block ] Got block #314811 with time 2015-09-30T08:19:54 from network with latency of 379 ms from delegate-clayop 1197207ms th_a application.cpp:388 handle_block ] Got block #314812 with time 2015-09-30T08:19:57 from network with latency of 207 ms from wackou 1200221ms th_a application.cpp:388 handle_block ] Got block #314813 with time 2015-09-30T08:20:00 from network with latency of 222 ms from init4 1200461ms th_a application.cpp:518 get_item ] Serving up block #314813 1203250ms th_a application.cpp:388 handle_block ] Got block #314814 with time 2015-09-30T08:20:03 from network with latency of 251 ms from init3 1207182ms th_a application.cpp:388 handle_block ] Got block #314814 with time 2015-09-30T08:20:06 from network with latency of 1182 ms from mr.agsexplorer 2209930ms th_a application.cpp:699 get_blockchain_synop ] synopsis: ["0004cdb3d2d7eb80189f83633c4cb9edfa428ca8","0004cdb90bdf86f48dd2d6695fe8f5edb3322e67","0004cdbcecb0901e9e26dabd0c5610f648a14108","0004cdbe86f24753a0133e23c6e26ebd3c05bf9e"]...
Code: [Select]
890491ms th_a application.cpp:518 get_item ] Serving up block #314811 890491ms th_a application.cpp:518 get_item ] Serving up block #314812 890491ms th_a application.cpp:518 get_item ] Serving up block #314813 890491ms th_a application.cpp:518 get_item ] Serving up block #314814 898941ms th_a application.cpp:699 get_blockchain_synop ] synopsis: ["0004cdb4a094bb65e4ddf13138fca35a9c5b4141","0004cdbab1c582f8ccc1e6396f0d62cb9c047323","0004cdbde932bd1fbe5e160b4dd22b1a9b1f8135","0004cdbe86f24753a0133e23c6e26ebd3c05bf9e"] witness_node: /home/daniel/Crypto/graphene/libraries/chain/db_market.cpp:290: bool graphene::chain::database::fill_order(const graphene::chain::call_order_object&, const graphene::chain::asset&, const graphene::chain::asset&): Assertion `order.get_collateral() >= pays' failed. ./run_node: line 1: 1063 Aborted (core dumped)
EDIT: The synopsis is just the last 4 blocks, right?
Title: Re: Test Net for Advanced Users
Post by: alt on September 30, 2015, 12:43:40 pm: Code: [Select]
last_block->id(): 0004cdbde932bd1fbe5e160b4dd22b1a9b1f8135 last_block->block_num(): 314813
Quote from: bytemaster on September 30, 2015, 12:29:20 pm
"head_block_num": 314836,
"head_block_id": "0004cdd471f6d83da5ddcfc8d93b65262538643a",
"head_block_age": "4 hours old"
Title: Re: Test Net for Advanced Users
Post by: clayop on September 30, 2015, 12:45:43 pm: Code: [Select]
"head_block_num": 314814, "head_block_id": "0004cdbe86f24753a0133e23c6e26ebd3c05bf9e", "head_block_age": "4 hours old",
Title: Re: Test Net for Advanced Users
Post by: ElMato on September 30, 2015, 12:47:41 pm: Quote from: bytemaster on September 30, 2015, 12:27:41 pm
All of my nodes were hung when I came in this morning. Looks like a major issue was discovered and we are looking into the cause.

Based upon the crash reports it looks like someone attempted a force settle.

I was testing force settlement.
I forced bitUSD, bitCNY, bitSILVER and bitGOLD to force settle, i don't remember the exact settlement date but was something like 8:00 AM GMT Sep 30 (need to double check)
Title: Re: Test Net for Advanced Users
Post by: spartako on September 30, 2015, 12:51:14 pm: This is my last info command before the witness crash (and the wallet exit after):

Code: [Select]
"head_block_num": 313187, "head_block_id": "0004c763d993633488acb5fdd6ec362112aae9b9", "head_block_age": "6 hours old",
Code: [Select]
Server has disconnected us. 9 canceled_exception: Canceled cancellation reason: [none given] {"reason":"[none given]"} th_a thread_d.hpp:463 start_next_fiber
Title: Re: Test Net for Advanced Users
Post by: iHashFury on September 30, 2015, 12:51:46 pm: info
{
"head_block_num": 314814,
"head_block_id": "0004cdbe86f24753a0133e23c6e26ebd3c05bf9e",
"head_block_age": "4 hours old",
"next_maintenance_time": "4 hours ago",
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 30, 2015, 12:59:51 pm: Upon looking closer here is what I have found:

1. If you were in debug build your witness crashed because of an assert we had to perform sanity checks
2. If you were in release build your witness didn't crash but went on to fill a force settlement request when the collateral in the call order is less than what was received by the force settle (printing CORE).

The crash appears to be the result of a call order which lacks sufficient collateral at the force settlement price.

As a result of this the network forked and all debug builds stopped producing.

The good news is that I can reproduce this particular issue on demand and can get to the root cause of it.

To prevent debug vs release forks in the future we will be converting all assert(...) calls to FC_ASSERT so that the code behaves the same in both builds and shouldn't "crash" in the future.
Title: Re: Test Net for Advanced Users
Post by: xeroc on September 30, 2015, 01:21:18 pm: Sounds like progress ..

We are getting closer by the minute
Title: Re: Test Net for Advanced Users
Post by: wuyanren on September 30, 2015, 01:24:04 pm: Quote from: xeroc on September 30, 2015, 01:21:18 pm
Sounds like progress ..

We are getting closer by the minute
You seem to comfort me
Title: Re: Test Net for Advanced Users
Post by: cube on September 30, 2015, 02:09:42 pm: Debug built witness crashed. It is restarting from block 0.

Edit: Resyn failed with the same 'fill order' error.
Title: Re: Test Net for Advanced Users
Post by: ElMato on September 30, 2015, 02:39:28 pm: "head_block_num": 314814,
"head_block_id": "0004cdbe86f24753a0133e23c6e26ebd3c05bf9e",
"head_block_age": "6 hours old",
"next_maintenance_time": "6 hours ago",
"chain_id": "0f8b631d7a9dfebf16d6776fab96b629a14429762bf9c3eb95db1e4e4af637a4",

While replaying the blockchain
Code: [Select]
90.212% 284000 of 314814 1858849ms th_a db_block.cpp:263 push_proposal ] e 1858850ms th_a db_update.cpp:140 clear_expired_propos ] Failed to apply proposed transaction on its expiration. Deleting it. {"id":"1.10.1","expiration_time":"2015-09-29T05:15:00","review_period_time":"2015-09-29T04:15:00","proposed_transaction":{"ref_block_num":0,"ref_block_prefix":0,"expiration":" 2015-09-29T05:15:00","operations":[[31,{"fee":{"amount":1000000,"asset_id":"1.3.0"},"new_parameters":{"current_fees":{"parameters":[[0,{"fee":2000000,"price_per_kbyte":1000000 }],[1,{"fee":500000}],[2,{"fee":0}],[3,{"fee":2000000}],[4,{}],[5,{"basic_fee":0,"premium_fee":200000000,"price_per_kbyte":100000}],[6,{"fee":2000000,"price_per_kbyte":100000} ],[7,{"fee":300000}],[8,{"membership_annual_fee":200000000,"membership_lifetime_fee":1000000000}],[9,{"fee":50000000}],[10,{"symbol3":"50000000000","symbol4":"30000000000","lo ng_symbol":500000000,"price_per_kbyte":10}],[11,{"fee":50000000,"price_per_kbyte":10}],[12,{"fee":50000000}],[13,{"fee":50000000}],[14,{"fee":2000000,"price_per_kbyte":100000} ],[15,{"fee":2000000}],[16,{"fee":100000}],[17,{"fee":10000000}],[18,{"fee":50000000}],[19,{"fee":100000}],[20,{"fee":500000000}],[21,{"fee":2000000}],[22,{"fee":2000000,"pric e_per_kbyte":10}],[23,{"fee":100000,"price_per_kbyte":10}],[24,{"fee":100000}],[25,{"fee":100000}],[26,{"fee":2000000}],[27,{"fee":0,"price_per_kbyte":10}],[28,{"fee":50000000 0}],[29,{"fee":100000}],[30,{"fee":100000}],[31,{"fee":2000000}],[32,{"fee":500000000}],[33,{"fee":100000}],[34,{"fee":100000}],[35,{"fee":100000,"price_per_kbyte":10}],[36,{" fee":2000000}],[37,{}],[38,{"fee":500000,"price_per_kbyte":10}],[39,{"fee":500000,"price_per_output":500000}]],"scale":5000},"block_interval":3,"maintenance_interval":5400,"ma intenance_skip_slots":4,"committee_proposal_review_period":300,"maximum_transaction_size":65536,"maximum_block_size":10485760,"maximum_time_until_expiration":86400,"maximum_pr oposal_lifetime":2419200,"maximum_asset_whitelist_authorities":10,"maximum_asset_feed_publishers":10,"maximum_witness_count":1001,"maximum_committee_count":1001,"maximum_autho rity_membership":10,"reserve_percent_of_fee":2000,"network_percent_of_fee":2000,"lifetime_referrer_percent_of_fee":3000,"cashback_vesting_period_seconds":7776000,"cashback_ves ting_threshold":10000000,"count_non_member_votes":true,"allow_non_member_whitelists":false,"witness_pay_per_block":500000,"worker_budget_per_day":"50000000000","max_predicate_ opcode":1,"fee_liquidation_threshold":10000000,"accounts_per_fee_scale":1000,"account_fee_scale_bitshifts":4,"max_authority_depth":2,"extensions":[]}}]],"extensions":[]},"requ ired_active_approvals":["1.2.0"],"available_active_approvals":["1.2.102","1.2.103","1.2.104","1.2.105","1.2.106","1.2.107","1.2.108","1.2.109","1.2.110"],"required_owner_appro vals":[],"available_owner_approvals":[],"available_key_approvals":[]} 10 assert_exception: Assert Exception itr->get_balance() >= -delta: Insufficient Balance: committee-account's balance of 0 CORE is less than required 10 CORE {"a":"committee-account","b":"0 CORE","r":"10 CORE"} th_a db_balance.cpp:67 adjust_balance {"account":"1.2.0","delta":{"amount":-1000000,"asset_id":"1.3.0"}} th_a db_balance.cpp:73 adjust_balance {} th_a evaluator.cpp:42 start_evaluate intenance_skip_slots":4,"committee_proposal_review_period":300,"maximum_transaction_size":65536,"maximum_block_size":10485760,"maximum_time_until_expiration":86400,"[540/1909] oposal_lifetime":2419200,"maximum_asset_whitelist_authorities":10,"maximum_asset_feed_publishers":10,"maximum_witness_count":1001,"maximum_committee_count":1001,"maximum_autho rity_membership":10,"reserve_percent_of_fee":2000,"network_percent_of_fee":2000,"lifetime_referrer_percent_of_fee":3000,"cashback_vesting_period_seconds":7776000,"cashback_ves ting_threshold":10000000,"count_non_member_votes":true,"allow_non_member_whitelists":false,"witness_pay_per_block":500000,"worker_budget_per_day":"50000000000","max_predicate_ opcode":1,"fee_liquidation_threshold":10000000,"accounts_per_fee_scale":1000,"account_fee_scale_bitshifts":4,"max_authority_depth":2,"extensions":[]}}]],"extensions":[]},"requ ired_active_approvals":["1.2.0"],"available_active_approvals":["1.2.102","1.2.103","1.2.104","1.2.105","1.2.106","1.2.107","1.2.108","1.2.109","1.2.110"],"required_owner_appro vals":[],"available_owner_approvals":[],"available_key_approvals":[]} 10 assert_exception: Assert Exception itr->get_balance() >= -delta: Insufficient Balance: committee-account's balance of 0 CORE is less than required 10 CORE {"a":"committee-account","b":"0 CORE","r":"10 CORE"} th_a db_balance.cpp:67 adjust_balance {"account":"1.2.0","delta":{"amount":-1000000,"asset_id":"1.3.0"}} th_a db_balance.cpp:73 adjust_balance {} th_a evaluator.cpp:42 start_evaluate {} th_a db_block.cpp:621 apply_operation {"proposal":{"id":"1.10.1","expiration_time":"2015-09-29T05:15:00","review_period_time":"2015-09-29T04:15:00","proposed_transaction":{"ref_block_num":0,"ref_block_prefix": 0,"expiration":"2015-09-29T05:15:00","operations":[[31,{"fee":{"amount":1000000,"asset_id":"1.3.0"},"new_parameters":{"current_fees":{"parameters":[[0,{"fee":2000000,"price_pe r_kbyte":1000000}],[1,{"fee":500000}],[2,{"fee":0}],[3,{"fee":2000000}],[4,{}],[5,{"basic_fee":0,"premium_fee":200000000,"price_per_kbyte":100000}],[6,{"fee":2000000,"price_pe r_kbyte":100000}],[7,{"fee":300000}],[8,{"membership_annual_fee":200000000,"membership_lifetime_fee":1000000000}],[9,{"fee":50000000}],[10,{"symbol3":"50000000000","symbol4":" 30000000000","long_symbol":500000000,"price_per_kbyte":10}],[11,{"fee":50000000,"price_per_kbyte":10}],[12,{"fee":50000000}],[13,{"fee":50000000}],[14,{"fee":2000000,"price_pe r_kbyte":100000}],[15,{"fee":2000000}],[16,{"fee":100000}],[17,{"fee":10000000}],[18,{"fee":50000000}],[19,{"fee":100000}],[20,{"fee":500000000}],[21,{"fee":2000000}],[22,{"fe e":2000000,"price_per_kbyte":10}],[23,{"fee":100000,"price_per_kbyte":10}],[24,{"fee":100000}],[25,{"fee":100000}],[26,{"fee":2000000}],[27,{"fee":0,"price_per_kbyte":10}],[28 ,{"fee":500000000}],[29,{"fee":100000}],[30,{"fee":100000}],[31,{"fee":2000000}],[32,{"fee":500000000}],[33,{"fee":100000}],[34,{"fee":100000}],[35,{"fee":100000,"price_per_kb yte":10}],[36,{"fee":2000000}],[37,{}],[38,{"fee":500000,"price_per_kbyte":10}],[39,{"fee":500000,"price_per_output":500000}]],"scale":5000},"block_interval":3,"maintenance_in terval":5400,"maintenance_skip_slots":4,"committee_proposal_review_period":300,"maximum_transaction_size":65536,"maximum_block_size":10485760,"maximum_time_until_expiration":8 6400,"maximum_proposal_lifetime":2419200,"maximum_asset_whitelist_authorities":10,"maximum_asset_feed_publishers":10,"maximum_witness_count":1001,"maximum_committee_count":100 1,"maximum_authority_membership":10,"reserve_percent_of_fee":2000,"network_percent_of_fee":2000,"lifetime_referrer_percent_of_fee":3000,"cashback_vesting_period_seconds":77760 00,"cashback_vesting_threshold":10000000,"count_non_member_votes":true,"allow_non_member_whitelists":false,"witness_pay_per_block":500000,"worker_budget_per_day":"50000000000" ,"max_predicate_opcode":1,"fee_liquidation_threshold":10000000,"accounts_per_fee_scale":1000,"account_fee_scale_bitshifts":4,"max_authority_depth":2,"extensions":[]}}]],"exten sions":[]},"required_active_approvals":["1.2.0"],"available_active_approvals":["1.2.102","1.2.103","1.2.104","1.2.105","1.2.106","1.2.107","1.2.108","1.2.109","1.2.110"],"requ ired_owner_approvals":[],"available_owner_approvals":[],"available_key_approvals":[]}} th_a db_block.cpp:269 push_proposal
Title: Re: Test Net for Advanced Users
Post by: betax on September 30, 2015, 04:23:16 pm: Any new nodes ? I have deleted the database, and try to sync, but after a few hours (just checked) still nothing.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 30, 2015, 05:20:32 pm: Quote from: ElMato on September 30, 2015, 02:39:28 pm
"head_block_num": 314814,
"head_block_id": "0004cdbe86f24753a0133e23c6e26ebd3c05bf9e",
"head_block_age": "6 hours old",
"next_maintenance_time": "6 hours ago",
"chain_id": "0f8b631d7a9dfebf16d6776fab96b629a14429762bf9c3eb95db1e4e4af637a4",

While replaying the blockchain
Code: [Select]
90.212% 284000 of 314814 1858849ms th_a db_block.cpp:263 push_proposal ] e 1858850ms th_a db_update.cpp:140 clear_expired_propos ] Failed to apply proposed transaction on its expiration. Deleting it. {"id":"1.10.1","expiration_time":"2015-09-29T05:15:00","review_period_time":"2015-09-29T04:15:00","proposed_transaction":{"ref_block_num":0,"ref_block_prefix":0,"expiration":" 2015-09-29T05:15:00","operations":[[31,{"fee":{"amount":1000000,"asset_id":"1.3.0"},"new_parameters":{"current_fees":{"parameters":[[0,{"fee":2000000,"price_per_kbyte":1000000 }],[1,{"fee":500000}],[2,{"fee":0}],[3,{"fee":2000000}],[4,{}],[5,{"basic_fee":0,"premium_fee":200000000,"price_per_kbyte":100000}],[6,{"fee":2000000,"price_per_kbyte":100000} ],[7,{"fee":300000}],[8,{"membership_annual_fee":200000000,"membership_lifetime_fee":1000000000}],[9,{"fee":50000000}],[10,{"symbol3":"50000000000","symbol4":"30000000000","lo ng_symbol":500000000,"price_per_kbyte":10}],[11,{"fee":50000000,"price_per_kbyte":10}],[12,{"fee":50000000}],[13,{"fee":50000000}],[14,{"fee":2000000,"price_per_kbyte":100000} ],[15,{"fee":2000000}],[16,{"fee":100000}],[17,{"fee":10000000}],[18,{"fee":50000000}],[19,{"fee":100000}],[20,{"fee":500000000}],[21,{"fee":2000000}],[22,{"fee":2000000,"pric e_per_kbyte":10}],[23,{"fee":100000,"price_per_kbyte":10}],[24,{"fee":100000}],[25,{"fee":100000}],[26,{"fee":2000000}],[27,{"fee":0,"price_per_kbyte":10}],[28,{"fee":50000000 0}],[29,{"fee":100000}],[30,{"fee":100000}],[31,{"fee":2000000}],[32,{"fee":500000000}],[33,{"fee":100000}],[34,{"fee":100000}],[35,{"fee":100000,"price_per_kbyte":10}],[36,{" fee":2000000}],[37,{}],[38,{"fee":500000,"price_per_kbyte":10}],[39,{"fee":500000,"price_per_output":500000}]],"scale":5000},"block_interval":3,"maintenance_interval":5400,"ma intenance_skip_slots":4,"committee_proposal_review_period":300,"maximum_transaction_size":65536,"maximum_block_size":10485760,"maximum_time_until_expiration":86400,"maximum_pr oposal_lifetime":2419200,"maximum_asset_whitelist_authorities":10,"maximum_asset_feed_publishers":10,"maximum_witness_count":1001,"maximum_committee_count":1001,"maximum_autho rity_membership":10,"reserve_percent_of_fee":2000,"network_percent_of_fee":2000,"lifetime_referrer_percent_of_fee":3000,"cashback_vesting_period_seconds":7776000,"cashback_ves ting_threshold":10000000,"count_non_member_votes":true,"allow_non_member_whitelists":false,"witness_pay_per_block":500000,"worker_budget_per_day":"50000000000","max_predicate_ opcode":1,"fee_liquidation_threshold":10000000,"accounts_per_fee_scale":1000,"account_fee_scale_bitshifts":4,"max_authority_depth":2,"extensions":[]}}]],"extensions":[]},"requ ired_active_approvals":["1.2.0"],"available_active_approvals":["1.2.102","1.2.103","1.2.104","1.2.105","1.2.106","1.2.107","1.2.108","1.2.109","1.2.110"],"required_owner_appro vals":[],"available_owner_approvals":[],"available_key_approvals":[]} 10 assert_exception: Assert Exception itr->get_balance() >= -delta: Insufficient Balance: committee-account's balance of 0 CORE is less than required 10 CORE {"a":"committee-account","b":"0 CORE","r":"10 CORE"} th_a db_balance.cpp:67 adjust_balance {"account":"1.2.0","delta":{"amount":-1000000,"asset_id":"1.3.0"}} th_a db_balance.cpp:73 adjust_balance {} th_a evaluator.cpp:42 start_evaluate intenance_skip_slots":4,"committee_proposal_review_period":300,"maximum_transaction_size":65536,"maximum_block_size":10485760,"maximum_time_until_expiration":86400,"[540/1909] oposal_lifetime":2419200,"maximum_asset_whitelist_authorities":10,"maximum_asset_feed_publishers":10,"maximum_witness_count":1001,"maximum_committee_count":1001,"maximum_autho rity_membership":10,"reserve_percent_of_fee":2000,"network_percent_of_fee":2000,"lifetime_referrer_percent_of_fee":3000,"cashback_vesting_period_seconds":7776000,"cashback_ves ting_threshold":10000000,"count_non_member_votes":true,"allow_non_member_whitelists":false,"witness_pay_per_block":500000,"worker_budget_per_day":"50000000000","max_predicate_ opcode":1,"fee_liquidation_threshold":10000000,"accounts_per_fee_scale":1000,"account_fee_scale_bitshifts":4,"max_authority_depth":2,"extensions":[]}}]],"extensions":[]},"requ ired_active_approvals":["1.2.0"],"available_active_approvals":["1.2.102","1.2.103","1.2.104","1.2.105","1.2.106","1.2.107","1.2.108","1.2.109","1.2.110"],"required_owner_appro vals":[],"available_owner_approvals":[],"available_key_approvals":[]} 10 assert_exception: Assert Exception itr->get_balance() >= -delta: Insufficient Balance: committee-account's balance of 0 CORE is less than required 10 CORE {"a":"committee-account","b":"0 CORE","r":"10 CORE"} th_a db_balance.cpp:67 adjust_balance {"account":"1.2.0","delta":{"amount":-1000000,"asset_id":"1.3.0"}} th_a db_balance.cpp:73 adjust_balance {} th_a evaluator.cpp:42 start_evaluate {} th_a db_block.cpp:621 apply_operation {"proposal":{"id":"1.10.1","expiration_time":"2015-09-29T05:15:00","review_period_time":"2015-09-29T04:15:00","proposed_transaction":{"ref_block_num":0,"ref_block_prefix": 0,"expiration":"2015-09-29T05:15:00","operations":[[31,{"fee":{"amount":1000000,"asset_id":"1.3.0"},"new_parameters":{"current_fees":{"parameters":[[0,{"fee":2000000,"price_pe r_kbyte":1000000}],[1,{"fee":500000}],[2,{"fee":0}],[3,{"fee":2000000}],[4,{}],[5,{"basic_fee":0,"premium_fee":200000000,"price_per_kbyte":100000}],[6,{"fee":2000000,"price_pe r_kbyte":100000}],[7,{"fee":300000}],[8,{"membership_annual_fee":200000000,"membership_lifetime_fee":1000000000}],[9,{"fee":50000000}],[10,{"symbol3":"50000000000","symbol4":" 30000000000","long_symbol":500000000,"price_per_kbyte":10}],[11,{"fee":50000000,"price_per_kbyte":10}],[12,{"fee":50000000}],[13,{"fee":50000000}],[14,{"fee":2000000,"price_pe r_kbyte":100000}],[15,{"fee":2000000}],[16,{"fee":100000}],[17,{"fee":10000000}],[18,{"fee":50000000}],[19,{"fee":100000}],[20,{"fee":500000000}],[21,{"fee":2000000}],[22,{"fe e":2000000,"price_per_kbyte":10}],[23,{"fee":100000,"price_per_kbyte":10}],[24,{"fee":100000}],[25,{"fee":100000}],[26,{"fee":2000000}],[27,{"fee":0,"price_per_kbyte":10}],[28 ,{"fee":500000000}],[29,{"fee":100000}],[30,{"fee":100000}],[31,{"fee":2000000}],[32,{"fee":500000000}],[33,{"fee":100000}],[34,{"fee":100000}],[35,{"fee":100000,"price_per_kb yte":10}],[36,{"fee":2000000}],[37,{}],[38,{"fee":500000,"price_per_kbyte":10}],[39,{"fee":500000,"price_per_output":500000}]],"scale":5000},"block_interval":3,"maintenance_in terval":5400,"maintenance_skip_slots":4,"committee_proposal_review_period":300,"maximum_transaction_size":65536,"maximum_block_size":10485760,"maximum_time_until_expiration":8 6400,"maximum_proposal_lifetime":2419200,"maximum_asset_whitelist_authorities":10,"maximum_asset_feed_publishers":10,"maximum_witness_count":1001,"maximum_committee_count":100 1,"maximum_authority_membership":10,"reserve_percent_of_fee":2000,"network_percent_of_fee":2000,"lifetime_referrer_percent_of_fee":3000,"cashback_vesting_period_seconds":77760 00,"cashback_vesting_threshold":10000000,"count_non_member_votes":true,"allow_non_member_whitelists":false,"witness_pay_per_block":500000,"worker_budget_per_day":"50000000000" ,"max_predicate_opcode":1,"fee_liquidation_threshold":10000000,"accounts_per_fee_scale":1000,"account_fee_scale_bitshifts":4,"max_authority_depth":2,"extensions":[]}}]],"exten sions":[]},"required_active_approvals":["1.2.0"],"available_active_approvals":["1.2.102","1.2.103","1.2.104","1.2.105","1.2.106","1.2.107","1.2.108","1.2.109","1.2.110"],"requ ired_owner_approvals":[],"available_owner_approvals":[],"available_key_approvals":[]}} th_a db_block.cpp:269 push_proposal

That is more of a status message than an error message and is OK to ignore.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 30, 2015, 05:29:53 pm: Quick Update:

We have identified the corner case that caused the problem and are preparing fixes for it now. A quick summary:

1. Early feed producers were off by a factor of 10
2. Early margin testors created margin positions based upon the old feed prices
3. Feed producers fixed their feed which left the early margin testors in black-swan territory
4. Attempt to force settle resulted in a condition that was previously believed to be impossible (a black swan)

The fix we are adding will cause BitUSD to black swan on the test network.

We are in the process of auditing the transaction history to answer a couple of questions:

1. Should the black swan have been triggered much earlier as a result of market orders being placed, canceled, etc?
2. If it should have, why wasn't it?

We are also evaluating if we should take any precautions to protect the network from future unexpected bugs. Right now there exist
a slew of operations that are applied outside the context of a transaction. If any of those operations fail then the network will be unable
to produce blocks. In effect, these operations should always succeed if the transaction evaluation maintains the proper invariants.

Will be back with more updates when we have them.
Title: Re: Test Net for Advanced Users
Post by: testz on September 30, 2015, 06:33:25 pm: Quote from: bytemaster on September 30, 2015, 05:29:53 pm
4. Attempt to force settle resulted in a condition that was previously believed to be impossible (a black swan)

+5% Very good that this happened, so this case can be properly reviewed and re-tested.
Title: Re: Test Net for Advanced Users
Post by: liondani on September 30, 2015, 07:25:25 pm: Quote from: testz on September 30, 2015, 06:33:25 pm
Quote from: bytemaster on September 30, 2015, 05:29:53 pm
4. Attempt to force settle resulted in a condition that was previously believed to be impossible (a black swan)

+5% Very good that this happened, so this case can be properly reviewed and re-tested.

+5%

Yep I am glad it occurred on the test-network too !
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 30, 2015, 08:22:04 pm: Quote from: liondani on September 30, 2015, 07:25:25 pm
Quote from: testz on September 30, 2015, 06:33:25 pm
Quote from: bytemaster on September 30, 2015, 05:29:53 pm
4. Attempt to force settle resulted in a condition that was previously believed to be impossible (a black swan)

+5% Very good that this happened, so this case can be properly reviewed and re-tested.

+5%

Yep I am glad it occurred on the test-network too !

We have identified the problem and have a solution in the works. A big thank you to all of the testers who are pushing the test network through all kinds of edge cases.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on September 30, 2015, 10:36:22 pm: I have just checked in a fix for this issue, but it resulted in a hard fork several days ago because BitUSD technically had a black swan event back then.

Theoretical is working on unit tests for the edge cases we have identified so that we can verify the fix works in all cases.

We will launch a new test network tomorrow based upon this fix and the party can continue.
Title: Re: Test Net for Advanced Users
Post by: Thom on September 30, 2015, 10:39:49 pm: Quote from: bytemaster on September 30, 2015, 10:36:22 pm
I have just checked in a fix for this issue, but it resulted in a hard fork several days ago because BitUSD technically had a black swan event back then.

Theoretical is working on unit tests for the edge cases we have identified so that we can verify the fix works in all cases.

We will launch a new test network tomorrow based upon this fix and the party can continue.

Awesome, I'll be ready to join back in with several VPS seed nodes to help.
Title: Re: Test Net for Advanced Users
Post by: abit on September 30, 2015, 10:43:55 pm: Quote from: bytemaster on September 29, 2015, 02:46:26 pm
Quote from: bytemaster on September 29, 2015, 12:55:18 pm
Quote from: abit on September 29, 2015, 02:00:32 am
It took 75 seconds to replay the 280k-blocks chain.

Maybe on a SLOW vps, but on my machine it takes a mere 11 8.79 seconds.

In Debug build it took me 59 seconds to reindex.
In Release build it took me 8.79 seconds to reindex.

There were a total of 444758 operations in the blockchain which means we are averaging over 50K TPS.
The average maintenance calculation time is: 7 ms
1.5 seconds were spent doing maintenance calculations (on the hour, instead of every day) leaving us at 62K TPS average
The vast majority of blocks have been empty which means our TPS average is being diluted by block processing overhead.

It looks like in Debug mode we process closer to 10K TPS.
Yes I'm running with debug build. I remember the log said replay took about 60 seconds, but CPU kept at 100% for 75 seconds. Maybe the 15 more seconds are before or after replay.
Title: Re: Test Net for Advanced Users
Post by: abit on September 30, 2015, 11:00:27 pm: Quote from: bytemaster on September 30, 2015, 10:36:22 pm
I have just checked in a fix for this issue, but it resulted in a hard fork several days ago because BitUSD technically had a black swan event back then.

Theoretical is working on unit tests for the edge cases we have identified so that we can verify the fix works in all cases.

We will launch a new test network tomorrow based upon this fix and the party can continue.
I'm unable to access my server right now. Wish I could be back when the new test network is ready.
Title: Re: Test Net for Advanced Users
Post by: xeroc on October 01, 2015, 05:16:07 am: @abit: Congratulations ... it seems the both of us were the very reason for the first every blockchain based black swan event :-P
Title: Re: Test Net for Advanced Users
Post by: liondani on October 01, 2015, 06:26:32 am: Quote from: bytemaster on September 30, 2015, 10:36:22 pm
... it resulted in a hard fork several days ago because BitUSD technically had a black swan event back then.

and why have we not identified the event just after it occurred and only a couple of days later?
Title: Re: Test Net for Advanced Users
Post by: CalabiYau on October 01, 2015, 06:30:16 am: Quote from: xeroc on October 01, 2015, 05:16:07 am
@abit: Congratulations ... it seems the both of us were the very reason for the first every blockchain based black swan event :-P

:) :) that`s what legends are made off.....
Title: Re: Test Net for Advanced Users
Post by: sittingduck on October 01, 2015, 12:04:15 pm: Quote from: liondani on October 01, 2015, 06:26:32 am
Quote from: bytemaster on September 30, 2015, 10:36:22 pm
... it resulted in a hard fork several days ago because BitUSD technically had a black swan event back then.

and why have we not identified the event just after it occurred and only a couple of days later?

Because the market was thin

Sent from my iPhone using Tapatalk
Title: Re: Test Net for Advanced Users
Post by: bytemaster on October 01, 2015, 12:28:15 pm: Quote from: sittingduck on October 01, 2015, 12:04:15 pm

Quote from: liondani on October 01, 2015, 06:26:32 am
Quote from: bytemaster on September 30, 2015, 10:36:22 pm
... it resulted in a hard fork several days ago because BitUSD technically had a black swan event back then.

and why have we not identified the event just after it occurred and only a couple of days later?

Because the market was thin

Sent from my iPhone using Tapatalk

Black Swan detection was only kicking in if there was a margin call, but margin calls were not triggering because there were no orders above the short-squeeze protection threshold.
Black Swan should only happen when the MAX( Highest Bid, Settlement Price ) < LeastCollateralizedPosition. I moved the check to catch sooner in the evaluation which means that
the BlackSwan occurred as soon as the price feed was updated rather than delayed until the first forced settlement.
Title: Re: Test Net for Advanced Users
Post by: bytemaster on October 01, 2015, 01:49:06 pm: https://bitsharestalk.org/index.php/topic,18699.msg240322.html#msg240322