Emmanuel Cecchet wrote:
Hi Alex,
.. then the controller's log output can be seen here:
http://ohmslaw.org.uk/controllerLog.txt
It looks like you have a problem with your group communication
configuration. For some reason the message seems to be never delivered.
Ah, interesting! Is this a message to the JMX controller running on that
very same machine you're referring to?
When I'm trying to run this example, I'm not running a mirrored
controller+db on another machine (although that is the ultimate intended
setup) - but that shouldn't be a showstopper for enabling a backend as I
described, right?
Do you have any firewall (iptables or such) configured on the machine
that could drop the packets?
This looks like a network configuration issue to me.
Yup, we're running iptables on the machine. Here's the current rules in
/etc/sysconfig/iptables:
# Firewall configuration written by system-config-securitylevel
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p 50 -j ACCEPT
-A RH-Firewall-1-INPUT -p 51 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m udp -p udp --dport 1090
-j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 1090
-j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 25322
-j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m udp -p udp --dport 25322
-j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 3306
-j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j
ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
As you can see, I'm permitted port 25322 and 1090 (both TCP and UDP)
from anywhere.
I could always run tcpdump to see exactly what is going on with network
traffic. Except that I think tcpdump tends not to see traffic to the
loopback interface (lo/127.0.0.1).
Keep us posted with your findings,
Yup, thanks for your support and help.
Alex
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
