Confirmed users
3,990
edits
ReleaseEngineering/BuildAPI: Difference between revisions
Jump to navigation
Jump to search
→Kicking
| Line 172: | Line 172: | ||
* self-serve requests not completing (check the self-serve agents and rabbit connections) | * 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]]) | * buildapi HTTP requests not working (check buildapi - [[ReleaseEngineering/How_To/Restart_BuildAPI]]) | ||
* builds-4hr.js not being updated (check the report crontask) | * builds-4hr.js not being updated (check the [[ReleaseEngineering/BuildAPI#report_crontask|report crontask]] report crontask) | ||
=== report crontask | === 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. | 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. | ||