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.

Why the Harvest Network that is only showing 5 IPs?

See original GitHub issue

I have 1 main farmer and 6 harvesters, but the Harvester Network is only showing 5 IPs and one of the IPs is always switching to other harvesters’ IP. And the debug log file is showing the following INFO:

2021-05-25T08:23:50.121 farmer farmer_server              : INFO     Connection closed: 192.168.1.33, node id: 61000a61e803f93b6bd42c78913ac219bd295
2021-05-25T08:23:50.122 farmer chia.farmer.farmer         : INFO     peer disconnected {'host': '192.168.1.33', 'port': 8448}
2021-05-25T08:23:50.359 farmer farmer_server              : INFO     Connection closed: 192.168.1.36, node id: 61000a61e803f93b6bd42c78913ac219bd295
2021-05-25T08:23:50.360 farmer chia.farmer.farmer         : INFO     peer disconnected {'host': '192.168.1.36', 'port': 8448}
2021-05-25T08:23:51.324 farmer farmer_server              : INFO     Connection closed: 192.168.1.31, node id: 61000a61e803f93b6bd42c78913ac219bd295
2021-05-25T08:23:51.325 farmer chia.farmer.farmer         : INFO     peer disconnected {'host': '192.168.1.31', 'port': 8448}

I have no idea it is a bug, but the Harvester Network there actually only show 5 IPs and one IP is always switching to the rest of harvesters’ IP. Is it possible to show all harvester’s IPs at the same time?

Issue Analytics

State:
Created 2 years ago
Comments:6

Top GitHub Comments

1reaction

anguschang007commented, May 29, 2021

The issue is solved. The issue is from me because some PC’s OS was cloned from one PC and they are using the same SSL key to communicate with the farmer. Now, the SSL keys are re-inited then the issue is gone.

0reactions

anguschang007commented, May 25, 2021

And on the rest of the switching Harvesters, their Ubuntu Firewall is also blocking some incoming packets.

May 25 22:16:21 chia-7 kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:a3:80:d6:70:85:c2:8b:7f:c1:08:00 SRC=192.168.1.30 DST=192.168.1.36 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=8447 DPT=50018 WINDOW=0 RES=0x00 RST URGP=0 
May 25 22:16:45 chia-7 kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:a3:80:d6:70:85:c2:8b:7f:c1:08:00 SRC=192.168.1.30 DST=192.168.1.36 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=8447 DPT=50034 WINDOW=0 RES=0x00 RST URGP=0 
May 25 22:16:48 chia-7 kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:a3:80:d6:70:85:c2:8b:7f:c1:08:00 SRC=192.168.1.30 DST=192.168.1.36 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=8447 DPT=50036 WINDOW=0 RES=0x00 RST URGP=0

May 25 21:53:51 chia-4 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=d8:cb:8a:27:35:16:70:85:c2:8b:7f:c1:08:00 SRC=192.168.1.30 DST=192.168.1.33 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=8447 DPT=39914 WINDOW=0 RES=0x00 RST URGP=0 
May 25 21:53:54 chia-4 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=d8:cb:8a:27:35:16:70:85:c2:8b:7f:c1:08:00 SRC=192.168.1.30 DST=192.168.1.33 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=8447 DPT=39916 WINDOW=0 RES=0x00 RST URGP=0 
May 25 22:01:54 chia-4 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=d8:cb:8a:27:35:16:70:85:c2:8b:7f:c1:08:00 SRC=192.168.1.30 DST=192.168.1.33 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=8447 DPT=40242 WINDOW=0 RES=0x00 RST URGP=0

May 25 21:51:58 Chia-1 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=d8:cb:8a:05:cd:9c:70:85:c2:8b:7f:c1:08:00 SRC=192.168.1.30 DST=192.168.1.31 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=8447 DPT=41642 WINDOW=0 RES=0x00 RST URGP=0 
May 25 21:52:43 Chia-1 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=d8:cb:8a:05:cd:9c:70:85:c2:8b:7f:c1:08:00 SRC=192.168.1.30 DST=192.168.1.31 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=8447 DPT=41672 WINDOW=0 RES=0x00 RST URGP=0 
May 25 21:52:52 Chia-1 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=d8:cb:8a:05:cd:9c:70:85:c2:8b:7f:c1:08:00 SRC=192.168.1.30 DST=192.168.1.31 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=8447 DPT=41678 WINDOW=0 RES=0x00 RST URGP=0

I have no idea why the firewall is blocking the incoming packets! However, I have been already allowed the internal network data transferring.

Status: active

To                         Action      From
--                         ------      ----            
224.0.0.0/24               ALLOW       Anywhere                  
Anywhere                   ALLOW       192.168.1.0/24            
8444                       ALLOW       Anywhere                  
8447                       ALLOW       Anywhere                  
192.168.1.0/24             ALLOW       Anywhere 
8444 (v6)                  ALLOW       Anywhere (v6)             
8447 (v6)                  ALLOW       Anywhere (v6)

And allow the INVALID packets by modifying before.rules.