How do we keep cPanel from updating?

[FreedomNet]

We have:

WHM 11.15.0 cPanel 11.18.6-S24739
REDHAT Enterprise 3 i686 on standard - WHM X v3.1.0

We have set the "Update Config" to "Never Update", but the auto update process is ignoring this and running anyway. Yesterday it updated to a "release" level and today it reset the "Update Config" settings back to automatic and ran upcp as normal.

We have some applications that do not work well with some of the newer cpanel changes and need to stop all cpanel updates until we can resolve these.

Is there a firewall setting we can set to prevent future updates? Any other method to prevent cpanel from updating?

Any help and guidance would be greatly appreciated.

[cPanelDavidG]

We have:

WHM 11.15.0 cPanel 11.18.6-S24739
REDHAT Enterprise 3 i686 on standard - WHM X v3.1.0

We have set the "Update Config" to "Never Update", but the auto update process is ignoring this and running anyway. Yesterday it updated to a "release" level and today it reset the "Update Config" settings back to automatic and ran upcp as normal.

We have some applications that do not work well with some of the newer cpanel changes and need to stop all cpanel updates until we can resolve these.

Is there a firewall setting we can set to prevent future updates? Any other method to prevent cpanel from updating?

Any help and guidance would be greatly appreciated.

I know in a 11.23 release, we added logic to prevent external scripts from attempting to update cPanel/WHM when updates were set to Never. However, 11.23 is not yet on STABLE.

[FreedomNet]

I know in a 11.23 release, we added logic to prevent external scripts from attempting to update cPanel/WHM when updates were set to Never. However, 11.23 is not yet on STABLE.

Thanks for the information.

I don't think it is an external script resetting the "when to update" indicators, but I could be wrong. Are any of these an option to keep the update upcp function from running?

- closing a firewall port

- removing a cron job

- renaming a script to keep the update upcp funtion form running?

[cPanelDavidG]

Thanks for the information.

I don't think it is an external script resetting the "when to update" indicators, but I could be wrong. Are any of these an option to keep the update upcp function from running?

- closing a firewall port

- removing a cron job

- renaming a script to keep the update upcp funtion form running?

Actually what was happening is sometimes third party scripts would be ignoring the "when to update" indicators and update cPanel anyway. The new logic prevents third party scripts from upgrading cPanel when updates are set to Never.

In the meantime, if you code your custom scripts to use our new hooks and APIs in cPanel 11 - these scripts are unlikely to break between upgrades. I'd be more than happy to assist you with matching your existing scripts to the appropriate APIs and hooks to ensure long-term functionality of your customizations. Just drop me an email to sales@cpanel.net

[FreedomNet]

...In the meantime, if you code your custom scripts to use our new hooks and APIs in cPanel 11 -

The problem is we don't have any custom scripts that we wrote on this server. While it is an older system, (RH Enterprise 3) about the only thing that was done to it beyong RH and cPanel/WHM was adding Mailscanner, BFD, Mailwatch, tripwire and rootkithunter.

[cpanelkenneth]

There was a bug, fixed during the 11.23 development cycle, where the /scripts directory would still be updated thus causing /scripts to be out of sync with /usr/local/cpanel. A hotfix was provided for this that changed the setting in /etc/cpupdate.conf from CPANEL=never to CPANEL=release. After the change a message about this, along with encouragement to re-run /scripts/upcp, is output.

To determine if this what happened, please examine the logs in /var/cpanel/updatelogs

[FreedomNet]

There was a bug, fixed during the 11.23 development cycle, where the /scripts directory would still be updated thus causing /scripts to be out of sync with /usr/local/cpanel. A hotfix was provided for this that changed the setting in /etc/cpupdate.conf from CPANEL=never to CPANEL=release. After the change a message about this, along with encouragement to re-run /scripts/upcp, is output.

To determine if this what happened, please examine the logs in /var/cpanel/updatelogs

Thank you, yes that is the case, that has happend. After we restored to a prior version (WHM 11.15.0 cPanel 11.18.6-S24739) it now appears that CPANEL=never is getting changed to "Manual Stable" now. Will the hot fix handle that also? If it will, can I trouble you for the hotfix id?

THANKS AGAIN!

[cpanelkenneth]

Thank you, yes that is the case, that has happend. After we restored to a prior version (WHM 11.15.0 cPanel 11.18.6-S24739) it now appears that CPANEL=never is getting changed to "Manual Stable" now. Will the hot fix handle that also? If it will, can I trouble you for the hotfix id?

THANKS AGAIN!

The hotfix is run every upcp cycle. If the hotfix detects the /scripts directory is out-of-sync with /usr/local/cpanel (the hotfix performs some specific checks) then the CPANEL value in /etc/cpupdate.conf will be changed to release. The hotfix will not change the CPANEL value to anything else.

Once /scripts and /usr/local/cpanel are in harmony, if you want to totally disable automatic updates, then use the following values in your /etc/cpupdate.conf:

BANDMINUP=never
COURIERUP=never
CPANEL=never
EXIMUP=never
FTPUP=never
MYSQLUP=never
PYTHONUP=never
RPMUP=never
SYSUP=never

[FreedomNet]

The hotfix is run every upcp cycle. If the hotfix detects the /scripts directory is out-of-sync with /usr/local/cpanel (the hotfix performs some specific checks) then the CPANEL value in /etc/cpupdate.conf will be changed to release. The hotfix will not change the CPANEL value to anything else.

Once /scripts and /usr/local/cpanel are in harmony, if you want to totally disable automatic updates, then use the following values in your /etc/cpupdate.conf:

BANDMINUP=never
COURIERUP=never
CPANEL=never
EXIMUP=never
FTPUP=never
MYSQLUP=never
PYTHONUP=never
RPMUP=never
SYSUP=never

Frankly this "Updating to Release" is broken!!!

I keep going in after UPCP runs and reseting it back to NEVER - every day. Today AGAIN it updated to RELEASE level from Stable. What part of NEVER UPDATE do you guys not understand?

Now I can not get cpanel back to a release that does not have all the tailwatch enhancements. These "enhancements" are driving my processor utilization numbers thorugh the roof and cpanelsync runs for hours.

Can anyone tell me how to get cpanel back to a Stable version, the one before the tailwatch enhancements were put in?????

Please help - I have a server that is crippled!

[cpanelkenneth]

Frankly this "Updating to Release" is broken!!!

I keep going in after UPCP runs and reseting it back to NEVER - every day. Today AGAIN it updated to RELEASE level from Stable. What part of NEVER UPDATE do you guys not understand?

Now I can not get cpanel back to a release that does not have all the tailwatch enhancements. These "enhancements" are driving my processor utilization numbers thorugh the roof and cpanelsync runs for hours.

Can anyone tell me how to get cpanel back to a Stable version, the one before the tailwatch enhancements were put in?????

Please help - I have a server that is crippled!

Please open a support ticket at https://tickets.cpanel.net/submit/