[gt-user] Globus Gatekepeer supports ONLY IPv6 protocol (GT 5.2 )
John-Paul Robinson
jpr at uab.edu
Wed Feb 15 06:03:18 CST 2012
We ran into this problem just last week.
We saw it in the context of testing the new OSG CE 3.0 RPM release on a
vanilla ROCKS install. With only IPv4 enabled the gatekeeper wouldn't
start. It errors out on the socket() call with a request for IPv6. Our
local bug tracking this:
https://dev.uabgrid.uab.edu/ticket/186
We reported it back to Alain Roy @ OSG because we weren't sure if this
was an RPM build issue or further upstream. (BTW, the spec file in the
RPM doesn't suggest any type of build flag was used to require IPv6.)
Alain said he'd ask some of the globus folk about it.
I guess, I could have done what you did and posted here. Thanks for
getting the ball rolling.
~jpr
On 02/15/2012 05:53 AM, Sebastian Czechowski wrote:
> Hi all,
>
> After upgade to GT 5.2 ( rpm version ) on host with only ipv4 addresses
> configured on eth0 interface , globus-gatekeeper service fail to start
> with following message:
>
> ----------snip-------------
> TIME: Fri Feb 10 09:40:11 2012
> PID: 13646 -- Notice: 6: /usr/sbin/globus-gatekeeper pid=13646 starting
> at Fri Feb 10 09:40:11 2012
>
> Failure: error check net_setup_anon_listener socket: Address family not
> supported by protocol
>
> TIME: Fri Feb 10 09:40:11 2012
> PID: 13646 -- Failure: error check net_setup_anon_listener socket:
> Address family not supported by protocol
>
> ----------snip-------------
>
> After reconfigurin host to load ipv6 module and autocinfiguration of
> "link scope" ipv6 adresses globus-gatekeeper starts withou any problems :
>
> ----------snip-------------
> TIME: Fri Feb 10 10:34:47 2012
> PID: 13935 -- Notice: 6: /usr/sbin/globus-gatekeeper pid=13935 starting
> at Fri Feb 10 10:34:47 2012
>
> TIME: Fri Feb 10 10:34:47 2012
> PID: 13935 -- Notice: 6: GRAM contact:
> gt01.ige.psnc.pl:2119:/C=PL/O=GRID/O=PSNC/CN=host/gt01.ige.psnc.pl
>
> TIME: Fri Feb 10 10:34:47 2012
> PID: 13935 -- Notice: 0: GATEKEEPER_ACCT_FD=6
> (/var/log/globus-gatekeeper.log)
> TIME: Fri Feb 10 10:35:11 2012
> PID: 13942 -- Notice: 6: /usr/sbin/globus-gatekeeper pid=13942 starting
> at Fri Feb 10 10:35:11 2012
>
> TIME: Fri Feb 10 10:35:11 2012
> PID: 13942 -- Notice: 6: GRAM contact:
> gt01.ige.psnc.pl:2119:/C=PL/O=GRID/O=PSNC/CN=host/gt01.ige.psnc.pl
>
> TIME: Fri Feb 10 10:35:11 2012
> PID: 13942 -- Notice: 0: GATEKEEPER_ACCT_FD=6
> (/var/log/globus-gatekeeper.log)
> TIME: Fri Feb 10 10:37:53 2012
> PID: 14003 -- Notice: 6: Got connection ::ffff:129.217.162.158 at Fri
> Feb 10 10:37:53 2012
>
> ----------snip-------------
>
> In addition :
> gsissh and globus-gatekkeper services bind to ipv6 adresses only :
>
> ----------snip-------------
> [root at gt01 ~]# netstat -apne | grep LISTEN | grep globus
> tcp 0 0 :::2119 :::* LISTEN 0 83267312 24480/globus-gateke
> [root at gt01 ~]# netstat -apne | grep LISTEN | grep gsi
> tcp 0 0 :::2222 :::* LISTEN 0 83267237 24474/gsisshd
> [root at gt01 ~]#
> ----------snip-------------
>
> Concusion : You can't start GT 5.2 on ipv4 only machine.
>
> Has anyone have this problem?
>
> Best regards,
> Sebastian
>
More information about the gt-user
mailing list