NetXMS Support Forum

I've installed current versions of java, but the eclipse log always shows that eclipse sees the current java version as 1.8.0 144. There seems to be some corruption inside either java  or eclipse that's causing this. I've decided to do a bare metal restore back to the day before my failed attempt to update to netxms 3.8. I don't have the time to keep researching this.  Thanks to -Zebbie for your advice.

I just realized that the error and logfile were both issued by eclipse. The file is in the \users\<username>\.nxmc\eclipse. Does anybody know why eclipse would have a problem after upgrading from 3.7 to 3.8?

Thanks again,

-Mark

As recommended, I've installed the most recent Java 15 JDK, but the problem is still there.

What puzzles me is that, until today, I was running on 3.7 just fine without any Java issues!

-Mark

Hi,

When I upgraded everything to 3.8, nxmc wouldn't start based on a problem with a java component. The server seems to be ok. I'm attaching the log file mentioned in the error message. As of now, I can't use the console at all Please help!

Thanks in advance!

I belatedly found the nxmc installation procedure in the netxms admin guide. Everything is working again!

I would still appreciate it if the combined server/console distribution could still be included in the downloads page.

Thanks again,

Mark

I understand what the message means. My question had to do with the change to the distributions that seems to have dropped the bundled server and console installation executables. I've been using windows-based netxms for quite awhile, and I've always used the bundled distribution and I've never had this problem. I did look in nxmc-3.2.380-win32-x64.zip. There are no installation instructions in the zip file, so I'm not at all sure how to proceed. I must be missing something.

So, my questions are:

Has the combined installer been removed permanently?

If so, how can I separately install nxmc?

Thanks!

Up to date win10.
Update from 3.1.260 to 3.2.380
nxmc fails to start with this message:

Server uses incompatible version of communication protocol (server=[52,4,1,1,1,27,1,2] Client=[52,3,1,1,126,1,2]

I didn't see the usual distribution containing both the server and the console, only the server distribution, so nxmc wasn't updated. What am I missing?

Thanks, as always, for your help.

Mark

Hi Victor,

I am embarrassed to report that this problem was actually caused by some overzealous antivirus software blocking the agent/server communications. This was not due to any issues with NetXMS!

Now I have to figure out how to tell the "Smart Firewall" to stop interfering with this legitimate traffic!

Thank you,

Mark

Hi Victor,

This is strange. All of the other nodes' agents can communicate with the server without any problems. The server's agent isn't seen by the core service, which I think is the reason for the errors I've seen. In the agent config file for the server, I've made sure that the server's correct IP address was in the MasterServers line, and I tried 127.0.0.1 and localhost, but no luck. I haven't added any nodes, so there wasn't an opportunity to get the server node confused. The issue seems to be that the server can't talk to the agent on the same machine. This is probably going to be something obscure: simple but not obvious (at least to me!).

After updating to 2.2.14, the server node's DCC display now has the internal parameter Server.AverageDCPollerQueueSize showing as unsupported. That entry under the template DCC shows as enabled, but when looking at the server node DCC, it shows as unsupported.

This is a very small home environment, so there's only a single unclustered server node.

This parameter has always worked without any problems. No other parameters seem to be affected. No changes have been made either to this parameter or to this node. No other node is so affected. Any ideas?

Thanks!

UPDATE

After rebooting the server today, I got the following additional alarms:

[Minor]   NetXMSServer   Status of DCI 86 (Internal: Server.ThreadPool.Usage(SCHEDULER)) changed to UNSUPPORTED
[Minor]   NetXMSServer   Status of DCI 95 (Internal: Server.ThreadPool.LoadAverage(SCHEDULER,1)) changed to UNSUPPORTED
[Minor]   NetXMSServer   Status of DCI 96 (Internal: Server.ThreadPool.CurrSize(SCHEDULER)) changed to UNSUPPORTED
[Minor]   NetXMSServer   Status of DCI 97 (Internal: Server.ThreadPool.Load(SCHEDULER)) changed to UNSUPPORTED

I'm also unable to see the server node's agent config file through the workbench. I get a communications failure.

None of these issues were showing before I did a bare metal restore, updated PostgreSQL, then updated to NetXMS 2.2.14.

Thank you, Victor! That was the problem! The rest of the install went without any errors.

Hi,

When I attempt to install 2.2.1 over 2.1.2 on a current Windows 10 machine, I get the error in the attached screenshot.

Using PostgreSQL 10 for the database.

I checked the database for errors before the installation.

I get the same error at the same point whether I run the installer as administrator or not.

I haven't changed any file permissions in the NetXMS folder hierarchy.

What am I missing?

Thanks,

Mark

After a new install of 1.2.11, everything is working except there are no initial contents in the Dashboards, Graphs or Reports folders. The Users Guide pages that describe the creation of these objects show populated folders for these objects. I reexamined the installation choices I made, but nothing suggests a decision to include or exclude those facilities.

Since there haven't been any responses to this, I should ask whether I'm mistaken about these folders having initial contents after the install. If that's the case, please let me know.

Thanks,

Mark