WHM/cPanel is not updated automatically

[sepehrmm]

my current WHM version is 11.46.1. but even though the update preferences settings are set as below it's not updated automatically to latest version which is 11.46.2.0 and I have to run update script (/scripts/upcp) or use "Upgrade to Latest Version" page in WHM.

Update Preferences:

Release Tier: RELEASE
Daily Updates: Automatic
Operating System Package Updates: Automatic

 

[JaredR.]

The 11.46.2.0 additions to the changelog are a little early; 11.46.2 is not in a public update tier yet. RELEASE is still 11.46.1 right now. You can see which version is in each update tier on this page:

Downloads - cPanel Inc.

Sometimes, the changelog is updated before a version is actually published to a public tier. The above page is authoritative for which version is available in each update tier at any given time.

 

[sepehrmm]

ok, tnx for your answer.

 

[sepehrmm]

Now that 11.46.2.3 is out on RELEASE tier on Downloads - cPanel Inc. and also the same is shown on 'Update Preferences' page on whm my version still is WHM 11.46.1 (build 4).
Usually how long does it take to be updated after a new version is released?
Which cron file is responsible for checking and updating?

 

[JaredR.]

upcp runs daily, at the time you set in Home » Server Configuration » Configure cPanel Cron Jobs. cPanel will update the next time cron runs upcp.

You can force a cPanel update at any time by running this command:

# /usr/local/cpanel/scripts/upcp --force

Note that for major version changes, such as the upcoming change from 11.46 to 11.48, we stagger updates over a four-day period, so that only some servers will update to the new version the first day, and then some more the next day, and so on. Even in this case, you can force an update to a new version at any time by using the above command. Staggered updates do not apply to minor version changes, such as 11.46.1 to 11.46.2.

 

[sepehrmm]

tnx for complete response.
Even after 8 days which 11.46.2 is release my panel is not udpated yet!
maybe there's a problem with cronjob. I searched in /etc/crontab file and other cron files in /etc/cron* directories but couldn't find the file which runs 'upcp' script. where this cron file is located?

 

[JaredR.]

Make sure that cron is actually running. You can restart cron using this command:

# /etc/rc.d/init.d/crond restart

You will not find the cron job that runs upcp in /etc/crontab or in /etc/cron*. The cron job that runs upcp is in root's crontab, which is stored in /var/spool/cron. You can see root's crontab by running this command:

# crontab -l -u root

You should see something like this in the output, though the configured time may be different:

0 1 * * * /usr/local/cpanel/scripts/upcp --cron

You can configure the time that upcp is set to run by clicking Home » Server Configuration » Configure cPanel Cron Jobs, in the WebHost Manager. If you click "Save" there, it will make the cron job for you, if it does not exist.

To edit root's crontab from the shell, use this command:

# crontab -e -u root

That opens root's crontab in either vi or nano, whichever is selected on your server. When you save the changes to the file and exit the editor, crond automatically loads the changes, so you do not need to restart the service.

Note: If you edit /var/spool/cron/root directly, the changes will not take effect until you restart crond. Use the crontab command I just mentioned instead of opening /var/spool/cron/root directly in an editor. Alternatively, use the WHM feature I mentioned above, which will edit root's crontab for you.

If cPanel still does not update, please submit a ticket using the link in my signature. There may be something else preventing an update, and if you submit a ticket, we will be able to access the server directly and determine the problem relatively quickly. Please post the ticket number here so that we can follow up.

 

[sepehrmm]

first thank for complete answer.
I don't know how but 'upcp', 'backup' and 'cpbackup' in Configure cPanel Cron Jobs section had a '#' character at the front of the line which made them be commented.
I fixed 'upcp' line and later will check the result.

 

[JaredR.]

Thanks for the update, and you are most welcome. Uncommenting the cron jobs should fix the problem, but please let us know if it does.

 

[sepehrmm]

I checked today morning and it's updated successfully.
sry for all the trouble

 

[JaredR.]

It's no problem at all! I'm glad I was able to help you find the answer.