Issues with V6.2 TLS Cluster

Using FoundationDB
3

Hi AJ,

I checked the port 4500. I believe it’s not in use.

root@tls62wt222-storage-01-7fdf658588-m8w5l:~# netstat -peanut
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode       PID/Program name
tcp        0      0 10.104.193.72:4501      0.0.0.0:*               LISTEN      105        2489893358  -               
root@tls62wt222-storage-01-7fdf658588-m8w5l:~#

Note: You may notice the IP above is different from my previous post. That’s becuase I rebuilt a new Docker image with the netstat utility in order to see ports in use, and created a new fdb cluster (tls62wt222).

From the fdb trace files, we suspect the following 2 issues:

  • The “4500:tls” process was not able to be started.
  • The “make_public.py -t” cmd made “4500:tls”, but didn’t make 4501 as tls.

I’d like upload the trace files for your reference, but it seems only image files can be uploaded to the forum.

Thank you.

Leo