Nodes gets a new external IP, and then fails

If I move my Windows Server Node, and it gets a new external IP address. The node stops working. I remove the node in windows, and reinstall. But is there a workaround ?

1 Like

If your network address changes then this may affect incoming connections to the node, but generally it should not stop working altogether. Perhaps you could give more details of what exactly you are experiencing?

In any case, it should generally not be necessary to remove and reinstall the node. Instead, stopping and restarting the node service should be sufficient. If after that the node fails to start, it most likely indicates a corrupted database, which requires deleting (part of) the node’s database before restarting it. If you are experiencing corruption each time you move your node, then stopping the service before the move and restarting it after would be likely to help avoid this.

There is an issue with a new IP. To day I tested my node, moved it from Telenor IP, to Energi Fyn IP, and the internal IP is the same. Shut down the node, made a restart, but i does not show up i the block explorer.

2022-01-12T18:11:11.123955700+01:00 ERROR concordium_node::p2p::connectivity - [sending to 62.199.73.68:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T18:11:11.139900500+01:00 ERROR concordium_node::p2p::connectivity - [sending to 83.249.169.130:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T18:11:11.149847+01:00 ERROR concordium_node::p2p::connectivity - [sending to 176.22.228.114:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T18:11:11.149978800+01:00 ERROR concordium_node::p2p::connectivity - [sending to 35.198.158.74:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T18:11:11.150134800+01:00 ERROR concordium_node::p2p::connectivity - [sending to 87.59.136.173:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T18:11:11.170655100+01:00 ERROR concordium_node::p2p::connectivity - [sending to 104.45.2.197:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T18:11:11.170802900+01:00 ERROR concordium_node::p2p::connectivity - [sending to 121.172.20.53:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)

2022-01-12T19:58:25.823934900+01:00 ERROR concordium_node::p2p::connectivity - [sending to 185.107.13.57:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T19:58:25.839579200+01:00 ERROR concordium_node::p2p::connectivity - [sending to 213.32.243.159:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T19:58:25.870788300+01:00 ERROR concordium_node::p2p::connectivity - [sending to 87.6.112.45:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T19:58:55.834132600+01:00 ERROR concordium_node::p2p::connectivity - [sending to 121.172.20.53:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T19:58:55.834268100+01:00 ERROR concordium_node::p2p::connectivity - [sending to 37.120.131.78:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T19:58:55.834384300+01:00 ERROR concordium_node::p2p::connectivity - [sending to 84.72.112.224:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T19:58:55.865464100+01:00 ERROR concordium_node::p2p::connectivity - [sending to 31.10.145.39:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T19:59:34.595952600+01:00 ERROR concordium_node::p2p::maintenance - Could not measure throughput: Received bytes were lost. Refusing to calculate average throughput.
2022-01-12T20:06:35.138197300+01:00 ERROR concordium_node::p2p::maintenance - Could not measure throughput: Received bytes were lost. Refusing to calculate average throughput.
2022-01-12T20:06:56.388855700+01:00 ERROR concordium_node::p2p::connectivity - [sending to 213.55.244.98:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:06:56.388991800+01:00 ERROR concordium_node::p2p::connectivity - [sending to 20.126.47.192:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:06:56.389109+01:00 ERROR concordium_node::p2p::connectivity - [sending to 124.121.183.29:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:06:56.389225500+01:00 ERROR concordium_node::p2p::connectivity - [sending to 77.33.35.164:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:06:56.420668400+01:00 ERROR concordium_node::p2p::connectivity - [sending to 176.234.225.101:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:11:05.559813900+01:00 ERROR concordium_node::p2p::maintenance - Could not measure throughput: Received bytes were lost. Refusing to calculate average throughput.
2022-01-12T20:11:26.795957500+01:00 ERROR concordium_node::p2p::connectivity - [sending to 213.55.244.98:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:11:26.796100200+01:00 ERROR concordium_node::p2p::connectivity - [sending to 31.10.145.39:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:11:26.796220400+01:00 ERROR concordium_node::p2p::connectivity - [sending to 20.76.133.36:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:11:26.796379100+01:00 ERROR concordium_node::p2p::connectivity - [sending to 185.107.13.57:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:11:26.875690400+01:00 ERROR concordium_node::p2p::connectivity - [sending to 89.3.78.187:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:14:05.796179600+01:00 ERROR concordium_node::p2p::maintenance - Could not measure throughput: Received bytes were lost. Refusing to calculate average throughput.
2022-01-12T20:14:26.876115200+01:00 ERROR concordium_node::p2p::connectivity - [sending to 178.237.46.147:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:14:26.876253600+01:00 ERROR concordium_node::p2p::connectivity - [sending to 80.167.75.164:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:14:26.876368300+01:00 ERROR concordium_node::p2p::connectivity - [sending to 46.63.5.156:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:14:26.922999800+01:00 ERROR concordium_node::p2p::connectivity - [sending to 5.186.53.32:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:14:26.954221+01:00 ERROR concordium_node::p2p::connectivity - [sending to 89.3.78.187:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)
2022-01-12T20:14:27.219891100+01:00 ERROR concordium_node::p2p::connectivity - [sending to 104.45.2.197:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)

The only thing that was changed, was the ip address.

Hi GSM,

These error messages indicate that some of the connections your node had to its peers have been dropped.
The node will automatically remove peers that are no longer responding after a bit, and then the messages will disappear (unless a new peer drops the connection, of course).

Are you still seeing these messages in the logs?

Best regards,
Kasper

Hello, yes there are lots of same messages in the log.

HI, now i have been doing at lot of testing. And the problem is Windows 2019, server, When i use Windows 10/11 or Ubuntu as a node, i can move from 1 to another external IP without any problems.

Thanks for letting us know. Perhaps there is some difference in how the network adapter is configured in Windows Server as opposed to other versions? (route print might give some indication if there is some difference in routing.)

Hi guys, did you get to the core of this error?

I am seeing a lot of these messages:
2022-02-20T17:42:44.812968200+01:00 ERROR concordium_node::p2p::connectivity - [sending to 79.78.40.101:8888] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (os error 10057)

I’m running a Win 10 node.
Port 8888 is forwarded to node.

Just wanna be a good citizen :slight_smile:
Tim

Hi Tim,

Aside from this error, are you seeing problems with your node? This error can occur if the connection drops for various reasons.

Hi Thomas,
no apart from that the node seem to be doing its job.
We’ll just leave it, cheers,
Tim