WHM post-update issues?
hey guys, circling back on that internal server error nightmare i had last week after the cPanel update. thanks to some of your tips, i managed to get the main site back online, but now i'm seeing some really strange issues with other services and general server performance. it's like the update partially worked but left some things hanging.
specifically, i'm seeing intermittent issues with certain cron jobs failing and some PHP applications timing out even though they were fine before. i've checked the standard apache error logs and php-fpm logs, and while there are some warnings, nothing obvious points to a direct cause. i'm starting to wonder if it's something deeper within the WHM configuration that got messed up or isn't optimized for the new cPanel version.
i've tried restarting apache and php-fpm multiple times through WHM, and even re-ran a 'yum update' and 'upcp --force' just in case something was missed. i also checked the easyapache4 profile to ensure everything looks correct, but i'm no WHM expert when it comes to deep-diving into post-update validation.
my question is, what are the common WHM areas or specific config files you guys usually check or re-optimize after a major cPanel update, especially if you're seeing weird performance or service stability issues? are there any specific WHM utilities or commands i should be running to check for inconsistencies or apply recommended post-update settings? any advice on specific WHM modules or settings to review would be super helpful. thanks in advance!
2 Answers
MD Alamgir Hossain Nahid
Answered 1 week agoit's like the update partially worked but left some things hanging.
I completely get this frustration; server updates can sometimes feel like playing whack-a-mole with services, and cPanel updates, in particular, occasionally leave a trail of minor inconsistencies that are a pain to track down. It sounds like you're dealing with some deeper WHM server management issues post-update, which is a common scenario when the update script doesn't quite nail all the configuration migrations.
Beyond the basic restarts and EasyApache re-provisioning, here are a few critical areas and commands I typically check when facing these kinds of performance and stability issues after a major cPanel update:
- PHP-FPM Configuration: Since you're seeing PHP timeouts, dive into
WHM > Service Configuration > PHP-FPM Configuration. Check both the global settings and any domain-specific overrides. Key directives to review arerequest_terminate_timeout(often the culprit for timeouts),pm.max_children,pm.start_servers, andpm.max_spare_servers. These might need adjusting based on your server's resources and traffic. Also, ensure PHP-FPM is actually enabled and correctly configured as the handler for your sites underWHM > Software > MultiPHP Manager. - Rebuild Configuration Files: Sometimes, an update can leave behind old config snippets or fail to properly integrate new ones. Running these commands via SSH can help force a refresh:
/scripts/rebuildhttpdconf(Rebuilds Apache configuration)/scripts/php_fpm_config --rebuild(Rebuilds PHP-FPM configuration)/scripts/update_php_ini_perms(Corrects permissions for PHP configuration files)
/usr/local/cpanel/scripts/restartsrv_allis a good idea. - Cron Job Environment: For failing cron jobs, verify the PHP binary path and environment variables within the cron job itself. A cPanel update might change default PHP versions or paths. Test the cron command manually via SSH to see if it executes correctly in that environment.
- System Logs: Beyond Apache and PHP-FPM logs, check
/var/log/messagesand rundmesgto look for any kernel-level warnings or out-of-memory errors that might indicate deeper resource contention or system issues related to the cPanel update troubleshooting.
Have you specifically reviewed your PHP-FPM pool configurations and adjusted the request_terminate_timeout value yet?
Miguel Martinez
Answered 1 week agoYeah, rebuilding the configs and tweaking those PHP-FPM pools totally sorted out the cron job failures and weird timeouts, so big thanks for that! Everything feels way more stable now, tho I've started noticing some odd delays with outbound emails from Exim and Mailman isn't sending new subscription notifications. Any common post-update checks for email services you guys usually do?