ReleaseEngineering/How To/Restart BuildAPI: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 15: Line 15:
  supervisorctl restart selfserve-agent
  supervisorctl restart selfserve-agent


= Redis =
= Memcached =
Buildapi also depends on Redis, see [[ReleaseEngineering/How_To/Restart_Redis]].
Buildapi also depends on a memcached server run by IT. This is worth investigating if reporter.py jobs are hanging.

Revision as of 21:15, 8 April 2014


First, figure out if it's buildapi or self-serve that's having issues. If you're getting jobs timing out, that's probably self-serve, so try restarting the agents. If you're getting HTTP errors or timeouts, that's probably buildapi and you should talk to webops.

Restarting the buildapi web app

Talk to webops - this involves restarting the entire releng cluster.

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 selfserve-agent

Memcached

Buildapi also depends on a memcached server run by IT. This is worth investigating if reporter.py jobs are hanging.