Quick update, it seems like the services PSC Health and vCenter Server both switched back to "Healthy", but the Postgres Archiver changed to stopped again. Very curious...
We have vCenter Appliance 6.7 Update 2a (22.214.171.124000) and confirmed that wal_sender_timeout settings are already set to 600s as default during the installation. Also, upgraded to vCenter Appliance 6.7 Update 3 (126.96.36.199000) but Postgres Archiver service keep shutting down.
Yep, exactly the same issue here - running latest VCSA and still getting the postgres archiver service stopping (confirmed that the timeout is set to 600ms in the config with this version of the VCSA).
However, I do also have a second VCSA running in our DR site with exact same config (no VM's other than SRM placeholders and the VCSA, SRM and VRA appliances) and it does not show the same issues?!?! - Go figure?
If I get time, I will study logs and report back any findings.
EDIT (Still had an open SSH session to the VCSA):
2019-09-17T21:35:21.947Z 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.
Exactly the same error then!
Moderator: Moved to vCenter Server
Any update on this issue ? I am getting this Postgres Archive Service Health Alarm as well after installation of the latest vCenter updates. No special configuration of vCenter / No backups configured.
The appliance management console does not report problems but the vCenter itself always generates the alarm.