Ticket #516 (closed enhancement: fixed)
syslog if auto-update fails
Reported by: | geofft | Owned by: | |
---|---|---|---|
Priority: | blocker | Milestone: | |
Component: | -- | Keywords: | |
Cc: | Fixed in version: | ||
Upstream bug: |
Description
and coordinate with ops so they pick up the logs and report on that usefully, so we know in advance when cluster machines haven't updated in a month.
Change History
comment:2 Changed 15 years ago by jdreed
- Status changed from closed to reopened
- Resolution fixed deleted
Hrm, or not. Camilla notes that ops is moving to Nagios and away from the gazette/reports for this sort of thing. Having Nagios parse update.log is suckful and prone to false positives, and we lose historical data
I propose we have auto-update create a flag file somewhere which contains the following:
date-of-last-update date-of-last-attempt up-to-date|failed msg
and expose that over athinfo.
So something like:
$ athinfo w20-575-1 update-status
3/12/10 2:00pm 3/12/10 2:00pm up-to-date
$ athinfo w20-575-1 update-status
10/3/09 1:00pm 3/12/10 2:00pm failed unable to download packages
auto-update already syslogs on user.notice if something bad happens.
Mail sent to ops about collecting failure notices, RT #1179647.
I think we can close this.