Failover banner causing rabbitMQ, tomcat and EDAA to appear as NOT RUNNING after failover

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

The Fail over for Presentation SAM with Rabbit MQ, Tomcat and EDAA will not work if the Unix Server which we are trying to login has a Banner; for the rest of the Services it works fine.

 

Environment

All supported releases of Smart

Cause

• For Rabbit MQ, Tomcat and EDAA if there is Unix welcome message banner it would not work.

• In the failover action logs for it tries to ssh login but prints the banner and then sets the status of the processes as NOT RUNNING:

ui-failover-instrument: 02-Mar-2016 14:16:54 GMT Failover Instrumentation of UI Services : begin.
ui-failover-instrument: 02-Mar-2016 14:16:54 GMT Input params = <Install-Dir>/SAM/smarts/bin/sm_service show /usr/bin/ssh -i /home/<failover user>/.ssh/id_rsa -n -l <failover user> <hostname> 2>&1 <Install-Dir>/SAM/smarts/bin/sm_service show SMARTS-TOMCAT,SMARTS-RABBIT,SMARTS-ELASTICSEARCH/OPENSEARCH
ui-failover-instrument: 02-Mar-2016 14:16:54 GMT Attemptng getting status of remote server UI process: SMARTS-TOMCAT
ui-failover-instrument: 02-Mar-2016 14:16:55 GMT Output :*******************************************************************************

Private Computer System **************************<hostname> *****************
*******************************************************************************

Resolution

Adding the "-q" option in the script where UI Services status is checked is the solution to this issue:

Script to be edited:

<basedir>/integration/ui-failover-instrument.pl

Original: $command = "$remoteCmd -n -l $user $rhost 2>&1 " . "$script";
Change to: $command = "$remoteCmd -q -n -l $user $rhost 2>&1 " . "$script";

NOTE: Ensure you use sm_edit to do this edit.