Skip to main content
We are aware of an issue after updating to cPanel versions 11.110.0.65, 11.126.0.21, or 11.128.0.11, some cPanel plugins or features are no longer functioning properly including WP Toolkit. Please see the following article for more information and updates:
Update to latest cPanel 110, 126, or 128 versions removes "addonfeatures" directory.

No response from subprocess

Comments

8 comments

  • cPanelMichael
    Hello, Please post the output from the following commands:
    cat /usr/local/cpanel/version arch
    Also, could you try running the "/scripts/upcp --force" command and let us know if the issue persists? Keep in mind that cPanel version 54 is nearing EOL status: cPanel Long-Term Support - Documentation - cPanel Documentation I recommend updating to a newer version at your earliest convenience. Thank you.
    0
  • caroseuk
    Hi Michael, Output below:
    cat /usr/local/cpanel/version 11.54.0.15 arch x86_64
    We haven't tried running upcp with --force. Will this break anything? This is a production server.
    0
  • cPanelMichael
    We haven't tried running upcp with --force. Will this break anything? This is a production server.

    cPanel updates should not break any services, but I encourage you to open a support ticket using the link in my signature if you'd like us to complete the update on your behalf. You can post the ticket number here and we can update this thread with the outcome. Thank you.
    0
  • caroseuk
    Thanks Michael, we will register with the support portal now.
    0
  • cPanelMichael
    Hello, To update, this relates to a bug that was fixed, with the resolution backported into cPanel version 54.0.32: Fixed case CPANEL-9827: Update cpanel-perl-514-Compress-Raw-Lzma to 2.068-2.cp1146. Updating cPanel to the latest version on the version 54 build tier should address the issue. Thank you.
    0
  • caroseuk
    Hi Michael, We ended up doing the upcp --force command and updated to version 60 build 28. Had a few issues with old tailwatchd process running but we killed it and WHM started the newer process. All seems to be working great now. Thanks!
    0
  • cPanelMichael
    I'm happy to see the issue is now resolved. Thank you for updating us with the outcome.
    0
  • paulysanju
    I also have get that error now it is cleared
    0

Please sign in to leave a comment.