NetXMS Support Forum

Dovol'no stranno. NetXMS dobavljaet "NAT adapter" v tom sluchae, esli IP address, po kotoromu server podkljuchilsja k agentu, otsutstvuet v spiske interfejsov, poluchennih s agenta. Obichno eto bivaet v sluchae, esli podkljuchaemsja k agentu cherez NAT, poetomu i "NAT adapter". A esli sdelat' prinuditel'nij configuration poll s konsoli, chto proishodit?

SVjazano v pervuju ochered' s tem, chto rabota s USB delaetsja sovershenno po raznomu v Windows i Linux, i s Linux'om ja nikak ne doberus' razobratsja. V principe vopros dolzen bit' reshaemij, skoree vsego eto mozno sdelat' s ispol'zovaniem libusb (http://www.libusb.org/). Esli est' vremja i zelanie dobavit' podderzku USB pod Linux, budet ochen' horosho.

Hi!

Attached is corrected MIB file. There was missing import for PhysAddress. I have added

    PhysAddress
        FROM SNMPv2-TC;

to the end of IMPORTS statement.

Also, not related to this issue, but please be aware that nxmibc places resulting netxms.mib into current directory, so if you running it form place other then c:\netxms\var\mibs, you should either specify correct output file with -o switch or copy netxms.mib to correct location after compilation.

Best regards,
Victor

Hi!

There are limits in code as well. I'll register an issue in our bugtracker (https://www.netxms.org/bugtrack/view.php?id=301) and will change this limit in future versions.

Best regards,
Victor

Da. Esche nemnogo dop. informacii zdes': https://www.netxms.org/forum/index.php/topic,356.0.html

Could you please post actual configs? Also, try to run agent on node (b) in debug mode (nxagentd -D 9) and post log file.

Best regards,
Victor

Poka ne udalos' povtorit' u sebja etu problemu. Na vihodnih budu testirovat' dal'she.

Most likely the problem is that default timeout for receiving data from agent is smaller then default connection timeout. I suggest to set connection timeout in port check subagent to some small value, and increase agent response timeout on server.

For example, to set agent response timeout to 5 seconds and connect timeout in port checker to 4 seconds, do the following:

Set server configuration variable AgentCommandTimeout to 5000;
Add the following to nxagentd.conf on node with port checker:

*portCheck
Timeout = 4000

Best regards,
Victor

Hi!

You do not have C++ compiler installed. You should install g++ package. Actual package name depends on Linux distribution you are using.

Best regards,
Victor

Hi!

ServiceCheck.Custom accepts two arguments - host name or IP address and port number. For example, to check port 8080 on address 10.1.2.3, use

ServiceCheck.Custom(10.1.2.3,8080)

All ServiceCheck.* parameters return the following values:

0 - success (server was connected and return expected response);
1 - invalid arguments was passed;
2 - cannot connect to server;
3 - bad server's response.

Best regards,
Victor

Hi all!

NetXMS version 1.0.2 is out. Changes from 1.0.1:

- Implemented custom graphs on Performance tab in Object Browser
- Solaris platform subagent improved (added I/O performnace counters, fixed bugs in CPU utilization counters)
- Fixed issues: #298

Best regards,
Victor

Unfortunately, all physical disk statistic functionality is quite outdated and often not working with modern hardware. It need to be rewritten, but unless someone will volunteer to do it, it will not happen in near future.

As a workaround, you can try to use smartmontools and call smartctl via agent's external parameter.

Best regards,
Victor

Попробуйте поставить этого агента: https://www.netxms.org/download/agent_packages/nxagent-1.1.0-rc12-x64.exe и запустить в дебаг режиме.

P.S. А можно прислать остальные парсеры?

На своей Windows машине повторить проблему не смог, теоретически, глядя в код, тоже ничего не обнаружил. Поэтому дополнительные вопросы:

1. Версия агента?
2. На какой ОС стоит агент?
3. Сколько параметров Target настроено (или просто прислать конфиг агента, если возможно)?
4. Как часто собираются значения?
5. Сколько раз выдается 20% - всегда только один?

К сожалению так и не смог повторить у себя эту ситуацию. Похоже проблема связана не напрямую с конкретным парсером, а проявляется при наличии каких-то дополнительных условий. А можно поставить логирование в файл и запустить агента в дебаг режиме (nxagentd -D 9), и прислать лог?