[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-290) mod_cluster's mod_advertise can not start on IPv6-only box

Michal Babacek (JIRA) jira-events at lists.jboss.org
Tue Apr 3 09:21:48 EDT 2012


     [ https://issues.jboss.org/browse/MODCLUSTER-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Babacek closed MODCLUSTER-290.
-------------------------------------



h3. {color:green}OK{color}
I am closing this JIRA, the original issue is not present in *1.2.1.Beta1* anymore. We can see the mod_cluster module advertises:
{noformat}
[hudson at dev06 mbabacek]$ java Advertize [ff01::1] 6666
ready waiting...
received: HTTP/1.0 200 OK
Date: Tue, 03 Apr 2012 10:43:21 GMT
Sequence: 204
Digest: 3713ded71d7a3f36716e7a4e036b35e1
Server: f774f881-b342-4ad1-aff3-52ae7452b82f
X-Manager-Address: 2620:52:0:105f:214:22ff:fe1c:c53c:8888
X-Manager-Url: /f774f881-b342-4ad1-aff3-52ae7452b82f
X-Manager-Protocol: http
X-Manager-Host: bogus_host_without_reverse_dns
{noformat}
The fact that ER4.1 does not pick up advertising is caused by [JBPAPP-7516] and that is not related to IPv6.
                
> mod_cluster's mod_advertise can not start on IPv6-only box
> ----------------------------------------------------------
>
>                 Key: MODCLUSTER-290
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-290
>             Project: mod_cluster
>          Issue Type: Bug
>    Affects Versions: 1.2.0.Final
>         Environment: Pure IPv6, Apache/2.2.21 (Unix), mod_cluster/1.2.0.Final, Fedora 15
>            Reporter: Michal Babacek
>            Assignee: Jean-Frederic Clere
>            Priority: Blocker
>             Fix For: 1.2.1.Beta1
>
>
> With the following network configuration on Fedora 15: 
> {noformat}
> lo        Link encap:Local Loopback
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> +++
> eth0      Link encap:Ethernet  HWaddr 08:00:27:2F:DD:4A
>           inet6 addr: fe80::a00:27ff:fe2f::dd4a/64 Scope:Link
>           inet6 addr: 1:0:0:1::11/128 Scope:Global
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> +++
> {noformat}
> and this *Apache/2.2.21* (Unix) *mod_cluster/1.2.0.Final* config:
> {code:title=httpd.conf|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1}
> +++
> Listen [1:0:0:1::11]:8000
> +++
> <IfModule manager_module>
>   Listen  [1:0:0:1::11]:6666
>   ManagerBalancerName mycluster
>   <VirtualHost  [1:0:0:1::11]:6666>
>     <Location />
>      Order deny,allow
>      Deny from all
>      Allow from all
>     </Location>
>     KeepAliveTimeout 300
>     MaxKeepAliveRequests 0
>     ServerAdvertise on http://[1:0:0:1::11]:6666
>     AdvertiseFrequency 5
>     AdvertiseGroup [ff01::1]:23364
>     EnableMCPMReceive
>     <Location /mcm>
>        SetHandler mod_cluster-manager
>        Order deny,allow
>        Deny from all
>        Allow from all
>     </Location>
>   </VirtualHost>
> </IfModule>
> {code}
> I get the undermentioned error:
> {code:title=httpd/logs/error_log|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1}
> [Mon Mar 05 13:47:26 2012] [notice] Digest: generating secret for digest authentication ...
> [Mon Mar 05 13:47:26 2012] [notice] Digest: done
> [Mon Mar 05 13:47:27 2012] [error] (EAI 9)Address family for hostname not supported: mod_advertise: ma_group_join apr_sockaddr_info_get(ff01::1:23364) failed
> [Mon Mar 05 13:47:27 2012] [error] (EAI 9)Address family for hostname not supported: mod_advertise: multicast join failed for ff01::1:23364.
> [Mon Mar 05 13:47:27 2012] [notice] Advertise initialized for process 2157
> [Mon Mar 05 13:47:27 2012] [notice] Apache/2.2.21 (Unix) mod_cluster/1.2.0.Final DAV/2 mod_jk/1.2.30 configured -- resuming normal operations
> {code}
> , Apache carries on and http://[1:0:0:1::11]:8000/ displays "It works!".
> What should one do in order to enable IPv6 in *apr* (apr_sockaddr_info_get) ?
> Do you see any configuration errors? Please, share your ideas and tips...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the mod_cluster-issues mailing list