cPanel publishes a change log for all EasyApache updates that you can use to track changes:
Whatever changes you find published there can be obtained on a standard cPanel server by running the update script
/scripts/upcp , or simply the
yum update command via SSH as the root user.
However, when cPanel is installed on CloudLinux, all updates are provided by the CloudLinux repositories which lag behind cPanel's official publish date by about 2 weeks in most cases.
If you're on a CloudLinux server and cPanel has published a change to EasyApache that you're waiting on, you can use the following procedure to determine if that change has been applied to your server.
- Open the Easy Apache change log page that contains the change that you are interested in:
cPanel's Additional Change Logs (Including EasyApache)
- Note the date that the change is listed under. You should expect the change to hit CloudLinux about two weeks after the published date on the cPanel ChangeLogs.
- Note the package name that the change is listed under. For example:
- Note the case ID associated with the change. For example:
- Login to your CloudLinux cPanel server via SSH or Terminal as the root user
- Run an update to ensure any available changes have been installed:
- or -
- Use the
--changelogoption for the rpm command to print the change log of the associated package that you noted from step 3:
rpm -q --changelog ea-nginxNOTE: The dates printed in the RPM change log represent the date when the developer finished writing that code, not when cPanel officially published the change.
- Search the output of the rpm command for the case ID that you noted in step 4 above. If you cannot find that case ID, it means that CloudLinux has not yet published the change for your server.
- Optionally, you can filter the output of the change log with grep:
rpm -q --changelog ea-nginx | grep EA-9924