WHM Service Diagnostics Misreporting cPanel service monitor Status Post-Kernel Update: Deep Dive Needed

Author
Hassan Ali Author
|
20 hours ago Asked
|
1 Views
|
0 Replies
0

Iโ€™m encountering a baffling issue on one of our production cPanel/WHM servers, running AlmaLinux 8, after a recent kernel update. The core problem revolves around WHMโ€™s cPanel service monitor, which is incorrectly reporting critical services as down or flapping, despite these services running optimally.

Problem Statement:
Immediately following a kernel patch, WHMโ€™s Service Diagnostics began to flag services like httpd, mysql, and even cPanel itself, as frequently failing and restarting. The peculiar aspect is that end-user experience remains completely unaffected, and manual checks via SSH confirm that all daemons are consistently up and processing requests without any hitches. This discrepancy is generating constant false alerts, which is, understandably, a major operational headache.

Troubleshooting Steps Taken:

  • Reviewed /var/log/chkservd.log and /usr/local/cpanel/logs/tailwatchd_log, which show the erroneous 'down' and 'started' entries corresponding to the WHM reports.
  • Verified service status for all affected daemons using systemctl status <service> and ps aux | grep <daemon> commands, consistently confirming they are active and running.
  • Attempted to restart chkservd and tailwatchd services via WHM and command line (systemctl restart chkservd) to refresh their state.
  • Thoroughly checked for any signs of resource exhaustion (RAM, CPU, I/O bottlenecks) and disk space issues; all metrics are well within normal operating parameters.
  • Examined network configuration and firewall rules (CSF/LFD) for any recent changes that might be intermittently blocking chkservd's health checks.
  • Rebuilt the cPanel service monitor configuration through WHM's interface.
  • Executed /scripts/upcp --force to ensure all cPanel components, including the service monitor and chkservd, are fully up-to-date and correctly configured for the current environment.

Observed Error/Output:

[2023-11-15 08:30:05 -0600] warn [chkservd] The httpd service is down.
[2023-11-15 08:30:06 -0600] info [chkservd] httpd started.
[2023-11-15 08:30:15 -0600] warn [chkservd] The mysql service is down.
[2023-11-15 08:30:16 -0600] info [chkservd] mysql started.
[2023-11-15 08:30:20 -0600] warn [chkservd] The cPanel service is down.
[2023-11-15 08:30:21 -0600] info [chkservd] cPanel started.
... (This cycle repeats every few minutes, triggering alerts but services remain functional)

Specific Question:
I'm seeking advanced diagnostic methodologies or insights into known kernel-level incompatibilities that could specifically interfere with WHM's internal cPanel service monitor mechanisms and how chkservd performs its checks, without actually impacting the underlying service uptime. Are there any specific kernel modules, system calls, or process introspection methods that chkservd relies on heavily which might be affected by recent kernel updates, leading to these false positives? Iโ€™m looking for deep-dive suggestions beyond standard cPanel troubleshooting.

Any insights from experienced WHM administrators who have faced similar phantom service alerts post-kernel update would be immensely appreciated. Help a brother out please...

0 Answers

No answers yet.

Be the first to provide a helpful answer!

Your Answer

You must Log In to post an answer and earn reputation.