it runs something similar that does the same thing. Might be a FC5 issue. Not interested in switching to an OS that isn't a testing OS?
it runs something similar that does the same thing. Might be a FC5 issue. Not interested in switching to an OS that isn't a testing OS?
since the version is on edge I am wondering if I should update it now or just wait until the june 13 for a stable version of cpanel 11 ??
It's best to wait if you can. EDGE is not recommended for production servers. You can upgrade to RELEASE or CURRENT to get cPanel 11 earlier. The release dates are listed at http://www.cpanel.net/cpanel11
Step 3 is not needed once you update to Perl 5.8.8. The SARE rules works fine then, as the bug uncovered by Spamassassin 3.2 is fixed in 5.8.8. For a while, Spamassassin was running as nobody as well although that seems to be fixed now. However if not, you may need to chown /var/spool/mqueue/.spamassassin to nobody.
You may also need to force an update of Compress::Raw::Zlib and Scalar::Util as some of our servers DNS stopped working after that.
If you have the script installers from the plugins, they may stop functioning too. This seems to be due to the fact that previously, the YAML files are owned by root. If you come across this, you would need chown them to the account owner. I wrote a simple script, but I leave it to your own devices as well.
If you have any host restrictions on tcpwrappers, such as on denying all by default on hosts.deny, you would need to add the following to hosts.allow:
cpaneld : ALL
whostmgrd : ALL
webmaild : ALL
Otherwise you would be completely lockout of Cpanel / WHM and Webmail after the upgrade till you add the above.
If you run Fantastico or Rvskin, please make sure you update them to the latest. Otherwise certain things may stop functioning.
You may also need to force an update of Compress::Raw::Zlib and Scalar::Util as some of our servers DNS stopped working after that.
If you have the script installers from the plugins, they may stop functioning too. This seems to be due to the fact that previously, the YAML files are owned by root. If you come across this, you would need chown them to the account owner. I wrote a simple script, but I leave it to your own devices as well.
If you have any host restrictions on tcpwrappers, such as on denying all by default on hosts.deny, you would need to add the following to hosts.allow:
cpaneld : ALL
whostmgrd : ALL
webmaild : ALL
Otherwise you would be completely lockout of Cpanel / WHM and Webmail after the upgrade till you add the above.
If you run Fantastico or Rvskin, please make sure you update them to the latest. Otherwise certain things may stop functioning.
Seems I am already running maildir. Said it was enabled when I ran that command.
Impressed
I've just finished installing Cpanel/WHM 11 and so far, I am very impressed that everything seems to be working fine on a CentOS 4.4 machine. I'm currently upgrading Apache to 2.2. Let's see what happens after that... Will my PHP scripts continue to work? Only time will tell...
I've just finished installing Cpanel/WHM 11 and so far, I am very impressed that everything seems to be working fine on a CentOS 4.4 machine. I'm currently upgrading Apache to 2.2. Let's see what happens after that... Will my PHP scripts continue to work? Only time will tell...
I know 2.2 builds still have a lot of issues, however 11.5.16-EDGE_12521 should handle them a lot better then the first release. I'd recommend 2.0 as it has had much more testing @ this point.
What would you recommend as a Enterprise OS?Beware of FC5, though, support for it ends in about a month. You'd be better advised to move to an Enterprise OS that doesn't need upgrading every 4 to 6 months
RedHat Enterprise (RHE4/5) if you want direct OS support from RedHat, or CentOS (v4/v5) if you don't want to fork out for the support license.
It is entirely dependent on the number of mailboxes and the number of messages in each. And the amount of resources available to the server (CPU power/RAM etc) - the lower the resource usage at the time you convert, the quicker the process should be.
Definitely plan to do the maildir conversion during a quiet period and give at least four hours, although this can vary greatly as mentioned above.
The number of mailboxes is not relevant, it's the amount of email in each mbox file that exists in each account together with the available server resources that will determine how long it will take. An example is a client server I did this for recently only had a handful of accounts, but one inbox file of ~5GB and a low spec server and it took around 15 hours to complete. A high spec server could munch through as much in quicker time.
It's not going to be possible to predict how long it is going to take, simply that you should be aware that it could take some time and you should not kill off the conversion processes and allow it to complete.
It's not going to be possible to predict how long it is going to take, simply that you should be aware that it could take some time and you should not kill off the conversion processes and allow it to complete.
I really wouldn't upgrading to any latest current or release build of CPANEL at this stage.
A lot of things wont work, like mail, account copying, 2 of which we tried.
If you run a couple of servers with different version of CP, you really SHOULD NOT upgrade to 11 at all unless you intend to upgrade ALL YOUR SERVERS to maintain "portability" of your sites.
A lot of things wont work, like mail, account copying, 2 of which we tried.
If you run a couple of servers with different version of CP, you really SHOULD NOT upgrade to 11 at all unless you intend to upgrade ALL YOUR SERVERS to maintain "portability" of your sites.
I am showing:
exim (exim-4.63-1_cpanel_smtpctl_av_rewrite_mm2_mmmtrap_exiscan_md5pass)
There are no mbox or maildir entries in the cpanel.config either. Will this be an issue when upgrading to v11? I'm on the release tree.
** Nevermind, it was mbox and have since migrated to maildir
Last edited:
