Jump to content
Sign in to follow this  
support

Troubleshooting High Availability polling health

Recommended Posts

As of Passwordstate build 8388, we have introduced a new feature where you can upgrade your High Availability instances directly from within the UI of the primary server.  Below is an example of this, and you'll see that in our current development set up our nodes are red, indicating that are not polling successfully:

 

2018-11-08_9-21-09.png

 

To troubleshoot why these polling health icons are red, please see the following:

 

Active/Passive Mode:

If you are using Active/Passive HA, the the Passwordstate service on the secondary server will make a call on a regular schedule to the primary site API.  If it can contact it, it will show a successful green icon.

 

Things to check:

  • When logged into to your Primary Passwordstate site, check the URL under Administration -> System Settings -> Miscellaneous is correct.
  • Ensure the Passwordstate Service on the secondary web server is running
  • From your Secondary server, perform a Powershell open port test back to your primary website to ensure no firewalls are blocking access.  Example is test-netconnection passwordstate.com.au -port 443
  • Look in the Application Event logs for any errors, and if you find any, but can't work out what they are, submit them to Click Studios support for review (support@clickstudios.com.au)

 

Active/Active Mode:

Active/Active mode works slightly different, and instead it will write the date, time and build number directly to the secondary database, and then when replication occurs this will be displayed in the primary Server UI

 

Things to check:

  • Passwordstate service on the secondary web server is running
  • Database replication is working
  • Look in the Application Event logs for any errors, and if you find any, but can't work out what they are, submit them to Click Studios support for review (support@clickstudios.com.au)

 

**TIP**

One quick way to check replication is working correctly is to do a count of auditing events against both databases.  This SQL query below will give you those count,s and they will be exactly the same if replication is working correctly.

 

Use Passwordstate

Select count(*) from auditing

 

 

Hope this helps!

 

Regards,

Support:)

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×