NetXMS Support Forum

Thank you.
I know this workaround.

Hi Victor,

thank you for your answer. It was good idea first ask before I started  to modify the sources  .

If I understand this right, there is no such posibility for the NXSL function executeSSHCommand. Is it so?

I've seen that that the SSH.Command uses fixed port 22.
It would be useful to have the possibility to specify different port. Can I add the fifth optional parameter port with default value 22 to the SSH.Command? Would you add it this change to your sources?

Hi Victor,

the systemd setting was the problem.

Thank you.

After I increased the number of monitored Nodes via one proxy agent, I see lot of following messages in the agent log:
2020.12.28 13:23:52.562 *E* [                   ] Unable to accept incoming connection (24 Too many open files)
2020.12.28 13:23:53.066 *E* [                   ] Unable to accept incoming connection (24 Too many open files)
2020.12.28 13:23:56.570 *E* [                   ] Unable to accept incoming connection (24 Too many open files)


I've tried to increase the operating system value for max number of open file descriptors but even the value 65535 is not sufficient.

The CPU usage and other parameters of the proxy agent and server are OK.
I use some SNMP DCIs for and some script DCIs which start Agent actions on the proxy agent, but the number of DCIs is lower than 65535.

Objects............: 4404
Monitored nodes....: 1221 (approximately 900 via this proxy agent)
Collectible DCIs...: 14683

What does this message mean?
Is there any possibility to solve the problem?

Hi Victor,

thank you for the confirmation that it is an error and for the workaround.

I am not sure if it is a bug or a feature  .

I use "Parent template name should match the following template (comma separated regular expression list)" filter for some Object Tools. This works correctly if the user has at least Read access right to Templates. If the user does not have this right, the tool will not appear in the Command section of the Node.

I think think that is not the expected behavior because a normal user does not need to see Templates for his daily work, but he needs to use Object tools.

Would it be possible to solve this problem and allow using this filter without having the Read access right to Templates?

The correct Parameter name is ICMP.ResponseTime.Average.

I forgot that the Ping subagent must be loaded on the Proxy too.
SubAgent = ping.nsm

The proxy Linux should be in the Default zone (with UIN = 0) and not in zone C.
It should be set as a Proxy node for zone C and for discovery.

Proxy must be enabled in the agent configuration:
EnableProxy = yes
EnableSNMPProxy = yes
EnableSNMPTrapProxy = yes
EnableSyslogProxy = yes
EnableTCPProxy = yes

I use this setting and it works well except for the ping problem (see https://www.netxms.org/forum/general-support/ping-status-behind-zone-proxy/).

What is the full path of the Templates for DCIs with IDs 6784, 6739 and 6503 in your first picture? These Templates generate the instances. 

These are instance DCIs generated form the Template. You can disable or delete the corresponding DCI in the Template definition.

According this:
https://www.netxms.org/forum/general-support/invalid-network-mask-4369/
and this:
https://www.netxms.org/forum/general-support/invalid-network-mask/

The network mask on first device found in certain subnet is considered as correct one, but I didn't test it, I have these alarms disabled in my installation.

You can disable the alarm, but it is probably not what you want.

Thank you.
I was probably blind that I didn't find it.