Connection was broken (all connections)

GRIDNET OS - Main Help Line
1

I know you are saying the “connection was broken” is standard, but I have nothing mined in the past week.
I have 1 more exactly the same machine, and I do mining with profits there, so I believe something is wrong.

appreciate any ideas that possibly could help me. thanks!

 [Bootstrap grace period]: Withholding block formation.. 310 sec.
 Ingress UDT conversation with 94.75.125.6 has begun.
 Ingress UDT conversation with 83.126.40.74 has begun.
 Ingress UDT conversation with 45.129.56.134 has begun.
 [UDT Error] for: UDT(3YVNWfrnt98yppKF9)  Reason: Connection was broken
 [DSM-sync]: establishing connection with: 193.143.121.226
 [UDT]: connecting to 193.143.121.226
 [UDT]: connected with 193.143.121.226
 Outgress UDT conversation with 193.143.121.226 has begun.
 Ingress UDT conversation with 5.185.117.226 has begun.
 [Vitals Monitoring]: Your CPU is running HOT!
 [UDT Error] for: UDT(5WnyMDcokxocboLEk)  Reason: Connection was broken
 Ingress UDT conversation with 185.232.80.207 has begun.
 [Bootstrap grace period]: Withholding block formation.. 305 sec.
 [Network Manager]: Network Threads:52
  -- Registered Swarms: 1 --
1) [Local Peers]: 0 [Remote Peers]: 0
 -----------------------

 [UDT Error] for: UDT(3vWUvRvNqfTRM6hFv)  Reason: Connection was broken
 [UDT Error] for: UDT(Q9D2ogHTwXxHxN2j)  Reason: Connection was broken
 Ingress UDT conversation with 91.218.113.144 has begun.
 Ingress UDT conversation with 185.237.158.114 has begun.
 Ingress UDT conversation with 109.125.255.72 has begun.
 [Kademlia: Reports] - aware of 17 nodes.
 [UDT Error] for: UDT(5HouhUvT9PPizyNw2)  Reason: Connection was broken
 Ingress UDT conversation with 213.76.108.243 has begun.
2 

 [Vitals Monitoring]: All looking Good.
 [UDT Error] for: UDT(2iKsKnP7eNkvx9Le6)  Reason: Operation not supported: Invalid socket ID
 Ingress UDT conversation with 83.7.154.26 has begun.
 [Network Manager]: Network Threads:48
 [UDT Error] for: UDT(2HnbFVns5iMkvKJWo)  Reason: Connection was broken
 Ingress UDT conversation with 45.134.222.51 has begun.
 [UDT Error] for: UDT(5fqE4nsdBGfduAxq8)  Reason: Connection was broken
 Ingress UDT conversation with 82.46.236.248 has begun.
 [Kademlia: Reports] - aware of 36 nodes.
 [UDT Error] for: UDT(RLjusKat8MQi9r8H)  Reason: Connection was broken
 Ingress UDT conversation with 216.205.168.31 has begun.
 [DSM Sync]:  processing chain-proof request from 194.247.182.40.
 [DSM Sync]:  constructed partial chain-proof for 194.247.182.40.
 [Vitals Monitoring]: All looking Good.
 Ingress UDT conversation with 94.75.125.6 has begun.
 [TestNet:Transaction Manager]: Min. # of objects for block formation: 1
 Ending 1 duplicate UDT connections..
 [Security]: Max connection time with 185.89.248.45 reached. Killing it.
 [Security]: Max connection time with 185.232.80.207 reached. Killing it.
 [Security]: Max connection time with 213.76.108.243 reached. Killing it.
 [Security]: Max connection time with 212.108.232.134 reached. Killing it.
3

Thank you for your report.

Recently we’ve spotted attacks targeting the very UDT layer of our system.

The above may or may not be related.

We advise the below mitigation measures:

  • make sure you are running same identity (mining wallet) only from a single computer.

  • one Operating Identity may be available only from a single public IP address

While ‘broken connections’ do not necessarily mean that your node is affect in any way it is always best to keep researching the underlying cause.

4 
 [TestNet:Blockchain Manager]: Freed 2 UDT Conversations
 [UDT Error] for: UDT(4rd6b1aY2uL872r2S)  Reason: Connection was broken
 [UDT Error] for: UDT(5G76ai4qn9timhpUx)  Reason: Connection was broken
 Ingress UDT conversation with 185.237.158.114 has begun.
 [UDT Error] for: UDT(4GxmDiRceUPHZaVTc)  Reason: Connection was broken
 Ingress UDT conversation with 85.187.182.240 has begun.
 [UDT Error] for: UDT(2uxkcTjbjgmVs9GW2)  Reason: Connection was broken
 [DSM-sync]: establishing connection with: 195.162.68.138
 [UDT]: connecting to 195.162.68.138
 [DSM-sync]: establishing connection with: 74.88.18.208

image
0 zero mined for 3 weeks.
GPU AMD 7900
can i get any advice, help pls?
.exe file from wizard added as well

5

This should have been fixed by now. Let us know.

6

yes. it is fixed. i have new problem now, so i will open new topic :smiley: