Smarts Failover: Failover is not Able to Complete a Failback Using Non Root User.
search cancel

Smarts Failover: Failover is not Able to Complete a Failback Using Non Root User.

book

Article ID: 331910

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Symptoms:


When Failover is run as non-root user, the local files need have the permissions and ownership by the non root user and usergroup. When the Smarts domains are running as root the file permissions get changed back to root.  

This causes failover not to be able to properly failover in the event that the Active site goes down.

In addition you may also find these errors in the log file which suggest that ssh is not properly setup.  

[October 12, 2015 1:12:17 PM CDT +529ms] t@2846848768 Monitor-Driver
ASL_MSG-*-ASLP-failover/failover-monitor.asl: Output:      'Unable to obtain list of active standby domains (remote), rc: 255, error: Host key verification failed.

Please note if the permissions are correct on the rps files and you are not using a non root user and are getting this message please review KB 450462

Environment

VMware Smart Assurance - SMARTS

Cause

The failover manager being run as non root in the current code, is not able to access the rps as non root user, or perform the resync and backup actions on the files if they have been changed back to root as owner and ownergroup 

When the domains are running as root the file permissions get changed back to root when the rps is saved by the rps save process..This causes the non root user in failover not to work properly when trying to access these files

Resolution

Contact technical support for current status of the patch release dates.