search

minio / warp

S3 benchmarking tool
GNU Affero General Public License v3.0
571 stars 108 forks source link

Cannot connect to clients #319

Closed polatsinan closed 5 months ago

polatsinan commented 5 months ago

I have 1 server and 5 client nodes. Installed package is warp_Linux_x86_64.deb, v0.10.0.

Command on clients: 

root@client:~# warp client 0.0.0.0:7761
warp: Listening on 0.0.0.0:7761

Testing with just 1 node:

root@server:~# warp put --warp-client 10.0.0.35 --host <host> --bucket <bucket> --access-key <accesskey> --secret-key <secretkey>
warp: <ERROR> Connection failed:Forbidden, retrying...                                                                                                                                                                                                                                     

warp: <ERROR> Connection failed:Forbidden, retrying...                                                                                                                                                                                                                                     

warp: <ERROR> Connection failed:Forbidden, retrying...                                                                                                                                                                                                                                     

warp: Connecting to ws://10.0.0.35:7761/ws                                                                                                                                                                                                                                             
warp: <ERROR> Unable to send benchmark info to warp client. Forbidden.

When I am not using the --warp-client 10.0.0.35 option, the server will act as a client and that just works fine.

Using nc I can reach the client:

root@server:~# nc 10.0.0.35 7761 -v
Connection to 10.0.0.35 7761 port [tcp/*] succeeded!

With --debug I am not getting any additional information. The client doesn't show any logging, except it is listening.

The following is not showing any lines (so, it seems the server isn't even trying to reach the client):

root@client:~# tcpdump -i any port 7761 -vvv
tcpdump: data link type LINUX_SLL2
tcpdump: listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes

When tcpdump is running and I am doing a nc I see traffic is reaching the client.

polatsinan commented 5 months ago

It seems it was a network issue in my environment.