NetXMS Support Forum

Getting the same problem with upgrade from latest 3.5 to 3.6 today.
Agents behind proxy stopped working.
We had to rollback

We are using Cluster object on small OpenVPN AS cluster with two nodes.
They have a floating IP switching between the nodes with UCARP detecting wich node should be primary.

Latly when doing apt upgrade for some reason primary detach the IP without secondary taking over so there is no master of the cluster. Probly some bug in UCARP setup, nothing todo with NetXMS..

But NetXMS does not detect that the floating IP is not active on any node, even not pingable..
First when old primary network is manually restarted alarm with "Cluster resource "X" moved from node A to node "
In Cluster log there is a event that floating/cluster IP is deleted too..
Some version back im pritty sure this situation caused this untouch netxms setup to trigger a "Cluster down" alarm.

Did anything change latly version of NetXMS for Cluster Objects?

In old NetXMS v2. days we didnt use this way of monitoring such cluster, but added a 3th node with the floating IP as PrimaryHostname.
But thats not possible anymore with the detection and merging of nodes with multi IPs to one Object..

Its up:
https://packages.netxms.org/ubuntu/pool/focal/main/n/netxms/

You can find how to reset admin password here: https://www.netxms.org/documentation/adminguide/advanced.html#troubleshooting

QuoteNew in version 2.1-M0.

Use following command to reset password and unlock account:

Code Select Expand

nxdbmgr reset-system-account

Try the path "nxmc-clarity" at the end, ie "host/nxmc-3.3.314/nxmc-clarity"

Hi

Requesting Ubuntu 20.04 (focal fossa) deb in repository 

Possible to set chmod and user rights (chown) in Agent Policy File Delivery.
Atleast possible to set chmod +x for scripts to be used later.

Latest proxmox 6.1 and up2date with apt.
Containers are Ubuntu 18.04.4 also up2date with apt.

Does not happen with all lxc in the cluster.
Had 2 out of 3 on same proxmox node having this when reporting.
It happens randomly, but it seems to hang after the containers have had a big load.

We have a few nodes inside LXC on Proxmox.
They get stuck on "High CPU utilization (100.000000%)" when CPU load hit that, but does not leave 100% before shutdown LXC and start again.

Looking at load avg, it isnt having much work todo.
How does NetXMS agent measure the CPU load?

16 CPU cores 32 Threads
@proxmox:~$ w
07:39:43 up 15 days,  9:28,  1 user,  load average: 0.59, 0.64, 0.72

1 vCPU
@lxc01:~$ w
07:36:43 up 1 day, 12:02,  1 user,  load average: 0.64, 0.73, 0.77

1 vCPU
@lxc02:~$ w
07:38:35 up 1 day, 13:18,  2 users,  load average: 0.59, 0.64, 0.73

You can run this command on server:
nxadm -c "sh sta"

Then use a ExternalParameter to extract the data you will keep track on.

Hi, im also ignoring UDF:

type = AgentReadParameter($node, "FileSystem.Type(" . $1 . ")");
if ((type == null) || (type == "") || (type == "CDFS") || (type == "UDF"))
   return false;
return true;

To identify type, you can add a DCI  with:

QuoteFileSystem.Type({instance})

Did you try install libc6?

Should work with minimal, just need to install the missing library

Are you using Ubuntu or other apt distro?

Quoteapt-get update
apt-get install libc6

You have the netxms dir in wrong path, move it from /root to /opt

mv /root/opt/netxms /opt/

If your script takes more than 3sec, i would use EXternalParameterProvider.

https://wiki.netxms.org/wiki/ExternalParametersProvider