NetXMS Support Forum

Hi,

you can safely ignores these errors - it just tries to re-create tables that are already exist. Normally it shouldn't happen though. Watch if there will be any other SQL errors.

Best regards,
Victor

Hi,

do you have JRE under C:\NetXMS\bin\jre? Try to remove it so console will pick up system JRE.

Best regards,
Victor

I've made some changes in installer - hopefully it will help. Please try 2.0-M2 when it will be available.

Best regards,
Victor

Hi,

try to use CPPFLAGS instead of CFLAGS - CFLAGS only affect C sources, while CPPFLAGS affects both C and C++.

Best regards,
Victor

Hi,

I likely fixed it in development branch. Fix will be part of 2.0-M2 release (will be published very soon). It works on my CentOS 6.5 test system.

Best regards,
Victor

Yes, upgrade procedure is the same - you just run nxdbmgr as usual and it will make necessary changes in DB.

Best regards,
Victor

Yes, it's exactly same bug - NetXMS was not read ipAddressTable. After upgrade to 2.0-M1 or newer your problem should be fixed.

Best regards,
Victor

Hi!

1. In Last Values for cluster you will see only those DCIs that are marked for aggregation (see Cluster property page of DCI) - and for them you'll see aggregated value (for example, average COU usage for cluster nodes).

2. Yes, it's not implemented yet.

3. Yes, it will be published soon. It is in my short TODO list.

4. Agree.

5. Cluster DCI configuration works like a template that is applied to all cluster nodes. So any DCI without resource association will be collected on each node.

6. Currently it's not possible to create template with cluster resource binding. I'll think how it could be implemented.

7. Interfaces on cluster nodes with addresses belonging to cluster networks excluded from network topology. It is quite common setup when multiple clusters has identical IP addresses on interconnect links.

Best regards,
Victor

Quote from: VMGuy on January 13, 2015, 10:23:59 PM

QuoteCheck agent's config file – server IP address should be whitelisted by using "MasterServers" option, all others ("Servers" and "ControlServers") don't have sufficient rights to edit configuration file remotely.

In the config file I have (and always had) this:
Servers = 192.168.x.y
ControlServers = 192.168.x.y
MasterServers = 192.168.x.y

But it doesn't work.

That's new bug introduced in 2.0 - server's access level determined by first statement insted of one with maximum access. If you leave only MasterServers (which implies ControlServers which in turn implies Servers) it will work.

Best regards,
Victor

There was very similar problem on VMWare ESX which was fixed in 2.0-M1. What NetXMS version you are using?

Best regards,
Victor

no, custom attributes are not intended to be copied when you apply template. You can use scripts to create custom attributes where needed (for example, handle SYS_NODE_ADDED event, identify node as SNOM phone and add this attribute).

Best regards,
Victor

Hi,

I was able to reproduce problem with netxmsd.exe hang (on Windows Server 2003 32 bit). I'll publish installer with a fix later today.

Best regards,
Victor

Can you please change LogFile from {syslog} to some file and run netxmsd -D9 from command line? It should show at least some messages.

Best regards,
Victor

Hi,

can you please show your netxmsd.conf?

Best regards,
Victor

Yes, it's a bug in installer. I just uploaded installer with a fix, please try it (file names are the same).

Best regards,
Victor