NetXMS Support Forum

Hi, was hoping you could build an nxagent RPM package set for Fedora 41 on packages.netxms.org? 

We're experimenting with layered netxms agent on Fedora IoT atomic and it has rolled to the 41 release.

Kind regards.

Hi I have some agents that have a config file and a couple of agent policies applied. 

I was wondering if there is a way to see a merged running config with effective settings from the config file and the polices?  Saves hunting through config poll logs for applied policies and then finding the relevant policy to see what config comes in that snippet.

Ideally it would be a table that showed line by line the config and in another column the winning source of that line (from local config file or from named policy).

I saw that there is an agent list Agent.RunningConfig available, however if I try to create an object tool to display that parameter it shows up empty.

Is that parameter populated or do I need a specific regex defined as per some other object tools (like show agent lists).

Cheers.

Hi, receiving a 404 attempting to download the windows client installer  https://netxms.com/download/releases/5.1/netxms-client-5.1.1-x64.exe

Quote from: Victor Kirhenshtein on May 11, 2024, 10:59:09 AMI just updated client application so that nodes without parent objects in infrastructure tree are not shown as root level objects. This change will be part of release 5.0.3.
Best regards,
Victor

Thanks Victor, look forward to it.

Quote from: Filipp Sudanov on May 10, 2024, 08:47:24 PMNot sure why this is happening. Can you run the script I've shared manually (via Execute Script from context menu) on a couple of nodes which we bound to that container, but should not and share the output.

Hi Filip, attached is a screenshot of executing the script on a node that had an existing parent.  It always seems to return true whether on a node that has no other parent or an existing node.

Quote from: Filipp Sudanov on May 03, 2024, 12:10:56 PMCurrently you can have "Unbound stuff" container somewhere with this auto-bind script, it will pick objects that are not present in any other containers:

for(p : $object.parents) {
  println(classof(p));
  if ((classof(p) == "Container") and p.id != $container.id) return false;
}
return true;

Thanks Filipp.  

I tried this script however it seems to pickup and autobind all nodes over time, not just those nodes outside the infrastructure services tree with no parent container.  

eg: attached an example of it filtered down to some APs that are already in parent containers and still trigger the autobind event.

I'm still primarily using the legacy console due to muscle memory and preferring how the object browser is not split into the different modules/perspectives like the new console. But I still load it up and check in on it every release to see how its coming along.

One thing I've noticed is that nodes discovered in the network that are not bound under a container in 'infrastructure services' show up outside of the infrastructure service folder heirachy.  Can't see a way to unbind them (as they have no parent container) if I don't want to track them. 

If I bind them to a container "unmonitored" they then move there and disappear.  Does this mean there should be a catch-all container for all nodes?  Or is this a bug?

The legacy console does not show unbound nodes anywhere (other than under their subnets in 'entire network').

Hi, the pinboard seems to not work in the 5.0.0 version of the new desktop client (with 5.0 server)?  You can pin left/right however if selecting the pinboard and then going to the pinboard screen it is still empty.

Appreciate it thanks Filipp.  Fedora IoT has been an interesting platform for some appliances we've been testing with netxms and some containerized apps.

Hi, just wondering if you could build a RPM package set for Fedora 39? 

I know its fairly new, we use Fedora IoT atomic distro and it is a rolling release and has moved to fedora 39 now.  We're just waiting on the netxms agent packages to be available for 39 before we can upgrade from 38.

Kind regards.

Hi Troffasky, are you using the legacy desktop client or the new desktop client?

I've noticed in the legacy client that in some screens right click doesn't seem to work unless you hold down the ctrl key as well.  Specifically I had that with the interfaces tab of a node, shift+select a range and hold down ctrl+right-click to get the popup.

Doesn't happen in the new client.

Agreed, I would also like to see a selectable list of columns and/or drag and drop column re-ordering.

Main bugbear is that the interface status column is now usually off-screen now for all but the largest/widest of monitors.

Also would like to see something here.  Example when upgrading the server and it disconnects the clients.  Would be great to have a tickbox option to 'try reconnect' and have a 5/10sec countdown a bit like the windows RDP client does when it gets disconnected.

OK, if I delete and re-add those elements they now work.  Some internal identifiers changed?

Hi, after upgrading to 4.1-377 I get an error on existing dashboards about missing DCI data.

It looks like the dashboard elements for rack diagram and DCI summary table are missing?  Editing properties of dashboard and trying to edit the dashboard elements for those types gives "Internal Error: no adaptor for dashboard element"

To add to this, the behaviour seems to only show up when you click on certain tabs in certain orders, eg:

• Click on a node in the object explorer and then select a sub-tab for that node like interfaces or physical connections or performance.  When you come back to the overview sub-tab you will see everything collapsed.  Selecting another node and coming back to the current one refreshes the overview.
• Alternatively, instead of selecting another node from object explorer and coming back, if you go to another parent tab like alarms or a dashboard tab and come back to the object details tab, the overview sub-tab won't be collapsed.  If you now select another sub-tab like interfaces or performance and come back to overview again its still not collapsed.

So given the second point above its possible depending on your habitual path through the MC you might not see this all the time.  But I was able to replicate it pretty consistently.  Going to and coming from parent tabs seem to force it to load in a way that doesn't collapse the overview headings.

This also happens on latest 4.1.333