Bug 820673 - glusterd crash when unable to resolve hostname
glusterd crash when unable to resolve hostname
Product: GlusterFS
Classification: Community
Component: glusterd (Show other bugs)
Unspecified Unspecified
low Severity medium
: ---
: ---
Assigned To: Kaushal
Depends On:
  Show dependency treegraph
Reported: 2012-05-10 12:20 EDT by Joe Julian
Modified: 2012-06-05 05:13 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-05 05:13:55 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1002560 None None None Never

  None (edit)
Description Joe Julian 2012-05-10 12:20:56 EDT
This crash from the IRC channel this morning.

[2012-05-10 11:13:20.290505] I [glusterfsd.c:1493:main] 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 3.2.6
[2012-05-10 11:13:20.292919] I [glusterd.c:550:init] 0-management: Using /etc/glusterd as working directory
[2012-05-10 11:13:20.294797] C [rdma.c:3934:rdma_init] 0-rpc-transport/rdma: Failed to get IB devices
[2012-05-10 11:13:20.294901] E [rdma.c:4813:init] 0-rdma.management: Failed to initialize IB Device
[2012-05-10 11:13:20.294931] E [rpc-transport.c:742:rpc_transport_load] 0-rpc-transport: 'rdma' initialization failed
[2012-05-10 11:13:20.294960] W [rpcsvc.c:1288:rpcsvc_transport_create] 0-rpc-service: cannot create listener, initing the transport failed
[2012-05-10 11:13:20.295121] I [glusterd.c:88:glusterd_uuid_init] 0-glusterd: retrieved UUID: 9cab7843-ff14-4c64-bdb9-d7f0588d4041
[2012-05-10 11:13:20.322226] E [common-utils.c:125:gf_resolve_ip6] 0-resolver: getaddrinfo failed (No address associated with hostname)
[2012-05-10 11:13:20.322298] E [name.c:253:af_inet_client_get_remote_sockaddr] 0-management: DNS resolution failed on host BTGlusterPC4
pending frames:
patchset: git://git.gluster.com/glusterfs.git
signal received: 11
time of crash: 2012-05-10 11:13:20
configuration details:
argp 1
backtrace 1
dlfcn 1
fdatasync 1
libpthread 1
llistxattr 1
setfsid 1
spinlock 1
epoll.h 1
xattr.h 1
st_atim.tv_nsec 1
package-string: glusterfs 3.2.6
Comment 1 Joe Julian 2012-05-21 18:41:29 EDT
This should not be a crash, but it should fail gracefully.

The problem arises from using NetworkManager to manage the network. Using static upstart managed network configuration should not produce this problem.
Comment 2 Amar Tumballi 2012-05-28 06:21:50 EDT
Kaushal, Check if this is still valid bug on master/release-3.3
Comment 3 Kaushal 2012-06-05 02:42:35 EDT
Doesn't happen on 3.3, on a failure of hostname resolution, the peer is marked as disconnected and glusterd continues its operation. A snippet of the glusterd log file is below

[2012-06-05 12:02:59.120357] D [rpc-transport.c:248:rpc_transport_load] 0-rpc-transport: attempt to load file /usr/local/lib
[2012-06-05 12:03:00.132951] E [common-utils.c:125:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Name or service not known
[2012-06-05 12:03:00.133021] E [name.c:245:af_inet_client_get_remote_sockaddr] 0-management: DNS resolution failed on host arch3
[2012-06-05 12:03:00.133049] D [glusterd-handler.c:2886:glusterd_peer_rpc_notify] 0-management: got RPC_CLNT_DISCONNECT 3
Comment 4 Kaushal 2012-06-05 05:13:55 EDT
Closing as this is fixed upstream in release-3.3

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