NetXMS Support Forum

Hi!

Actually looks like a bug. I'll check it a bit later.

Best regards,
Victor

Hi!

Yes, you can use either ODBCquery or dbquery subagent to execute SQL queries periodically. ODBCquery subagent description is here: http://wiki.netxms.org/wiki/Subagent:ODBCQuery.

For DBquery, agent configuration file can be like this:


# standard stuff here ...
SubAgent = dbquery.nsm

*DBQUERY
Database = id=db1;driver=mysql.ddr;server=127.0.0.1;dbname=mydb;login=user;password=pass


Then to get number of records in table t1, you can use parameter

DB.Query(db1,"SELECT count(*) FROM t1")

Please note that DBquery is a new subagent intended to replace ODBCquery, but it's not 100% ready yet.

Best regards,
Victor

From the log I can see that agent does not receive connection from server. This can be firewall or routing problem. Can you telnet to port 4700 on problematic machine?

Best regards,
Victor

Hi!

Try to run agent with debug level 9:

nxagentd -D9

run configuration poll for that node and see what happens on agent.

Best regards,
Victor

Can you also post results of configuration poll (right click on node, then Poll -> Configuration)? I suppose that for some reason server cannot communicate with agent (maybe firewall in between or on target node?).

Best regards,
Victor

Hi!

Most correct way would be to add IPMI support to NetXMS server, so it can query IPMI directly and allow easy configuration of IPMI based DCIs. I'll check if this will require significant development effort.

Best regards,
Victor

Hi!

Please provide detailed description of a system you have problem with (OS version, agent version, how did you install agent, is agent service running).

Best regards,
Victor

Can you please send screenshots of your configuration?

Best regards,
Victor

Похоже на переполнение буфера на сервере. Это UNICODE сборка или нет? Если нет, то какое значение поставлено для CodePage в netxmsd.conf?

Hi!

You can turn on "active discovery" in network discovery configuration and add subnets you want to scan into "active discovery target" list. Regarding non-working discovery in first post - can you please share screenshot of your network discovery configuration?

Best regards,
Victor

Hi!

When you change threshold itself, it loses it's state - from the system point of view, it's like you remove threshold with value 74, and add threshold with value 65. Because this threshold is inactive already, you don't get deactivation event.
In general, it is not recommended to change thresholds to test them - instead, you can change DCI value using transformation script and see if thresholds work correctly. In your case, transformation script could be as simple as


return 60;


to test low temp threshold for example.

Best regards,
Victor

Да, можно. Для того, чтобы подставить имя узла можно использовать макрос %n. Полный список макросов есть здесь: https://www.netxms.org/documentation/adminguide/event-processing.html#macros-for-event-processing.

В принципе это не очень хорошо - это означает, что какие-то процессы внутри сервера надолго блокируют список обьектов. Понаблюдайте, если ситуация сохранится после того, как большая часть хостов в сети будет найдена, то надо будет разбиратся детально.

Проверьте что CheckTrustedNodes в настройках сервера выставлен в 0.

Так и должно быть Если успею, то в 1.2.11 поправлю.