NetXMS Support Forum

Seems to be a bug in 2.1.2. We will check.

Best regards,
Victor

Hi,

please share your configuration - maybe I'll spot the error.

Best regards,
Victor

Macros within parameter name expanded only when you apply template to node. If it is fine, you can use script macro, and read custom attribute in script. But if you want that DCI will use current value of custom attribute immediately after your change it, themn the only option is to switch to script DCI and use AgentReadParameter function. For example:


return AgentReadParameter($node, "ServiceCheck.Custom(" . GetCustomAttribute($node, "IP") . ",80)");


Best regards,
Victor

Hi,

scripts are case-sensitive - i.e. node and Node are two different identifiers. There are no restrictions on formatting, white spaces, new lines, etc.

You can test your scripts by selecting "execute server script" option on a node. Script will have $node variable set, and you can use trace function or print statement to generate debug output that will be seen in output field during script execution.

Best regards,
Victor

Hi,

please check that you don't have ICMP disabled and that netxmsd process can send ICMP packets (runs as root or given necessary access). I will check why SNMP responses are not understood.

Best regards,
Victor

Hi,

currently it's half-done feature. So far it determines if SNMP device is a physical device (only for some devices). Agent already have parameter System.IsVirtual - but currently it is ignored by server. We will implement it in the future, and yes, it will require agent to work on generic OS.

Best regards,
Victor

Hi,

isn't disk time the same thing? It is time spent on I/O - which seems to be the same as disk latency defined in Windows documentation as "A measure of the time delay from the time a disk IO request is created, until the time the disk IO request is completed".

Best regards,
Victor

Just rename them to .txt and use usual procedure.

Best regards,
Victor

Currently no. We have a feature request for that.

Best regards,
Victor

Hi!

"logical not" operation (!) has higher priority than "match" operation (~=). So your script actually does logical not on text string ($node->platformName) which causes runtime error. It only happens on nodes without agent. You should get match operation in brackets:

(!($node->platformName ~= "windows.*"))

Also, I suspect you have logical error here. You probably want to return false if there is no agent OR platform is not Windows - but current condition uses AND which is pointless - if node has no agent platform name will be empty anyway and won't match anyway.

Best regards,
Victor

Hi,

check if you have subnet object with /2 mask. If yes and it is not correct, delete it and run configuration poll on any router connected to problematic subnet with correct netmask. Most likely you have some machine with /2 mask and it was first in subnet discovered by NetXMS server.

Best regards,
Victor

Hi,

seems that server cannot connect to agent. Try to check agent log (you may need to run agent on higher debug level - 6 should shouw you all communication related messages).

Best regards,
Victor

Hi,

seems to be bug in installer. Will fix it today or tomorrow. As a workaround you can copy sql directory from share to lib directory and re-run initialization wizard.

Best regards,
Victor

Hi,

correct bug tracker link is https://track.radensolutions.com/issue/<issue_id>, for example: https://track.radensolutions.com/issue/NX-1147

Best regards,
Victor

Seems you messed agent and server ports. Please do the following:

1. Stop both server and agent.
2. Delete ListenPort line from both netxmsd.conf and nxagentd.conf
3. Run command
nxdbmgr set ClientListenerPort 4701
4. Start both client and server
5. Check in netxmsd.log that server is listening on port 4701

Best regards,
Victor