Are you still stuck with the error ‘glusterfs transport endpoint is not connected’? We can help you in fixing it.

GlusterFS is a distributed file system which mainly reduces the size of the data.

Here at Bobcares, we often receive requests to fix GlusterFS errors as a part of our Server Management Services.

Today, let’s discuss about what causes this error and also see how our Support Engineers fix this error.

What causes the transport endpoint connection to fail?

We’ve seen many of our customers experiencing this error. However, this error can occur due to many reasons which include:

• There is no port open for proper communication between the bricks.
• A firewall can also be a problem.

Now, let’s see how our Support Engineers fix this error for our customers.

How we fix the error ‘glusterfs transport endpoint is not connected’?

Recently, we came across an error relating to GlusterFS.

The customer wanted to verify about whether the write/read ops permission when one storage node is down.

After killing the gluster processes on one of the non-arbiter nodes (using pkill ^gluster*) the client mount point fails with the error message.

Transport endpoint is not connect

Glusterfs-client is already set on Ubuntu. Here is the Gluster volume information in the screenshot.

We found that the operations on the client-side fail with this error message.

Our Support Engineers started troubleshooting the error by checking the glusterfs-client log file.

Then we found that these additional options were set:

gluster volume set brick01 cluster.quorum-reads false
gluster volume set brick01 cluster.quorum-count 1

Also, we found that by default arbiter brick was failing to heal (sync) simultaneously when any file operation occurs. So we reconfigured the option ‘cluster.self-heal-daemon by running the below command.

gluster volume heal brick01 enable

This finally, fixed the error.

[Need any further assistance in fixing GlusterFS errors? – We’ll help you]

Conclusion

In short, the error glusterfs transport endpoint connection fails mainly due to port unavailability or firewall problems. Today, we saw how our Support Engineers fix this error.