NetXMS Support Forum

В аттаче исперавленный nxdbmgr. Замените тот, что в дистрибутиве M3 и сделайте upgrade еще раз.

Quote from: lindeamon on April 15, 2015, 02:00:51 PM
Hi Victor,

when do you plan to publish the new installation packages with all the fixes ?
up until now i was under the impression that all the new releases are stable ones, what happened ? why does 1.2.17 is considered stable ? we are losing a lot of new and cool features if do not use the latest version.
when will the next stable release is due ?

Best Regards,
Lindeamon

Hi,

we do lot of internal changes (mostly targeted at IPv6 support), so few next M releases could have problems. It can be used in production, although you always should test it on test system if possible. We plan to rerlease M4 very soon which will fix most important issues found so far in M3. I think that stability will improve with next releases as major internal changes are already made and we will focus on fixing bugs and adding features that do not require so big changes in system core.

Best regards,
Victor

Hi,

please send result of command

netxmsd -v

and version and build number shown in bottom right corner of Web UI login screen.

Best regards,
Victor

Quote from: djex81 on April 14, 2015, 03:04:57 AM

Quote from: Victor Kirhenshtein on April 13, 2015, 09:14:15 PM
What address you have set as primary host name for management server node? Can you do nxsnmpwall on that address?

Best regards,
Victor

For the server node I am using the local address 10.0.0.2 . Yes, I can nxsnmpwalk on 10.0.0.2 without any issues.

What operating system and SNMP version used? If you are using SNMP v3, do you use authentication and encryption, and what algorithms?

Best regards,
Victor

Hi!

Quote from: brettmilfos on April 13, 2015, 12:36:19 AM
I have found a couple of problems with ping after the upgrade from 2.0-M2 to 2.0-M3.

One is the ping agent not working, but have got around that by reversing the IP addresses in the conf file.

The second is the ICMP proxy is not working. I would assume it is related to the same issue as the ping agent?

yes, both are related to same problem (also discussed in another post). You can apply patch posted earlier if you are building from sources, or I can provide compiled ping subagent for Windows. Also, we likely to publish patch release soon which will fix issues found so far.

Best regards,
Victor

Quote from: djex81 on April 13, 2015, 06:57:32 PM

Quote from: djex81 on April 11, 2015, 02:20:22 AM
Hi Victor, in this new update you fixed the broken SNMP in agents and that works great but now I am unable to use SNMP from the server netxms is installed on. It was working in version 2.0-M2. What happens is this:

1. I do a configuration poll on the netxms server node. SNMP is connected to and values read.
2. I try to do a SNMP walk from netxms on the local netxms server node and it fails or gives no results back.
3. If I then do another configuration poll on the netxms server node SNMP fails and isn't found.

I know SNMP works as I can SNMP walk with a separate program without any issues. I tried deleting the netxms server node and having it recreate it self but that did not help. Could it be something to do with the new IPv6 interfaces in this new version?

Basically, SNMP is working for all other nodes except the node netxms server is installed on.

To add to my previous post quoted above when I do a status poll on the netxms server node SNMP errors with:

[13.04.2015 11:50:24] Checking SNMP agent connectivity
[13.04.2015 11:50:32] SNMP agent unreachable

The SNMP agent is local so I'm not sure why it's unreachable. I can sometimes get it to connect to SNMP but most of the time it will not. I find if I am able to connect and I try to do a SNMP walk from netxms it will loose SNMP connection and return no results. I have had it return results successfully but only a few times. What debug level should I use so I can check the logs? I tried debug 7 but I couldn't see much in the way of SNMP errors.

What address you have set as primary host name for management server node? Can you do nxsnmpwall on that address?

Best regards,
Victor

Hi,

seems that I have to fix upgrade procedure for MS SQL. I'll try to reproduce it later today and make a fix for database manager.

Best regards,
Victor

Hi!

NetXMS server can support 10k nodes (and even more). Server process itself will consume significant amount of memory (can be few gigabytes) but should not put high load on CPU. It can generate lot of network traffic, but you can control it by choosing longer polling intervals for less important information. Most load will be on database - there will be tenths of thousands of tables (NetXMS creates 4 database tables for each monitored node) with lot of inserts. You should be able to fine tune database of your choice.
From the practical experience, I personally do not know installations of 10k nodes, but one of our customers (which we provide with technical support) runs system that monitors about 3k nodes, and it runs on single Linux server (with secondary server on cold standby with database synchronized) with 8GB RAM and quad core CPU and PostgreSQL as backend database (located on same server).

Best regards,
Victor

А что он там показывает? Пустоту? Можно скриншоты в UP и v DOWN для одного и того-же интерфейса?

Hi,

do you have portcheck subagent loaded on agent running on management server? Can you please share your nxagentd.conf from your management server?

Best regards,
Victor

Hi,

can you please show me your agent config and content of registry entries under HKEY_USERS\.DEFAULT\Software\NetXMS\LogParserLibrary (assuming you run agent under Local System account - otherwise check same registry path under appropriate user)?

Best regards,
Victor

Hi,

would be nice if you registered it as feature request - then it will not be forgotten again I will schedule it for next release.

Best regards,
Victor

Hi,

I fixed ping subagent. You can try to replace ping.cpp and ping.h in src/agent/subagents/ping with attached ones and recompile agent. As side effect, it should also work correctly with IPv6 targets (IPv6 addresses in config should be enclosed in square brackets).

Best regards,
Victor

Hi,

your request should be

intranet.website.com:/testDB.php

(without http:// prefix). Also, there is a typo in response regexp, likely it should be

^HTTP/1\.[01] 200.*OK.*

(note the dot before second asterisk) - otherwise it will match anything with just letter O.

Best regards,
Victor

Hi,

try to increase value for server configuration parameter AgentCommandTimeout (it defines how long server will wait for response from agent, in milliseconds).

Best regards,
Victor