ReleaseEngineering/How To/TroubleshootSelfServe: Difference between revisions
< ReleaseEngineering | How To
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
To stop the selfserve agent, just kill the process. | To stop the selfserve agent, just kill the process. | ||
To start the selfserve agent: | To start the selfserve agent (verify that the previous selfserve pid dead): | ||
$ builds/selfserve-agent/bin/python2.7 /builds/selfserve-agent/bin/selfserve-agent --config-file /builds/selfserve-agent/selfserve-agent.ini --wait -v | $ builds/selfserve-agent/bin/python2.7 /builds/selfserve-agent/bin/selfserve-agent --config-file /builds/selfserve-agent/selfserve-agent.ini --wait -v | ||
Revision as of 20:12, 24 January 2014
selfserve is accessed at https://secure.pub.build.mozilla.org/buildapi/self-serve and via the TBPL interface.
Sheriffs use this system to retrigger jobs. Sometimes selfserve stops responding and needs troubleshooting.
Look for selfserve_agent nodes in moco-nodes.pp to find which hosts it is running on. Log files are kept at /builds/selfserve-agent/agent.log on each node.
To stop the selfserve agent, just kill the process.
To start the selfserve agent (verify that the previous selfserve pid dead):
$ builds/selfserve-agent/bin/python2.7 /builds/selfserve-agent/bin/selfserve-agent --config-file /builds/selfserve-agent/selfserve-agent.ini --wait -v