Displaying 20 results from an estimated 22 matches for "106487".
2018 Jan 14
0
Volume can not write to data if this volume quota limits capacity and mount itself volume on arm64（aarch64） architecture
...fully
[2018-02-02 11:21:58.201432] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: bitd already stopped
[2018-02-02 11:21:58.201589] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: scrub already stopped
[2018-02-02 11:22:00.302648] I [MSGID: 106487] [glusterd-handler.c:1472:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req
[2018-02-02 11:22:32.998693] I [MSGID: 106487] [glusterd-handler.c:1472:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req
[2018-02-02 11:23:24.792241] W [common-utils.c:1685:gf_string...
2017 Nov 30
2
Problems joining new gluster 3.10 nodes to existing 3.8
...t07
Uuid: 4baff5cf-6e81-4b2e-b31f-be725b2da4b3
State: Peer Rejected (Connected)
The node where I'm probing from complains about not able to find
information on elkpinfglt07 but then it's found anyway and checksums
on data0 volume aren't the same:
[2017-11-30 20:12:24.278996] I [MSGID: 106487]
[glusterd-handler.c:1241:__glusterd_handle_cli_probe] 0-glusterd:
Received CLI probe req elkpinfglt07 24007
[2017-11-30 20:12:24.279999] I [MSGID: 106129]
[glusterd-handler.c:3670:glusterd_probe_begin] 0-glusterd: Unable to
find peerinfo for host: elkpinfglt07 (24007)
[2017-11-30 20:12:24.281020]...
2017 Dec 01
0
Problems joining new gluster 3.10 nodes to existing 3.8
...-be725b2da4b3
> State: Peer Rejected (Connected)
>
> The node where I'm probing from complains about not able to find
> information on elkpinfglt07 but then it's found anyway and checksums
> on data0 volume aren't the same:
>
> [2017-11-30 20:12:24.278996] I [MSGID: 106487]
> [glusterd-handler.c:1241:__glusterd_handle_cli_probe] 0-glusterd:
> Received CLI probe req elkpinfglt07 24007
> [2017-11-30 20:12:24.279999] I [MSGID: 106129]
> [glusterd-handler.c:3670:glusterd_probe_begin] 0-glusterd: Unable to
> find peerinfo for host: elkpinfglt07 (24007)
>...
2018 Mar 06
0
Fixing a rejected peer
...0-glusterd: Responded to sc5-gluster-10g-1 (0), ret: 0, op_ret: -1
> [2018-03-06 00:14:06.164819] I [MSGID: 106143] [glusterd-pmap.c:295:pmap_registry_bind]
> 0-pmap: adding brick /gluster-bricks/sc5_ovirt_engine/sc5_ovirt_engine on
> port 49152
> [2018-03-06 00:14:06.443882] I [MSGID: 106487] [glusterd-handler.c:1485:__
> glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>
------------...
2018 Mar 06
4
Fixing a rejected peer
...fer_friend_add_resp] 0-glusterd: Responded to sc5-gluster-10g-1 (0), ret: 0, op_ret: -1
[2018-03-06 00:14:06.164819] I [MSGID: 106143] [glusterd-pmap.c:295:pmap_registry_bind] 0-pmap: adding brick /gluster-bricks/sc5_ovirt_engine/sc5_ovirt_engine on port 49152
[2018-03-06 00:14:06.443882] I [MSGID: 106487] [glusterd-handler.c:1485:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req
2018 Feb 06
5
strange hostname issue on volume create command with famous Peer in Cluster state error message
...ectory /var/lib/glusterd
15: end-volume
16:
+------------------------------------------------------------------------------+
[2018-02-06 13:29:44.628451] I [MSGID: 101190] [event-epoll.c:602:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1
[2018-02-06 13:46:38.530154] I [MSGID: 106487] [glusterd-handler.c:1484:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req
[2018-02-06 13:47:05.745357] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe] 0-glusterd: Received CLI probe req sec.ostechnix.lan 24007
[2018-02-06 13:47:05.746465] I [MSGID: 1061...
2018 Feb 06
0
strange hostname issue on volume create command with famous Peer in Cluster state error message
...: end-volume
> 16:
> +------------------------------------------------------------------------------+
> [2018-02-06 13:29:44.628451] I [MSGID: 101190]
> [event-epoll.c:602:event_dispatch_epoll_worker] 0-epoll: Started thread with
> index 1
> [2018-02-06 13:46:38.530154] I [MSGID: 106487]
> [glusterd-handler.c:1484:__glusterd_handle_cli_list_friends] 0-glusterd:
> Received cli list req
> [2018-02-06 13:47:05.745357] I [MSGID: 106487]
> [glusterd-handler.c:1242:__glusterd_handle_cli_probe] 0-glusterd: Received
> CLI probe req sec.ostechnix.lan 24007
> [2018-02-06 1...
2018 Feb 06
0
strange hostname issue on volume create command with famous Peer in Cluster state error message
...end-volume
> 16:
> +-----------------------------------------------------------
> -------------------+
> [2018-02-06 13:29:44.628451] I [MSGID: 101190] [event-epoll.c:602:event_dispatch_epoll_worker]
> 0-epoll: Started thread with index 1
> [2018-02-06 13:46:38.530154] I [MSGID: 106487] [glusterd-handler.c:1484:__
> glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req
> [2018-02-06 13:47:05.745357] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe]
> 0-glusterd: Received CLI probe req sec.ostechnix.lan 24007
> [2018-02-06 13:47:05.7...
2018 Feb 06
1
strange hostname issue on volume create command with famous Peer in Cluster state error message
...> 15: end-volume
> 16:
> +------------------------------------------------------------------------------+
> [2018-02-06 13:29:44.628451] I [MSGID: 101190] [event-epoll.c:602:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1
> [2018-02-06 13:46:38.530154] I [MSGID: 106487] [glusterd-handler.c:1484:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req
> [2018-02-06 13:47:05.745357] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe] 0-glusterd: Received CLI probe req sec.ostechnix.lan 24007
> [2018-02-06 13:47:05.746465] I [M...
2011 Oct 18
3
Ordering of stack in ggplot (package ggplot2)
...tacks sorted in alphabetical order from
the bottom up. I'd like the stacks to be in the order "Europe", "Asia",
"Americas, "Africa", "Oceania". Is there an easy way to manipulate ggplot or
geom_bar to do this?
/library(ggplot2)
df <- structure(c(106487, 495681, 1597442,
2452577, 2065141, 2271925, 4735484, 3555352,
8056040, 4321887, 2463194, 347566, 621147,
1325727, 1123492, 800368, 761550, 1359737,
1073726, 36, 53, 141, 41538, 64759, 124160,
69942, 74862, 323543, 247236, 112059, 16595,
37028, 153249, 427642, 1588178, 27381...
2018 Jan 15
2
Using the host name of the volume, its related commands can become very slow
...ler.c:2821:__glusterd_handle_friend_update] 0-management: Received my uuid as Friend
[2018-02-03 13:55:09.333350] I [MSGID: 106493] [glusterd-rpc-ops.c:696:__glusterd_friend_update_cbk] 0-management: Received ACC from uuid: d8ee609f-d47e-46e4-96ac-ef78cddf45b8
[2018-02-03 13:55:38.833207] I [MSGID: 106487] [glusterd-handler.c:1472:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req
[2018-02-03 13:57:09.161466] I [MSGID: 106487] [glusterd-handler.c:1472:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req
[2018-02-03 13:58:39.566130] I [MSGID: 106487] [glusterd-hand...
2017 Jun 14
2
gluster peer probe failing
...other on port 24007.
When I try to create the first peering by running on node1 the command:
gluster peer probe <node2 ip address>
I get the error:
"Connection failed. Please check if gluster daemon is operational."
And Glusterd.log shows:
[2017-06-14 14:46:09.927510] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe] 0-glusterd: Received CLI probe req 192.168.1.17 24007
[2017-06-14 14:46:09.928560] I [MSGID: 106129] [glusterd-handler.c:3690:glusterd_probe_begin] 0-glusterd: Unable to find peerinfo for host: 192.168.1.17 (24007)
[2017-06-14 14:46:09.930783]...
2018 Jan 16
0
Using the host name of the volume, its related commands can become very slow
...d_handle_friend_update]
> 0-management: Received my uuid as Friend
> [2018-02-03 13:55:09.333350] I [MSGID: 106493] [glusterd-rpc-ops.c:696:__glusterd_friend_update_cbk]
> 0-management: Received ACC from uuid: d8ee609f-d47e-46e4-96ac-ef78cddf45b8
> [2018-02-03 13:55:38.833207] I [MSGID: 106487] [glusterd-handler.c:1472:__
> glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req
> [2018-02-03 13:57:09.161466] I [MSGID: 106487] [glusterd-handler.c:1472:__
> glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req
> [2018-02-03 13:58:39.566130] I [MSGID:...
2017 Jun 15
0
gluster peer probe failing
...nning on node1 the command:
>
> gluster peer probe <node2 ip address>
>
>
>
> I get the error:
>
> ?Connection failed. Please check if gluster daemon is operational.?
>
>
>
> And Glusterd.log shows:
>
>
>
> [2017-06-14 14:46:09.927510] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe]
> 0-glusterd: Received CLI probe req 192.168.1.17 24007
>
> [2017-06-14 14:46:09.928560] I [MSGID: 106129] [glusterd-handler.c:3690:glusterd_probe_begin]
> 0-glusterd: Unable to find peerinfo for host: 192.168.1.17 (24007)
>
>...
2017 Jun 15
2
gluster peer probe failing
...ode to the other on port 24007.
When I try to create the first peering by running on node1 the command:
gluster peer probe <node2 ip address>
I get the error:
?Connection failed. Please check if gluster daemon is operational.?
And Glusterd.log shows:
[2017-06-14 14:46:09.927510] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe] 0-glusterd: Received CLI probe req 192.168.1.17 24007
[2017-06-14 14:46:09.928560] I [MSGID: 106129] [glusterd-handler.c:3690:glusterd_probe_begin] 0-glusterd: Unable to find peerinfo for host: 192.168.1.17 (24007)
[2017-06-14 14:46:09.930783]...
2017 Jun 16
2
gluster peer probe failing
...<node2 ip address>
>>
>>
>>
>> I get the error:
>>
>> ?Connection failed. Please check if gluster daemon is operational.?
>>
>>
>>
>> And Glusterd.log shows:
>>
>>
>>
>> [2017-06-14 14:46:09.927510] I [MSGID: 106487]
>> [glusterd-handler.c:1242:__glusterd_handle_cli_probe] 0-glusterd:
>> Received CLI probe req 192.168.1.17 24007
>>
>> [2017-06-14 14:46:09.928560] I [MSGID: 106129]
>> [glusterd-handler.c:3690:glusterd_probe_begin] 0-glusterd: Unable to
>> find peerinfo for ho...
2017 Jun 20
2
gluster peer probe failing
...com> wrote:
> Hi,
>
> Below please find the reserved ports and log, thanks.
>
>
>
> sysctl net.ipv4.ip_local_reserved_ports:
>
> net.ipv4.ip_local_reserved_ports = 30000-32767
>
>
>
>
>
> glusterd.log:
>
> [2017-06-18 07:04:17.853162] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe]
> 0-glusterd: Received CLI probe req 192.168.1.17 24007
>
> [2017-06-18 07:04:17.853237] D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr]
> 0-management: 192.168.1.17
>
> [2017-06-18 07:04:17.854093] D [logging.c:1952:_gf_m...
2017 Jun 18
0
gluster peer probe failing
Hi,
Below please find the reserved ports and log, thanks.
sysctl net.ipv4.ip_local_reserved_ports:
net.ipv4.ip_local_reserved_ports = 30000-32767
glusterd.log:
[2017-06-18 07:04:17.853162] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe] 0-glusterd: Received CLI probe req 192.168.1.17 24007
[2017-06-18 07:04:17.853237] D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr] 0-management: 192.168.1.17
[2017-06-18 07:04:17.854093] D [logging.c:1952:_gf_msg_internal] 0-logging-infra:...
2017 Jun 15
0
gluster peer probe failing
...nning on node1 the command:
>
> gluster peer probe <node2 ip address>
>
>
>
> I get the error:
>
> ?Connection failed. Please check if gluster daemon is operational.?
>
>
>
> And Glusterd.log shows:
>
>
>
> [2017-06-14 14:46:09.927510] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe]
> 0-glusterd: Received CLI probe req 192.168.1.17 24007
>
> [2017-06-14 14:46:09.928560] I [MSGID: 106129] [glusterd-handler.c:3690:glusterd_probe_begin]
> 0-glusterd: Unable to find peerinfo for host: 192.168.1.17 (24007)
>
>...
2018 Feb 07
2
Ip based peer probe volume create error
On 8/02/2018 4:45 AM, Gaurav Yadav wrote:
> After seeing command history, I could see that you have 3 nodes, and
> firstly you are peer probing 51.15.90.60? and 163.172.151.120 from?
> 51.15.77.14
> So here itself you have 3 node cluster, after all this you are going
> on node 2 and again peer probing 51.15.77.14.
> ?Ideally it should work, with above steps, but due to some