Error on Server Monitoring (first major cPanel update 110 to 130 since Elevate)

Answered

CBAWS

• August 25, 2025 15:00

Last week I elevated Centos 7.9 to AlmaLinux 8 after a long testing. Everything went smoothly (except I had to disable Comodo rules in ModSecurity in order to get Apache working again). I did not manually update cPanel after the elevate completed, and I kind of let it happen on schedule. Today I saw bunch of new features including server monitoring. But after clicking on save it showed me this error below. I had to go back and select "No Thank you" to get back to cPanel. Does anyone know how to fix this? Current cPanel version is now 130.0.5

 

Unable to create an user account in Server Monitoring for user: “root”. at /usr/local/cpanel/Whostmgr/360Monitoring/Setup.pm line 128.

 at /usr/local/cpanel/Whostmgr/360Monitoring/Setup.pm line 128.

Whostmgr::360Monitoring::Setup::initialize() called at /usr/local/cpanel/Whostmgr/360Monitoring/Setup.pm line 340

Whostmgr::360Monitoring::Setup::local_enable() called at /usr/local/cpanel/Cpanel/Config/ConfigObj/Driver/ServerMonitoring.pm line 40

Cpanel::Config::ConfigObj::Driver::ServerMonitoring::enable(Cpanel::Config::ConfigObj::Driver::ServerMonitoring=HASH(0x35e9d08), HASH(0x3e89970)) called at /usr/local/cpanel/Cpanel/Config/ConfigObj.pm line 757

Cpanel::Config::ConfigObj::action(Cpanel::FeatureShowcase=HASH(0x288b678), "enable", "server_monitoring") called at whostmgr/bin/whostmgr3.pl line 482

main::feature_showcase_do("feature_showcase_do") called at /usr/local/cpanel/Whostmgr/Dispatch.pm line 384

Whostmgr::Dispatch::_do_call("feature_showcase_do", HASH(0x285f928), HASH(0x285faf0)) called at /usr/local/cpanel/Whostmgr/Dispatch.pm line 177

Whostmgr::Dispatch::dispatch("feature_showcase_do", 14337, ARRAY(0x285fa78)) called at whostmgr/bin/whostmgr3.pl line 182

 

• 

  cPRex Jurassic Moderator

  • August 26, 2025 17:10

  Hey there!  Are you referring to the Feature Showcase that is presented when you first access WHM?  If so, you are correct that you need to choose one of the options in order to continue to WHM, but I wouldn't expect the "save" option to throw an error.

  Unfortunately I don't have any details on that specific error on my end so it would be best to create a ticket so this can be investigated directly on the machine.

  0
• 

  CBAWS

  • August 26, 2025 18:53

  Hi,

  Yes, I am referring to the showcase screen. By default, all the options come with "Enabled" switch on. Until it is saved, it does not enable anything. So once the Save it clicked it tries to do something but fails. I will create a ticket because right now I cannot even access the plugins screen.

   

  Not a HASH reference at /usr/local/cpanel/Whostmgr/Addons/Pkgr/Cache.pm line 222.

   at /usr/local/cpanel/Whostmgr/Addons/Pkgr/Cache.pm line 222.

  Whostmgr::Addons::Pkgr::Cache::_modules(HASH(0x34aeb00)) called at /usr/local/cpanel/Whostmgr/Addons/Pkgr/Cache.pm line 92

  Whostmgr::Addons::Pkgr::Cache::_LOAD_FRESH("Whostmgr::Addons::Pkgr::Cache") called at /usr/local/cpanel/Cpanel/CacheFile.pm line 239

  Cpanel::CacheFile::load("Whostmgr::Addons::Pkgr::Cache") called at /usr/local/cpanel/Whostmgr/Addons/Pkgr/Cache.pm line 81

  Whostmgr::Addons::Pkgr::Cache::load("Whostmgr::Addons::Pkgr::Cache") called at /usr/local/cpanel/Whostmgr/Addons/Pkgr.pm line 62

  Whostmgr::Addons::Pkgr::get_modules() called at whostmgr/bin/whostmgr2.pl line 2477

  main::manage_plugins("manage_plugins") called at /usr/local/cpanel/Whostmgr/Dispatch.pm line 384

  Whostmgr::Dispatch::_do_call("manage_plugins", HASH(0x32c48f0), HASH(0x32c85b8)) called at /usr/local/cpanel/Whostmgr/Dispatch.pm line 177

  Whostmgr::Dispatch::dispatch("manage_plugins", 1, ARRAY(0x32c80d8), HASH(0x32c85b8)) called at whostmgr/bin/whostmgr2.pl line 775

   

  0
• 

  cPRex Jurassic Moderator

  • August 26, 2025 18:53

  If you could post that ticket number here once you have it I'd like to follow along.

  0
• 

  CBAWS

  • August 26, 2025 20:43
  • Edited

  Support's AI suggested this and it worked :)

  /scripts/check_cpanel_pkgs --fix

  Edit: Ticket #95775174 can be closed now. Thank you.

  0
• 

  cPRex Jurassic Moderator

  • August 27, 2025 14:28

  I'm glad that's all it took!  If that resolved the issue it would seem a forced update also would have likely taken care of this.

  0

Please sign in to leave a comment.