ReleaseEngineering/BuildAPI: Difference between revisions

ReleaseEngineering/BuildAPI (view source)

550 bytes added , 2 May 2014

canmove, Confirmed users

1,394

edits

@@ Line 169: / Line 169: @@
 == Kicking ==
-Sometimes the buildapi server becomes unresponsive. To get it back up and running see [[ReleaseEngineering/How_To/Restart_BuildAPI]].
+If things are broken, figure out if it's
+* self-serve requests not completing (check the self-serve agents and rabbit connections)
+* buildapi HTTP requests not working (check buildapi - [[ReleaseEngineering/How_To/Restart_BuildAPI]])
+* builds-4hr.js not being updated (check the report crontask)
-If the Redis server is failing (eg sherrifs report builds-4hrs.js.gz is stale), see [[ReleaseEngineering/How_To/Restart_Redis]].
+=== report crontask ====
+There's a crontask on relengwebadm that runs every minute to generate the builds-4hr.js file.  If this crontask gets "hung", it will prevent updates from occuring.  This can happen due to DB connection issues, or bad data in the DB.  In these cases, killing the hung crontask is the appropriate fix.
+However, the crontask takes about 15 minutes to run on a cold cache.  So if its cache (memcached) has gone cold, then killing it before 15 minutes have elapsed is only delaying the failure.
 = Staging =