Comments (9)
pgstef
commented on September 17, 2024
Hi,
Could you provide :
- pgbackrest.conf
- pgbackrest info output
- OS version
I'll try to reproduce your setup.
If check_pgbackrest is launched with the backrest user, I don't see any obvious problem.
Thanks,
Kind regards,
from check_pgbackrest.
renesepp
commented on September 17, 2024
Hi,
- OS version
CentOS Linux release 7.6.1810 (Core)
- Backup host pgbackrest.conf
[global]
repo-type=cifs
repo-path=/var/lib/pgbackrest/mountpoint2
process-max=4
compress=n
compress-level-network=3
retention-full=4
retention-diff=15
start-fast=y
stop-auto=y
[arendusdok]
db-host=example.domain
db-path=/var/lib/pgsql/9.4/data
db-user=postgres
process-max=2
- DB pgbackrest.conf
[global]
backup-host=pgbackrest.example.domain
backup-user=backrest
log-level-file=detail
archive-async=n[global:archive-get]
process-max=2
[global:archive-push]
process-max=2[arendusdok]
db-path=/var/lib/pgsql/9.4/data
- pgbackrest info output
stanza: arendusdok
status: ok
cipher: none
db (current)
wal archive min/max (9.4-1): 00000001000000BD000000DF/00000001000000C4000000E3
full backup: 20190714-200002F
timestamp start/stop: 2019-07-14 20:00:02 / 2019-07-14 20:37:45
wal start/stop: 00000001000000BD000000DF / 00000001000000BD000000E0
database size: 13.7GB, backup size: 13.7GB
repository size: 13.7GB, repository backup size: 13.7GB
full backup: 20190721-200001F
timestamp start/stop: 2019-07-21 20:00:01 / 2019-07-21 20:36:43
wal start/stop: 00000001000000BF000000B0 / 00000001000000BF000000B0
database size: 13.8GB, backup size: 13.8GB
repository size: 13.8GB, repository backup size: 13.8GB
diff backup: 20190721-200001F_20190722-200001D
timestamp start/stop: 2019-07-22 20:00:01 / 2019-07-22 20:06:21
wal start/stop: 00000001000000BF000000D8 / 00000001000000BF000000D8
database size: 13.8GB, backup size: 8.2GB
repository size: 13.8GB, repository backup size: 8.2GB
backup reference list: 20190721-200001F
diff backup: 20190721-200001F_20190723-200001D
timestamp start/stop: 2019-07-23 20:00:01 / 2019-07-23 20:07:39
wal start/stop: 00000001000000C000000003 / 00000001000000C000000003
database size: 13.9GB, backup size: 9.2GB
repository size: 13.9GB, repository backup size: 9.2GB
backup reference list: 20190721-200001F
diff backup: 20190721-200001F_20190724-200002D
timestamp start/stop: 2019-07-24 20:00:02 / 2019-07-24 20:07:47
wal start/stop: 00000001000000C00000002F / 00000001000000C00000002F
database size: 13.9GB, backup size: 10.3GB
repository size: 13.9GB, repository backup size: 10.3GB
backup reference list: 20190721-200001F
diff backup: 20190721-200001F_20190725-200001D
timestamp start/stop: 2019-07-25 20:00:01 / 2019-07-25 20:09:38
wal start/stop: 00000001000000C00000009F / 00000001000000C00000009F
database size: 14GB, backup size: 12.4GB
repository size: 14GB, repository backup size: 12.4GB
backup reference list: 20190721-200001F
diff backup: 20190721-200001F_20190726-200001D
timestamp start/stop: 2019-07-26 20:00:01 / 2019-07-26 20:09:35
wal start/stop: 00000001000000C0000000E1 / 00000001000000C0000000E1
database size: 14.1GB, backup size: 12.4GB
repository size: 14.1GB, repository backup size: 12.4GB
backup reference list: 20190721-200001F
diff backup: 20190721-200001F_20190727-200001D
timestamp start/stop: 2019-07-27 20:00:01 / 2019-07-27 20:11:48
wal start/stop: 00000001000000C100000013 / 00000001000000C100000013
database size: 14.1GB, backup size: 12.4GB
repository size: 14.1GB, repository backup size: 12.4GB
backup reference list: 20190721-200001F
full backup: 20190728-200002F
timestamp start/stop: 2019-07-28 20:00:02 / 2019-07-28 20:37:00
wal start/stop: 00000001000000C100000045 / 00000001000000C100000046
database size: 14.1GB, backup size: 14.1GB
repository size: 14.1GB, repository backup size: 14.1GB
diff backup: 20190728-200002F_20190729-200001D
timestamp start/stop: 2019-07-29 20:00:01 / 2019-07-29 20:06:57
wal start/stop: 00000001000000C1000000C2 / 00000001000000C1000000C2
database size: 14.3GB, backup size: 9.5GB
repository size: 14.3GB, repository backup size: 9.5GB
backup reference list: 20190728-200002F
diff backup: 20190728-200002F_20190730-200001D
timestamp start/stop: 2019-07-30 20:00:01 / 2019-07-30 20:08:48
wal start/stop: 00000001000000C200000003 / 00000001000000C200000003
database size: 14.3GB, backup size: 10.3GB
repository size: 14.3GB, repository backup size: 10.3GB
backup reference list: 20190728-200002F
diff backup: 20190728-200002F_20190731-200001D
timestamp start/stop: 2019-07-31 20:00:01 / 2019-07-31 20:09:27
wal start/stop: 00000001000000C2000000AF / 00000001000000C2000000AF
database size: 14.6GB, backup size: 12GB
repository size: 14.6GB, repository backup size: 12GB
backup reference list: 20190728-200002F
diff backup: 20190728-200002F_20190801-200001D
timestamp start/stop: 2019-08-01 20:00:01 / 2019-08-01 20:11:50
wal start/stop: 00000001000000C30000006A / 00000001000000C30000006A
database size: 14.8GB, backup size: 12.3GB
repository size: 14.8GB, repository backup size: 12.3GB
backup reference list: 20190728-200002F
diff backup: 20190728-200002F_20190802-200001D
timestamp start/stop: 2019-08-02 20:00:01 / 2019-08-02 20:09:48
wal start/stop: 00000001000000C3000000B4 / 00000001000000C3000000B4
database size: 14.8GB, backup size: 12.3GB
repository size: 14.8GB, repository backup size: 12.3GB
backup reference list: 20190728-200002F
diff backup: 20190728-200002F_20190803-200002D
timestamp start/stop: 2019-08-03 20:00:02 / 2019-08-03 20:14:15
wal start/stop: 00000001000000C3000000E6 / 00000001000000C3000000E6
database size: 14.8GB, backup size: 12.3GB
repository size: 14.8GB, repository backup size: 12.3GB
backup reference list: 20190728-200002F
full backup: 20190804-200001F
timestamp start/stop: 2019-08-04 20:00:01 / 2019-08-04 21:15:35
wal start/stop: 00000001000000C400000017 / 00000001000000C400000019
database size: 14.8GB, backup size: 14.8GB
repository size: 14.8GB, repository backup size: 14.8GB
diff backup: 20190804-200001F_20190805-200002D
timestamp start/stop: 2019-08-05 20:00:02 / 2019-08-05 20:08:32
wal start/stop: 00000001000000C4000000B6 / 00000001000000C4000000B6
database size: 15GB, backup size: 10.9GB
repository size: 15GB, repository backup size: 10.9GB
backup reference list: 20190804-200001F
from check_pgbackrest.
pgstef
commented on September 17, 2024
Hm. I don't really see any problem here. I tried to replicate your setup, that gave me :
-bash-4.2$ pgbackrest info
stanza: arendusdok
status: ok
cipher: none
db (current)
wal archive min/max (9.4-1): 000000010000000000000003/00000001000000020000001A
full backup: 20190808-101420F
timestamp start/stop: 2019-08-08 10:14:20 / 2019-08-08 10:14:33
wal start/stop: 000000010000000000000003 / 000000010000000000000003
database size: 20.1MB, backup size: 20.1MB
repository size: 20.1MB, repository backup size: 20.1MB
diff backup: 20190808-101420F_20190808-102200D
timestamp start/stop: 2019-08-08 10:22:00 / 2019-08-08 10:22:34
wal start/stop: 0000000100000000000000A1 / 0000000100000000000000A1
database size: 1.5GB, backup size: 1.5GB
repository size: 1.5GB, repository backup size: 1.5GB
backup reference list: 20190808-101420F
full backup: 20190808-103358F
timestamp start/stop: 2019-08-08 10:33:58 / 2019-08-08 10:34:52
wal start/stop: 000000010000000100000058 / 00000001000000010000005A
database size: 1.5GB, backup size: 1.5GB
repository size: 1.5GB, repository backup size: 1.5GB
diff backup: 20190808-103358F_20190808-103553D
timestamp start/stop: 2019-08-08 10:35:53 / 2019-08-08 10:36:18
wal start/stop: 00000001000000010000006A / 000000010000000100000071
database size: 309.8MB, backup size: 283.8MB
repository size: 309.8MB, repository backup size: 283.8MB
backup reference list: 20190808-103358F
-bash-4.2$ perl check_pgbackrest --service=archives --stanza=arendusdok --repo-path=/var/lib/pgbackrest/mountpoint2/archive
WAL_ARCHIVES OK - 536 WAL archived, latest archived since 4m18s | latest_archive_age=4m18s num_archives=536
With pgbackrest 2.15, PostgreSQL 9.4 and check_pgbackrest master.
from check_pgbackrest.
renesepp
commented on September 17, 2024
Hm. I don't really see any problem here. I tried to replicate your setup, that gave me :
-bash-4.2$ pgbackrest info stanza: arendusdok status: ok cipher: none db (current) wal archive min/max (9.4-1): 000000010000000000000003/00000001000000020000001A full backup: 20190808-101420F timestamp start/stop: 2019-08-08 10:14:20 / 2019-08-08 10:14:33 wal start/stop: 000000010000000000000003 / 000000010000000000000003 database size: 20.1MB, backup size: 20.1MB repository size: 20.1MB, repository backup size: 20.1MB diff backup: 20190808-101420F_20190808-102200D timestamp start/stop: 2019-08-08 10:22:00 / 2019-08-08 10:22:34 wal start/stop: 0000000100000000000000A1 / 0000000100000000000000A1 database size: 1.5GB, backup size: 1.5GB repository size: 1.5GB, repository backup size: 1.5GB backup reference list: 20190808-101420F full backup: 20190808-103358F timestamp start/stop: 2019-08-08 10:33:58 / 2019-08-08 10:34:52 wal start/stop: 000000010000000100000058 / 00000001000000010000005A database size: 1.5GB, backup size: 1.5GB repository size: 1.5GB, repository backup size: 1.5GB diff backup: 20190808-103358F_20190808-103553D timestamp start/stop: 2019-08-08 10:35:53 / 2019-08-08 10:36:18 wal start/stop: 00000001000000010000006A / 000000010000000100000071 database size: 309.8MB, backup size: 283.8MB repository size: 309.8MB, repository backup size: 283.8MB backup reference list: 20190808-103358F -bash-4.2$ perl check_pgbackrest --service=archives --stanza=arendusdok --repo-path=/var/lib/pgbackrest/mountpoint2/archive WAL_ARCHIVES OK - 536 WAL archived, latest archived since 4m18s | latest_archive_age=4m18s num_archives=536With pgbackrest 2.15, PostgreSQL 9.4 and check_pgbackrest master.
Hm. Did you test with a repo-type=cifs or only posix?
I did test with posix and archive check seems to work there.
CIFS mount options
vers=3.0,sec=ntlmssp,uid=backrest,gid=backrest,dir_mode=0750,file_mode=0740
from check_pgbackrest.
pgstef
commented on September 17, 2024
I tried with repo-type=cifs, exact same configuration file as yours. But indeed, not on a real CIFS mount. I will try that.
Meanwhile, that's a pgBackRest configuration option. It shouldn't impact check_pgbackrest.
Could you provide the result of the pgbackrest info --stanza=arendusdok --output=json command with repo-type as cifs and as posix to check if there's any difference there ?
I don't really see why it would have an impact on check_pgbackrest itself but it worth trying.
Kind regards
from check_pgbackrest.
pgstef
commented on September 17, 2024
Ok. I was on a "local" repository even if pgbackrest had the repo-type=cifs option.
I've tried to put the repo on a real cifs mount point and have been able to reproduce the "UNKNOWN" error.
To solve the problem, I have to add follow => 1 there : https://github.com/dalibo/check_pgbackrest/blob/d8d45effa1986ba88f8e1aefbe64aa676fb224f6/check_pgbackrest#L662
(You can temporarily add it to solve your problem)
I'll try to run some regression tests with that modification on other test cases to see if I need to add a specific option to activate it or not.
That will be added in the next release.
Thanks for reporting and helping debug the behaviour.
Kind regards
from check_pgbackrest.
Krysztophe
commented on September 17, 2024
Problem reproduced; fix confirmed; seems at 1st not to have a negative impact
from check_pgbackrest.
renesepp
commented on September 17, 2024
Ok. I was on a "local" repository even if pgbackrest had the repo-type=cifs option.
I've tried to put the repo on a real cifs mount point and have been able to reproduce the "UNKNOWN" error.To solve the problem, I have to add
follow => 1there :(You can temporarily add it to solve your problem)
I'll try to run some regression tests with that modification on other test cases to see if I need to add a specific option to activate it or not.
That will be added in the next release.
Thanks for reporting and helping debug the behaviour.
Kind regards
Fix confirmed, works fine now with a real CIFS mount.
Thanks.
from check_pgbackrest.
pgstef
commented on September 17, 2024
Hi,
The commit af85ec8 adds that modification and add some regress test with a CIFS mount.
Thanks again for reporting.
Kind regards
from check_pgbackrest.
Related Issues (20)
- Warning issued if pgbackrest.conf contains repo1-retention-archive-type=diff HOT 5
- --service=archives list missing archives but it's not true HOT 15
- Support other compression types than gz HOT 2
- service=retention should check presence of backups HOT 4
- Service archive Azure Storage account support HOT 2
- Memory leak? HOT 10
- New release planned soon? HOT 8
- invalid perfdata warnings (by ElasticsearchWriter and GraphiteWriter) HOT 9
- archives service will not work if the WAL files are not compressed HOT 2
- Option for check of minimum age of oldest full backup HOT 3
- Min WAL not found after stanza upgrade HOT 3
- Feature: zabbix integration HOT 3
- Failed to decode json when there's a WARNING for the pgbackrest HOT 6
- Problems after a few switchovers "found a boundary" HOT 5
- Version pgbackrest compatible avec check_pgbackrest 2.3 HOT 2
- Perl warning errors when running the check_pgbackrest command HOT 2
- Archive checking very slow or fails to check at all HOT 6
- Bug with RPM packaging from PGDG HOT 3
- Bug with --repo-s3 HOT 7
- Malformed JSON HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from check_pgbackrest.