Hello David,
I saw the backup fail. The backup logged that it terminated the walsender,
and correlating the moment it failed to the metrics of my storage, shows
the storage at that time was facing a huge IOWAIT. And this was a network
mounted storage.
The backup process continued, but because of
On Sunday, October 20, 2024, Koen De Groote wrote:
>
>
> I'm going to be testing this. If someone could confirm that this is how
> writing WAL files works, that being: that it is only considered "done" when
> the archive_command is done, that would be great.
>
The archiving of WAL files by the pr
On 10/21/24 13:49, Koen De Groote wrote:
See, I'm reading that, and my conclusion is "Ah great, it will try
again, everything will be fine."
Unless it never completes and you hit the timeout.
There's a link between the archive_command, pg_basebackup and
wal_sender_timeout, but that link isn
See, I'm reading that, and my conclusion is "Ah great, it will try again,
everything will be fine."
There's a link between the archive_command, pg_basebackup and
wal_sender_timeout, but that link isn't clear from just reading all these
documentation pages when learning about their concepts separat
On 10/20/24 14:03, Koen De Groote wrote:
So I'm assuming the process of writing WAL files, if there is an
archive_command set, is only considered to be finished after the archive
is written, not just when the WAL file is written in pg_wal.
https://www.postgresql.org/docs/current/continuous-ar
Hello Adrian, and everyone else.
It has finally happened, the backup ran into an error again, and the
verbose output set me on the right path.
I'm getting this error message:
> pg_basebackup: could not receive data from WAL stream: server closed the
connection unexpectedly
> This probably means
Hi,
You can enable verbose to get more detail about what is happening during
backup
pg_basebackup -h your_host -U your_user -D /mnt/base_backup/dir/ -v
Also examine recent postgres logs
Verify backup directory permissions
On Sun, 29 Sept 2024 at 19:49, Koen De Groote wrote:
> Having run a baseba
On 9/29/24 08:57, Koen De Groote wrote:
> What is the complete command you are using?
The full command is:
pg_basebackup -h localhost -p 5432 -U basebackup_user -D
/mnt/base_backup/dir -Ft -z -P
So output Format as tar, gzipped, and with progress being printed.
> Have you looked at the Po
> What is the complete command you are using?
The full command is:
pg_basebackup -h localhost -p 5432 -U basebackup_user -D
/mnt/base_backup/dir -Ft -z -P
So output Format as tar, gzipped, and with progress being printed.
> Have you looked at the Postgres log?
> Is --verbose being used?
This
On 9/29/24 07:48, Koen De Groote wrote:
Having run a basebackup, I'm getting this output at the very end:
pg_basebackup: child process exited with error 1
pg_basebackup: removing contents of data directory "/mnt/base_backup/dir/"
What is the complete command you are using?
Is there a way to
Having run a basebackup, I'm getting this output at the very end:
pg_basebackup: child process exited with error 1
pg_basebackup: removing contents of data directory "/mnt/base_backup/dir/"
Is there a way to get more information as to what exactly happened?
I'd like to look into fixing this or d
11 matches
Mail list logo
