Bug 1631437 - Mount process hangs if remote server is unavailable
Summary: Mount process hangs if remote server is unavailable
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: rpc
Version: mainline
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Rinku
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-20 14:55 UTC by steven8354
Modified: 2020-03-12 12:56 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-12 12:56:22 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description steven8354 2018-09-20 14:55:08 UTC
Description of problem:
Mount process hangs if the remote file server is unavailable.

Version-Release number of selected component (if applicable):
3.12.6 and 3.8.13

How reproducible:
I can only reproduce this in our production environment and it happens 100% of the time there.  Every testing environment i've tried works as expected.


Steps to Reproduce:
1. mount -t glusterfs glusterfs.example.com:/volume-name /mnt/test


Actual results:
Process hangs and has to be sent a SIGKILL.


Expected results:
Process ends and returns "Mount failed. Please check the log file for more details"


Additional info:
Log information

[2018-09-07 19:56:06.533943] E [MSGID: 101075] [common-utils.c:294:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Name or service not known)
[2018-09-07 19:56:06.534061] E [name.c:262:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution failed on host glusterfs.example.com
[2018-09-07 19:56:06.535370] I [timer.c:212:gf_timer_registry_init] (-->/usr/lib64/libglusterfs.so.0(+0x36bb6) [0x7fba8ad51bb6] -->/usr/lib64/libgfrpc.so.0(rpc_clnt_reconnect+0x11f) [0x7fba8ab0f56f] -->/usr/lib64/libglusterfs.so.0(gf_timer_call_after+0x238) [0x7fba8ad51958] ) 0-timer: ctx cleanup started
[2018-09-07 19:56:06.535587] E [timer.c:44:gf_timer_call_after] (-->/usr/lib64/libglusterfs.so.0(+0x36bb6) [0x7fba8ad51bb6] -->/usr/lib64/libgfrpc.so.0(rpc_clnt_reconnect+0x11f) [0x7fba8ab0f56f] -->/usr/lib64/libglusterfs.so.0(gf_timer_call_after+0x280) [0x7fba8ad519a0] ) 0-timer: !reg
[2018-09-07 19:56:06.535777] E [rpc-clnt.c:433:rpc_clnt_reconnect] 0-glusterfs: Error adding to timer event queue


OS is Centos6.6

Comment 1 Shyamsundar 2018-10-23 14:53:56 UTC
Release 3.12 has been EOLd and this bug was still found to be in the NEW state, hence moving the version to mainline, to triage the same and take appropriate actions.

Comment 3 Worker Ant 2020-03-12 12:56:22 UTC
This bug is moved to https://github.com/gluster/glusterfs/issues/971, and will be tracked there from now on. Visit GitHub issues URL for further details


Note You need to log in before you can comment on or make changes to this bug.