NetXMS Support Forum

Windows 2003 R2
32bit systems running the 1.04 client

The netXMS client is monitoring system, security, and application windows event logs and 1 file log from a jboss/tomcat server using the following configuration. Whenever I restart the jboss/tomcat portal service the NXAGENTD peg's the processor at 100% utilization and my server takes 30 minutes to restart the portal. Even when the portal finally completes and is started the NXAGENTD service continues to hammer the processor until I kill the process and restart the service.

I have this exact scenario happening on two different systems. Both are the same environment.

Any input on how I can keep the process from going crazy and/or pinpoint why it is happening? The only thing I have played around with is the processAll option, I have turned that on and off a couple times.

<parser processAll="0">
   <file>C:\portal\server\default\log\server.log</file>
   <macros>
      <macro name="timestamp">[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}:[0-9]{2},[0-9]{3}</macro>
   </macros>
   <rules>
      <rule break="1">
         <match>@{timestamp}.ERROR (.*)</match>
         <event params="1">100002</event>
      </rule>
        </rules>
</parser>

Hi!

Could you please test agent version 1.0.6 (available at https://www.netxms.org/download/agent_packages/nxagent-1.0.6.exe)? There are some changes in text log file monitoring, and it may work better in your case.

Best regards,
Victor

Victor,

Yes, thank you that seemed to correct the processor pegging issue.

Regards,

Clark