Your client hanging at the point where it first tries to use the database implies that it is not successfully able to connect. The most common reasons for this would be:
- You are using a different
fdb.cluster file that doesn’t match the cluster
- You are using a client library (e.g.
libfdb_c.so on linux) that is not compatible with the cluster (they need to have the same major minor version, such as 6.2).
There are other possibilities as well, such your client being unable to reach the server over the network (less likely if you are running
fdbcli from the same place) or an issue with TLS configuration.
It looks like your
fdbcli run is getting its cluster file from the current working directory. Are you running your Python program from the same directory? If not, then it’s worth checking that the cluster file it’s loading has the same contents (see Administration — FoundationDB 6.2).
One other way you can get a sense for what’s happening is to turn on trace logging for your client:
After you’ve terminated your program, you can check the log file (trace*.xml) for events that suggest what is happening. If it can’t connect at all, I believe you’ll see a
ConnectionTimedOut event. If it gets rejected for being incompatible, you’ll instead see something like