[GENERAL] archive_command fails but works outside of Postgres - Mailing list pgsql-general

From twoflower
Subject [GENERAL] archive_command fails but works outside of Postgres
Date
Msg-id 1503081628787-5979040.post@n3.nabble.com
Whole thread Raw
Responses Re: [GENERAL] archive_command fails but works outside of Postgres  (Scott Marlowe <scott.marlowe@gmail.com>)
Re: [GENERAL] archive_command fails but works outside of Postgres  (Mark Watson <mark.watson@jurisconcept.ca>)
List pgsql-general
I changed my archive_command to the following:
archive_command = 'gsutil cp /storage/postgresql/9.6/main/%p gs://my_bucket/pg_xlog/'
and it fails, leaving the following in the log:

2017-08-18 18:34:25.057 GMT [1436][0]: [104319] LOG:  archive command failed with exit code 1
2017-08-18 18:34:25.057 GMT [1436][0]: [104320] DETAIL:  The failed archive command was: gsutil cp  /storage/postgresql/9.6/main/000000010000038B000000D8 gs://my_bucket/pg_xlog/
2017-08-18 18:34:25.057 GMT [1436][0]: [104321] WARNING:  archiving transaction log file "000000010000038B000000D8" failed too many times, will try again later

But the command works when executed manually:
root$ su postgres -c "gsutil cp /storage/postgresql/9.6/main/000000010000038B000000D8 gs://my_bucket/pg_xlog/"
root$ echo $?
0
The last command verifies that gsutil indeed exited with 0.

How to best debug this issue?

View this message in context: archive_command fails but works outside of Postgres
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

pgsql-general by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: [GENERAL] make postgresql 9.5 default on centos 7
Next
From: Igor Korot
Date:
Subject: Re: [GENERAL] Results interpretation