Smarts Failover: server banner causing rabbitMQ, tomcat and EDAA to appear as NOT RUNNING after failover; NOT RUNNING FTS-ELASTIC, NOT RUNNING FTS-RABBIT, NOT RUNNING FTS-TOMCAT
search cancel

Smarts Failover: server banner causing rabbitMQ, tomcat and EDAA to appear as NOT RUNNING after failover; NOT RUNNING FTS-ELASTIC, NOT RUNNING FTS-RABBIT, NOT RUNNING FTS-TOMCAT

book

Article ID: 331784

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Symptoms:


The Failover for the Presentation SAM with Rabbit MQ, Tomcat and EDAA will not work if the Unix Server which is being failed over to, has a banner message following a login, for the rest of the Services it works fine. For Rabbit MQ, Tomcat and EDAA if there is Unix welcome message banner it would not work.

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

using ELASTIC process as an example: 

1. It attempts the login, and displays the banner:

ui-failover-instrument: 02-Mar-2016 14:16:55 GMT Attemptng getting status of remote server UI process: FTS-ELASTIC
ui-failover-instrument: 02-Mar-2016 14:16:56 GMT Output :******************************************************************************* banner content ********************

The data held on this host system is PRIVATE PROPERTY. Access
to the data is only available for authorised users and purposes. Unauthorised 
entry contravenes the Computer Misuse Act 1990 and may incur criminal penalties
as well as damages. Please proceed if you are an authorised user. 

2. Appears as it its running 

RUNNING FTS-ELASTIC

3. But then outputs the following:

 

ui-failover-instrument: 02-Mar-2016 14:20:53 GMT Failover Instrumentation of UI Services : begin.
ui-failover-instrument: 02-Mar-2016 14:20:53 GMT Input params = /opt/smarts/InCharge94/SAM/smarts/bin/sm_service show /usr/bin/ssh -i /home/smartsusr/.ssh/id_rsa -n -l smartsusr testsystem.com 2>&1 /opt/smarts/InCharge94/SAM/smarts/bin/sm_service show FTS-TOMCAT,FTS-RABBIT,FTS-ELASTIC
ui-failover-instrument: 02-Mar-2016 14:20:53 GMT Attemptng getting status of remote server UI process: FTS-TOMCAT
ui-failover-instrument: 02-Mar-2016 14:20:54 GMT Output :NOT RUNNING FTS-TOMCAT

ui-failover-instrument: 02-Mar-2016 14:20:54 GMT Attemptng getting status of remote server UI process: FTS-RABBIT
ui-failover-instrument: 02-Mar-2016 14:20:54 GMT Output :NOT RUNNING FTS-RABBIT

ui-failover-instrument: 02-Mar-2016 14:20:54 GMT Attemptng getting status of remote server UI process: FTS-ELASTIC
ui-failover-instrument: 02-Mar-2016 14:20:54 GMT Output :NOT RUNNING FTS-ELASTIC


Environment

VMware Smart Assurance - SMARTS

Cause



The banner is preventing these services from starting correctly.

Resolution


If the banner is removed or ignored, the processes will start.

The workaround here will ignore the banner when one exists and will allow the processes to start. 

Please do the following on both Primary and Secondary SAM server:

1. use sm_edit to edit the following file: <basedir>/integration/ui-failover-instrument.pl

2. locate the following command (around line 101): 
$command = "$remoteCmd -n -l $user $rhost 2>&1 " . "$script";
Change this line to the following (add the -q): 
$command = "$remoteCmd -q -n -l $user $rhost 2>&1 " . "$script";

3. Save and close the file