Gluster users - Feb 2016 - Troubleshooting Gluster Client Mount Disconnection

I am new user / admin of  Gluster.

I am involved in a support issue where access to a gluster mount fails and the
error is displayed when users attempt to access the mount:  -bash: cd: /app/:
Transport endpoint is not connected
A reboot restores the access to the gluster mount since there is an fstab entry.
After an undetermined amount of time the mount is "lost"

There are 2 client Centos servers configured to establish an NFS mount to
gluster volumes upon boot in the fstab.
Each have three mounts to gluster.

/u
/app
/claimsdata



*         Server A has not experienced any issues on any of the mounts.

*         Server B loses the mount to /app. The other two mounts are not
affected.


Client Info:
Centos
fuse init (API version 7.14)

REQUEST:
Any feedback on where to look in client logs for details on this failure would
be appreciated.

I am pursuing this from the view that Server B has an issue since Server A has
no issues.
I think the issue is with the client and not the gluster instance.

Thanks!

Won




IMPORTANT NOTICE: This communication, including any attachment, contains
information that may be confidential or privileged, and is intended solely for
the entity or individual to whom it is addressed.  If you are not the intended
recipient, you should delete this message and are hereby notified that any
disclosure, copying, or distribution of this message is strictly prohibited. 
Nothing in this email, including any attachment, is intended to be a legally
binding signature.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160219/e79980d2/attachment.html>

On 02/20/2016 02:08 AM, Takemura, Won wrote:
> I am new user / admin of  Gluster.
>
> I am involved in a support issue where access to a gluster mount fails
> and the error is displayed when users attempt to access the mount:
>   -bash: cd: /app/: Transport endpoint is not connected
This error is typically thrown when the connection to gluster volume 
brick processes is lost. Could you check the status of the bricks of 
that volume when this issue is seen. For nfs-mounts check if the volume 
is still exported using the command 'showmount -e <server_ip>'.

The logs are copied to '/var/log/glusterfs' folder.

For issues with nfs-mount, look at '/var/log/glusterfs/nfs.log' and for 
brick logs, check '/var/log/glusterfs/bricks/*'

Thanks,
Soumya
>
> A reboot restores the access to the gluster mount since there is an
> fstab entry.
>
> After an undetermined amount of time the mount is ?lost?
>
> There are 2 client Centos servers configured to establish an NFS mount
> to gluster volumes upon boot in the fstab.
>
> Each have three mounts to gluster.
>
> /u
>
> /app
>
> /claimsdata
>
> ?Server A has not experienced any issues on any of the mounts.
>
> ?Server B loses the mount to /app. The other two mounts are not affected.
>
> *Client Info:*
>
> Centos
>
> fuse init (API version 7.14)
>
> *REQUEST:*
>
> Any feedback on where to look in client logs for details on this failure
> would be appreciated.
>
> I am pursuing this from the view that Server B has an issue since Server
> A has no issues.
>
> I think the issue is with the client and not the gluster instance.
>
> Thanks!
>
> Won
>
> IMPORTANT NOTICE: This communication, including any attachment, contains
> information that may be confidential or privileged, and is intended
> solely for the entity or individual to whom it is addressed. If you are
> not the intended recipient, you should delete this message and are
> hereby notified that any disclosure, copying, or distribution of this
> message is strictly prohibited. Nothing in this email, including any
> attachment, is intended to be a legally binding signature.
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>