[tracking bug] scheduled restart for production-master02 Feb. 25th

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
8 years ago
5 years ago

People

(Reporter: armenzg, Assigned: armenzg)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

8 years ago
Production master 2 is a weird state since the beginning of this week:
* twsitd.log has become old and nothing new is being appended
* runaway maemo repack that kept respawning
* desktop repacks were not happening
* memory usage is 50%

Before we get into a worst state we better restart the machine and turn on again the l10n builds for mobile. Check bug 548178.

The downtime will restart the master and I will retrigger nightly builds and dependent builds for aborted builds. Therefore, everyone should be getting their builds but later than usual.

The downtime will be from 5AM PST to 8AM PST.

The branches affected are:
* tracemonkey
* 1.9.1
* electrolysis
* lorentz
* all mobile builds

To start the master again:
nohup ./start_buildbot.sh &
disown
(Assignee)

Comment 1

8 years ago
Created attachment 428904 [details]
twistd.log when buildbot had stopped logging
(Assignee)

Comment 2

8 years ago
The restart is done and the build retriggered.

> To start the master again:
> nohup ./start_buildbot.sh &
> disown

I have modified /etc/nagios/nrpe.cfg to check for a twistd process instead of a buildbot one.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.