nagios checks for monitoring master uptime

RESOLVED WORKSFORME

Status

Release Engineering
General
P3
normal
RESOLVED WORKSFORME
7 years ago
8 months ago

People

(Reporter: catlee, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [nagios][buildbotmaster])

(Reporter)

Description

7 years ago
masters shouldn't be up and running for months at a time, they should be restarted periodically (that's another bug). We need nagios checks to assert that master processes are no more than X days old. I'm thinking 14 is a good number to start with.

Leaving in releng until we figure out exactly what we want here.
(Reporter)

Updated

7 years ago
Blocks: 661523

Updated

7 years ago
Priority: -- → P3
(In reply to Chris AtLee [:catlee] from comment #0)
> masters shouldn't be up and running for months at a time, they should be
> restarted periodically (that's another bug). We need nagios checks to assert
> that master processes are no more than X days old. I'm thinking 14 is a good
> number to start with.
An alert for any master with >14days uptime sounds good to me also. This will help us keep masters "fresh" by rebooting them. We can always adjust the 14 threshold up/down later based on how this feels after trying it.

> Leaving in releng until we figure out exactly what we want here.

I think thats all we need - anything else before we push over to IT for the nagios setup?
Component: Release Engineering → Release Engineering: Developer Tools
QA Contact: hwine
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
Do we still think masters shouldn't be running for so long?
Flags: needinfo?(catlee)
(Reporter)

Comment 3

4 years ago
doesn't seem to be an issue latetly
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Flags: needinfo?(catlee)
Resolution: --- → WORKSFORME
(Assignee)

Updated

8 months ago
Component: Tools → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.