Administrator Controls

Reload configuration files (blade, crews, limits):

Reload a single configuration file, for example: limits.config

Query basic engine state:

Query current active limit tallies:
http://ENGINE/Tractor/queue?q=limits

NOTE: this query is relatively expensive, it locks all threads. Add &full=1 to also include zero-valued "transitory" limits not defined in limits.config:**

Query unrolled crew definitions:

Query unrolled blade profile definitions:

List recently connected Dashboard users (session mailboxes):

Trace engine assignment decisions:
http://ENGINE/Tractor/ctrl?q=tracer&fmt=plain -- next assignment pass

add &t=bbbb -- for blade named bbbb add &t=jjjj -- for job with jid jjjj

Remove an old entry from the displayed list of active blades:
http://ENGINE/Tractor/btrack?q=delist&id=hhhhh/aa.aa.aa.aa

where hhhhh is the blade's hostname and aa.aa.aa.aa is the blade's current tcp/ip address.

Diagnostic: query engine internal message queue lengths:
http://ENGINE/Tractor/ctrl?q=status&qlen=1

NOTE: this query is relatively expensive, it locks all threads.

Engine log level: change the logging threshold level of the engine's own diagnostic logs:
http://ENGINE/Tractor/ctrl?q=loglevel&v=debug

Recognized level names are: severe, notice, info, debug, trace

Engine database contexts: bounce the engine's own internal client connections to the database server:

Blade Queries and Controls

List all of the currently connected blades, with a recent status snapshot:

Stop and Requeue all currently active tasks on a particular blade:

Query the engine for its information on a specific blade:

Query the engine for blade information, and include results from an (expensive) direct probe of the blade itself:
http://ENGINE/Tractor/monitor?q=bdetails&b=NAME&probe=1

Use this query cautiously, especially in scripts, since it can cause processing delays on the engine as it waits for the blade response -- especially when probing blades that are slow to respond. In this form of the query, the NAME parameter can be "hostname" or "hostname/address". The address portion is historical and is ignored, the engine derives blade addresses from the last entry in the blade database.

Query the current state of a blade directly:

Change the NIMBY state of a blade, via the engine:

First, send a login request to receive a session ID (tsid), then:

http://ENGINE/Tractor/ctrl?q=battribute&tsid=SSS&b=BBB&nimby=NNN

where:

Change the NIMBY state of a blade via direct http connection to the blade:
http://BLADE/blade/ctrl?nimby=NNN

Where NNN is the same as for the engine proxy case, above. Note that this direct type of connection may be disallowed by the NimbyConnectPolicy setting in blade.config.