Centos 6.6 + 0.9.8.2

With a fresh install of Centos 6.6 on a Vultr.com VPS (1 gig ram),
Installed CWP 0.9.8.1, and all systems and functions worked ok.

Wiped system and reinstalled Centos 6.6
Installed CWP 0.9.8.2
1)
To permanently set hostname required adding two keys to /etc/sysctl.conf.  I added "kernel.hostname = vps.domain.com" and "kernel.domainname = domain.com", then ran "#sysctl -p /etc/sysctl.conf"
sysctl produced several errors:
error: "net.bridge.bridge-nf-call-ip6tables" is an unknown key
error: "net.bridge.bridge-nf-call-iptables" is an unknown key
error: "net.bridge.bridge-nf-call-arptables" is an unknown key
I don't know if this is important, and probably the keys I added were not the cause.  However these errors did not occur with CWM 0.9.8.1

2)  Dovecot will not run.
"Starting Dovecot Imap: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 94: Unknown setting: service_count [FAILED]" is the error message on the CWM dashboard
After Postfix Rebuild with no options selected, Dovecot again fails to start with a new error message:
"Starting Dovecot Imap: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 135: Unknown setting: managesieve_max_line_length [FAILED]" is the error message on dashboard.

3) Turning on CSF locked up CWM.  I had to reboot server to regain CWM functions.
Once CSF is started, it produces error messages to root's mail, like:
Fri Mar 13 11:04  22/928   "lfd on vps.domain.com: Excessive resource usage: mysql (1210 (Parent PID:1108))"
Fri Mar 13 11:13  18/635   "lfd on vps.domain.com: Suspicious File Alert"
Fri Mar 13 11:39  21/768   "lfd on vps.domain.com: Excessive resource usage: postfix (1474 (Parent PID:1466)"

4) Clicked on 'View iptables rules' which locked up CWP again for a long period of time
Output of 'top' command yields:
top - 12:14:29 up  1:05,  2 users,  load average: 0.00, 0.00, 0.00
Tasks:  98 total,   1 running,  97 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   1020228k total,   568664k used,   451564k free,    61856k buffers

Apache is running and serving the main sample web site while CWP is locked up.

It seems 0.9.8.2 is unusable as is on Centos 6.6

looks like

1. this is related with your server, and why are you even changing it in the sysctl.conf

In the CWP you have an option to change the hostname, but hostname needs to be set when VPS is installed and your provider can do that.

2. once you change the hostname you need to rebuild mail server configuration, instructions are on the cwp wiki

3. again test if your vps provider has all required modules for the CSF firewall

4. looks like also related with the same thing.

In reference to #1, the change hostname function in CWP does not completely work.  When the server is rebooted, it reverts to its original setting if not changed with sysctl on my Vultr VPS.  Otherwise, I would not done it.  This is a standard minimal install of Centos, and as far as I can tell there are no customizations.

Ref #2,  yes I did that.

Ref #3, the test said I did.

Ref #4, fireing off mails to root every few minutes is not helpful.  I had to disable lfd to stop the warning mails.  There were over 600 warning mails to root in less than a day.  These were only accessible after installing the 'mail' program.... they were not sent to the mail account set up in CWP, but they are a problem none the less. 
I have CWP installed on two different VPS at two different hosting providers, and both have the same problems.  One vps is a Centos 6.5 at dotblock.com and the other is a Centos 6.6 at Vultr.com.

installation of the CWP doesn't make any kind of changes in your kernel settings and for all information's regarding this you will need to check with your hosting provider since kernel settings  one the VPS are part of the hosting provider.

Also when installing CWP you already need to have set hostname properly before starting the installation, as stated in the installation instructions.

installation of the CWP doesn't make any kind of changes in your kernel settings and for all information's regarding this you will need to check with your hosting provider since kernel settings  one the VPS are part of the hosting provider.

Also when installing CWP you already need to have set hostname properly before starting the installation, as stated in the installation instructions.

And in fact I did set the hostname before installing CWP, and since it was a fresh install of CENTOS 6.6, I had no reason to change any of the settings except as noted in your installation instructions.  I had set the  hostname with the hostname command, I edited /etc/hosts,  etc.  When I saw it reverted to a default every time I rebooted the server, I tried the 'Change Hosname" function in CWP, but again, the hostname change was only temporary.

The reason I reported this is to help you, not me, as it seems to be a bug where your 'Change Hostname' function does not work, at least with Centos 6.6.  The hostname reverts to its previous value upon reboot unless sysctl.conf is also modified with the kernel keys.  CWP is a very nice product, but it does have some bugs it seems.  Is this a problem with just Centos 6.6?  or is it a problem with just one hosting provider?  I don't know the answer to that because dotblock does not offer Centos 6.6 and Vultr does not offer 6.5, so I can't compare them.

hostname change doesn't have anything with the CWP, since this is only the part of the CentOS and you need to check on that with your hosting provider.

You probably didn't change the hostname on all required locations like.
/etc/hosts
/etc/sysconfig/network
hostname "new.hostname.com"

but CWP.admin integrated functions is doing all required changes mentioned above.
Also changing the hostname from command line you would need to regenerate new ssl and all other things.

Instructions
- Hostname needs to be set before installing any kind of control panel

If you are changing the hostname after ithe installation of the control panel then you'll need to change it from the CWP.admin and rebuild your mail server with this new hostname by using "Postfix Manager" which is also in the CWP.admin.

hostname change doesn't have anything with the CWP, since this is only the part of the CentOS and you need to check on that with your hosting provider.

You probably didn't change the hostname on all required locations like.
/etc/hosts
/etc/sysconfig/network
hostname "new.hostname.com"

As I said before, I did those things first, and they don't permanently change the hostname in Centos 6.6

but CWP.admin integrated functions is doing all required changes mentioned above.
Also changing the hostname from command line you would need to regenerate new ssl and all other things.

Well, obviously not, as the hostname change was not permanent.
At the time of installation, the hostname was correct... this was not a problem.  It reverted to its original incorrect value upon reboot.

Instructions
- Hostname needs to be set before installing any kind of control panel

If you are changing the hostname after ithe installation of the control panel then you'll need to change it from the CWP.admin and rebuild your mail server with this new hostname by using "Postfix Manager" which is also in the CWP.admin.
[/quote]
Well, in Centos 6.6, you web panel change hostname function does not work as I detailed.  I suppose you can ignore this, but if it caused me a problem, someone else is going to have the same problem.

we are not ignoring any issue but since you have an issue with the hostname on reboot this is your operating system issue and you will need to check it with your hosting provider.

I had the same problem after adding an -A- record for a subdomain.  Deleting the A record solved the problem, no more email.  I stumbled upon by reading the mail logs in /etc/var/.  There I discovered fake email address using my subdomain.  I have no idea why that fixed it but it did.