NetXMS Support Forum

Какая версия сервера используется? Откуда ставилась - из пакетов, или компилировалась?
Какая база данных?

You can change logging level for particular debug tags, e.g.:
nxadm -c "debug obj.sync 6"
Then you can check current status of logging
nxadm -c "debug"
And reset logging to default level for particular tag:
nxadm -c "debug obj.sync -1"

"SQL query failed" are errors, so should be visible on debug level 0, so we assume there is no such errors on your system.

obj.sync messages are delayed, should happen within about a minute after deletion on the front-end. Try setting debug level 6 to obj.sync and see what's going to be in the log.

1) please show full output of nxadm -c 'sh st'
2) please show full output of nxadm -c 'sh q'
3) please show graph of NetXMS server: physical memory used by process for the duration for few days - from server start till out of memory event.

Try checking server log either for SQL query error messages or messages with tag [obj.sync           ] saying something like "Unable to delete...". If you see nothing, try increasing debug level to 6.

Agent reads it's configuration file only on start-up, so you have to restart the agent so it will be able to ran this custom parameter.
Now, the server reads available parameters from the agent on configuration poll only. So once you've restarted the agent, you can do a manual configuration poll and then the parameter should appear in the list.

ssh functionality is implemented only in ssh.nsm subagent, server does not do ssh communications. So, if you have zoning, you need to load ssh.nsm on zone proxies. If there's no zoning, agent running on netxms server will be used for ssh commands, so you need to enable ssh.nsm there.

Try to use -P instead of -p.
(one day nxpush will give correct error message in that case )

ldconfig says that there's something wrong with files in /usr/lib/arm-linux-gnueabihf/ - but that's not related to netxms.
What about nxagentd - what happens if you try to start it?

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.