why so many fork???

[Thom]

so bad I have set the log lever to "error"
there is totally no log except the output to the console

I ran into some logging anomalies myself and ended up with no logs at all. I forgot how I resolved that.

[alt]

so bad I have set the log lever to "error"
there is totally no log except the output to the console

[Fox]

Respectfully, may I request you @alt to review your P2P logs to determine if the multiple blocks received contain distinct hashes? Is it possible your P2P node(s) are receiving the same block multiple times? I hope to isolate our troubleshooting to either the block generation side or the P2P transport/receipt side.

If you can identify blocks from a given witness with distinct block hashes, this would indicate generation issues, introducing a deliberate fork.

Best,
Fox

[Thom]

Sorry you're experiencing these difficulties @alt.

In the future if you have such an (urgent) issue please use Telegram to reach witnesses more effectively and timely, as that is real-time communications.
 

[alt]

sorry I'm busy on handle the fork issue for btsbots.com
I thought you have enable two nodes at the beginning
if it's not, I have no idea what happened
almost all bots from btsbots.com  failed when the fork happend again and again

I have to improve the code of btsbots.com to handle all these fork ASAP.

[Fox]

Can you elaborate on what you believe is going on? Are witnesses malfunctioning/misbehaving?

This is the witness node that generated the block(s) in question:

Code: [Select]

get_witness fox
{
  "id": "1.6.16",
  "witness_account": "1.2.167",
  "last_aslot": 15771235,
  "signing_key": "BTS5WsSbrh5tcF77d524MXHGkJoRgj2nSuK6KWfuM1hnv9VDgy7F5",
  "pay_vb": "1.13.32",
  "vote_id": "1:26",
  "total_votes": "72686675707190",
  "url": ".",
  "total_missed": 2892,
  "last_confirmed_block_num": 15672555
}


Code: [Select]

about
{
  "client_version": "2.0.161031-53-g4dc1001",
  "graphene_revision": "4dc1001a9b8be9bba9c1b45221371283cb9a750a",
  "graphene_revision_age": "21 weeks ago",
  "fc_revision": "31adee49d91275cc63aa3a47b3a9e3c826baccca",
  "fc_revision_age": "55 weeks ago",
  "compile_date": "compiled on Dec 29 2016 at 22:52:26",
  "boost_version": "1.58",
  "openssl_version": "OpenSSL 1.0.2g  1 Mar 2016",
  "build": "linux 64-bit"
}

Each of my other witness nodes contain distinct signing keys, therefore I can guarantee that only a single [witness_node] program is able to generate a block. My logs do not indicate generating multiple blocks as indicated by your P2P log.

I am keen to determine why this occurring.

[Thom]

@alt, can you not get on Telegram witness alert channel?

[Thom]

The output of node does not indicate 2 blocks generated. A bug in code brought on by volume? Seems highly unlikely.

[Thom]

What makes you so sure the issue is with us? Logs log fine, just published feeds, memory fine, ~30 network connections, normal from what I have observed for quite a while now.

[alt]

these witness generate 2 block at the same time, so we got fork again and again
I don't know what's wrong with them

[Thom]

Indeed, please explain yourself

[R]

Can you elaborate on what you believe is going on? Are witnesses malfunctioning/misbehaving?

[alt]

WTF are you doing?

[alt]

and  xn-delegate xman
2880314ms th_a       application.cpp:523           handle_block         ] Got block: #15658874 time: 2017-04-14T00:48:00 latency: 321 ms from: xn-delegate  irreversible: 15658857 (-17)
2881009ms th_a       application.cpp:523           handle_block         ] Got block: #15658874 time: 2017-04-14T00:48:00 latency: 1016 ms from: xn-delegate  irreversible: 15658859 (-15)
2709246ms th_a       application.cpp:523           handle_block         ] Got block: #15658817 time: 2017-04-14T00:45:09 latency: 253 ms from: xman  irreversible: 15658802 (-15)
2709467ms th_a       application.cpp:523           handle_block         ] Got block: #15658817 time: 2017-04-14T00:45:09 latency: 474 ms from: xman  irreversible: 15658803 (-14)

[alt]

and verbaltech2

2966554ms th_a       application.cpp:523           handle_block         ] Got block: #15658902 time: 2017-04-14T00:49:24 latency: 2536 ms from: verbaltech2  irreversible: 15658887 (-15)
2966639ms th_a       application.cpp:523           handle_block         ] Got block: #15658902 time: 2017-04-14T00:49:24 latency: 2646 ms from: verbaltech2  irreversible: 15658888 (-14)