Closed fbarbu15 closed 5 months ago
This error happens because when we restart the lightpush service node container (container_id1
) a new multiaddress is generated, so the lightpush client node is trying to dial the old multiaddress with no response.
To fix that, we have to start the service node with the --nodekey
parameter.
For example, using '--nodekey=6a29e767c96a2a380bb66b9a6ffcd6eb54049e14d796a1d866307b8beb7aee58'
That is, replacing line 15 in the script for
container_id1=$(docker run -d -i -t -p 37343:37343 -p $tcp_port:$tcp_port -p 37345:37345 -p 37346:37346 -p 37347:37347 $node_1 --listen-address=0.0.0.0 --rest=true --rest-admin=true --websocket-support=true --log-level=TRACE --rest-relay-cache-capacity=100 --websocket-port=37345 --rest-port=37343 --tcp-port=$tcp_port --discv5-udp-port=37346 --rest-address=0.0.0.0 --nat=extip:$ext_ip --peer-exchange=true --discv5-discovery=true --cluster-id=$cluster_id --metrics-server=true --metrics-server-address=0.0.0.0 --metrics-server-port=37347 --metrics-logging=true --pubsub-topic=/waku/2/rs/2/0 --lightpush=true --relay=true --nodekey=6a29e767c96a2a380bb66b9a6ffcd6eb54049e14d796a1d866307b8beb7aee58)
We avoid having a new multiaddress generated after container restart, and there's no more dial failures anymore
@fbarbu15 please confirm if it makes sense and works for you too
thanks, this fixes the test!
To reproduce
Expected behavior
Should work
Actual behavior
Failed to request a message push: dial_failure
Script to reproduce it:
Logs lightpush_node.log relay_node.log