NetXMS Support Forum

I'm building from source and I'm failing at the MariaDB database driver, because I can't find "mariadb.h". There is a comment about "your own wrapper header", thus I'm assuming this is not part of the MariaDB library.
Is this file missing in the repo? 

https://github.com/netxms/netxms/blob/1d3c9de01bf9df8a07189aebc4b5973c679dd206/src/db/dbdrv/mariadb/mariadbdrv.h#L50C11-L50C20

I'm using table metrics extensively for collecting data which changes frequently, like running processes or some kind information on user sessions on a terminal server (instead of using instance discovery which I use for metrics which stay unchanged most of the time).

I have an issue with table thresholds and I'm not sure if this is expected behavior:

• Let'say, I'm monitoring the expiration date of TLS certificates with a table metric.
• At some point the expiration date reaches the threshold and an event is generated.
• On the system, the certificate is replaced with a new one and the old (expired) one is removed. This means, the table metric will drop the row for the expired certificate. 
• The issue is: The table metric still displays that the threshold has been reached, even if this row has disappeared.

I understand that this is sometimes useful, but in this case the "row" for the expired certificate will never appear again and the threshold on the table metric is reached indefinitely. Even clearing the collected data won't reset this state.

Is there some workaroud for this situation? If no, I would request a new option for table metrics to trigger the threshold "Deactivation event" for disappearing rows.
  

See here Source node override with templates (netxms.org)

With the new Collector object class I think this will be even more useful.

We are using the WebApi for creating different objects. Creating new nodes or containers works without problems, but the API returns an error when creating a new zone. We are sending this JSON:

{
    objectType: 6
    name: "NewZone"
    parentId: 1
}We are setting parentId = 1, because the object "Entire Network" has object id 1. This returns an "Internal error" with code 46.

I did take a look at the code and it seems impossible to create a node with parentId = 1.
https://github.com/netxms/netxms/blob/62c5f9ec1837c93023a40a71781ea2c73037b4c9/src/client/nxapisrv/java/src/main/java/org/netxms/websvc/handlers/Objects.java#L377

Can you check this?

Ok, I did some further testing. As I said, I installed a blank server, but the agent had already some configuration pulled from our production server, and one setting trigged the crash apparently.
The issue seems to be an "Action" with long command:

Action = Test:echo abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890!@$%abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890!@$%abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890!@$%abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890!@$%abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890!@$%abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890!@$%
Add this to the agent's configuration and the object tool "Supported actions" will crash the server process.

Thank you.

Can you explain what this class is for? It looks like a mixture of node and a container?

I just did an empty server installation for testing, it still happens. The server process just exits.

Attached.

I did that, I see there a log file created, but no dump files unfortunately.

I switched to DebugLevel = 7 before trying the crash dump, so I have this already:

Quote2024.09.10 08:35:09.059 *D* [db.cpool          ] Handle 00000217E16C5300 acquired (call from c:\jenkins\workspace\release-windows\src\server\core\objtools.cpp:86)
2024.09.10 08:35:09.060 *D* [db.cpool          ] Handle 00000217E16C5300 released
2024.09.10 08:35:09.060 *D* [db.cpool          ] Handle 00000217E16C5300 acquired (call from c:\jenkins\workspace\release-windows\src\server\core\objtools.cpp:120)
2024.09.10 08:35:09.060 *D* [db.cpool          ] Handle 00000217E16C5300 released
2024.09.10 08:35:09.060 *D* [db.cpool          ] Handle 00000217E16C5300 acquired (call from c:\jenkins\workspace\release-windows\src\server\core\objtools.cpp:561)
2024.09.10 08:35:09.060 *D* [db.cpool          ] Handle 00000217E16C5300 released
2024.09.10 08:35:09.060 *D* [client.session.0  ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.09.10 08:35:09.060 *D* [db.cpool          ] Handle 00000217E16C5300 acquired (call from c:\jenkins\workspace\release-windows\src\server\core\objtools.cpp:255)
2024.09.10 08:35:09.061 *D* [node.agent        ] Node::createAgentConnection(XXXX [46389]): using agent tunnel
2024.09.10 08:35:09.061 *D* [agent.conn.403    ] New connection created (address=UNSPEC port=0 compression=allowed)
2024.09.10 08:35:09.061 *D* [agent.tunnel.180  ] Sending message CMD_CREATE_CHANNEL (2)
2024.09.10 08:35:09.063 *D* [agent.tunnel.180  ] Received message CMD_REQUEST_COMPLETED (2)
2024.09.10 08:35:09.063 *D* [agent.tunnel.180  ] createChannel: new channel created (ID=290)
2024.09.10 08:35:09.064 *D* [agent.tunnel.180  ] Received message CMD_CHANNEL_DATA (290)
2024.09.10 08:35:09.064 *D* [agent.conn.403    ] Using NXCP version 5
2024.09.10 08:35:09.064 *D* [agent.conn.403    ] Sending message CMD_REQUEST_SESSION_KEY (1) to agent at UNSPEC
2024.09.10 08:35:09.066 *D* [agent.tunnel.180  ] Received message CMD_CHANNEL_DATA (290)
2024.09.10 08:35:09.066 *D* [agent.conn.403    ] Received message CMD_SESSION_KEY (1) from agent at UNSPEC
2024.09.10 08:35:09.079 *D* [agent.conn.403    ] Sending message CMD_AUTHENTICATE (2) to agent at UNSPEC
2024.09.10 08:35:09.080 *D* [agent.tunnel.180  ] Received message CMD_CHANNEL_DATA (290)
2024.09.10 08:35:09.080 *D* [agent.conn.403    ] Received message CMD_REQUEST_COMPLETED (2) from agent at UNSPEC
2024.09.10 08:35:09.080 *D* [agent.conn.403    ] Sending message CMD_SET_SERVER_CAPABILITIES (3) to agent at UNSPEC
2024.09.10 08:35:09.080 *D* [agent.tunnel.180  ] Received message CMD_CHANNEL_DATA (290)
2024.09.10 08:35:09.080 *D* [agent.conn.403    ] Received message CMD_REQUEST_COMPLETED (3) from agent at UNSPEC
2024.09.10 08:35:09.081 *D* [node.agent        ] Node::createAgentConnection(XXXX [46389]): conn=000002178265C090
2024.09.10 08:35:09.081 *D* [agent.conn.403    ] Sending message CMD_GET_LIST (4) to agent at UNSPEC
2024.09.10 08:35:09.081 *D* [agent.tunnel.180  ] Received message CMD_CHANNEL_DATA (290)
2024.09.10 08:35:09.081 *D* [agent.conn.403    ] Received message CMD_REQUEST_COMPLETED (4) from agent at UNSPEC

I tried that but it seems there is no crash dump created. Is this possible or am I looking at the wrong place?

I'm getting a server crash on object tool "Supported actions". It is the pre-defined object tool.
I first noticed it in 5.0.7 and it still happens on 5.0.8. Server is running on Windows, agent is also on 5.0.8, but it seems the agent version does not make any difference.

Just upgraded to 5.0.8 and everything looks fine again, thank you!

Currently files can be easily delived by agent policy. It would be nice to have an option to remove/delete a specific file from a remote system, defined in the File Delivery policy.