Whe currently testing the CSF clust feature. At first everything looks fine and works okay.
Until today, now i see that CSf tries to talk to the other servers with other IP addresses.
Not all the servers in the same cluster have this issue. Al servers are CentOS with cpanel
Cluster env: description with example IP's
Server1
main IP: 11.22.33.44
multi shared IP's
nameserver 11.22.33.12
server2
main IP: 11.22.33.45
multi shared IP's
nameserver 11.22.33.20
server3
main IP: 11.22.33.46
multi shared IP's
server4
main IP: 44.33.22.11
multi shared IP's
server5
main IP: 33.44.22.11
multi shared IP's
CSF Cluster configured with Main IP's.
Now some servers use a other IP address of that server.
What is see is that it take's the IP address of de nameserver on that server.
For example.. that without any config change de server uses de ip of de nameserver.
That gives the message:
Apr 14 18:53:57 server1 lfd[8926]: *WARNING* 11.22.33.20 (NL/Netherlands/ns1.server1.net) attempted to connect to the Cluster but not a member!
CSF Cluster use wrong IP address
-
- Moderator
- Posts: 1524
- Joined: 01 Oct 2008, 09:24
CSF v 5.02 does the trick but...
for this case... whe have serveral servers with multiple ip's of multible classes
because of the same classes and subnets (in our case 255.255.255.192) the server can talk to the other servers without a gateway (1 hop to compleet)
i use the new setting to force CSF to use the main IP and not the IP from same class then the destination server.
thanks again for this quick fix... it solved my problem...
when the new field is empty it still uses the wrong IP..
Advice: change the text:
[original text]
# If a cluster member should send requests on an IP other than the default IP,
# set it here
[change to]
# If a cluster member should send requests on an Fixed IP set it here.
because of the same classes and subnets (in our case 255.255.255.192) the server can talk to the other servers without a gateway (1 hop to compleet)
i use the new setting to force CSF to use the main IP and not the IP from same class then the destination server.
thanks again for this quick fix... it solved my problem...
when the new field is empty it still uses the wrong IP..
Advice: change the text:
[original text]
# If a cluster member should send requests on an IP other than the default IP,
# set it here
[change to]
# If a cluster member should send requests on an Fixed IP set it here.