cPanel 11 Partial/Broken Updates

[KH-Paul]

If you're having troubles with account creation / modification / termination or with cPanel-level one time account backups then run the following commands in the root-level ssh session to fix the problem and to complete update from cPanel v10 to v11 on your system:

/usr/local/cpanel/bin/checkperlmodules
/scripts/upcp –force


Here is a copy of the email we've received from cPanel which also contains information about how to check if your cPanel installation might be broken:

=============
Dear cPanel Partner,

Since the release of cPanel 11, we have noticed a number of instances
where the cPanel 11 release update failed to complete. The symptoms can
vary, including blank pages being drawn from certain features, with the
most commonly reported issue being that account creations are exiting
prematurely, claiming immediately that the account creation is complete.
Additionally, account creation, suspension, unsuspension and removal may
fail.

This is occurring because /scripts/updatenow was executed (or run from update system software in whm) without a
subsequent call to upcp. As a result, /scripts is updated to the latest
available modules available with cPanel 11, while the rest of the system
remains configured for the older builds.

You can confirm whether or not this is the case on your system by
executing from the command line:
perl -c /scripts/wwwacct

If this command returns errors, then you will need to update. Here is what
you can expect to see if a problem exists:
root@localhost [~]# perl -c /scripts/wwwacct
Can't locate Whostmgr/Accounts/Create.pm in @INC (@INC contains:
/usr/local/cpanel /scripts /usr/lib/perl5/5.8.7/i686-linux
/usr/lib/perl5/5.8.7 /usr/lib/perl5/site_perl/5.8.7/i686-linux
/usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.5
/usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3
/usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl/5.8.1
/usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl .) at
/scripts/wwwacct line 10.
BEGIN failed--compilation aborted at /scripts/wwwacct line 10.
root@localhost [~]#

Suggested Fixes:

If you wish to stay with cPanel 10.x, you will need to execute the
following commands from the command line:

/usr/local/cpanel/bin/checkperlmodules
echo "CPANEL=stable" >> /etc/cpupdate.conf
/scripts/upcp --force

If you would like to continue with the cPanel 11 updates (recommended),
you will need to execute the following commands from the command line:

/usr/local/cpanel/bin/checkperlmodules
/scripts/upcp –force

If the problems persists after applying the updates, please contact our
support team ASAP with an outline of the symptoms and the login
credentials for the system, and we will take care of it with the utmost
priority.
=============

Regards,
Paul

 

[Dan]

Paul,

If I am reading this correctly

/usr/local/cpanel/bin/checkperlmodules
echo "CPANEL=stable" >> /etc/cpupdate.conf
/scripts/upcp --force

updates are simply being set to the stable version. Well in a couple of weeks even the stable version will be updated to version 11. If a person is serious about not upgrading couldn't they just go into their WHM and set updates to manual?

 

[KH-Paul]

Dan,

This is correct. Run these 3 commands if you want to run cPanel 10 for a little while. At the end it will also be replaced with сPanel v11 after it will be pushed to STABLE tree. As for not upgrading - it might be a bit late to talk about this if any but STABLE tree was selected and cPanel was upgraded already.
During last couple days cPanel team fixed number of issues and it seems to be running more or less ok if you use RELEASE tree. I, personally, like v11 - it suppose to reduce number of support tickets we receive as, for example, it is now possible to edit php.ini right through WHM, etc. The biggest problem I'm seeing at this time is integration of various 3rd party products such as RVskin - not everything is working in current RVskin version if you run cPanel v11.

Regards,
Paul

US hosting from KnownHost, the US VPS specialists.

 

[khiltd]

I'm not so sure I want WHM going anywhere near my php.ini file. This isn't stable yet, right?

 

[Dan]

I'm not so sure I want WHM going anywhere near my php.ini file. This isn't stable yet, right?

Khiltd,

I'm not sure if it is or not as I wouldn't use it either