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