cPanel & WHM 76 - Known Issues
Hello Everyone!
cPanel & WHM version 76 is published to the STABLE Workaround: Rename the hostname to something other than "whm.domain.tld". Note that service subdomains are not recommended for use as the hostname per the guidelines at:
Fixed in Version 76.0.5
[SPOILER="CPANEL-23314 - CSF Suspicious File Alerts (/tmp/pma_template_compiles) after V76 Update"]
Case Number: CPANEL-23314
Status: Fixed in version 76.0.5.
Description: Accessing phpMyAdmin as a cPanel user in cPanel & WHM version 76 leads to the creation of pma_template_compiles_$user files in the system's /tmp directory instead of in the /home/$user/tmp/ directory (as with Roundcube and Horde).
Workaround: See instructions in thread below.
Forums Thread: Case Number: CPANEL-23589
Status: Fixed in 76.0.2
Description: Updates to v76 can break dovecot if the configuration is customized in a supported manner via our configuration templating
Workaround: Move/Rename /var/cpanel/templates/dovecot2.2/main.local then run /scripts/builddovecotconf and restart dovecot.
Forums Thread: = 5.22.1 dependency"]
Case Number: CPANEL-23793
Status: Fixed by reinstalling the Let's Encrypt plugin.
Description: cPanel updates fail with the following error message when outdated iterations of the cpanel-letsencrypt RPM are installed:
Workaround: Manually reinstall the Let's Encrypt plugin using the following commands:
Then, proceed with the cPanel update:
Forums Thread: Case Number: N/A Description: In cPanel & WHM version 76, we upgraded the PHP version used for cPanel & WHM (cpsrvd) from PHP 5.6 to PHP 7.2: Implemented case CPANEL-22332: Update cPanel internal PHP to upstream version 7.2.7 As part of this change, a different ionCube Loader version is utilized. This change requires plugin developers to publish updates to their plugins that include files re-encoded with the newer ionCube version. Otherwise, the plugin will fail to load and generate error messages like this in /usr/local/cpanel/logs/error_log upon the upgrade to cPanel & WHM version 76:
Workaround: See Case Number: N/A Description: SpamAssassin may fail to start in version 76 if a custom or OS SpamAssassin version was manually installed on the system in the past. Attempts to restart SpamAssassin via "/scripts/restartsrv_spamd" will result in an error message like this in the output:
An error is also seen when running the /usr/local/cpanel/3rdparty/bin/sa-update command:
Workaround: Run the following commands via SSH as root to ensure the cPanel-provided SpamAssassin is utilized:
[SPOILER="Incoming email stops working after v76 upgrade when using Anti-spam DNSBL plugin by BOates"] Case Number: N/A - The plugin is not updated to work with the latest SpamAssassin version. Description: Incoming email will stop working on systems using Anti-spam DNSBL plugin by BOates upon upgrading to cPanel & WHM version 76. Here's an example of the error message visible in /var/log/exim_mainlog on affected systems: [QUOTE] failed to expand ACL string "domain.tld/${perl{trimdomain}{$sender_address_domain}}": Can't locate Mail/SpamAssassin/Util/RegistrarBoundaries.pm in @INC (you may need to install the Mail::SpamAssassin::Util::RegistrarBoundaries module)
Workaround: Remove the plugin using the plugin developer's uninstall instructions: [QUOTE]UNINSTALL 1.) Remove the file: /usr/local/cpanel/etc/exim/perl/trimdomain 2.) Remove the snippet previously added to the file: /usr/local/cpanel/etc/exim/acls/ACL_MAIL_POST_BLOCK/custom_begin_mail_post 3.) Rebuild exim.conf by running: /scripts/buildeximconf 4.) Restart Exim by running: /scripts/restartsrv_exim 5.) The DNSBL is now entirely uninstalled
Forums Thread: You can ask questions or add comments about an issue by replying to its corresponding forums thread. Additionally, please feel free to
***** FATAL: Test install failed: error: Failed dependencies:
cpanel-perl(CryptX) >= 5.22.1 is needed by (installed) cpanel-letsencrypt-2.16-6.1.noarch
Workaround: Manually reinstall the Let's Encrypt plugin using the following commands:
/scripts/uninstall_lets_encrypt_autossl_provider
/scripts/install_lets_encrypt_autossl_provider
Then, proceed with the cPanel update:
/scripts/upcp
Forums Thread: Case Number: N/A Description: In cPanel & WHM version 76, we upgraded the PHP version used for cPanel & WHM (cpsrvd) from PHP 5.6 to PHP 7.2: Implemented case CPANEL-22332: Update cPanel internal PHP to upstream version 7.2.7 As part of this change, a different ionCube Loader version is utilized. This change requires plugin developers to publish updates to their plugins that include files re-encoded with the newer ionCube version. Otherwise, the plugin will fail to load and generate error messages like this in /usr/local/cpanel/logs/error_log upon the upgrade to cPanel & WHM version 76:
PHP Fatal error: The file /usr/local/cpanel/whostmgr/docroot/cgi/plugin-name/index.php was encoded by the ionCube Encoder for PHP 5.6 and cannot run under PHP 7.1 or later.
Workaround: See Case Number: N/A Description: SpamAssassin may fail to start in version 76 if a custom or OS SpamAssassin version was manually installed on the system in the past. Attempts to restart SpamAssassin via "/scripts/restartsrv_spamd" will result in an error message like this in the output:
info [restartsrv_spamd] The service 'spamd' failed to restart. Trying '/usr/local/cpanel/3rdparty/perl/526/bin/spamd'.
"warn [restartsrv_spamd] The system encountered an error while starting the "spamd" service with the command "/usr/local/cpanel/3rdparty/perl/526/bin/spamd --daemonize --max-spare=1 --max-children=3 --allowed-ips=127.0.0.1,::1 --pidfile=/var/run/spamd.pid": The subprocess reported error number 255 when it ended.
"failed.
An error is also seen when running the /usr/local/cpanel/3rdparty/bin/sa-update command:
# /usr/local/cpanel/3rdparty/bin/sa-update
config: failed to parse line, skipping, in "/etc/mail/spamassassin/v310.pre"
Workaround: Run the following commands via SSH as root to ensure the cPanel-provided SpamAssassin is utilized:
1. /usr/local/bin/perl /scripts/perlmods -u Mail::SpamAssassin
Or, if your system perl is in /usr/bin, use this command instead:
/usr/bin/perl /scripts/perlmods -u Mail::SpamAssassin
2. mv /etc/mail/spamassassin /etc/mail/spamassassin-backup
3. /scripts/check_cpanel_rpms --fix
4. /scripts/upcp --force
[SPOILER="Incoming email stops working after v76 upgrade when using Anti-spam DNSBL plugin by BOates"] Case Number: N/A - The plugin is not updated to work with the latest SpamAssassin version. Description: Incoming email will stop working on systems using Anti-spam DNSBL plugin by BOates upon upgrading to cPanel & WHM version 76. Here's an example of the error message visible in /var/log/exim_mainlog on affected systems: [QUOTE] failed to expand ACL string "domain.tld/${perl{trimdomain}{$sender_address_domain}}": Can't locate Mail/SpamAssassin/Util/RegistrarBoundaries.pm in @INC (you may need to install the Mail::SpamAssassin::Util::RegistrarBoundaries module)
Workaround: Remove the plugin using the plugin developer's uninstall instructions: [QUOTE]UNINSTALL 1.) Remove the file: /usr/local/cpanel/etc/exim/perl/trimdomain 2.) Remove the snippet previously added to the file: /usr/local/cpanel/etc/exim/acls/ACL_MAIL_POST_BLOCK/custom_begin_mail_post 3.) Rebuild exim.conf by running: /scripts/buildeximconf 4.) Restart Exim by running: /scripts/restartsrv_exim 5.) The DNSBL is now entirely uninstalled
Forums Thread: You can ask questions or add comments about an issue by replying to its corresponding forums thread. Additionally, please feel free to
Please sign in to leave a comment.
Comments
0 comments