Skip to main content
Question

Issue with WebConsole – Reports and SLA failing after failover

  • March 30, 2026
  • 1 reply
  • 9 views

Forum|alt.badge.img+1

hello

We are experiencing an issue with the WebConsole on our Commvault environment following a failover.

 

Failover windows cs to linux cs  

Environment

  • Commvault version: 11.40.26
  • CommServe OS: Linux
  • WebConsole / Command Center hosted on: linux

Issue Description

  • The WebConsole is not functioning correctly.
  • Scheduled reports and SLA reports are failing.
  • jobs are working without any issue.

Observed Behavior

  • Access to Command Center (/commandcenter) is working (HTTP 200).
  • Access to WebConsole (/webconsole) returns HTTP 404 (Application Not Found).
  • Reports fail with the following error:
    • "Failed to get the list of command centers"
    • "There is no WebConsole available to proceed further"

Logs (relevant excerpts)

  • scheduleReport.log:
    • GetWebConsoleURLList() - There is no WebConsole available to proceed further
  • JobManager.log:
    • Failed to get the list of command centers for web server id [0]
  • Apache logs:
    • /commandcenter → 200
    • /webconsole → 404

Actions Already Performed

  • Verified that WebConsole and Command Center components are installed
  • Restarted Commvault services
  • Performed repair via cvpkgadd
  • Verified Apache and WebServer services are running
  • Confirmed WebConsole binaries are present on disk

Current Assessment

It appears that:

  • Command Center is operational
  • WebConsole (legacy UI) is not deployed or not registered properly
  • No Web Server entry seems available from CommServe perspective (web server id = 0)

Request

Could you please assist with:

  • Verifying the Web Server / WebConsole registration in the CommServe database
  • Providing the correct procedure to redeploy or re-register the WebConsole
  • Confirming if this behavior is expected after failover and if additional steps are required

Please let us know if additional logs or diagnostics are required.

 

1 reply

Sougato Roy
Vaulter
Forum|alt.badge.img+11
  • Vaulter
  • March 30, 2026

hello

We are experiencing an issue with the WebConsole on our Commvault environment following a failover.

 

Failover windows cs to linux cs  

Environment

  • Commvault version: 11.40.26
  • CommServe OS: Linux
  • WebConsole / Command Center hosted on: linux

Issue Description

  • The WebConsole is not functioning correctly.
  • Scheduled reports and SLA reports are failing.
  • jobs are working without any issue.

Observed Behavior

  • Access to Command Center (/commandcenter) is working (HTTP 200).
  • Access to WebConsole (/webconsole) returns HTTP 404 (Application Not Found).
  • Reports fail with the following error:
    • "Failed to get the list of command centers"
    • "There is no WebConsole available to proceed further"

Logs (relevant excerpts)

  • scheduleReport.log:
    • GetWebConsoleURLList() - There is no WebConsole available to proceed further
  • JobManager.log:
    • Failed to get the list of command centers for web server id [0]
  • Apache logs:
    • /commandcenter → 200
    • /webconsole → 404

Actions Already Performed

  • Verified that WebConsole and Command Center components are installed
  • Restarted Commvault services
  • Performed repair via cvpkgadd
  • Verified Apache and WebServer services are running
  • Confirmed WebConsole binaries are present on disk

Current Assessment

It appears that:

  • Command Center is operational
  • WebConsole (legacy UI) is not deployed or not registered properly
  • No Web Server entry seems available from CommServe perspective (web server id = 0)

Request

Could you please assist with:

  • Verifying the Web Server / WebConsole registration in the CommServe database
  • Providing the correct procedure to redeploy or re-register the WebConsole
  • Confirming if this behavior is expected after failover and if additional steps are required

Please let us know if additional logs or diagnostics are required.

 

Hi ​@mahmoud Hatira ,

Please refer to Web Console Deprecation: What Customers Need to Know article and check if that helps with your issue. ​@Pradeep Could you please assist here?

Thank you,

Roy