Just a note that I ran into a problem with certain cluster members were not responding. I double checked their configurations and everything looked good. Restarting LFD wouldn't fix anything. When I ran csf --cping from the master node two of them reported "no reply" even though when I looked at their logs you could see "lfd[16189]: Cluster member <ip> (CA/Canada/<hostname>) said PING!"
It turns out that they were a few CSF versions behind (Upgrading csf from v9.27 to 9.29...) Upgrading all the cluster members to 9.29 fixed the issue and all could talk to each other again.
I'm not sure its a bug or what but I guess its pretty good to make sure that all members in the cluster are upgraded the same version at the same time.
some cluster members not responding
-
ForumAdmin
- Moderator
- Posts: 1524
- Joined: 01 Oct 2008, 09:24
Re: some cluster members not responding
That is completely to be expected since v9.29 is the first version to have responding cluster members, so all members have to be running v9.29+ to respond.
Re: some cluster members not responding
That makes sense. Something else I'm noticing is that cluster member denied reasons are getting cut off. Is that by design?
Code: Select all
lfd: Cluster member <ip> (CA/Canada/web1.myhostname.com) said, DENY 163.172.68.103, Reason:[(apache-useragents) Failed apache-u]
Code: Select all
lfd: Cluster member <ip> (CA/Canada/web1.myhostname.com) said, DENY 2.134.172.211, Reason:[2.134.172.211 (KZ/Kazakhstan/-), 3 distribut]
-
ForumAdmin
- Moderator
- Posts: 1524
- Joined: 01 Oct 2008, 09:24
Re: some cluster members not responding
No, it should not be cutting it off. I'm hoping v9.30 which we're about to release will resolve this.
Re: some cluster members not responding
Just a note that v9.30 fixed this now. Nothing is getting cut off any more 