Nagios for age of backup.log fails initially
Bug #1329816 reported by
Michael Nelson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| postgresql (Juju Charms Collection) |
Fix Released
|
Low
|
Stuart Bishop | ||
Bug Description
Deploying the trusty/postgresql charm works fine, but one of the nagios checks fails as there's no backup.log initially:
10.0.3.23: + /usr/lib/
10.0.3.23: FILE_AGE CRITICAL: File not found - /var/lib/
The charm should either touch the backups.log during install to create it (with the correct perms/owner) or run a backup during install?
I can skip this nagios check during our deployments, but it'd be great not to have to do that. (Or as another work-around, I can have our deployment script touch the file as postgres user).
Related branches
lp:~stub/charms/precise/postgresql/bug-1329816-backup-log-spurious-alert
- Michael Nelson (community): Approve
-
Diff: 33 lines (+8/-1)1 file modifiedhooks/hooks.py (+8/-1)
lp:charms/postgresql
- Marco Ceppi (community): Needs Resubmitting
- Richard Asbridge: Pending requested
- Diff: 0 lines
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
| Changed in postgresql (Juju Charms Collection): | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → Stuart Bishop (stub) |
| importance: | Medium → Low |
| Changed in postgresql (Juju Charms Collection): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Touching the file on install if it doesn't already exist seems best. It is more robust than adjusting the check, and backing up a freshly minted database cluster is pointless.