Displaying 16 results from an estimated 16 matches for "gf_resolve_ip6".
2017 Aug 20
2
Glusterd not working with systemd in redhat 7
...0.382334] D [socket.c:4284:socket_init] 0-glusterfs:
using system polling thread
[2017-08-20 20:30:40.382343] D
[rpc-clnt.c:1581:rpcclnt_cbk_program_register] 0-glusterfs: New program
registered: GlusterFS Callback, Num: 52743234, Ver: 1
[2017-08-20 20:30:40.466338] D [MSGID: 0]
[common-utils.c:327:gf_resolve_ip6] 0-resolver: returning ip-192.168.1.8
(port-24007) for hostname: web1.dasilva.network and port: 24007
[2017-08-20 20:30:40.466364] D [MSGID: 0]
[common-utils.c:327:gf_resolve_ip6] 0-resolver: returning ip-192.168.1.8
(port-24007) for hostname: web1.dasilva.network and port: 24007
[2017-08-20 20:30:...
2017 Aug 21
0
Glusterd not working with systemd in redhat 7
...4:socket_init] 0-glusterfs:
> using system polling thread
> [2017-08-20 20:30:40.382343] D [rpc-clnt.c:1581:rpcclnt_cbk_program_register]
> 0-glusterfs: New program registered: GlusterFS Callback, Num: 52743234,
> Ver: 1
> [2017-08-20 20:30:40.466338] D [MSGID: 0] [common-utils.c:327:gf_resolve_ip6]
> 0-resolver: returning ip-192.168.1.8 (port-24007) for hostname:
> web1.dasilva.network and port: 24007
> [2017-08-20 20:30:40.466364] D [MSGID: 0] [common-utils.c:327:gf_resolve_ip6]
> 0-resolver: returning ip-192.168.1.8 (port-24007) for hostname:
> web1.dasilva.network and port:...
2017 Aug 21
1
Glusterd not working with systemd in redhat 7
...sterfs:
>> using system polling thread
>> [2017-08-20 20:30:40.382343] D [rpc-clnt.c:1581:rpcclnt_cbk_program_register]
>> 0-glusterfs: New program registered: GlusterFS Callback, Num: 52743234,
>> Ver: 1
>> [2017-08-20 20:30:40.466338] D [MSGID: 0] [common-utils.c:327:gf_resolve_ip6]
>> 0-resolver: returning ip-192.168.1.8 (port-24007) for hostname:
>> web1.dasilva.network and port: 24007
>> [2017-08-20 20:30:40.466364] D [MSGID: 0] [common-utils.c:327:gf_resolve_ip6]
>> 0-resolver: returning ip-192.168.1.8 (port-24007) for hostname:
>> web1.dasil...
2017 Jun 15
1
peer probe failures
...ing thread
[2017-04-03 22:20:24.787263] T [rpc-clnt.c:418:rpc_clnt_reconnect]
0-management: attempting reconnect
[2017-04-03 22:20:24.787273] T [socket.c:2887:socket_connect] 0-management:
connecting 0x7ff7fc005640, state=0 gen=0 sock=-1
[2017-04-03 22:20:24.787288] T [MSGID: 0]
[common-utils.c:290:gf_resolve_ip6] 0-resolver: DNS cache not present,
freshly probing hostname: 10.1.0.7
[2017-04-03 22:20:24.787843] D [MSGID: 0]
[common-utils.c:333:gf_resolve_ip6] 0-resolver: returning ip-10.1.0.7
(port-24007) for hostname: 10.1.0.7 and port: 24007
[2017-04-03 22:20:24.787863] D [socket.c:2833:socket_fix_ssl_opt...
2013 Sep 30
1
Using gluster with ipv6
...e ipv6 in my network, but just can't setup glusterfs for.
I tried configuring IPv6 or DNS (only resolving at IPv6), got errors in both case.
Here last test I did + error:
/usr/sbin/glusterfsd -s ipv6.google.com --volfile-id testvol5.XXX....
[2013-09-30 14:09:24.424624] E [common-utils.c:211:gf_resolve_ip6] 0-resolver: getaddrinfo failed (System error)
[2013-09-30 14:09:24.424683] E [name.c:249:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution failed on host ipv6.google.com
On same computer:
#host ipv6.google.com
ipv6.google.com is an alias for ipv6.l.google.com.
ipv6.l.google.com ha...
2017 Jun 20
2
gluster peer probe failing
...ling thread
>
> [2017-06-18 07:04:17.856664] D [name.c:168:client_fill_address_family]
> 0-management: address-family not specified, marking it as unspec for
> getaddrinfo to resolve from (remote-host: 192.168.1.17)
>
> [2017-06-18 07:04:17.861800] D [MSGID: 0] [common-utils.c:334:gf_resolve_ip6]
> 0-resolver: returning ip-192.168.1.17 (port-24007) for hostname:
> 192.168.1.17 and port: 24007
>
> [2017-06-18 07:04:17.861830] D [socket.c:2982:socket_fix_ssl_opts]
> 0-management: disabling SSL for portmapper connection
>
> [2017-06-18 07:04:17.861885] D [MSGID: 0] [commo...
2017 Oct 24
0
trying to add a 3rd peer
Are you shure about possibility to resolve all node names on all other nodes?
You need to use names used previously in Gluster - check their by ?gluster peer status? or ?gluster pool list?.
Regards,
Bartosz
> Wiadomo?? napisana przez Ludwig Gamache <ludwig at elementai.com> w dniu 24.10.2017, o godz. 03:13:
>
> All,
>
> I am trying to add a third peer to my gluster
2017 Jun 18
0
gluster peer probe failing
...0-management: using system polling thread
[2017-06-18 07:04:17.856664] D [name.c:168:client_fill_address_family] 0-management: address-family not specified, marking it as unspec for getaddrinfo to resolve from (remote-host: 192.168.1.17)
[2017-06-18 07:04:17.861800] D [MSGID: 0] [common-utils.c:334:gf_resolve_ip6] 0-resolver: returning ip-192.168.1.17 (port-24007) for hostname: 192.168.1.17 and port: 24007
[2017-06-18 07:04:17.861830] D [socket.c:2982:socket_fix_ssl_opts] 0-management: disabling SSL for portmapper connection
[2017-06-18 07:04:17.861885] D [MSGID: 0] [common-utils.c:3106:gf_ports_reserved] 0...
2017 Jun 20
0
gluster peer probe failing
...;> [2017-06-18 07:04:17.856664] D [name.c:168:client_fill_address_family]
>> 0-management: address-family not specified, marking it as unspec for
>> getaddrinfo to resolve from (remote-host: 192.168.1.17)
>>
>> [2017-06-18 07:04:17.861800] D [MSGID: 0] [common-utils.c:334:gf_resolve_ip6]
>> 0-resolver: returning ip-192.168.1.17 (port-24007) for hostname:
>> 192.168.1.17 and port: 24007
>>
>> [2017-06-18 07:04:17.861830] D [socket.c:2982:socket_fix_ssl_opts]
>> 0-management: disabling SSL for portmapper connection
>>
>> [2017-06-18 07:04:17...
2017 Oct 24
2
trying to add a 3rd peer
All,
I am trying to add a third peer to my gluster install. The first 2 nodes
are running since many months and have gluster 3.10.3-1.
I recently installed the 3rd node and gluster 3.10.6-1. I was able to start
the gluster daemon on it. After, I tried to add the peer from one of the 2
previous server (gluster peer probe IPADDRESS).
That first peer started the communication with the 3rd peer. At
2017 Jun 20
1
gluster peer probe failing
...0-management: using system polling thread
[2017-06-18 07:04:17.856664] D [name.c:168:client_fill_address_family] 0-management: address-family not specified, marking it as unspec for getaddrinfo to resolve from (remote-host: 192.168.1.17)
[2017-06-18 07:04:17.861800] D [MSGID: 0] [common-utils.c:334:gf_resolve_ip6] 0-resolver: returning ip-192.168.1.17 (port-24007) for hostname: 192.168.1.17 and port: 24007
[2017-06-18 07:04:17.861830] D [socket.c:2982:socket_fix_ssl_opts] 0-management: disabling SSL for portmapper connection
[2017-06-18 07:04:17.861885] D [MSGID: 0] [common-utils.c:3106:gf_ports_reserved] 0...
2017 Jun 16
2
gluster peer probe failing
Could you please send me the output of command "sysctl
net.ipv4.ip_local_reserved_ports".
Apart from output of command please send the logs to look into the issue.
Thanks
Gaurav
On Thu, Jun 15, 2017 at 4:28 PM, Atin Mukherjee <amukherj at redhat.com> wrote:
> +Gaurav, he is the author of the patch, can you please comment here?
>
>
> On Thu, Jun 15, 2017 at 3:28
2017 Aug 16
0
Is transport=rdma tested with "stripe"?
...[2017-08-16 11:09:08.794585] I [MSGID: 100030] [glusterfsd.c:2475:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.10.3 (args: /usr/sbin/glusterfs --volfile-server=glusterfs-s1-fdr --volfile-id=/gv0 /mnt)
[2017-08-16 11:09:08.949784] E [MSGID: 101075] [common-utils.c:307:gf_resolve_ip6] 0-resolver: getaddrinfo failed (unknown name or service)
[2017-08-16 11:09:08.949815] E [name.c:262:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution failed on host glusterfs-s1-fdr
[2017-08-16 11:09:08.949956] I [glusterfsd-mgmt.c:2134:mgmt_rpc_notify] 0-glusterfsd-mgmt: disconnecte...
2017 Aug 15
2
Is transport=rdma tested with "stripe"?
On Tue, Aug 15, 2017 at 01:04:11PM +0000, Hatazaki, Takao wrote:
> Ji-Hyeon,
>
> You're saying that "stripe=2 transport=rdma" should work. Ok, that
> was firstly I wanted to know. I'll put together logs later this week.
Note that "stripe" is not tested much and practically unmaintained. We
do not advise you to use it. If you have large files that you
2017 Aug 18
1
Is transport=rdma tested with "stripe"?
...17-08-16 11:09:08.794585] I [MSGID: 100030] [glusterfsd.c:2475:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.10.3 (args: /usr/sbin/glusterfs --volfile-server=glusterfs-s1-fdr --volfile-id=/gv0 /mnt)
> [2017-08-16 11:09:08.949784] E [MSGID: 101075] [common-utils.c:307:gf_resolve_ip6] 0-resolver: getaddrinfo failed (unknown name or service)
> [2017-08-16 11:09:08.949815] E [name.c:262:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution failed on host glusterfs-s1-fdr
> [2017-08-16 11:09:08.949956] I [glusterfsd-mgmt.c:2134:mgmt_rpc_notify] 0-glusterfsd-mgmt: d...
2011 Jun 09
1
NFS problem
Hi,
I got the same problem as Juergen,
My volume is a simple replicated volume with 2 host and GlusterFS 3.2.0
Volume Name: poolsave
Type: Replicate
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: ylal2950:/soft/gluster-data
Brick2: ylal2960:/soft/gluster-data
Options Reconfigured:
diagnostics.brick-log-level: DEBUG
network.ping-timeout: 20
performance.cache-size: 512MB