Displaying 18 results from an estimated 18 matches for "106129".
Did you mean:
10612
2017 Nov 30
2
Problems joining new gluster 3.10 nodes to existing 3.8
...mation 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] I
[rpc-clnt.c:1046:rpc_clnt_connection_init] 0-management: setting
frame-timeout to 600
[2017-11-30 20:12:24.288605] I [MSGID: 106498]
[glusterd-handler.c:...
2017 Dec 01
0
Problems joining new gluster 3.10 nodes to existing 3.8
...en 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] I
> [rpc-clnt.c:1046:rpc_clnt_connection_init] 0-management: setting
> frame-timeout to 600
> [2017-11-30 20:12:24.288605] I [MSGID...
2017 Jun 14
2
gluster peer probe failing
...:
"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] W [MSGID: 106062] [glusterd-handler.c:3466:glusterd_transport_inet_options_build] 0-glusterd: Failed to get tcp-user-timeout
[2017-06-14 14:46:09.930837] I...
2017 Jun 15
0
gluster peer probe failing
...er 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] W [MSGID: 106062] [glusterd-handler.c:3466:
> glusterd_transport_inet_options_build] 0-glusterd: Failed to get
> tcp-user-timeout
>...
2017 Jun 15
2
gluster peer probe failing
...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] W [MSGID: 106062] [glusterd-handler.c:3466:glusterd_transport_inet_options_build] 0-glusterd: Failed to get tcp-user-timeout
[2017-06-14 14:46:09.930837] I...
2017 Jun 16
2
gluster peer probe failing
...>> 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] W [MSGID: 106062]
>> [glusterd-handler.c:3466:glusterd_transport_inet_options_build]
>> 0-glusterd: Failed...
2017 Jun 20
2
gluster peer probe failing
...glusterd_peerinfo_find_by_hostname] 0-management: Unable to find friend:
> 192.168.1.17
>
> [2017-06-18 07:04:17.854271] D [MSGID: 0] [glusterd-peer-utils.c:246:glusterd_peerinfo_find]
> 0-management: Unable to find hostname: 192.168.1.17
>
> [2017-06-18 07:04:17.854306] 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-18 07:04:17.854343] D [MSGID: 0] [glusterd-peer-utils.c:486:glusterd_peer_hostname_new]
> 0-glusterd: Returning 0
>
> [2017-06-18 07:04:17.854367] D [M...
2017 Jun 18
0
gluster peer probe failing
...0] [glusterd-peer-utils.c:132:glusterd_peerinfo_find_by_hostname] 0-management: Unable to find friend: 192.168.1.17
[2017-06-18 07:04:17.854271] D [MSGID: 0] [glusterd-peer-utils.c:246:glusterd_peerinfo_find] 0-management: Unable to find hostname: 192.168.1.17
[2017-06-18 07:04:17.854306] 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-18 07:04:17.854343] D [MSGID: 0] [glusterd-peer-utils.c:486:glusterd_peer_hostname_new] 0-glusterd: Returning 0
[2017-06-18 07:04:17.854367] D [MSGID: 0] [glusterd-utils.c:706...
2017 Jun 15
0
gluster peer probe failing
...er 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] W [MSGID: 106062] [glusterd-handler.c:3466:
> glusterd_transport_inet_options_build] 0-glusterd: Failed to get
> tcp-user-timeout
>...
2017 Jun 20
0
gluster peer probe failing
...y_hostname] 0-management: Unable to find friend:
>> 192.168.1.17
>>
>> [2017-06-18 07:04:17.854271] D [MSGID: 0] [glusterd-peer-utils.c:246:glusterd_peerinfo_find]
>> 0-management: Unable to find hostname: 192.168.1.17
>>
>> [2017-06-18 07:04:17.854306] 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-18 07:04:17.854343] D [MSGID: 0] [glusterd-peer-utils.c:486:glusterd_peer_hostname_new]
>> 0-glusterd: Returning 0
>>
>>...
2017 Jun 20
1
gluster peer probe failing
...0] [glusterd-peer-utils.c:132:glusterd_peerinfo_find_by_hostname] 0-management: Unable to find friend: 192.168.1.17
[2017-06-18 07:04:17.854271] D [MSGID: 0] [glusterd-peer-utils.c:246:glusterd_peerinfo_find] 0-management: Unable to find hostname: 192.168.1.17
[2017-06-18 07:04:17.854306] 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-18 07:04:17.854343] D [MSGID: 0] [glusterd-peer-utils.c:486:glusterd_peer_hostname_new] 0-glusterd: Returning 0
[2017-06-18 07:04:17.854367] D [MSGID: 0] [glusterd-utils.c:706...
2018 Feb 06
5
strange hostname issue on volume create command with famous Peer in Cluster state error message
...6487] [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: 106129] [glusterd-handler.c:3623:glusterd_probe_begin] 0-glusterd: Unable to find peerinfo for host: sec.ostechnix.lan (24007)
[2018-02-06 13:47:05.751131] W [MSGID: 106062] [glusterd-handler.c:3399:glusterd_transport_inet_options_build] 0-glusterd: Failed to get tcp-user-timeout
[2018-02-06 13:47:05.7511...
2018 Feb 06
0
strange hostname issue on volume create command with famous Peer in Cluster state error message
...er.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: 106129] [glusterd-handler.c:3623:glusterd_probe_begin]
> 0-glusterd: Unable to find peerinfo for host: sec.ostechnix.lan (24007)
> [2018-02-06 13:47:05.751131] W [MSGID: 106062] [glusterd-handler.c:3399:
> glusterd_transport_inet_options_build] 0-glusterd: Failed to get
> tcp-user-timeout
>...
2008 Feb 15
1
help on loop function
Dear lists,
Anysuggestion on how to write a loop function which has nx2 matrix as an input, where each of the row represents an interval. the function should return a mx2 matrix containing the no matched interval of x?? i've tried my own function but it's only applies for 2x2 matrix.
Here is my code:
overlap<-function(x,y){
m=length(x)
n=length(y)
for(i in 1:m){
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
2018 Feb 06
0
strange hostname issue on volume create command with famous Peer in Cluster state error message
...: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: 106129]
> [glusterd-handler.c:3623:glusterd_probe_begin] 0-glusterd: Unable to find
> peerinfo for host: sec.ostechnix.lan (24007)
> [2018-02-06 13:47:05.751131] W [MSGID: 106062]
> [glusterd-handler.c:3399:glusterd_transport_inet_options_build] 0-glusterd:
> Failed to get tcp-user-timeout...
2018 Feb 06
1
strange hostname issue on volume create command with famous Peer in Cluster state error message
...sterd-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: 106129] [glusterd-handler.c:3623:glusterd_probe_begin] 0-glusterd: Unable to find peerinfo for host: sec.ostechnix.lan (24007)
> [2018-02-06 13:47:05.751131] W [MSGID: 106062] [glusterd-handler.c:3399:glusterd_transport_inet_options_build] 0-glusterd: Failed to get tcp-user-timeout
> [2018-02-06 13:...
2017 Jun 15
1
peer probe failures
...[MSGID: 0]
[glusterd-peer-utils.c:133:glusterd_peerinfo_find_by_hostname]
0-management: Unable to find friend: 10.1.0.7
[2017-04-03 22:20:24.707260] D [MSGID: 0]
[glusterd-peer-utils.c:247:glusterd_peerinfo_find] 0-management: Unable to
find hostname: 10.1.0.7
[2017-04-03 22:20:24.707293] I [MSGID: 106129]
[glusterd-handler.c:3600:glusterd_probe_begin] 0-glusterd: Unable to find
peerinfo for host: 10.1.0.7 (24007)
[2017-04-03 22:20:24.707314] D [MSGID: 0]
[glusterd-peer-utils.c:458:glusterd_peer_hostname_new] 0-glusterd:
Returning 0
[2017-04-03 22:20:24.707329] D [MSGID: 0]
[glusterd-utils.c:5974:gl...