Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Forger with 8 relays (2)

See original GitHub issue

Describe the bug Forger with 6 relays will fail with fork 6.

Follow up of #886 bugfix.

To Reproduce Steps to reproduce the behavior:

Setup 6 relays Whitelist the forger on all 8 relays Put all 6 relays as hosts on the forger Stop all 8 relays. Wait for Forging Fork 6 Expected behavior Forging works.

Screenshots n/a

Server (please complete the following information):

OS: Ubuntu Version 18.04

Additional context

2|ark-core-forger  | [2018-08-20 15:40:26][DEBUG]                      : http://104.238.159.113:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:26][DEBUG]                      : http://198.13.38.68:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:26][DEBUG]                      : http://66.42.60.249:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:26][DEBUG]                      : http://66.42.60.249:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:27][DEBUG]                      : http://198.13.38.68:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:27][DEBUG]                      : Sending wake-up check to relay node http://127.0.0.1:4002
2|ark-core-forger  | [2018-08-20 15:40:33][DEBUG]                      : http://198.13.38.68:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:33][DEBUG]                      : http://149.28.165.214:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:33][DEBUG]                      : http://149.28.165.214:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:33][DEBUG]                      : http://45.76.94.199:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:33][DEBUG]                      : http://66.42.60.249:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:34][DEBUG]                      : http://149.28.165.214:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:34][DEBUG]                      : http://149.28.165.214:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:34][DEBUG]                      : http://198.13.38.68:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:34][DEBUG]                      : http://45.76.94.199:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:34][DEBUG]                      : http://66.42.60.249:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:35][DEBUG]                      : http://198.13.38.68:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:35][DEBUG]                      : http://45.76.94.199:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:35][DEBUG]                      : http://45.76.94.199:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:35][DEBUG]                      : http://66.42.60.249:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:35][DEBUG]                      : http://45.76.94.199:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:35][DEBUG]                      : http://104.238.159.113:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:35][DEBUG]                      : http://149.28.165.214:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:35][DEBUG]                      : http://104.238.173.32:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:35][DEBUG]                      : http://104.238.159.113:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:36][DEBUG]                      : http://149.28.165.214:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:36][DEBUG]                      : http://198.13.38.68:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:36][INFO]                       : Fork 6 - Not enough quorum to forge next block.
2|ark-core-forger  | [2018-08-20 15:40:36][DEBUG]                      : Network State: {"quorum":0,"nodeHeight":182870,"lastBlockId":"2131554865183332057","overHeightBlockHeader":null,"minimumNetworkReach":true,"coldStart":false}
2|ark-core-forger  | [2018-08-20 15:40:43][DEBUG]                      : http://104.238.159.113:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:43][DEBUG]                      : http://104.238.173.32:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:43][DEBUG]                      : http://149.28.165.214:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:43][DEBUG]                      : http://104.238.173.32:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:43][DEBUG]                      : http://66.42.60.249:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:43][DEBUG]                      : http://45.76.94.199:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:43][DEBUG]                      : http://104.238.159.113:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:43][DEBUG]                      : http://104.238.173.32:4002 didn't respond to the forger. Trying another host 🎇
2|ark-core-forger  | [2018-08-20 15:40:43][DEBUG]                      : http://104.238.173.32:4002 didn't respond to the forger. Trying another host 🎇

Issue Analytics

State:
Created 5 years ago
Comments:13 (10 by maintainers)

Top GitHub Comments

1reaction

kristjankcommented, Aug 22, 2018

this should keep multiple relays working and not loosing time… i.e. when we syncCheck (meaning choose a host and select it - we keep it until forging is done - i.e. no host choosing in between for network state and getTransactions)…

https://github.com/ArkEcosystem/core/pull/904

1reaction

faustbriancommented, Aug 22, 2018

Feel free to send a PR with any improvements.

Top Results From Across the Web

Web SNMP controlled 8 Relay Board with DAEnetIP2v2

This is kit of DAEnetIP2 v2 IP Controller and card with 8 SPDT relays. It is for home automation, hobby and commercial projects....

SainSmart 8-Channel Relay Module - Amazon.com

- This 8 channel 5V relay has both optical and magnetic isolation, providing a lot of protection to the inputs from electrical faults...

The Forge Ultra 50K / 50K Relay - RunSignup

The race will utilize two different courses, run in segments by individual or relay team members. Total Course Length = ~ 50K /...

Eaton 31M-000-2 Mulitplex Vehicle Electrical Center, 8 ...

Eaton 31M-000-2 Mulitplex Vehicle Electrical Center (mVEC), 8 relays, 16 Fuses · (8) - ISO Micro Relay with Resistor · NO Amp: 35A...

8 RELAYS 8-layer stackable card for RASPBERRY PI

Eight RELAYS with Status LEDs and NO/NC contacts; Eight layer stackable to 64 relays; Pluggable Connectors 26-16 AWG wires; 120VAC/4A or 24VDC/4A on...