Solution
You can get and set the debug level with the cmtool application that is part of your ElectricAccelerator installation. The supported values are:
-
all - log everything
-
commands - log actual commands that are sent from eMake to run for each job
-
environment - log environment variables and environment-related information such as eMake roots
-
fileinfo - log information about files that are sent from eMake, as well as files that are loaded from other agent hosts in agent-to-agent transfers
-
log - log messages of the "system log" type only, that is, messages that display on the Cluster Manager "Messages" tab
-
other - log miscellaneous messages that do not belong in any category
-
profile - log performance-related statistics
-
registry - log all operations related to accessing the Windows registry, including requests to/from eMake for registry keys/values
-
requests - log requests that eMake makes to the agents, such as instructing agents to create a certain file, setting a command result for proxy commands, and so on
-
state - log state changes in the agent, such as waiting for eMake to connect, running command, aborting session, and so on
-
usage - log the EFS file usage information that is eventually sent back to eMake, such as file lookups, creations, deletions, and so on
-
nothing - do not log messages at all
The log levels refer only to messages that appear in the ecagent*.log files.
Examples
You must log in to the Cluster Manager named "testcm" before you can query or set debug levels on the agents and EFS. To log in to the Cluster Manager, run the following command. After you log in, you do not have to log in again for 36 hours.
> cmtool --cm=testcm login
To get the Agent debug level on all Agents in the "testcm" Cluster Manager, use this command:
> cmtool --cm=testcm runAgentCmd "session trace"
To set the Agent debug level on all Agents in the "testcm" Cluster Manager to "requests", use this command (log files are in c:/ECloud/ecagent*.log on Windows, and /var/log/ecagent*.log on Unix):
> cmtool --cm=testcm setAgentDebug requests
To set the Agent debug level on all Agents in the "testcm" Cluster Manager to collect all messages, use this command (log files are in c:/ECloud/ecagent*.log on Windows, and /var/log/ecagent*.log on Unix):
> cmtool --cm=testcm setAgentDebug all
To set the Agent debug level on all Agents in the "testcm" Cluster Manager to "nothing" (turn logging off), use this command (log files are in c:/ECloud/ecagent*.log on Windows, and /var/log/ecagent*.log on Unix):
> cmtool --cm=testcm setAgentDebug nothing
To get the EFS debug level on all Agents in the "testcm" Cluster Manager, use this command (Unix only):
> cmtool --cm=testcm runAgentCmd "efs unixdebuglevel"
To set the EFS debug level on all Agents in the "testcm" Cluster Manager to the default, use this command (Unix only):
> cmtool --cm=testcm runAgentCmd "efs unixdebuglevel 11"
To set the EFS debug level on all Agents in the "testcm" Cluster Manager, use this command (Unix only):
> cmtool --cm=testcm runAgentCmd "efs unixdebuglevel 17"
To get the logging level for EFS on all Agents in the "testcm" Cluster Manager, use this command (log files are in c:/ECloud/efs*.log on Windows, and /var/log/efs*.log on Unix):
> cmtool --cm=testcm runAgentCmd "findEfs get logLocalMask"
To set logging for EFS on all Agents in the "testcm" Cluster Manager to the default, use this command (log files are in c:/ECloud/efs*.log on Windows, and /var/log/efs*.log on Unix):
> cmtool --cm=testcm runAgentCmd "findEfs set logLocalMask 0xF"
To enable logging for EFS on all Agents in the "testcm" Cluster Manager, use this command (log files are in c:/ECloud/efs*.log on Windows, and /var/log/efs*.log on Unix):
> cmtool --cm=testcm runAgentCmd "findEfs set logLocalMask 0x1FF"