This is simply an automation that is based on the supported way to back up Pivotal Cloud Foundry
35
stars
24
forks
source link
cfops v3.1.7 backup failed on ERT-1.9.47 with no matching pgdump path postgres-9.4.9 #117
Open
kymenglim opened 6 years ago
Hi folks, we got a cfops v3.1.7 ccdb and uaadb backup failed on ERT-1.9.47 (upgraded from working ERT 1.8 to 1.9.47).
The debug log shows backup using the old postgres-9.4.6 path: ... 2018/02/01 04:11:27 I0201 04:11:27.325443 8192 elasticruntime.go:175] Exporting %s ccdb 2018/02/01 04:11:27 D0201 04:11:27.613448 8192 pgdump.go:67] pgdump Dump called: PGPASSWORD=XXXX /var/vcap/ ackages/postgres-9.4.6/bin/pg_dump -Fc -h localhost -U admin -p 2544 ccdb Process exited with status 127 2018/02/01 04:11:27 D0201 04:11:27.614785 8192 elasticruntime.go:180] Done backing up ccdb Process exited with status 127 ...
The ERT-1.9.47, Postgres Server has path file: /var/vcap/ ackages/postgres-9.4.9/bin/pg_dump
The cfpos v3.1.7 does not appear to have an update /var/vcap/ ackages/postgres-9.4.9/bin/pg_dump that's causing postgres backup to fail.
Not certain if it uses cfbackup installation_settings.go, but it looks like the latest support for pg dump is 9.4.6 according to https://github.com/pivotalservices/cfbackup/blob/develop/installation_settings.go
latestPGDumpBin = "/var/vcap/packages/postgres-9.4.6/bin/pg_dump"
Is there an update patch/fix release that will work with ERT-1.9, Postgres-9.4.9?