| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Dipanjan Das <mail(dot)dipanjan(dot)das(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_basebackup fails with "COPY stream ended" |
| Date: | 2021-06-16 05:12:20 |
| Message-ID: | 20210616051220.bqfgq2rechkzru6u@nol |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jun 15, 2021 at 09:53:45PM -0700, Dipanjan Das wrote:
>
> I am running "pg_basebackup -h <host> -U postgres -D <dir> -X stream". It
> fails with either of the following two error messages:
> [...]
> WARNING: terminating connection because of crash of another server process
> DETAIL: The postmaster has commanded this server process to roll back the
> current transaction and exit, because another server process exited
> abnormally and possibly corrupted shared memory.
Do you have frequent emergency restarts like that? You should start by
investigating on why this is happening. The logs should tell you what process
crashed and what it was executing, could you report those messages?
We will also probably need a backtrace, see
https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD#Getting_a_trace_from_a_randomly_crashing_backend
on how do to that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2021-06-16 06:05:57 | Re: some questions regarding replication issues and timeline/history files |
| Previous Message | Dipanjan Das | 2021-06-16 04:53:45 | pg_basebackup fails with "COPY stream ended" |