NetXMS Support Forum

Yes, it looks like message is too big (or rather supplied buffer is too small). I've registered an issue in our bug tracker: https://track.radensolutions.com/issue/NX-1863

Best regards,
Victor

Hi,

agent configuration file looks correct. What is set as primary host name / primary IP address in proxy node settings? Could it be that firewall itself also responds to your NetXMS server via SNMP, possibly providing different set of interfaces? Please check what is displayed in overview and interfaces tab for proxy node. Ideally please post screenshots of those two tabs along with forced configuration poll output.

For agents inside client network you should use proxy node's IP address as master server address. It is good to specify ZoneUIN in proxy agent configuration but is not necessary for each agent inside zone.

Best regards,
Victor

Hi,

this is bug in the agent that should have been fixed in version 3.3.314. Try to upgrade agent to that version if not already done, and then delete agent's local database file (usually C:\Windows\system32\config\systemprofile\AppData\Local\nxagentd\nxagentd.db) and restart agent. It should re-create database with correct structure.

Best regards,
Victor

Hello,

what is GUI version and operating system?

Best regards,
Victor

Hi,

starting with 3.2 you can also define web service and use it for data collection. For example you can define web service named TestService with correct URL and authentication options and then create DCI with origin "web service". As parameter you should use service_name:path_to_element. For example, to access number_of_pending_tasks element:

TestService:/number_of_pending_tasks


Best regards,
Victor

Hi,

this is caused by lazy object sync introduced in 3.2 - interface objects are no longer synced on login, but only when you expand node or select interfaces tab. We will add appropriate on-demand synchronization for maps as well. In the meantime as a workaround you can try to turn on option "full object synchronization on startup" in console properties (File -> Properties -> Object Browser). This is client-side setting so should be done on each client.

Best regards,
Victor

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