NetXMS Support Forum

It can be a problem for NetXMS, because if during status poll it determines that node is down, data collection will not be scheduled for that node. But, if there are no status polls, NetXMS will try to establish TCP connection for each parameter to be collected. With connection timeout about 1 minute, it can easily cause long data collection queues.

What is the reason for disabling status polls? If you don't want alarms, mails, etc. for SYS_NODE_DOWN events, you can just block them in the first rule of event processing policy.

Best regards,
Victor

Hello!

It's fixed in 0.2.21.

Best regards,
Victor

If you take a look at node object representing NetXMS server itself, you'll find some automatically created DCIs. There are queue length for status poller, configuration poller, data collector, and database writer, as well as average time to queue DCI for polling. You can setup thresholds on these parameters as for any other DCI and generate alarms, etc. General rule is that any of this parameters is higher than 0 for long period of time, you have a problem and should do something.

Best regards,
Victor

Very interesting information... Thank you for reporting!

Best regards,
Victor

Hi!

Further increase of data collectors will not help - we have similar problem at one of our customer's site, and it's related to SNMP. I'll publish updated version of NetXMS server today, it may help.

Best regards,
Victor

Quote from: xenth on May 05, 2008, 10:27:55 AM
I just noticed something very disturbing, the polling isn't going properly.

My set intervals aren't being listened to, I'll give you an example, this is one of my workstations.
I have set the interval to 60 seconds, yet it does NOT poll every 60 seconds 

It should poll every 60 seconds, yet when I view the history:

This is a VERY big problem as well, is it related to my other problem? 

Yes, most likely they are related. If you take a look at a result of "show queues" console command, you can see quite big number (330) in data collector queue. This means that at the moment when you type this command 330 requests for collecting data was waiting for processing, because all data collectors was busy. You can try to increase number of data collectors to 40 or 50 (by changing server's parameter NumberOfDataCollectors), this may help a bit, but will not remove the problem completely.

Some additional questions: do you have SNMP on the nodes? Do you use SNMP for data collection?

Best regards,
Victor

Yes, it's a best way - it's what situations was designed for.

Best regards,
Victor

Hello!

If you wish to execute batch file, you should run CMD.EXE explicitely. Try to use command line like


cmd.exe /C "echo test >> c:\test.txt"


To pass additional information to your script, you can use same macros as in alarms (%m, %n, etc.) in action's command line.

Best regards,
Victor

Совсем скоро. Мы натолкнулись на проблему со сбором информации по SNMP, как только ее решим сразу сделаем 0.2.21.

Я сделаю опцию в консоли "показывать время в тайм зоне сервера". Должно помочь.

Yes, it's possible via advanced schedule. Just check "advanced schedule" checkbox in DCI configuration, and add one or more schedules in CRON format on advanced schedule tab. For example, to collect data every minute from 9:00 till 18:00, add schedule


* 9-18 * * *


See cron manpage or NetXMS user manual for detailed description of schedule syntax.

Best regards,
Victor

Hello!

Currently it's not possible without patching mysql dat5abase driver in NetXMS. However, because you are running MySQL server on the same machine, you can use UNIX sockets for communications. Just specify socket:path instead of host name in DBServer parameter.

Best regards,
Victor

What you mean by "monitor DCI"? DCI has a value by itself, you don't need another DCI to monitor it. I think you was asking about network service objects...

Best regards,
Victor

Макрос %a. Все возможные макросы описаны здесь: https://www.netxms.org/documentation/netxms_user_manual.pdf в разделе 8.6.

You can use ChildStatus(*) internal parameter to monitor status of child objects for a node (interfaces and services). It takes child object ID or name as an argument, like


ChildStatus(eth0)


for interface eth0 on the node.

Best regards,
Victor