mdiag

Synopsis

mdiag -a [accountid]
mdiag -b [-l policylevel] [-t partition]
mdiag -c [classid]
mdiag -C [configfile]  // diagnose config file syntax
mdiag -e [-w <starttime>|<endtime>|<eventtypes>|<oidlist>|<eidlist>|<objectlist>] --xml
mdiag -f [-o user|group|acct|qos|class] [-v]
mdiag -g [groupid]
mdiag -G [Green]
mdiag -j [jobid] [-t <partition>] [-v] [--blocking]
mdiag -L [-v]  // diagnose usage limits
mdiag -m [rackid]
mdiag -n [-A <creds>] [-t partition] [nodeid] [-v]
mdiag -p [-t partition] [-v] // diagnose job priority
mdiag -q [qosid]
mdiag -r [reservationid] [-v] [-w type=<type>] [--blocking]
mdiag -R [resourcemanagername] [-v]
mdiag -s [standingreservationid] [--blocking]
mdiag -S [-v] // diagnose scheduler
mdiag -t [-v] // diagnose partitions
mdiag -T [triggerid] [-v] [--blocking]
mdiag -u [userid]
mdiag -x
mdiag [--format=xml]

Overview

The mdiag command is used to display information about various aspects of the cluster and the results of internal diagnostic tests. In summary, it provides the following:

Some mdiag options gather information from the Moab cache which prevents them from interrupting the scheduler, but the --blocking option can be used to bypass the cache and interrupt the scheduler.

Arguments

ArgumentDescription
display account information
display information on jobs blocked by policies, holds, or other factors.
NoteIf blocked job diagnostics are specified, the '-t' option is also available to constrain the report to analysis of particular partition. Also, with blocked job diagnosis, the '-l' option can be used to specify the analysis policy level.
display class information
analyze configuration file for errors including use of invalid parameters, deprecated parameters, and illegal values. (If you start Moab with the -e flag, Moab evaluates the configuration file at startup and quits if an error exists.)

Moab will do a query for all events whose eventtime starts at <starttime> and matches the search criteria. This works only when Moab is configured with ODBC MySQL. The syntax is:
mdiag -e[-w <starttime>|<eventtypes>|<oidlist>|<eidlist>|<objectlist>] --xml

Moab will do a query for all events whose eventtime starts at <starttime> and matches the search criteria. This works only when Moab is configured with ODBC MySQL. The syntax is:
mdiag -e[-w <starttime>|<eventtypes>|<oidlist>|<eidlist>|<objectlist>] --xml

starttime default is -

eventtypes default is command delimited, the default is all event types (possible values can be found in the EventType table in the Moab database)
oidlist is a comma-delimited list of object ids, the default is all objects ids
eidlist is a comma-delimited list of specific event ids, the default is all event ids
objectlist is a comma-delimited list of object types, the default is all object types (possible values can be found in the ObjectType table in the Moab database)

display fairshare information
display group information
display power management information
display job information
display limits
display rack/frame information
display nodes
NoteIf node diagnostics are specified, the '-t' option is also available to constrain the report to a particular partition.
display job priority.
NoteIf priority diagnostics are specified, the '-t' option is also available to constrain the report to a particular partition.
display qos information
display reservation information
display resource manager information
display standing reservation information
display general scheduler information
display configuration, usage, health, and diagnostic information about partitions maintained by Moab
display trigger information
display user information
display advanced system information
display output in XML format

XML Output

Information for most of the options can be reported as XML as well. This is done with the command "mdiag -<option> <CLASS_ID> --format=xml". For example, XML-based class information will be written to STDOUT in the following format:

<Data>
  <class <ATTR>="<VAL>" ... >
    <stats <ATTR>="<VAL>" ... >
      <Profile <ATTR>="<VAL>" ... >
      </Profile>
    </stats>
  </class>
<Data>
  ...
</Data>

Of the mdiag options, only -G and -L cannot be reported as XML.

See Also

Copyright © 2012 Adaptive Computing Enterprises, Inc.®