Confirmed users
1,364
edits
ReleaseEngineering/Queue directories: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Queue directories (view source)
Revision as of 21:32, 15 November 2014
, 15 November 2014leave bread crumb
m (added to howto category) |
(leave bread crumb) |
||
| Line 20: | Line 20: | ||
If a processor isn't running, they can be restarted via /etc/init.d/command_runner or /etc/init.d/pulse_publisher | If a processor isn't running, they can be restarted via /etc/init.d/command_runner or /etc/init.d/pulse_publisher | ||
If there are dead jobs, you can read the log files in the dead directory. After resolving the issue, job files should be moved back into <tt>'''new'''</tt> to be retried, or deleted. | If there are dead jobs, you can read the log files in the dead directory. After resolving the issue, job files should be moved back into <tt>'''new'''</tt> to be retried, or deleted. ''Note: there is a <tt>retry_dead_queue</tt> sub-command for [http://hg.mozilla.org/build/tools/file/5053b0ea4564/buildfarm/maintenance/manage_masters.py manage_masters.py]'' | ||
== implementation == | == implementation == | ||