pgbouncer logrotate found error, skipping

[pgdba pgdba]

Hello ,

When I want to create a logrotate in postgresql, I get this error when I want 
to work later. Does anyone have any idea about this error?
logrotate -f /etc/logrotate.conf error after error:
pgbouncer: 1 unknown option 'var' - ignoring line
error: pgbouncer: 11 unknown unit 'm'
error: found error in file pgbouncer, skipping

Postgres Wal Full

[pgdba pgdba]

Hi ,

I have a problem from pg_wal. I am using postgresql version 11 and taking 
backup and writing archive_command in postgresql.conf but did not archive wal 
and my disk ise full from pg_wal. I research why is my wal is full and dont 
found anything could  you help me please ?

Ynt: Postgres Wal Full

[pgdba pgdba]

Hi, thanks your feedback but not have same error in my log file. I am using 
streaming replication and have 1 master and 2 slave nodes in async. master node 
different size file wal from slave nodes such as;
[root@master1 pg_wal]# ls | wc -l
6400
[root@slave2 pg_wal]# ls | wc -l
332
[root@slave3 pg_wal]#  ls | wc -l
344

wal_keep_segments = 512
max_wal_size = 2GB
min_wal_size = 1GB
data size : 290G
 cpu:8
ram:16

Gönderen: Kyotaro Horiguchi 
Gönderildi: 3 Mart 2022 Perşembe 11:22
Kime: postgresdb...@outlook.com 
Bilgi: pgsql-general@lists.postgresql.org 
Konu: Re: Postgres Wal Full

At Thu, 3 Mar 2022 07:46:45 +, pgdba pgdba  
wrote in
> I have a problem from pg_wal. I am using postgresql version 11 and taking 
> backup and writing archive_command in postgresql.conf but did not archive wal 
> and my disk ise full from pg_wal. I research why is my wal is full and dont 
> found anything could  you help me please ?

The immediate cause of the WAL retension is the archive failure.
PostgreSQL, while archiving is enabled, won't remove a WAL file until
it is successfully archived.

You will see the lines like the following in sergver log if archive
failure happened.

> 2022-03-03 17:15:21.314 JST LOG:  archive command failed with exit code 1

If the archive command emitted some error messages, it can be caught
in the server log together.  The follwoing error is emitted by the
archive_command "cp %p /archive/%f".

> cp: cannot create regular file '/archive/00010001': No such 
> file or directory

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

FATAL: could not receive timeline history file from the primary server: ERROR: could not open file "pg_wal/0000000x.history": No such file or directory

[pgdba pgdba]

hello everyone,

I want to install a two-node streaming replication with postgresql version 11, 
but I'm getting this error when starting the service of my slave node. Can you 
support me? I couldn't find the solution.

FATAL:  could not receive timeline history file from the primary server: ERROR: 
 could not open file "pg_wal/0002.history": No such file or directory


slave node has recovery.conf file and include primary_con_info informations.


Thanks

Pgbackrest Restore Error - Segmentation fault (core dumped)

[pgdba pgdba]

Hello, when I restore with Pgbackrest, I get the following error, I couldn't 
find a solution when I researched, can you support?

postgres@dev-test:~$ pgbackrest --config=/etc/pgbackrest/pgbackrest.conf 
--stanza=db3 --log-level-console=info --type=immediate restore
WARN: configuration file contains invalid option 'archive-mode'
2023-09-06 06:54:45.826 P00 INFO: restore command begin 2.27: 
--config=/etc/pgbackrest/pgbackrest.conf --log-level-console=info 
--pg1-path=/var/lib/ postgresql/11 --repo1-host=0.0.0.1 
--repo1-host-user=postgres --stanza=db3 --type=immediate
Segmentation fault (core dumped)

Thanks,

Ynt: Pgbackrest Restore Error - Segmentation fault (core dumped)

[pgdba pgdba]

I removed  it but I keep getting the same error

Gönderen: Rob Sargent 
Gönderildi: 6 Eylül 2023 Çarşamba 16:32
Kime: pgsql-general@lists.postgresql.org 
Konu: Re: Pgbackrest Restore Error - Segmentation fault (core dumped)

On 9/6/23 05:08, pgdba pgdba wrote:
Hello, when I restore with Pgbackrest, I get the following error, I couldn't 
find a solution when I researched, can you support?

postgres@dev-test:~$ pgbackrest --config=/etc/pgbackrest/pgbackrest.conf 
--stanza=db3 --log-level-console=info --type=immediate restore
WARN: configuration file contains invalid option 'archive-mode'
2023-09-06 06:54:45.826 P00 INFO: restore command begin 2.27: 
--config=/etc/pgbackrest/pgbackrest.conf --log-level-console=info 
--pg1-path=/var/lib/ postgresql/11 --repo1-host=0.0.0.1 
--repo1-host-user=postgres --stanza=db3 --type=immediate
Segmentation fault (core dumped)

Thanks,
Have you tried removing the invalid option ('archive-mode') from the config 
file?