canmove, Confirmed users
2,850
edits
ReleaseEngineering/How To/Process nagios alerts: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Process nagios alerts (view source)
Revision as of 02:50, 26 April 2016
, 26 April 2016→builds-4hr
ChrisCooper (talk | contribs) No edit summary |
ChrisCooper (talk | contribs) |
||
| Line 19: | Line 19: | ||
== builds-4hr == | == builds-4hr == | ||
* Affects: treeherder. This data is used to provide job history in treeherder. | * Affects: treeherder. This data is used to provide job history in treeherder. The specific file can be found here: http://builddata.pub.build.mozilla.org/buildjson/builds-4hr.js.gz | ||
* Runs on: relengwebadm host, as a cronjob under the buildapi user | * Runs on: relengwebadm host, as a cronjob under the buildapi user | ||
* Possible solutions: usually this script fails or runs slowly when there are problems with the buildbot status database, either a lock, another long-running query, or simply load. Killing off the offending query and re-running the report-4hr script will fix this but be aware that the report-4hr script can take a while to run, especially on a cold cache. | * Possible solutions: usually this script fails or runs slowly when there are problems with the buildbot status database, either a lock, another long-running query, or simply load. Killing off the offending query and re-running the report-4hr script will fix this but be aware that the report-4hr script can take a while to run, especially on a cold cache. | ||