TF_E_CLIENT_IPC error with Linux client (4.1.9.0)

One of our customers is receiving the error TF_E_CLIENT_IPC on a system that was recently working. Their installation is a Linux cluster of identical machines and most of the machines are able to fetch a lease. Until recently the whole system was working, but now one or two machines has developed this problem. The failure also doesn't happen for every user account on the system; another user is able to request a lease on the affected systems. Both the client and license server are TF release 4.1.9.0.

Is that enough detail to have an idea of what might be happening here? I suspect a local file or other IPC resource used by TF might be corrupted, but I don't know where to look for something like that. We did remove the hidden file created by TF_SaveServer() in "$HOME/.TurboFloat" to see if that might help, but the behavior didn't change.

Start by upgrading the TFS, and then all TF library instances on that machine. Then try again. If you're still having problems try to create a reproducible example.

Also, don't mix-and-match TF library versions. Your app on any particular machine should all use the same (preferably the newest) version of the TF library. Don't have some instances use old TF library versions and some use new TF library versions.

The consequence of mixing-and-matching? TF_E_CLIENT_IPC (or other errors, depending on the circumstances).

Reply
Discard post