Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Manually Replicate Primary Postgres DB to Replica DB When Replica is out of sync (52162)

Last Updated: 8/10/2023Categories: TroubleshootingTotal Views: 6808Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

While attempting to configure/reset the vRA Postgres Database you get an error similar to:

"Could not configure replica for node: <cafe.node.760065698.31327> on address: <primary fqdn>, reason is: I/O error on GET request for \"https://<primary fqdn>:5480/config/cluster/replica?noLock=false&reset=true&baseBackup=true&masterNodeHost=<secondary fqdn>\": null; nested exception is org.apache.http.client.ClientProtocolException"

postgresql.csv error in pg_hba.conf file
'2017-11-18 19:39:30.865 UTC,,,23971,,5a108c72.5da3,2,,2017-11-18 19:39:30 UTC,,0,LOG,F0000,"authentication option not in name=value format: e.",,,,,"
line 105 of configuration file ""/var/vmware/vpostgres/current/pgdata/pg_hba.conf""",,,,""'

shell-ui-app service not running -> UNREGISTERED

Cause

Error may occur when one of the nodes becomes disconnected for a long period of time. Error may occur when both nodes are in replica or primary node at the same time.

Impact / Risks

possible loss of data. Be sure to take a snapshot and a backup of the postgres database before attempting this procedure.

Resolution

1. Take snap shots of vRA VA appliances and postgres database backup of primary node.
2. Following steps are to be performed only on replica/secondary database server
a. Stop postgres service: sevice vpostgres stop
b. Synchronize replica database with primary database:

vcac-config -e cluster-config-replica --master-node-host <fqdn of master postgres> --reset

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Operations Management Pack for vRealize Automation

VMware Aria Automation

Related Versions:

VMware vRealize Operations Management Pack for vRealize Automation 2.0.x

VMware vRealize Automation Desktop 6.2.x

VMware vRealize Automation Desktop 6.2

VMware vRealize Automation 7.x

VMware vRealize Automation 7.3.x

VMware vRealize Automation 7.2.x

VMware vRealize Automation 7.1.x

VMware vRealize Automation 7.0.x

VMware vRealize Automation 6.x

VMware vRealize Automation 6.2.x

VMware vRealize Automation 6.2

view all

Take Our Survey

Support Assistant