NetXMS Support Forum

Server is, Windows 2008 R2 64 Bit with SQL Server 2008 db on a separate machine. Running 1.0.5 server with 1.0.6 clients.

The following error is happening,



We have about 450 agents and maybe a total of 1500 nodes. Only about 4-6 DCI per node, vast majority are just monitoring windows event logs for errors and criticals.

I am noticing that we are getting a fair amount of agents dropping connectivity and then restoring in blocks of about 10-20 every 10-20 minutes. The crashes only started after we went from about 300 agents installed to 450 agents installed. I put the numberofstatuspollers up to 50 at first and that didn't seem to help, now I am putting the number back down to 30. That seems related but I'm not sure. The netowrk utilization is steady at about 2-3 percent. The processor is steady at about 10-20 percent. Disk IO is nothing...

Any suggestions based on this information would be helpful.

I have configured DCI's for checking drive space that are working on the 1.06 32 bit client but the x64 clients are never executing, even though the items are defined and active on the client. I noticed by default the x64 client was showing them as disabled, but I set them active and they still never update.

As I wrote this post I then realized the FileSystem.FreePerc is not working on the x64 agent but the Disk.FreePerc is working on the x64 client.

I was going to cancel the post but I thought it would be good information to share.

Thanks

Windows 2008 Enterprise R2 64 bit
SQL Server DB backend
netXMS Server 1.04

QuoteScript (Agentcfg: :1) execution error: Error in line 9: syntax error, unexpected $end

Any ideas on what the source of this would be or how to correct?

Thanks,

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>

How can I setup a logmonitor parser for a variable filename?

log_20100920.txt

The filename is not reset daily it is reset each time the server is restarted, so what I want is to monitor the most recent created filename in the folder starting with log_

Is this accomplished using a macro? If so what the best way to approach this?

Thanks for any input