Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Filipp Sudanov

#1396
General Support / Re: server is taking 12GB memory
April 01, 2020, 02:35:29 PM
Even 5GB is way too high for installation of that size. Can you please run this script and share the results:
https://github.com/netxms/netxms/blob/master/src/server/tools/scripts/nx-collect-server-diag.cmd

There are a few things, like process list or ip addresses, that you might not want to publish, you can either send me the output in PM, or modify the .cmd file so they are not collected.
#1397
General Support / Re: server is taking 12GB memory
April 01, 2020, 12:10:57 AM
Please check "NetXMS server: physical memory used by process" DCI on NetXMS server node. How it's graph looks for a couple of days - is it stable or growing?

Memory usage depends on number of objects, number of data collection threads, etc.
Please show the output of "sh st" command executed in server console.
#1398
Hi!

One day in a future version behaviour regarding certificate expiry might change. As of 3.2 it still the same.

Normally discovered DCIs should not get lost - after rebinding server continues to perform discovery and if it gets all instances, all stays as it was. The problem could be with particular discovery method that is used.

Does it affect only some of the DCIs, not all of them? What method of instance discovery is used for these?

In server configuration there is setting InstanceRetentionTime. It defines, how long instances are retained, if they stop to get discovered. Setting this to some value will keep discovered DCIs for some time, allowing to fix problems with their discovery.
#1399
Can you give more details on what are you trying to achieve?
Do you have a node which has SNMP data for these OIDs?
Do you have any DCIs on that node?
What result of the filtering do you expect?
#1400
I believe PushDCIData will update only DCIs that have origin "Push".
#1401
A "locked" way of map viewing was discussed, but it not yet implemented. Current situation is that all elements are movable, but when user closes the map, no question about saving changes is asked. When opening the map again all items will be on positions when the map was last saved.
#1402
Portcheck subagent does not support authentication. There's another subagent - netsvc - that is based on libcurl and supports authentication by specifying address like: proto://user:pass@host
The difference is that it's not possible to use netsvc as data source for "Network service". The only way to access netsvc is to create a DCI.
#1403
3.2 bugfix release is out. Please check, if it fixed this issue.
#1404
General Support / Re: Mib Explorer result Filter ?
March 30, 2020, 03:26:34 PM
Check the tiny triangle next to Refresh button in the top of Mib explorer view. It hides the menu which enables the filter.
#1405
The thing is that we can't run local commands when using WEB management console - browsers do not allow that. So local commands are only supported in desktop management console.
#1406
Lat/lon of nodes are used on the map in View -> World map. It's using Open Street Map background from server configurable in Server Configuration (TileServerURL).
#1407
First of all, please try to undeploy and deploy again the web console.
#1408
print $node->productCode;
should work. What version are you using?
#1409
Added object count to above reply. All three installations are well below 1 million.
#1410
Network service is using portcheck subagent. This subagent provides a number or parameters that we can directly request for debugging purposes (https://www.netxms.org/documentation/adminguide/service-monitoring.html#portcheck-configuration).

So you can try on the server:
nxget <agent_ip_address> 'ServiceCheck.HTTP(www.google.com,80,/)'
The possible responses are:
0 Success, connection to target was established and expected response was received.
1 Invalid arguments were passed.
2 Cannot connect to target.
3 Invalid / Unexpected response from target

For response = 3 Portcheck can save HTTP server reply in a file that can be inspected to understand if the regex is wrong. For this to happen the following should be specified in agent config:
[portcheck]
FailedDirectory=/tmp/