NetXMS Support Forum

Что странно, все 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

Hi!

There are different functionality in NetXMS that is called proxy. One is agent proxy - when one agent used as a proxy to connect to another agent - this functionality you don't need. What you need is "proxy node" in DCI configuration - it allows you to configure DCI on one node but specify that real data collection will occur on another (proxy) node. In your case you will configure agent DCIs on ESX node and set proxy node to some ode with agent which can really collect this data. Don't forget to add ESX nodes to the list of trusted nodes on collecting node or disable trusted nodes check altogether.

Best regards,
Victor

Quote from: scuq on March 31, 2014, 02:05:45 AM

Code Select Expand

if (AddrInSubnet($node->ipAddr, "10.16.0.0", "255.255.0.0")) {
return;
}

is this valid syntax?

Syntax is valid, but depending on context (for example if you are writing a filter script) you may need to return TRUE or FALSE instead of null value.

Best regards,
Victor

Then to clear flag you can use the following construct:


  newFlags = node.getFlags() & ~Node.NF_DISABLE_NXCP
  #newFlags = node.getFlags() & ~(Node.NF_DISABLE_NXCP | Node.NF_DISABLE_SNMP)
  md = NXCObjectModificationData(node.getObjectId())
  md.setObjectFlags(newFlags)
  session.modifyObject(md)


Best regards,
Victor

Можете подцепить gdb к процессу и сделать stack trace всех потоков?

А Windows английский или русский? Попробуйте запустить агента как сервис с дебагом и посмотреть PDH ошибки в логе.

Quote from: raypetter on March 29, 2014, 11:50:16 PM
Victor, please update the postgresql package so that it does NOT depend on postgresql 8.4

Most of us are running 9.1 and newer. For every update I need to extract the package and remove/update the package dependency (DEBIAN/control).

Thanks

I've changed dependency for Debian 7 package. Next release should be ok.

Best regards,
Victor