Main Menu

Test Net for Advanced Users

Started by bytemaster, August 14, 2015, 10:39:33 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

spartako

I have found this error in my witness:


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?
wallet_account_set_approval spartako

lafona

BTS Witnesses: delegate-1.lafona     Witness Thread: [url="https://bitsharestalk.org/index.php/topic,21569.msg280911/topicseen.html#msg280911"]https://bitsharestalk.org/index.php/topic,21569.msg280911/topicseen.html#msg280911[/url]
MUSE Witness: lafona

puppies

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 cmake . instead of cmake -DCMAKE_BUILD_TYPE=Debug but that didn't help. Also if it is helpful to anyone the loop is 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.

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

[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

lafona

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 cmake . instead of cmake -DCMAKE_BUILD_TYPE=Debug but that didn't help. Also if it is helpful to anyone the loop is 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.
BTS Witnesses: delegate-1.lafona     Witness Thread: [url="https://bitsharestalk.org/index.php/topic,21569.msg280911/topicseen.html#msg280911"]https://bitsharestalk.org/index.php/topic,21569.msg280911/topicseen.html#msg280911[/url]
MUSE Witness: lafona

xeroc

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.

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!

puppies

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.

0 exception: unspecified
3030001 tx_missing_active_auth: missing required active authority
Missing Active Authority 1.2.63353
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Xeldal

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

xeroc

@betax: could you put your tutorial into the github wiki please? If not, may I do it for you?

puppies

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.
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Xeldal

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%

puppies

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. 
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

cryptosile

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.

spartako

Quote from: puppies on August 23, 2015, 01:30:28 PM
That's odd spartako I see 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!!!
wallet_account_set_approval spartako

puppies

That's odd spartako I see 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.
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

spartako

#477
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:


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?
wallet_account_set_approval spartako