Skip to main content

CPANEL-40724 - Constant cpanel_php_fpm failed on a dnsonly server

Comments

8 comments

  • cPRex Jurassic Moderator
    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
    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.
    0
  • tyuuu
    Hi,i also get the notify mail on dnsonly server.
    0
  • ejsolutions
    Did I not already say (another DNS-only thread) the WP-Toolkit had no right to be there? :rolleyes:
    0
  • 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.)
    0
  • cPRex Jurassic Moderator
    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.
    0
  • cPRex Jurassic Moderator
    Update - this is scheduled to be fixed in version 106 when that is released to the public.
    0
  • ejsolutions
    this is scheduled to be fixed in version 106

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

Please sign in to leave a comment.