Skip to main content
Solved

Web console not available on Passive node during Test failover


Forum|alt.badge.img+7

Hi,

We have CommServe LiveSync setup. During test failover I noticed that Web Console and Command Center is not running on passive node, with error message “This service is currently unavailable”.
Is it expected behavior or not for Test failover? 
 

 

Best answer by AndresL

Problem solved, .NET core installation repair helped on Passive node.

View original
Did this answer your question?

4 replies

Forum|alt.badge.img+11
  • Vaulter
  • 237 replies
  • May 27, 2024

Hi @AndresL ,

 

It might be expected depending in your configuration.

We won’t know without checking logs, but I would assume the WebServer is only installed on the Active CS Node, therefore we can expect this when that Node becomes passive.

 

If you want the WebConsole and CommandCenter to remain operational during CS Failover, you could configure the WebServer and CommandCenter packages on a dedicated server, then set TPPM for the WebServer communication back to the CSDB


Forum|alt.badge.img+7
  • Author
  • Byte
  • 37 replies
  • May 27, 2024
Javier wrote:

Hi @AndresL ,

 

It might be expected depending in your configuration.

We won’t know without checking logs, but I would assume the WebServer is only installed on the Active CS Node, therefore we can expect this when that Node becomes passive.

 

If you want the WebConsole and CommandCenter to remain operational during CS Failover, you could configure the WebServer and CommandCenter packages on a dedicated server, then set TPPM for the WebServer communication back to the CSDB

No, we have Identical configuration of Primary and passive nodes, both with web server.


Forum|alt.badge.img+11
  • Vaulter
  • 237 replies
  • May 27, 2024

Thank you @AndresL ,

 

Which WebServer is configured on the Passive CommandCenter? It may be used to configure the Active Node’s WebServer which should be stopped during Failover.


Forum|alt.badge.img+7
  • Author
  • Byte
  • 37 replies
  • Answer
  • May 28, 2024

Problem solved, .NET core installation repair helped on Passive node.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings