[Bugs] [Bug 1672318] "failed to fetch volume file" when trying to activate host in DC with glusterfs 3.12 domains

bugzilla at redhat.com bugzilla at redhat.com
Tue Mar 26 13:24:04 UTC 2019


https://bugzilla.redhat.com/show_bug.cgi?id=1672318

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(sabose at redhat.com
                   |                            |)



--- Comment #24 from Atin Mukherjee <amukherj at redhat.com> ---
[2019-03-18 11:29:01.000279] I [glusterfsd-mgmt.c:2424:mgmt_rpc_notify]
0-glusterfsd-mgmt: disconnected from remote-host: *.*.*.14

Why did we get a disconnect. Was glusterd service at *.14 not running?

[2019-03-18 11:29:01.000330] I [glusterfsd-mgmt.c:2464:mgmt_rpc_notify]
0-glusterfsd-mgmt: connecting to next volfile server *.*.*.15
[2019-03-18 11:29:01.002495] E [rpc-clnt.c:346:saved_frames_unwind] (-->
/lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fb4beddbfbb] (-->
/lib64/libgfrpc.so.0(+0xce11)[0x7fb4beba4e11] (-->
/lib64/libgfrpc.so.0(+0xcf2e)[0x7fb4beba4f2e] (-->
/lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x91)[0x7fb4beba6531] (-->
/lib64/libgfrpc.so.0(+0xf0d8)[0x7fb4beba70d8] ))))) 0-glusterfs: forced
unwinding frame type(GlusterFS Handshake) op(GETSPEC(2)) called at 2019-03-18
11:13:29.445101 (xid=0x2)

The above log seems to be the culprit here. 

[2019-03-18 11:29:01.002517] E [glusterfsd-mgmt.c:2136:mgmt_getspec_cbk]
0-mgmt: failed to fetch volume file (key:/ssd9)

And the above log is the after effect.


I have few questions:

1. Does the mount fail everytime?
2. Do you see any change in the behaviour when the primary volfile server is
changed?
3. What are the gluster version in the individual peers?

(Keeping the needinfo intact for now, but request Sahina to get us these
details to work on).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list