SOLVED CPANEL-40724 - Constant cpanel_php_fpm failed on a dnsonly server

[benito]

Hello!

Since a day or two one of my dnsonly servers started to send me emails about this service now working.

(XID px2a5q) The “cpanel_php_fpm” service is down.
The subprocess “/usr/local/cpanel/scripts/restartsrv_cpanel_php_fpm” reported error number 255 when it ended.

I can disable the notifications, but I like to know if its something that needs to be fixed. I have two dnsonly servers, exactly the same hard and software on both. I don't log into them since a year, so, no human intervention on this. Only one it's having this error.

Thanks

 

[cPRex]

Hey there! This is a known issue that our developers are checking out in case CPANEL-40724. I'll be sure to let them know about this post as well.

There isn't anything you need to do to fix this as the warning is being sent in error. To stop the warnings, you can run these commands to ensure the WordPress Toolkit software is not installed, and that monitoring for PHP-FPM is disabled:

rpm -e wp-toolkit-cpanel
whmapi1 configureservice service=cpanel_php_fpm enabled=0 monitored=0

 

[benito]

Thanks @cPRex,

I saw wp-toolkit-cpanel in Top Processes column and already disable it. It has nothing to do on a DNSOnly server.

Doing the same with cpanel_php_fpm service and monitor.

 

[tyuuu]

Hi,i also get the notify mail on dnsonly server.

 

[ejsolutions]

Did I not already say (another DNS-only thread) the WP-Toolkit had no right to be there?

 

[PeteS]

Hey there! This is a known issue that our developers are checking out in case CPANEL-40724. I'll be sure to let them know about this post as well.

There isn't anything you need to do to fix this as the warning is being sent in error. To stop the warnings, you can run these commands to ensure the WordPress Toolkit software is not installed, and that monitoring for PHP-FPM is disabled:

rpm -e wp-toolkit-cpanel
whmapi1 configureservice service=cpanel_php_fpm enabled=0 monitored=0

Is the issue simply limited to WTK being rolled into DNSOnly in error, and along with it the monitoring?

Since the notificationst just started this morning for me, and only on one DNSOnly server, am I correct to expect other DNSOnly servers to follow in time? What was it that got rolled on in a daily update, and why? (In part I'm asking if WTK was already there (why?) and just the monitoring that changed, or more.)

 

[cPRex]

Is the issue simply limited to WTK being rolled into DNSOnly in error, and along with it the monitoring?

Yes, that's the whole issue summed up nicely.

 

[cPRex]

Update - this is scheduled to be fixed in version 106 when that is released to the public.

 

[ejsolutions]

this is scheduled to be fixed in version 106

Would be good if munin was reinstated at the same time!