-
1. Re: Cannot start cluster slave - connection timed out
victor213 Jan 10, 2013 2:32 PM (in response to victor213)Well.... Disabling iptables temporarily has resolved the issue. But this is not a solution, just confirmation that iptables is the cause. Not sure how I can be more permissive than opening tcp and udp ports 1024-65535
-
2. Re: Cannot start cluster slave - connection timed out
victor213 Jan 10, 2013 3:49 PM (in response to victor213)I've wiresharked the connection and I see them talking to one another on port 9999. Why the time out?
-
3. Re: Cannot start cluster slave - connection timed out
victor213 Jan 10, 2013 5:24 PM (in response to victor213)Confirmed - disabling iptables resolves the issue. This is not acceptable tho.
What access is required to join a slave into the master domain?
-
4. Re: Cannot start cluster slave - connection timed out
rhusar Jan 11, 2013 7:44 AM (in response to victor213)For the domain mode, port 9999 will be necessary, so you will need to allow outgoing and allow incoming on that port on both nodes. Are all the other necessary ports in
socket-binding-group
open too?BTW For clustering itself you will typically need to allow multicast. So something like:
[root@localhost ~]$ iptables -t filter -A INPUT -i eth0 -d 224.0.0.0/4 -j ACCEPT