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

• current object health and state information
• current object configuration (resources, policies, attributes, etc)
• current and historical performance/utilization information
• reports on recent failure
• object messages

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

Argument	Description
-a [accountid]	display account information
-b	display information on jobs blocked by policies, holds, or other factors. If 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.
-c [classid]	display class information
-C [file]	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.)
-e	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)
-f	display fairshare information
-g [groupid]	display group information
-G [Green]	display power management information
-j [jobid]	display job information
-L	display limits
-m rackid	display rack/frame information
-n [nodeid]	display nodes If node diagnostics are specified, the '-t' option is also available to constrain the report to a particular partition.
-p	display job priority. If priority diagnostics are specified, the '-t' option is also available to constrain the report to a particular partition.
-q [qosid]	display qos information
-r [reservationid]	display reservation information
-R [rmid]	display resource manager information
-s [srsv]	display standing reservation information
-S	display general scheduler information
-t	display configuration, usage, health, and diagnostic information about partitions maintained by Moab
-T [triggerid]	display trigger information
-u [userid]	display user information
-x	display advanced system information
--format=xml	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

• Moab Client Installation - explains how to distribute this command to client nodes
• checkjob
• checknode