NetXMS Forum

Hi Victor.  Thanks, I'll try doing that.  I've turned on deadlock logging also, so hopefully I can capture something. Regards, Richard

When I open a dashboard in Edit Mode, make some changes, but decide not to save, the changes remain persistent until I close and reopen the console again. Console build 2284.

Hi Victor, Attached is the log. I also removed some of the DCI's from the template assigned to this node, which resulted in ~200 fewer DCI's for this node, and the problem seems to have resolved itself.  After doing this I was able to confirm that the node has around 4200 DCI's configured. Regards, Richard .log.zip

Thanks Tatjana.  Actually, since I ran netxmsd direct from the shell (without the -d flag) rather that from it's init script, it hasn't crashed since. I'll implement what you suggest and try again using service. Rich

Thanks Victor.  Yes, that may be a good idea if it's not too difficult. Perhaps a suggestion for a new feature would be to add a "filter" script that sits between the DCI and, say, a graph.  Or perhaps have the ability to select a script as the input to a graph instead of (as well as) a DCI. Rich

If you are looking for a 95th percentile for all interfaces you are collecting data for, you can probably use the same type of instance discovery you are using for monitoring those interfaces to create the 95th DCIs. As part of that 95th instance discovery, you can pass parameters to the script. For example if your script is called "myScript" you could call it as "myScript("{instance}")" to pass the instance value through. That should allow you to locate the DCI to pull the data for the calculation from. Alternatively, you can configure a custom attribute on each node that lists all interfaces you care about. You can then read in that custom attribute in your script.

Try http://mysqltuner.com/, it usually gives you quite decent ideas about MySQL configuration (it's not a silver bullet though).

Thanks Victor.  Just did an upgrade to 2.0.4 (which was surprisingly easy) and it's all good now. Rich

Hi, actually NetXMS server supposed to reconnect after DB failure (and it seems that all internal threads other than idata writer done it correctly). I'll try to simulate this situation and check what's going on. Best regards, Victor

I was wondering what the outcome of this is as I somehow seem to have a similar problem. Network discovery = off. Add device if trap received = on About 300 CISCO Routers added - SNMP is working. Every 30 minutes (topology polling interval) - auth failure trap received. Disable topology polling - alerts go away. Given I have not touched these devices, but in my list of communities there will be at least one that does not work, why would topology polling not only not be working, but on not receiving a correct response, why not trigger an event for topology polling failure. More importantly though - having not set anything on these auto discovered devices - how did I break it and how do I fix it?

Let me summarize to make it easy for other beginners like me: for inward traffic (using the 64bit snmp oid) In "Data Collection Confiugration:" Description: Traffic on {instance-name} - bits/s IN Parameter: .1.3.6.1.2.1.31.1.1.1.6.{instance} Origin: SNMP - Unsigned Int 64bit Transformation: Average delta per sec Transform script: $1 * 8 Instance discovery: SNMP Walk - OIDs Base SNMP OID: .1.3.6.1.2.1.31.1.1.1.1 Instance discovery script: return %(true, $1, $2); For OUT traffic just change: Description: Traffic on {instance-name} - bits/s OUT Parameter: .1.3.6.1.2.1.31.1.1.1.10.{instance}

Yes, upgrade procedure is the same - you just run nxdbmgr as usual and it will make necessary changes in DB. Best regards, Victor