NetXMS Support Forum

What's in the log file of agent at the moment when they became unsupported?

Probable reason could be some problems with platform subagent - it's winnt.nsm in case if the agent is on windows.

config file absence is not an issue yet - it's not able to find a .so library.

Try to create a file /etc/ld.so.conf.d/netxms.conf with the following contents:
/opt/netxms/lib/

Then run
ldconfig

This should add /opt/netxms/lib/ to the list of places where system searches for shared libraries.

Then attempt to launch nxagentd -D 6 should give something like this:
Configuration loading error: Could not process "/etc/nxagentd.conf"!
Error loading configuration from "/etc/nxagentd.conf" section CORE
Error loading configuration file

The next step is to create agent config file /etc/nxagentd.conf. The minimal config could be like this (replace the address in MasterServers to actual address of your NetXMS server):

LogFile = /var/log/nxagentd
DebugLevel = 2
MasterServers = 192.168.1.2


The first thing to try is generic ARM agent that's available among downloads:

https://www.netxms.org/download/releases/3.1/nxagent-3.1.343-linux-arm.tar.gz

Extract it to the root of the filesystem - the files will get to /opt/netxms - and try running
/opt/netxms/bin/nxagentd -D 6

If we are lucky, it will start - and will blame that there is no config file - you could create one in /etc/nxagentd.conf. Or it will not start, then you'd have to compile it from sources.
Please report the results.

This happens only when map is scrolled - the coordinates where the node appears do not consider the offset due to scrolling. Created https://track.radensolutions.com/issue/NX-1790 for that.

What kind of map is it? Is automatic layout disabled?

Hi!

Under what OS do you run the management console?

Can you show the screenshot of how the policy is configured - what's the root folder, are there any subfolders?

Also, if you set debug level on server and agent to 6, you could find some information in the log files. On server you can change that on the fly: nxadm -c "debug 6"
After changing debug level, you can perform "Force deployment of agents policies" and there should be something in the logs.

Currently there is a bug in Mac console, that nothing happens when trying to add a file. If you are on mac, try console on linux or windows.

For this function to work, filemgr should be enabled in agent configuration and root folder(s) should be set:

SubAgent=filemgr.nsm
[FILEMGR]
RootFolder=C:\

In current version all folders along the path should exists on the target system. In future versions agent will create folders. Files are only sent to agents, they are not deleted, when removed from policy / renamed in a policy.

If you edit agent policy, the settings will get applied (files sent to agents) the moment, when you close the list of agent policies. They should also get applied on configuration poll. And in context menu of template there's an option "Force deployment of agents policies".

templates = $node->templates;
foreach(t : templates)
{
   if (t->name == "Windows") {
      $node->setMapImage("Windows");
      break;
   }
}


Логика такова, что диапазон для обнаружения элементов сети определяет только то, какие именно IP адреса сервер пробует, на маску подсетей, которые создадутся в Entire Network это не оказывает никакого влияния.
Маску сервер пытается получить с обнаруженных девайсов, но для этого нужно, чтоб девайс на девайсе был или агент или SNMP. Если устройство только ответило на пинг, но больше про него ничего не известно, то будет создана подсеть /24. Далее, если найдется хоть одно устройство, которое сообщит, какая у него маска, то сервер должен поменять маску на правильную.
Есть ли у вас там устройства, сообщающие свою подсеть. Если да, то стоит посмотреть в логах, что конкретно происходит при обнаружении.

You could create Hook::ConfigurationPoll script and change icon for node with NXSL script. It is necessary to specify GUID of image, currently in image library GUIDs are not visible, but will be visible starting from version 3.2 that should be out soon.

Can you set DebugLevel=6 in netxms server configuration file and show what's in the log file?

Also, how did you create the database? Using NetXMS installer? Can you just attach a screenshot of netxms installer on the step called "Select database" with all the checkboxes in the state as you use them to created the database?

There is a log file you can inspect to find the reasons. The exact file name is specified in NetXMS server's config file, usually it's  C:\NetXMS\log\netxmsd.log.

What is your PS and Windows versions?

Can you please attach a high-resolution screenshot and describe what you were doing:
- from what version you were upgrading
- to what version
- exact steps you did