Closed Bug 1054048 Opened 10 years ago Closed 3 years ago

Should monitor lock files for new (mozharness) vcs sync

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INACTIVE

People

(Reporter: pmoore, Unassigned)

References

Details

If vcs sync gets stuck (like it did today in bug 1053960) then a new vcs sync won't run, and we have no way of finding out if we are not getting the "success" emails.

In order to resolve this, we should get nagios alerts if the lock files (e.g. vcssync1.srv.releng.usw2.mozilla.com:/opt/vcs2vcs/beagle.lock) are older than, say 30 mins.

These nagios alerts should also be reported in #buildduty
See Also: → 1053960
Component: Tools → General

Not actively working on this at the moment.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.