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?

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!

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?

What's your chain_id?

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

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 Expand


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 ...

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?

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 Expand


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.

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

Btw: How do you read this:


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?

Quote from: roadscape on August 21, 2015, 04:16:54 PM
Finally got the witness registered and the witness_node syncing reliably.

Code Select Expand

get_witness roadscape
{
  "id": "1.6.5249",
  "witness_account": "1.2.67334",

But haven't yet produced a block:

Code Select Expand

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.

Finally got the witness registered and the witness_node syncing reliably.

get_witness roadscape
{
  "id": "1.6.5249",
  "witness_account": "1.2.67334",

But haven't yet produced a block:
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..

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..]

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?

I was showing 16 peers on one of my nodes before it stopped working overnight2015-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$



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 :)