ZCM agent debugging

More how-to guides. This one is turning on ZCM agent-side debugging.

First set the zmd logging to be at debug level; there are two ‘true’ settings in the conf file:

%ZENWORKS_HOME%conflogger-zmd-conf.xml

<configuration>
<log4net>
    <!–Appender to log event to console–>
    <appender name=”ConsoleAppender” type=”log4net.Appender.ConsoleAppender”>
    <param name=”Threshold” value=”DEBUG” />
    <layout type=”Novell.Zenworks.Logger.SimpleLayout, Novell.Zenworks.Logger”></layout>
    </appender>

    <!–This section is used to enable or disable the above configured appenders –>
    <logger name=”ZEN_LOGGER” additivity = “true“>
        <level value=”DEBUG”/>
        <appender-ref ref=”ConsoleAppender” />
    </logger>

    <!– This section is used to Enable component Logging –>
<!–
        <logger name = “ZEN_LOGGER.TestLogger” additivity =”true”>
                   <level value=”DEBUG”/>
        </logger>
–>
</log4net>

<ZenworksMessageLogger>
    <!– This section is used to turn on/off the Global Debug Flag –>
    <param name=”FileDebug” type=”Boolean” value =”true” />
</ZenworksMessageLogger>
</configuration>

Next restart the ZENworks agent

net stop “novell zenworks agent service”

The Novell ZENworks Agent Service service is stopping.
The Novell ZENworks Agent Service service was stopped successfully.

net start “novell zenworks agent service”

The Novell ZENworks Agent Service service is starting..
The Novell ZENworks Agent Service service was started successfully.

The log file for the agent is in %ZENWORKS_HOME%logsLocalStorezmd-messages.log

The log rolls – so you might need to collect the zip as well.