you are AWESOME, thanks for posting this!!!!Here's a checklist of items that can help things go smoothly when upgrading to cPanel 11:
1) Make sure you're running Perl 5.8.8:
a) check perl -v to make sure it says 5.8.8
b) if you see 5.8.7 or something else, follow these steps:
1) wget http://layer1.cpanel.net/perl588installer.tar.gz
2) tar xfvz perl588installer.tar.gz
3) cd perl588installer
4) ./install
5) /usr/local/cpanel/bin/checkperlmodules
2) Upgrade YAML::Syck:
1) /scripts/realperlinstaller YAML::Syck
3) Remove any SARE/openprotect spamassassin rules
These seem to be not compatible with SpamAssassin v3.2 see This Thread for more info.
4) Upgrade from mbox to maildir.
This can be done by running /scripts/convert2maildir.
WARNING: Make sure to run the option to back up your mail first.
When running the conversion, you should watch out for the following:
**IT WILL TAKE A LONG TIME. Don't kill the process or you'll be left with a lot of half-converted mailboxes and angry clients who aren't getting mail.
**Mail will not be delivered during the conversion, it will be instead queued until the conversion is complete and then delivered.
**Make sure your mailbox permissions are ok before converting and make sure your clients aren't currently using mailboxes called /cur /new or /tmp
These 3 steps should make things a lot smoother if you are running an older version of cPanel.
When I
Code:
/scripts/realperlinstaller File::Copy::Recurisve
Code:
[email protected] [/etc]# /scripts/realperlinstaller File::Copy::Recurisve
Fetching CPAN timestamp...Done
Testing connection speed...(this could take a while)...Done
Ping:1.168 Testing connection speed to cpan.hexten.net using pureperl...(158800.00 bytes/s)...Done
Ping:8.357 Testing connection speed to mirror.hiwaay.net using pureperl...(157350.00 bytes/s)...Done
Ping:15.687 Testing connection speed to cpan-du.viaverio.com using pureperl...(62880.00 bytes/s)...Done
Three usable mirrors located
Three usable mirrors located
Mirror Check passed for cpan.hexten.net (/index.html)
commit: wrote '/usr/lib/perl5/5.8.8/CPAN/Config.pm'
CPAN: File::HomeDir loaded ok (v0.65)
CPAN: Storable loaded ok (v2.16)
Going to read /home/.cpan/Metadata
Database was generated on Sat, 09 Jun 2007 09:05:59 GMT
Warning: Cannot install File::Copy::Recurisve, don't know what it is.
Try the command
i /File::Copy::Recurisve/
to find objects with matching identifiers.
CPAN: Time::HiRes loaded ok (v1.9707)
perlmod--Install done
Code:
[email protected] [/etc]# i /File::Copy::Recurisve/
-bash: i: command not found
Code:
Modules matching your query (click to install)
No Modules MatchcPanel: 10.9.0-S13517 (STABLE)
Perl5.8.8
What am I missing?
Last edited:
M
Matt_Carey
Guest
updated checklist
Here's a checklist of items that can help things go smoothly when upgrading to cPanel 11:
2) Upgrade YAML::Syck and File::Copy::Recurisve:
1) /scripts/realperlinstaller YAML::Syck
2) /scripts/realperlinstaller File::Copy::Recurisve
There's a typo in the preceding checklist. Recursive is spelled incorrectly. Following is the corrected checklist:
2) Upgrade YAML::Syck and File::Copy::Recursive:
1) /scripts/realperlinstaller YAML::Syck
2) /scripts/realperlinstaller File::Copy::Recursive
Here's a checklist of items that can help things go smoothly when upgrading to cPanel 11:
2) Upgrade YAML::Syck and File::Copy::Recurisve:
1) /scripts/realperlinstaller YAML::Syck
2) /scripts/realperlinstaller File::Copy::Recurisve
There's a typo in the preceding checklist. Recursive is spelled incorrectly. Following is the corrected checklist:
2) Upgrade YAML::Syck and File::Copy::Recursive:
1) /scripts/realperlinstaller YAML::Syck
2) /scripts/realperlinstaller File::Copy::Recursive
I believe that is a perl command. You would enter it as if you were running perl directly from cli.
Typo?
I tried pasting this and my server complained that it didn't know what "File::Copy::Recurisve" was.
I used "/scripts/realperlinstaller File::Copy::Recursive" and it worked just fine.
Now I feel like an idiot that I quick replied instead of reading the latest posts.
Last edited:
Hi!
I got a new box prepared for CPanel11 for testing purpose, how should I do to install the newest version of cpanel 11 ? (this box never installed cpanel before)
I mean if for normal install, it should begin with cd /home and sh latest, for cpanel 11, what should I do ?
I got a new box prepared for CPanel11 for testing purpose, how should I do to install the newest version of cpanel 11 ? (this box never installed cpanel before)
I mean if for normal install, it should begin with cd /home and sh latest, for cpanel 11, what should I do ?
Since cPanel 11 is now in the RELEASE build, when you perform an installation of cPanel/WHM, by default you are installing the latest RELEASE version of cPanel 11.
No worries, thanks for trying to help
I thought it might be a typo, but then I've seen plenty of *nix file names with odd spellings, so I decided not to question it, for once. Won't be doing *that* again!
I have done with my new box installed cpanel 11, but, why the apache not 2.0 ? Do I need to do something ?
Also, when creating the first account in WHM, it seems all right but httpd failed, and I found if I comment out this line, httpd can be restart, it is:
Also, when creating the first account in WHM, it seems all right but httpd failed, and I found if I comment out this line, httpd can be restart, it is:
Code:
#BytesLog /usr/local/apache/domlogs/joe.myname.com-bytes_logUpgrading cPanel does NOT automatically upgrade Apache.
If you are on a version of cPanel that has EA3, you will be able to upgrade to Apache 2/2.2 by going in WHM -> Software -> Apache Update.
Thanks for starting this thread guys, it was a huge help to me. I followed DaveDark's guidelines here and have WHM/cPanel 11 running just fine on my production server. So far, I really like the changes, ESP the security center, and the server is running very well.
On my other machine, one that I use for testing only, I had exactly this problem when adding the first account to the server. I'm concerned, however, that it will happen when I add a new account to my production server, which already has dozens of accounts set up on it. What's the word on this?
After install of cPanel do:
There is a race condition in the installer where the installer attempts to build and install those modules, but /usr/local/cpanel doesn't exist (let alone any contents). It doesn't always happen, but we are examining how to best resolve it.
Code:
cd /usr/local/cpanel/apache
make all
make installThis worked for the testing server, thanks. Looks like /usr/local/cpanel exists on the production server, so maybe this won't be an issue there.
This is what i get too.
One more thing, i upgraded to v11.1.0 before i upgraded perl from 587 to 588, will it make a difference, if so what should i do (previous whm v10.8.0
For those of you that ended up with only partially converted mbox mail boxes, here's what I did:
I used mb2md to convert them folder by folder. Here is what I did:
1. in SSH as root:
/usr/local/cpanel/3rdparty/mb2md/mb2md -s /home/username/mail/specificuser/PERSONAL
-d /home/username/mail/specificuser/.del
2. in Horde create a new Folder called PERSONAL.
3. mv .del/cur/*.* .PERSONAL/cur/
4. rm .del -r -f
5. repeat for the next folder, just changing the folder name.
You wouldn't want to do this for hundreds of folders, but it isn't bad for just a few, and it works like a charm.
I used mb2md to convert them folder by folder. Here is what I did:
1. in SSH as root:
/usr/local/cpanel/3rdparty/mb2md/mb2md -s /home/username/mail/specificuser/PERSONAL
-d /home/username/mail/specificuser/.del
2. in Horde create a new Folder called PERSONAL.
3. mv .del/cur/*.* .PERSONAL/cur/
4. rm .del -r -f
5. repeat for the next folder, just changing the folder name.
You wouldn't want to do this for hundreds of folders, but it isn't bad for just a few, and it works like a charm.
great thread!!
after upgrading my freebsd machine to cpanel 11 I tried to convert the mailboxes lastnight and everything seems to have worked because I got a mail with subject: "[maildir] SERVERNAME been converted to maildir" twice.
And accessing mail with imap works fine, but pop3 seems to be broken. Am I the first to have this problem?
ran /scripts/upcp --force and /scripts/eximup --force and /scripts/courierup --force all multiple times in different orders, reinstalled the libtool port (couldn't find libtool-libs in ports), but still pop3 doesn't work...
opened a ticked (196737)
after upgrading my freebsd machine to cpanel 11 I tried to convert the mailboxes lastnight and everything seems to have worked because I got a mail with subject: "[maildir] SERVERNAME been converted to maildir" twice.
And accessing mail with imap works fine, but pop3 seems to be broken. Am I the first to have this problem?
ran /scripts/upcp --force and /scripts/eximup --force and /scripts/courierup --force all multiple times in different orders, reinstalled the libtool port (couldn't find libtool-libs in ports), but still pop3 doesn't work...
opened a ticked (196737)
Last edited:
