search for: rpc_clnt_reconnect

Displaying 17 results from an estimated 17 matches for "rpc_clnt_reconnect".

TCP connection incresement when reconfigure and question about multi-graph
2011 Apr 07
0
TCP connection incresement when reconfigure and question about multi-graph
...0 0 127.0.0.1:1020 127.0.0.1:6998 ESTABLISHED 8595/glusterfs lookup at the example above, the TCP connection increased by 3. I wonder if this is the normal? Further, I checked the log of client, and found something like this: [2011-04-07 11:28:06.92451] T [rpc-clnt.c:405:rpc_clnt_reconnect] 0-client0: breaking reconnect chain [2011-04-07 11:28:06.92596] T [rpc-clnt.c:405:rpc_clnt_reconnect] 0-client1: breaking reconnect chain [2011-04-07 11:28:06.92648] T [rpc-clnt.c:405:rpc_clnt_reconnect] 0-client2: breaking reconnect chain [2011-04-07 11:29:05.101120] T [rpc-clnt.c:405:rpc_cln...
peer probe failures
2017 Jun 15
1
peer probe failures
...t-ping.c:281:rpc_clnt_start_ping] 0-glusterfs: ping timeout is 0, returning [2017-04-03 22:20:24.705723] D [MSGID: 0] [event-epoll.c:591:event_dispatch_epoll_handler] 0-epoll: generation bumped on idx=1 from gen=1 to slot->gen=2, fd=7, slot->fd=7 [2017-04-03 22:20:27.614881] T [rpc-clnt.c:418:rpc_clnt_reconnect] 0-glusterfs: attempting reconnect [2017-04-03 22:20:27.615151] T [socket.c:2879:socket_connect] (--> /usr/lib/x86_64-linux-gnu/libglusterfs.so.0(_gf_log_callingfn+0x1a3)[0x7f012fd21953] (--> /usr/lib/x86_64-linux-gnu/glusterfs/3.7.6/rpc-transport/socket.so(+0x6c1b)[0x7f012a697c1b] (--> /u...
Glusterd not working with systemd in redhat 7
2017 Aug 20
2
Glusterd not working with systemd in redhat 7
...20:30:46.931469] D [socket.c:3050:socket_fix_ssl_opts] 0-glusterfs: disabling SSL for portmapper connection [2017-08-20 20:30:46.931585] I [timer.c:198:gf_timer_registry_init] (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x2ff6f) [0x7f8f703a8f6f] -->/usr/lib/x86_64-linux-gnu/libgfrpc.so.0(rpc_clnt_reconnect+0xee) [0x7f8f7016c54e] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(gf_timer_call_after+0x204) [0x7f8f703a9324] ) 0-timer: ctx cleanup started [2017-08-20 20:30:46.931626] E [timer.c:44:gf_timer_call_after] (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x2ff6f) [0x7f8f703a8f6f] -->/us...
Glusterd not working with systemd in redhat 7
2017 Aug 21
0
Glusterd not working with systemd in redhat 7
...socket.c:3050:socket_fix_ssl_opts] > 0-glusterfs: disabling SSL for portmapper connection > [2017-08-20 20:30:46.931585] I [timer.c:198:gf_timer_registry_init] > (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x2ff6f) > [0x7f8f703a8f6f] -->/usr/lib/x86_64-linux-gnu/libgfrpc.so.0(rpc_clnt_reconnect+0xee) > [0x7f8f7016c54e] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(gf_timer_call_after+0x204) > [0x7f8f703a9324] ) 0-timer: ctx cleanup started > [2017-08-20 20:30:46.931626] E [timer.c:44:gf_timer_call_after] > (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x2ff6f) > [...
gluster peer probe failing
2017 Jun 14
2
gluster peer probe failing
...s_reserved_ports+0xbe)[0x7f69625e470e] /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(+0xd158)[0x7f6954568158] /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(client_bind+0x93)[0x7f69545685a3] /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(+0xa875)[0x7f6954565875] /lib64/libgfrpc.so.0(rpc_clnt_reconnect+0xc9)[0x7f69623a3f89] /lib64/libgfrpc.so.0(rpc_clnt_start+0x39)[0x7f69623a4049] /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24218)[0x7f69570f9218] /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24843)[0x7f69570f9843] /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24ae0)[0...
gluster peer probe failing
2017 Jun 15
0
gluster peer probe failing
...4/glusterfs/3.10.3/rpc-transport/socket.so(+ > 0xd158)[0x7f6954568158] > > /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(client_bind+0x93)[ > 0x7f69545685a3] > > /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(+ > 0xa875)[0x7f6954565875] > > /lib64/libgfrpc.so.0(rpc_clnt_reconnect+0xc9)[0x7f69623a3f89] > > /lib64/libgfrpc.so.0(rpc_clnt_start+0x39)[0x7f69623a4049] > > /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+ > 0x24218)[0x7f69570f9218] > > /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+ > 0x24843)[0x7f69570f9843] > > /usr/lib64/...
gluster peer probe failing
2017 Jun 15
2
gluster peer probe failing
...s_reserved_ports+0xbe)[0x7f69625e470e] /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(+0xd158)[0x7f6954568158] /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(client_bind+0x93)[0x7f69545685a3] /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(+0xa875)[0x7f6954565875] /lib64/libgfrpc.so.0(rpc_clnt_reconnect+0xc9)[0x7f69623a3f89] /lib64/libgfrpc.so.0(rpc_clnt_start+0x39)[0x7f69623a4049] /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24218)[0x7f69570f9218] /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24843)[0x7f69570f9843] /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24ae0)[0...
gluster peer probe failing
2017 Jun 16
2
gluster peer probe failing
...ket.so(+0xd158) >> [0x7f6954568158] >> >> /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(client_ >> bind+0x93)[0x7f69545685a3] >> >> /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(+0xa875) >> [0x7f6954565875] >> >> /lib64/libgfrpc.so.0(rpc_clnt_reconnect+0xc9)[0x7f69623a3f89] >> >> /lib64/libgfrpc.so.0(rpc_clnt_start+0x39)[0x7f69623a4049] >> >> /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24218 >> )[0x7f69570f9218] >> >> /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24843 >> )[0x7f6...
Glusterd not working with systemd in redhat 7
2017 Aug 21
1
Glusterd not working with systemd in redhat 7
...sl_opts] >> 0-glusterfs: disabling SSL for portmapper connection >> [2017-08-20 20:30:46.931585] I [timer.c:198:gf_timer_registry_init] >> (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x2ff6f) >> [0x7f8f703a8f6f] -->/usr/lib/x86_64-linux-gnu/l >> ibgfrpc.so.0(rpc_clnt_reconnect+0xee) [0x7f8f7016c54e] >> -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(gf_timer_call_after+0x204) >> [0x7f8f703a9324] ) 0-timer: ctx cleanup started >> [2017-08-20 20:30:46.931626] E [timer.c:44:gf_timer_call_after] >> (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(...
gluster peer probe failing
2017 Jun 20
2
gluster peer probe failing
...4/glusterfs/3.10.3/rpc-transport/socket.so(+ > 0xd158)[0x7fbde9c24158] > > /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(client_bind+0x93)[ > 0x7fbde9c245a3] > > /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(+ > 0xa875)[0x7fbde9c21875] > > /lib64/libgfrpc.so.0(rpc_clnt_reconnect+0xc9)[0x7fbdf7a5ff89] > > /lib64/libgfrpc.so.0(rpc_clnt_start+0x39)[0x7fbdf7a60049] > > /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+ > 0x24218)[0x7fbdec7b5218] > > /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+ > 0x24843)[0x7fbdec7b5843] > > /usr/lib64/...
gluster peer probe failing
2017 Jun 18
0
gluster peer probe failing
...s_reserved_ports+0xbe)[0x7fbdf7ca070e] /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(+0xd158)[0x7fbde9c24158] /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(client_bind+0x93)[0x7fbde9c245a3] /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(+0xa875)[0x7fbde9c21875] /lib64/libgfrpc.so.0(rpc_clnt_reconnect+0xc9)[0x7fbdf7a5ff89] /lib64/libgfrpc.so.0(rpc_clnt_start+0x39)[0x7fbdf7a60049] /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24218)[0x7fbdec7b5218] /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24843)[0x7fbdec7b5843] /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24ae0)[0...
gluster peer probe failing
2017 Jun 15
0
gluster peer probe failing
...4/glusterfs/3.10.3/rpc-transport/socket.so(+ > 0xd158)[0x7f6954568158] > > /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(client_bind+0x93)[ > 0x7f69545685a3] > > /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(+ > 0xa875)[0x7f6954565875] > > /lib64/libgfrpc.so.0(rpc_clnt_reconnect+0xc9)[0x7f69623a3f89] > > /lib64/libgfrpc.so.0(rpc_clnt_start+0x39)[0x7f69623a4049] > > /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+ > 0x24218)[0x7f69570f9218] > > /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+ > 0x24843)[0x7f69570f9843] > > /usr/lib64/...
gluster peer probe failing
2017 Jun 20
0
gluster peer probe failing
...ket.so(+0xd158) >> [0x7fbde9c24158] >> >> /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(client_ >> bind+0x93)[0x7fbde9c245a3] >> >> /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(+0xa875) >> [0x7fbde9c21875] >> >> /lib64/libgfrpc.so.0(rpc_clnt_reconnect+0xc9)[0x7fbdf7a5ff89] >> >> /lib64/libgfrpc.so.0(rpc_clnt_start+0x39)[0x7fbdf7a60049] >> >> /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24218 >> )[0x7fbdec7b5218] >> >> /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24843 >> )[0x7fb...
gluster peer probe failing
2017 Jun 20
1
gluster peer probe failing
...s_reserved_ports+0xbe)[0x7fbdf7ca070e] /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(+0xd158)[0x7fbde9c24158] /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(client_bind+0x93)[0x7fbde9c245a3] /usr/lib64/glusterfs/3.10.3/rpc-transport/socket.so(+0xa875)[0x7fbde9c21875] /lib64/libgfrpc.so.0(rpc_clnt_reconnect+0xc9)[0x7fbdf7a5ff89] /lib64/libgfrpc.so.0(rpc_clnt_start+0x39)[0x7fbdf7a60049] /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24218)[0x7fbdec7b5218] /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24843)[0x7fbdec7b5843] /usr/lib64/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x24ae0)[0...
volume start: gv01: failed: Quorum not met. Volume operation not allowed.
2018 Apr 11
0
volume start: gv01: failed: Quorum not met. Volume operation not allowed.
On Wed, Apr 11, 2018 at 4:35 AM, TomK <tomkcpr at mdevsys.com> wrote: > On 4/9/2018 2:45 AM, Alex K wrote: > Hey Alex, > > With two nodes, the setup works but both sides go down when one node is > missing. Still I set the below two params to none and that solved my issue: > > cluster.quorum-type: none > cluster.server-quorum-type: none > > yes this disables
volume start: gv01: failed: Quorum not met. Volume operation not allowed.
2018 Apr 11
3
volume start: gv01: failed: Quorum not met. Volume operation not allowed.
On 4/9/2018 2:45 AM, Alex K wrote: Hey Alex, With two nodes, the setup works but both sides go down when one node is missing. Still I set the below two params to none and that solved my issue: cluster.quorum-type: none cluster.server-quorum-type: none Thank you for that. Cheers, Tom > Hi, > > You need 3 nodes at least to have quorum enabled. In 2 node setup you > need to
volume start: gv01: failed: Quorum not met. Volume operation not allowed.
2018 May 08
1
volume start: gv01: failed: Quorum not met. Volume operation not allowed.
...0x90)[0x7f327e299720] (--> /usr/lib64/glusterfs/3.13.2/xlator/protocol/client.so(fini+0x28)[0x7f32701a7c88] ))))) 0-gv01-client-1: forced unwinding frame type(GF-DUMP) op(DUMP(1)) called at 2018-05-05 01:38:46.965204 (xid=0x2) ganesha-gfapi.log:[2018-05-05 01:38:50.457456] E [rpc-clnt.c:417:rpc_clnt_reconnect] 0-gv01-client-1: Error adding to timer event queue ganesha-gfapi.log:[2018-05-07 03:05:58.522295] E [rpc-clnt.c:350:saved_frames_unwind] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7f45af6d6f0b] (--> /lib64/libgfrpc.so.0(saved_frames_unwind+0x1de)[0x7f45af49be7e] (--> /l...