search for: __glusterd_handle_cli_get_volume

Displaying 20 results from an estimated 27 matches for "__glusterd_handle_cli_get_volume".

2018 Jan 11
3
Creating cluster replica on 2 nodes 2 bricks each.
...ch] 0-: Exiting with: 0 ?? etc-glusterfs-glusterd.vol.log ? [2018-01-10 14:59:23.676814] I [MSGID: 106499] [glusterd-handler.c:4349:__glusterd_handle_status_volume] 0-management: Received status volume req for volume scratch [2018-01-10 15:00:29.516071] I [MSGID: 106488] [glusterd-handler.c:1537:__glusterd_handle_cli_get_volume] 0-management: Received get vol req [2018-01-10 15:01:09.872082] I [MSGID: 106482] [glusterd-brick-ops.c:447:__glusterd_handle_add_brick] 0-management: Received add brick req [2018-01-10 15:01:09.872128] I [MSGID: 106578] [glusterd-brick-ops.c:499:__glusterd_handle_add_brick] 0-management: replica-...
2018 Jan 12
0
Creating cluster replica on 2 nodes 2 bricks each.
...tch] 0-: Exiting with: 0 ?? etc-glusterfs-glusterd.vol.log ? [2018-01-10 14:59:23.676814] I [MSGID: 106499] [glusterd-handler.c:4349:__glusterd_handle_status_volume] 0-management: Received status volume req for volume scratch [2018-01-10 15:00:29.516071] I [MSGID: 106488] [glusterd-handler.c:1537:__glusterd_handle_cli_get_volume] 0-management: Received get vol req [2018-01-10 15:01:09.872082] I [MSGID: 106482] [glusterd-brick-ops.c:447:__glusterd_handle_add_brick] 0-management: Received add brick req [2018-01-10 15:01:09.872128] I [MSGID: 106578] [glusterd-brick-ops.c:499:__glusterd_handle_add_brick] 0-management: replica-...
2018 Jan 15
1
Creating cluster replica on 2 nodes 2 bricks each.
...etc-glusterfs-glusterd.vol.log ? > > [2018-01-10 14:59:23.676814] I [MSGID: 106499] > [glusterd-handler.c:4349:__glusterd_handle_status_volume] 0-management: > Received status volume req for volume scratch > [2018-01-10 15:00:29.516071] I [MSGID: 106488] > [glusterd-handler.c:1537:__glusterd_handle_cli_get_volume] 0-management: > Received get vol req > [2018-01-10 15:01:09.872082] I [MSGID: 106482] > [glusterd-brick-ops.c:447:__glusterd_handle_add_brick] 0-management: > Received add brick req > [2018-01-10 15:01:09.872128] I [MSGID: 106578] > [glusterd-brick-ops.c:499:__glusterd_handle_add...
2018 Jan 11
0
Creating cluster replica on 2 nodes 2 bricks each.
Hi Jose, Gluster is working as expected. The Distribute-replicated type just means that there are now 2 replica sets and files will be distributed across them. A volume of type Replicate (1xn where n is the number of bricks in the replica set) indicates there is no distribution (all files on the volume will be present on all the bricks in the volume). A volume of type Distributed-Replicate
2018 Jan 10
2
Creating cluster replica on 2 nodes 2 bricks each.
Hi Nithya This is what i have so far, I have peer both cluster nodes together as replica, from node 1A and 1B , now when i tried to add it , i get the error that it is already part of a volume. when i run the cluster volume info , i see that has switch to distributed-replica. Thanks Jose [root at gluster01 ~]# gluster volume status Status of volume: scratch Gluster process
2014 Apr 28
2
volume start causes glusterd to core dump in 3.5.0
...friend_update] 0-: Added uuid: 84c0bb8e-bf48-4386-ada1-3e4db68b980f, host: fed-gfs4 [2014-04-28 21:49:18.262901] I [glusterd-rpc-ops.c:553:__glusterd_friend_update_cbk] 0-management: Received ACC from uuid: 84c0bb8e-bf48-4386-ada1-3e4db68b980f [2014-04-28 21:49:20.401429] I [glusterd-handler.c:1169:__glusterd_handle_cli_get_volume] 0-glusterd: Received get vol req [2014-04-28 21:49:20.402072] I [glusterd-handler.c:1169:__glusterd_handle_cli_get_volume] 0-glusterd: Received get vol req pending frames: frame : type(0) op(0) patchset: git://git.gluster.com/glusterfs.git signal received: 6 time of crash: 2014-04-28 21:53:12conf...
2018 Jan 16
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...mance.low-prio-threads: 32 performance.io-cache: off performance.read-ahead: off performance.quick-read: off transport.address-family: inet nfs.disable: off performance.client-io-threads: off /var/log/glusterfs/glusterd.log: [2018-01-15 14:17:50.196228] I [MSGID: 106488] [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] 0-management: Received get vol req [2018-01-15 14:25:09.555214] I [MSGID: 106488] [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] 0-management: Received get vol req (empty because today it's 2018-01-16) /var/log/glusterfs/glustershd.log: [2018-01-14 02:23:02.731245] I [gluster...
2018 Jan 16
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...off > performance.read-ahead: off > performance.quick-read: off > transport.address-family: inet > nfs.disable: off > performance.client-io-threads: off > > /var/log/glusterfs/glusterd.log: > > [2018-01-15 14:17:50.196228] I [MSGID: 106488] > [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] > 0-management: Received get vol req > [2018-01-15 14:25:09.555214] I [MSGID: 106488] > [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] > 0-management: Received get vol req > > (empty because today it's 2018-01-16) > > /var/log/glusterfs/glustershd.log: &g...
2018 Jan 17
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...transport.address-family: inet >>> nfs.disable: off >>> performance.client-io-threads: off >>> >>> /var/log/glusterfs/glusterd.log: >>> >>> [2018-01-15 14:17:50.196228] I [MSGID: 106488] >>> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >>> 0-management: Received get vol req >>> [2018-01-15 14:25:09.555214] I [MSGID: 106488] >>> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >>> 0-management: Received get vol req >>> >>> (empty because today it&...
2018 Jan 17
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...ff >> performance.quick-read: off >> transport.address-family: inet >> nfs.disable: off >> performance.client-io-threads: off >> >> /var/log/glusterfs/glusterd.log: >> >> [2018-01-15 14:17:50.196228] I [MSGID: 106488] >> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] 0-management: >> Received get vol req >> [2018-01-15 14:25:09.555214] I [MSGID: 106488] >> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] 0-management: >> Received get vol req >> >> (empty because today it's 2018-01-16) >> >> /var/log...
2018 Jan 17
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...nfs.disable: off >>>> performance.client-io-threads: off >>>> >>>> /var/log/glusterfs/glusterd.log: >>>> >>>> [2018-01-15 14:17:50.196228] I [MSGID: 106488] >>>> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >>>> 0-management: Received get vol req >>>> [2018-01-15 14:25:09.555214] I [MSGID: 106488] >>>> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >>>> 0-management: Received get vol req >>>> >&...
2018 Jan 17
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...f >>>>> performance.client-io-threads: off >>>>> >>>>> /var/log/glusterfs/glusterd.log: >>>>> >>>>> [2018-01-15 14:17:50.196228] I [MSGID: 106488] >>>>> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >>>>> 0-management: Received get vol req >>>>> [2018-01-15 14:25:09.555214] I [MSGID: 106488] >>>>> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >>>>> 0-management: Received get vol req >&g...
2018 Jan 16
1
Problem with Gluster 3.12.4, VM and sharding
Also to help isolate the component, could you answer these: 1. on a different volume with shard not enabled, do you see this issue? 2. on a plain 3-way replicated volume (no arbiter), do you see this issue? On Tue, Jan 16, 2018 at 4:03 PM, Krutika Dhananjay <kdhananj at redhat.com> wrote: > Please share the volume-info output and the logs under /var/log/glusterfs/ > from all your
2018 Jan 18
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...t; performance.client-io-threads: off >>>>>> >>>>>> /var/log/glusterfs/glusterd.log: >>>>>> >>>>>> [2018-01-15 14:17:50.196228] I [MSGID: 106488] >>>>>> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >>>>>> 0-management: Received get vol req >>>>>> [2018-01-15 14:25:09.555214] I [MSGID: 106488] >>>>>> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >>>>>> 0-management: Received ge...
2018 Jan 18
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...ad: off >>> transport.address-family: inet >>> nfs.disable: off >>> performance.client-io-threads: off >>> >>> /var/log/glusterfs/glusterd.log: >>> >>> [2018-01-15 14:17:50.196228] I [MSGID: 106488] >>> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >>> 0-management: Received get vol req >>> [2018-01-15 14:25:09.555214] I [MSGID: 106488] >>> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >>> 0-management: Received get vol req >>> >>> (empty because today it's 2018-01-16) &g...
2018 Jan 19
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...-threads: off >>>>>>> >>>>>>> /var/log/glusterfs/glusterd.log: >>>>>>> >>>>>>> [2018-01-15 14:17:50.196228] I [MSGID: 106488] >>>>>>> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >>>>>>> 0-management: Received get vol req >>>>>>> [2018-01-15 14:25:09.555214] I [MSGID: 106488] >>>>>>> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >>>>>>>...
2017 Oct 05
2
Glusterd not working with systemd in redhat 7
...ing. Seems that gluster starts before network layer. Some logs here: Thanks [2017-10-04 15:33:00.506396] I [MSGID: 106143] [glusterd-pmap.c:277:pmap_registry_bind] 0-pmap: adding brick /opt/glusterfs/advdemo on port 49152 [2017-10-04 15:33:01.206401] I [MSGID: 106488] [glusterd-handler.c:1538:__glusterd_handle_cli_get_volume] 0-management: Received get vol req [2017-10-04 15:33:01.206936] I [MSGID: 106488] [glusterd-handler.c:1538:__glusterd_handle_cli_get_volume] 0-management: Received get vol req [2017-10-04 15:33:18.043104] W [glusterfsd.c:1360:cleanup_and_exit] (-->/lib64/libpthread.so.0(+0x7dc5) [0x7fc47d9e4dc5...
2017 Oct 05
0
Glusterd not working with systemd in redhat 7
...t; >> Thanks >> >> >> [2017-10-04 15:33:00.506396] I [MSGID: 106143] >> [glusterd-pmap.c:277:pmap_registry_bind] 0-pmap: adding brick >> /opt/glusterfs/advdemo on port 49152 >> [2017-10-04 15:33:01.206401] I [MSGID: 106488] >> [glusterd-handler.c:1538:__glusterd_handle_cli_get_volume] 0-management: >> Received get vol req >> [2017-10-04 15:33:01.206936] I [MSGID: 106488] >> [glusterd-handler.c:1538:__glusterd_handle_cli_get_volume] 0-management: >> Received get vol req >> [2017-10-04 15:33:18.043104] W [glusterfsd.c:1360:cleanup_and_exit] >>...
2017 Oct 04
2
Glusterd not working with systemd in redhat 7
...ing. Seems that gluster starts before network layer. Some logs here: Thanks [2017-10-04 15:33:00.506396] I [MSGID: 106143] [glusterd-pmap.c:277:pmap_registry_bind] 0-pmap: adding brick /opt/glusterfs/advdemo on port 49152 [2017-10-04 15:33:01.206401] I [MSGID: 106488] [glusterd-handler.c:1538:__glusterd_handle_cli_get_volume] 0-management: Received get vol req [2017-10-04 15:33:01.206936] I [MSGID: 106488] [glusterd-handler.c:1538:__glusterd_handle_cli_get_volume] 0-management: Received get vol req [2017-10-04 15:33:18.043104] W [glusterfsd.c:1360:cleanup_and_exit] (-->/lib64/libpthread.so.0(+0x7dc5) [0x7fc47d9e4dc5...
2018 Jan 16
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...f >> performance.quick-read: off >> transport.address-family: inet >> nfs.disable: off >> performance.client-io-threads: off >> >> /var/log/glusterfs/glusterd.log: >> >> [2018-01-15 14:17:50.196228] I [MSGID: 106488] >> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >> 0-management: Received get vol req >> [2018-01-15 14:25:09.555214] I [MSGID: 106488] >> [glusterd-handler.c:1548:__glusterd_handle_cli_get_volume] >> 0-management: Received get vol req >> >> (empty because today it's 2018-01-16) >> >> /var/...