Ask the Community
Groups
Troubleshooting: Turn on additional WMI logging - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>PROBLEM:</strong></p> <p>In order to troubleshoot issues with WMI tests, it may be necessary to enable additional debugging to collect data from both the DGE component and the WMI Query Daemon. To do so, kindly follow these instructions.</p> <p><strong>SOLUTION:</strong></p> <p>In the instructions below please replace 'TRAVERSE_HOME' with the actual Traverse installation path. (Note: The instructions are for a Windows installation but also apply to GNU/Linux by using / in place of \ for the directory paths)</p> <p>On the DGE/DGEX in question</p> <p> <strong>1.</strong> Follow the instructions <a href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/hc/en-gb/articles/229043928-Troubleshooting-Turn-on-additional-debug-logging" rel="noopener nofollow">'here'</a> to enable additional logging for the DGE component by adding these logging classes:</p> <pre class="code codeBlock" spellcheck="false" tabindex="0"><logger name="monitor.monitors.Monitor" level="DEBUG"><br> <appender-ref ref="FILEdebug"/><br></logger><br><logger name="monitor.monitors.streaming.wmi" level="DEBUG"><br> <appender-ref ref="FILEdebug"/><br></logger><br><logger name="monitor.clients.wmi.streaming" level="DEBUG"><br> <appender-ref ref="FILEdebug"/><br></logger></pre> <p><br><strong>2.</strong> Edit the file <TRAVERSE_HOME>\etc\nvwmiqd.ini</p> <p>Look for the entry:</p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> ; log level (FATAL,ERROR, WARNING, INFO, DEBUG, TRACE) , Must Set <br>Level = INFO</pre> <p>Change it to:</p> <pre class="code codeBlock" spellcheck="false" tabindex="0">Level = TRACE </pre> <p>Increase the max size of the file and the rotation (backup cycle)</p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> ; max log file size in MB FileSize = 100 <br> ; number of log files to save in rotation FileCount = 10</pre> <p><strong>3. </strong>Restart the WMI Query Daemon component.</p> <p> </p> <p><strong>Be warned that this may generate large files and consume additional hard disk space.</strong></p> <p>Once the issue has happened, please zip and attach all instances of the monitor, debug, and nvwmiqd log files for review on the support ticket that has been opened. Please do not post the files here.</p> <p>To turn off the additional WMI Query Daemon logging, please restore the saved nvwmiqd.ini to TRAVERSE_HOME\etc\nvwmiqd.ini</p> <p> </p> </article> </main>