NetXMS Support Forum

Regarding the crash - do you have core dump from the crash? Also, what exact version and on what platform you are using?

Best regards,
Victor

Hi,

for event generation you can use PostEvent function. You can put everything into your filter script, but this seems a bit illogical, or create a script action. I would create a rule that matches event and executes script action. Inside that script (either filter script or action script) you can use something like this:


if ($event->parameters[1] ~= "^SNMP_TRAP: Virtual (.*) has become unavailable")
{
   PostEvent($node, "CUSTOM_EVENT", null, $1);
}


This will generate new event named CUSTOM_EVENT with path extracted from original event passed as first parameter.

Best regards,
Victor

Hi,

most likely you did not specify correct address of NetXMS server in agent's configuration file. You can run agent with debug level 6 and check what is going on during connection attempt from server.

Best regards,
Victor

Hi!

What agent versions you are using, and on what platform? We've seen such issue with Windows agents and it was solved by rebuilding agent with newer OpenSSL.

Best regards,
Victor

Hi,

this option is in object browser's view menu (see attached screenshot).

Best regards,
Victor

Hi all!

We just updated NetXMS server to version 3.3.323. It contains fix for bug in template import during server startup.

Best regards,
Victor

Hi,

what Debian version you are using? Did you install server from packages? If possible, please run server under gdb and provide stack trace after crash.

Best regards,
Victor

Hi,

this is bug in template import on server startup. I just fixed it in stable and development branch, and we will release server version 3.3.323 with the fix later today. As a workaround you can manually re-import templates or restart server with configuration parameter ImportConfigurationOnStartup set to "Always".

Best regards,
Victor

IPv6 is supported by all components for many years already.

Best regards,
Victor

You need at least one agent with SSH subagent loaded. It could be agent on NetXMS server itself.

Best regards,
Victor

Hello,

links for world map are considered for some time already, but it is not high priority feature. Layers also could be possible to implement. You could register feature request in our tracker with more detailed description how layers can be configured and displayed.

Best regards,
Victor

You do not need source node if you have configured it on NetXMS server node. It defines where actual data collection will happen, in case of "agent" origin - what agent will be queried. You'll need source node to be set in the opposite case - when you configure DCI on "myserver" node but SSH subagent is on NetXMS server - then you'll have to set source node to NetXMS server node.

Best regards,
Victor

Hi all!

We have updated server and agents to version 3.3.305. This version fixes some critical issues discovered in last few days:

- Server crash when receiving ill-formed SNMP response
- Server crash when accessing zone object attributes from NXS
- Error in initialization agent local database (issue NX-1849)

This version also contains driver for Moxa industrial routers.

Best regards,
Victor

First configure run fails because you didn't have "make" installed. I suggest to unpack source package into clean directory and re-run configure. You should not run automake and autoconf if you get source package - it may lead to broken configure. You should just run configure as it provided in the package.

Best regards,
Victor

Hi,

on this tab you will see charts for DCIs marked as "show on performance tab". It is configurable in DCI properties (right click on node, then "data collection", double click on any DCI).

Best regards,
Victor