[
https://issues.jboss.org/browse/MODCLUSTER-290?page=com.atlassian.jira.pl...
]
Michal Babacek commented on MODCLUSTER-290:
-------------------------------------------
Well, I've tried with *dev06* with this configuration:
{code:title=.../conf.d/modcluster.conf|borderStyle=solid|borderColor=#ccc|
titleBGColor=#F7D6C1}
# MOD_CLUSTER_ADDS
<IfModule manager_module>
Listen [2620:52:0:105f:214:22ff:fe1c:c53c]:8888
ManagerBalancerName qacluster
<VirtualHost [2620:52:0:105f:214:22ff:fe1c:c53c]:8888>
<Location />
Order deny,allow
Deny from all
Allow from all
</Location>
KeepAliveTimeout 60
MaxKeepAliveRequests 0
#ServerAdvertise on http://@IP@:port
AdvertiseFrequency 5
#AdvertiseSecurityKey secret
AdvertiseGroup [ff01::1]:6666
EnableMCPMReceive
<Location /mcm>
SetHandler mod_cluster-manager
Order deny,allow
Deny from all
Allow from all
</Location>
</VirtualHost>
</IfModule>
{code}
{code:title=.../standalone/configuration/standalone-ha.xml|borderStyle=solid|borderColor=#ccc|
titleBGColor=#F7D6C1}
+++
<subsystem xmlns="urn:jboss:domain:modcluster:1.0">
<mod-cluster-config advertise-socket="modcluster"
sticky-session="true" sticky-session-force="false"/>
</subsystem>
</profile>
<interfaces>
<interface name="management">
<inet-address
value="${jboss.bind.address.management:[2620:52:0:105f:214:22ff:fe1c:c53c]}"/>
</interface>
<interface name="public">
<inet-address
value="${jboss.bind.address:[2620:52:0:105f:214:22ff:fe1c:c53c]}"/>
</interface>
<interface name="unsecure">
<inet-address
value="${jboss.bind.address.unsecure:[2620:52:0:105f:214:22ff:fe1c:c53c]}"/>
</interface>
</interfaces>
<socket-binding-group name="standard-sockets"
default-interface="public"
port-offset="${jboss.socket.binding.port-offset:0}">
+++
<socket-binding name="modcluster" port="0"
multicast-address="[ff01::1]" multicast-port="6666"/>
+++
</socket-binding-group>
+++
{code}
h3. Apache
No problem in the log:
{noformat}
notice] SELinux policy enabled; httpd running as context user_u:system_r:unconfined_t
notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
warn] module proxy_ajp_module is already loaded, skipping
notice] Digest: generating secret for digest authentication ...
notice] Digest: done
notice] Advertise initialized for process 21019
debug] proxy_util.c(1818): proxy: grabbed scoreboard slot 0 in child 21021 for worker
proxy:reverse
debug] proxy_util.c(1934): proxy: initialized single connection worker 0 in child 21021
for (*)
debug] proxy_util.c(1818): proxy: grabbed scoreboard slot 0 in child 21023 for worker
proxy:reverse
debug] proxy_util.c(1837): proxy: worker proxy:reverse already initialized
debug] proxy_util.c(1934): proxy: initialized single connection worker 0 in child 21023
for (*)
debug] proxy_util.c(1818): proxy: grabbed scoreboard slot 0 in child 21025 for worker
proxy:reverse
debug] proxy_util.c(1837): proxy: worker proxy:reverse already initialized
debug] proxy_util.c(1934): proxy: initialized single connection worker 0 in child 21025
for (*)
debug] proxy_util.c(1818): proxy: grabbed scoreboard slot 0 in child 21027 for worker
proxy:reverse
debug] proxy_util.c(1837): proxy: worker proxy:reverse already initialized
debug] proxy_util.c(1934): proxy: initialized single connection worker 0 in child 21027
for (*)
notice] Apache/2.2.17 (Unix) DAV/2 mod_cluster/1.2.1.Beta1 configured -- resuming normal
operations
info] Server built: Apr 18 2011 10:59:17
debug] prefork.c(1018): AcceptMutex: sysvsem (default: sysvsem)
debug] proxy_util.c(1818): proxy: grabbed scoreboard slot 0 in child 21029 for worker
proxy:reverse
debug] proxy_util.c(1837): proxy: worker proxy:reverse already initialized
debug] proxy_util.c(1934): proxy: initialized single connection worker 0 in child 21029
for (*)
debug] mod_proxy_cluster.c(678): update_workers_node starting
debug] mod_proxy_cluster.c(693): update_workers_node done
debug] mod_proxy_cluster.c(678): update_workers_node starting
debug] mod_proxy_cluster.c(693): update_workers_node done
debug] mod_proxy_cluster.c(678): update_workers_node starting
debug] mod_proxy_cluster.c(693): update_workers_node done
debug] mod_proxy_cluster.c(678): update_workers_node starting
debug] mod_proxy_cluster.c(693): update_workers_node done
debug] mod_proxy_cluster.c(678): update_workers_node starting
debug] mod_proxy_cluster.c(693): update_workers_node done
{noformat}
I can even see:
{noformat}
[hudson@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}
h3. EAP6 ER4.1
Startup looks good:
{noformat}
(MSC service thread 1-3) Initializing mod_cluster 1.2.1.Beta1-redhat-1
(MSC service thread 1-3) Listening to proxy advertisements on ff01:0:0:0:0:0:0:1:6666
{noformat}
h3. Telnet /mcm
So, why there are no nodes connecting to the balancer and Mod_cluster Manager console
shows:
{code}
[hudson@dev06 mbabacek]$ telnet 2620:52:0:105f:214:22ff:fe1c:c53c 8888
Trying 2620:52:0:105f:214:22ff:fe1c:c53c...
Connected to 2620:52:0:105f:214:22ff:fe1c:c53c.
Escape character is '^]'.
GET /mcm
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html><head>
<title>Mod_cluster Status</title>
</head><body>
<h1>mod_cluster/1.2.1.Beta1</h1>
<a
href="/mcm?nonce=b9cdd776-684f-4a0f-933b-9372ce15b0a7&refresh=10">Auto
Refresh</a>
<a
href="/mcm?nonce=b9cdd776-684f-4a0f-933b-9372ce15b0a7&Cmd=DUMP&Range=ALL">show
DUMP output</a>
<a
href="/mcm?nonce=b9cdd776-684f-4a0f-933b-9372ce15b0a7&Cmd=INFO&Range=ALL">show
INFO output</a>
</body></html>
{code}
Hmm...
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