CSF 6.28 WARNING: CLUSTER_PORT sanity check.

[Ilia]

I just updated to the latest CSF and have a bug when saving configuration:

Code: Select all

WARNING: CLUSTER_PORT sanity check. CLUSTER_PORT = . Recommended range: 1023-65535 (Default: 7777) 

It doesn't matter which value I put - it always return an error?

Anybody else reproduces the same error?

Thanks in advance,
Ilia

[ForumAdmin]

I'm not able to replicate the problem. What is the full line that you have for CLUSTER_PORT in /etc/csf/csf.conf?

[Ilia]

I have had default sence ever, never changed it. After update I started to see it!

Code: Select all

# Cluster communication port (must be the same on all member servers). There
# is no need to open this port in the firewall as csf will automatically add
# in and out bound rules to allow communication between cluster members
CLUSTER_PORT = "7777"

I din't install version 6.27 and went directly from 6.26 to 6.28? Could that be the issue?

P.S. Then I tried to change it as I saw the error but it was just the same error!?

[ForumAdmin]

For now, I'd suggest doing the following:

Code: Select all

sed -i 's/^CLUSTER_PORT.*$//' /usr/local/csf/lib/sanity.txt

We'll look at the sanity code for the next release.

[Ilia]

It appears, that I don't have sanity.txt at the moment, is this correct?

Code: Select all

cat /usr/local/csf/lib/sanity.txt
cat: /usr/local/csf/lib/sanity.txt: No such file or director

[ForumAdmin]

That makes no sense at all. I'd suggest running:

Code: Select all

csf -uf

Then do:

Code: Select all

/bin/ls /usr/local/csf/lib

which should look like:

Code: Select all

Crypt  csf.div  csf.help  Geo  HTTP  Net  restricted.txt  sanity.txt  webmin

[Ilia]

Very sorry! I was on the local machine (logged out) from the server when was runnning it!

Everything is correct about

Code: Select all

sed -i

command.

Sould I uninstall CSF maybe and reinstall it anew?

[Ilia]

I would like to confirm that the discribed above error has been fixed in version 6.29!

All is fine now!

Thanks!

[ForumAdmin]

It should be fixed now:
http://blog.configserver.com/?p=1973

[Ilia]

Yes, it's fixed!
Thanks!