ReleaseEngineering/How To/Restart BuildAPI: Difference between revisions
< ReleaseEngineering | How To
Jump to navigation
Jump to search
No edit summary |
|||
| Line 9: | Line 9: | ||
= Restarting the agent = | = Restarting the agent = | ||
selfserve-agent instances are run on multiple masters under supervisor, so it should be restarted in case of failure. In some cases (multiple fast failures) supersor disables the service. | |||
* Search for "include selfserve_agent" in hg.mozilla.org/build/puppet/file/default/manifests/moco-nodes.pp to figure out what masters should be checked. | |||
* Search for errors in <tt>/builds/selfserve-agent/agent.log</tt> | |||
* start the service as root: | |||
supervisorctl restart selefserve-agent | |||
= Redis = | = Redis = | ||
Buildapi also depends on Redis, see [[ReleaseEngineering/How_To/Restart_Redis]]. | Buildapi also depends on Redis, see [[ReleaseEngineering/How_To/Restart_Redis]]. | ||
Revision as of 23:49, 16 November 2013
Restarting the buildapi web app
As root@buildapi01.build.mozilla.org
service buildapi restart tail -n 300 -f ~buildapi/buildapi.log
Use the tail to verify that buildapi restarted cleanly.
Restarting the agent
selfserve-agent instances are run on multiple masters under supervisor, so it should be restarted in case of failure. In some cases (multiple fast failures) supersor disables the service.
- Search for "include selfserve_agent" in hg.mozilla.org/build/puppet/file/default/manifests/moco-nodes.pp to figure out what masters should be checked.
- Search for errors in /builds/selfserve-agent/agent.log
- start the service as root:
supervisorctl restart selefserve-agent
Redis
Buildapi also depends on Redis, see ReleaseEngineering/How_To/Restart_Redis.