From: | "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Archive command failed - WAL SEGMENT |
Date: | 2016-01-04 21:21:15 |
Message-ID: | CAE_gQfXZvJ0-L93qKceehcA2KLoXLX=YpBzk7MSyA4L43UaHkw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Yep.. found the problem!
It was on my key_host file!
Cheers;
On 5 January 2016 at 09:31, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Drum,
>
> * drum(dot)lucas(at)gmail(dot)com (drum(dot)lucas(at)gmail(dot)com) wrote:
> > I've configured a new SLAVE Hot Standby server to my production.
> >
> > The problem is that, I've got some errors on Master:
> >
> > archive command failed with exit code 4
> > Failed to archive WAL segment `pg_xlog/0000000100000C2100000029` on host
> > `db-02`
> >
> > Do you guys know what I may be doing wrong?
>
> Whatever you have set as your archive_command in postgresql.conf is
> returning exit code 4. It's either broken, and you need to fix it, or,
> if it's working, you need to change it to return error code 0
> (indicating success).
>
> Thanks!
>
> Stephen
>
From | Date | Subject | |
---|---|---|---|
Next Message | Federico Campoli | 2016-01-06 13:56:38 | pglogical bug report |
Previous Message | Stephen Frost | 2016-01-04 20:31:17 | Re: Archive command failed - WAL SEGMENT |