NetXMS Support Forum

Сейчас -D в командной строке имеет приоритет. Проверьте что при запуске агента не указывается -D0.

It should be there.

Best regards,
Victor

I hope it will be available in a week or two.

Best regards,
Victor

Можно пробовать использовать ExternalParametersProvider - на форуме довольно много сообщений на эту тему, например это: https://www.netxms.org/forum/configuration/reading-in-values-from-a-file/msg10173/#msg10173.

Первая версия в ветке 1.3.x будет думаю в начале мая.

Hi!

Yes, there is a bug which prevents web UI from running on port 80 (any other port will work). I'll fix it in next release.

Best regards,
Victor

А что это за база?

Что странно, все topology pollers сидят на ожидании ответа на SNMP запрос. Есть ли возможность посмотреть tcpdump'ом, как быстро приходят ответы на запросы, есть ли повторы?

Quote from: andrey--k on March 31, 2014, 03:55:32 PM
Debian 7 + Oracle
next error apears:

Code Select Expand


[31-Mar-2014 12:13:06.971] [ERROR] SQL query failed (Query = "INSERT INTO event_log (event_id,event_code,event_timestamp,event_source,event_severity,event_message,root_event_id,user_tag) VALUES (?,?,?,?,?,?,?,?)"): ORA-12899: value too large for column "NETXMS"."EVENT_LOG"."USER_TAG" (actual: 73, maximum: 63)
[31-Mar-2014 12:13:31.038] [ERROR] SQL query failed (Query = "INSERT INTO event_log (event_id,event_code,event_timestamp,event_source,event_severity,event_message,root_event_id,user_tag) VALUES (?,?,?,?,?,?,?,?)"): ORA-12899: value too large for column "NETXMS"."EVENT_LOG"."USER_TAG" (actual: 71, maximum: 63)


Fixed.

Best regards,
Victor

Hi!

Upgrade goes as following:

1. server transfers installer file to the remote machine (file is placed into directory specified in FileStore parameter in nxagentd.conf). For file transfer server uses same agent connection.
2. Agent launch downloaded installer.
3. Installer issues stop command to agent service.
4. Installer copies new files.
5. Installer issues start command to agent service.

Best regards,
Victor

Hi!

Usually this can happen when connecting to address given as node's primary IP address actually ends up on NetXMS server's loopback interface. Can you check this with command line tools (for example, use nxsnmpwalk on problematic node's IP address and see what data you'll get)?

Best regards,
Victor

Hi!

Active discovery should not do anything good or bad regarding this problem. I suspect that this is action #2 that helps (but still don't understand why). Do I understand you correctly that you disable discovery polling on only one node? If yes, can you describe this node in as much details as you can (most important are OS, number of interfaces, routing)?

Best regards,
Victor

Hi!

Currently it's useless (I should hide this menu item). It's incomplete functionality which will allow you to create rack objects and put nodes inside to indicate how physical equipment located in racks.

Best regards,
Victor

Hi!

Check where critical status comes from - it could be either interface object below host or outstanding alarm. Terminate alarm(s) if they are not relevant. For interface object, set expected state to IGNORE. Also you may want to disable configuration polls for that node.

Best regards,
Victor

Hi!

You probably need to show your event processing policy. I suppose there is a flaw in event processing logic.

Best regards,
Victor

You can add special threshold type "data collection error" on DCIs where you want to detect collection errors.

Best regards,
Victor