Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Barman cron is executed twice #7

Closed
alhafoudh opened this issue Apr 4, 2017 · 0 comments · Fixed by #9
Closed

Barman cron is executed twice #7

alhafoudh opened this issue Apr 4, 2017 · 0 comments · Fixed by #9
Labels
bug

Comments

@alhafoudh
Copy link

alhafoudh commented Apr 4, 2017 •
edited
Loading

barman deb package installs cron task to /etc/cron.d/barman and barman user also has {{barman cron}} task configured resulting in these log messags:

2017-04-04 11:38:01,371 [323] barman.server INFO: Another cron process is already running on server postgresql.postgresql.rancher.internal. Skipping to the next server
2017-04-04 11:38:01,521 [339] barman.wal_archiver INFO: No xlog segments found from streaming for postgresql.postgresql.rancher.internal.
2017-04-04 11:39:01,576 [348] barman.server INFO: Another cron process is already running on server postgresql.postgresql.rancher.internal. Skipping to the next server
2017-04-04 11:39:01,722 [362] barman.wal_archiver INFO: No xlog segments found from streaming for postgresql.postgresql.rancher.internal.
2017-04-04 11:40:01,786 [367] barman.server INFO: Another cron process is already running on server postgresql.postgresql.rancher.internal. Skipping to the next server
2017-04-04 11:40:01,940 [385] barman.wal_archiver INFO: No xlog segments found from streaming for postgresql.postgresql.rancher.internal.
2017-04-04 11:41:01,965 [390] barman.server INFO: Another cron process is already running on server postgresql.postgresql.rancher.internal. Skipping to the next server
2017-04-04 11:41:02,117 [408] barman.wal_archiver INFO: No xlog segments found from streaming for postgresql.postgresql.rancher.internal.
rsilva4-zz pushed a commit that referenced this issue Apr 4, 2017
fixed cron, lock files and exporter
c9099d4 
closes #5, closes #8, closes #7

Lock files kept in `/tmp` dir and cleaned up on container startup. Duplicate `cron` for `barman cron` removed.
Major refactor on exporter. Maybe Prometheus scrape interval should be in ten 5-10 minute range. Will evaluate.
@rsilva4-zz rsilva4-zz mentioned this issue Apr 4, 2017
Merged
@rsilva4-zz rsilva4-zz added the bug label Apr 4, 2017
@rsilva4-zz rsilva4-zz mentioned this issue Apr 4, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fixed cron, lock files and exporter DECSIS/docker-barman
2 participants
@alhafoudh @rsilva4-zz