NetXMS Support Forum

Hi!

I plan 1.0.8 to be mostly a bugfix release (plus custom SNMP port feature), and if everything will go as expected, I'll will release it in a week.

Best regards,
Victor

Few additional questions:

Do you have a Windows firewall running on server machine?
Is there any error messages in netxmsd log?

Best regards,
Victor

I suspect that it may hit some limits for open connections. There was a limit of around 4000 outgoing TCP connections in Windows 2003, I'm not sure how it is in Windows 2008. Could you please run netstat -n and count connections to external IPs on port 4700? And how many of them are not in ESTABLISHED state?

Best regards,
Victor

Hi!

Unfortunately I cannot reproduce this on my system. Could you please run nxagentd under gdb and send me a backtrace after crash?

To run agent under gdb:

1. Run command
gdb /opt/netxms/bin/nxagentd

You will get gdb prompt:
(gdb)

Type command:
run -f

Agent will run in foreground. After crash, gdb prompt will appear:
(gdb)

Type command
bt

and send it's output to me.

Best regards,
Victor

Some additional questions:

1. where the packets was captured?
2. is it possible that incoming SNMP packets blocked by firewall at NetXMS server machine?
3. could you run server with debug level set to at least 6 (command line option -D 6) and post log file?

Best regards,
Victor

Added to bugtracker as feature request.

Btw, some message customization can be done using custom attributes for the object. For example, you can define custom attribute MESSAGE and then insert it's value into alarm text by using macro %{MESSAGE}. Of course, this is not a replacement for functionality you was asking for, because it requires manual attribute configuration on each node, but it can help in some cases.

Best regards,
Victor

Queues looks much better now. The only possibly problematic number is data collector's queue. Is it always like this, or it was just a short pike? Btw, by default server create DCIs for internal queue sizes. If those DCIs are configured, could you post a charts of them for last hour or two?

Few things I forgot:

- Remove ProcessAffinityMask option from netxmsd.conf. It does not help with the crash issue, but prevents using of all CPUs in the system.

- Some additional questions:

1. How many memory consumes netxmsd process? Is it growing?
2. What is the state of SQL server? So high value for database writer queue means that either NetXMS server cannot send requests as fast as needed or SQL server cannot process them as fast as needed. Increasing value for NumberOfDatabaseWriters will speed up request sending, but will SQL server be able to handle them?

Best regards,
Victor

Hi!

Numbers are quite high, especially database writer queue. I would suggest to change some server parameters, taking into account number of nodes you have:

NumberOfStatusPollers = 100
NumberOfConfigurationPollers = 25
NumberOfRoutingTablePollers = 25

NumberOfDatabaseWriters = 5


I would also suggest to increase status and configuration polling intervals, which are one minute and one hour respectively. My recommended settings is to set configuration polling interval to at least 4 hours, and status polling interval to 90 seconds. It can be done by setting the following parameters:

StatusPollingInterval = 90
ConfigurationPollingInterval = 14400


Best regards,
Victor

Hi!

No, it's not possible. I can add this as feature request.

Best regards,
Victor

Hi!

Am I understand your correctly - you have one three-node cluster, and each node has two SNMP agents?

Right now the only working solution I could imagine is to configure lot of external parameters on agent which will call nxsnmpget - but this cannot be considered as good solution. I think that easiest way is to allow change of SNMP port on node and DCI basis - this is relatively easy change and will solve this problem. I'll try to implement it in 1.0.8 release.

Best regards,
Victor

Hi!

Could you please post a screenshots of your trap configuration? Also, try to set server's configuration parameter LogAllSNMPTraps to 1 and check SNMP trap log. Ensure that server generating the trap is registered as a node in NetXMS.

Best regards,
Victor

I create full build with changed memory management. Installer available at https://www.netxms.org/download/rc/netxms-1.0.8-rc1.exe. It can be installed as usual, and replaced back to 1.0.7 if needed.

Best regards,
Victor

Thank you! I hope that we will be able to finally solve this issue without forcing you to switch to another OS.
Donations are welcome in any form In fact, even your patience with this strange issue resolution is very helpful - because we are unable to reproduce this issue at our systems. And yes, Raden Solutions is owned by me and Alex.

Attaches is another build of libnetxms. Could you try to run server with it?

Best regards,
Victor

Most likely you have one extra 0 in your event code. Automatically assigned codes starts with 100000, so 100009 could be correct.

Parameters after event code are event-specific data, accessible on server via %1, %2, etc. macros and appropriate variables in NXSL scripts.

Best regards,
Victor