VMware Postgres Archiver Service changes status to "stopped"

Products

• VMware vCenter Server
• VMware vCenter Server 7.0
• VMware vCenter Server 8.0

Issue/Introduction

VMware Postgres Archiver Service changes status to “stopped” after configuring scheduled backups for the vCenter server appliance.

In /var/log/vmware/vpostgres/pg_archiver.log-[n].stderr, you see error similar to:

yyyy-mm-ddThh:mm:ss.mssZ ERROR  pg_archiver could not receive data from WAL stream: server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.

In /var/log/vmware/vpostgres/postgresql-[nn].log you see error similar to:

yyyy-mm-ddThh:mm:ss.mssZ UTC 5ae81b07.c7c9 0 [unknown] archiver LOG:  terminating walsender process due to replication timeout

Environment

VMware vCenter Server Appliance 6.7.x, 7.x and 8.x.

Cause

This is caused by the wal_sender_timeout value being too low. If the vCenter Server appliance experiences high CPU load, the Postgres service may stop the archiver, as it cannot report within the timeout limit configured by default. 

Resolution

Please note: Take snapshot of VC or backup of VC prior to making any changes.

 

1. Accessing the PostgreSQL Configuration File via SSH

• Establish SSH Connection:

  • Open PuTTY.
  • In the "Session" category, enter the hostname or IP address of your vCenter server in the "Host Name (or IP address)" field.
  • In the "Connection" -> "SSH" -> "Auth" category, browse and select your private key file if you're using SSH key-based authentication. Otherwise, enter the root password.
  • Click "Open" to establish the SSH connection.

• Navigate to the Configuration File:

  • Once connected, use the cd command to navigate to the PostgreSQL configuration file directory:

    cd /storage/db/vpostgres/ 
    

• Open the Configuration File:

  • Use a suitable text editor with root privileges.
    • Using vi:

      vi postgresql.conf 
      

      • Utilities of vi command:
      • Navigate within the file using arrow keys.
      • Press i to enter insert mode.
      • Make the necessary changes.
      • Press Esc to exit insert mode.
      • Type :wq and press Enter to save and quit.

2. Uncomment and Modify the wal_sender_timeout Parameter

• Locate the Parameter:

  • Search for the line: #wal_sender_timeout = 60s within the postgresql.conf file.

• Uncomment the Line:

  • Remove the leading # character to activate the parameter.

• Modify the Value:

  • Change the value from 60s to 600s:

    wal_sender_timeout = 600s 
    

  • This increases the timeout for the write-ahead log (WAL) sender from 60 seconds to 600 seconds.

3. Save the Changes

• Using vi:
  • Press :wq! and Enter to save the changes and exit the editor.

 

4. Restart PostgreSQL Services:

• • Important: Ensure no active tasks are running on the vCenter Server to avoid data inconsistencies.
  • Stop the PostgreSQL services: service-control --stop vmware-postgres-archiver vmware-vpostgres
  • Start the PostgreSQL services: service-control --start vmware-postgres-archiver vmware-vpostgres

This adjustment increases the timeout for the write-ahead log (WAL) sender, potentially resolving issues related to slow or intermittent network connections that may cause timeouts during data replication.

 

Additional Information

How to stop, start, or restart vCenter Server 6.x services and above 

Stopping, Starting or Restarting VMware vCenter Server Appliance 6.x & above services