vPostgres replication of a Vware vRealize Automation instance fails with the error: waiting for server to start
search cancel

vPostgres replication of a Vware vRealize Automation instance fails with the error: waiting for server to start

book

Article ID: 342260

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • After configuring replication in vPostgres for VMware vRealize Automation, the postgres instance fails to start when running this command:

    service vpostgres start

  • The console reports:

    waiting for server to start.......

  • The attempt times out


Environment

VMware vRealize Automation 6.2.x
VMware vRealize Automation Desktop 6.2.x

Cause

This issue occurs if there is a low value set for the maximum Write-Ahead Logging (WAL) senders.

Resolution

This is a known issue affecting VMware vRealize Automation 6.2.x.

This issue is resolved in vRealize Automation 6.2.3, available at VMware Downloads.

If you are unable to upgrade at this time, you can resolve this issue by increasing the server count:
  1. Log in to the vPostgres server.
  2. Using a text editor, open /storage/db/pgdata/postgresql.conf
  3. Increase the sender count by setting the value: max_wal_senders = 20
  4. Restart vPostgres on all cluster servers, by running the command:

    service vpostgres start


Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box..
Vware vRealize Automation インスタンスの vPostgres レプリケーションが次のエラーで失敗する: サーバが起動するのを待機しています