NetXMS Support Forum

Upgrade Java to version 7 at least. I, however, highly recommend to use latest Java8 because of numerous security issues in older java versions.

1.2.16

Can you please enable slow query logging (>1sec, for example) and post explain here (or send it to [email protected])?
If it's delete query (most likely), you can do it in transaction and roll it back:
BEGIN;
EXPLAIN ANALYZE DELETE FROM idata_...;
ROLLBACK;

Yes, my bad – packages will be available tomorrow.

Нужен томкат 7 или выше (или любой другой servlet container, который поддерживает Servlet API 3.0)

I think I've seen only one server where this query was working properly.
Check this thread for another solution: https://www.netxms.org/forum/general-support/windows-temperature-monitoring-solution/

What version of NetXMS you are using? It was a known bottleneck and we did a major optimisation in 2.0-M3.

It's known issue – we fixed that already and pushed updated version of the agent installer on the web (version remains the same).
Download agent installer once again and reinstall, it should fix this issue.

From directory name I assume it's installed by hand. Most likely it will work if you create nxmc.properties in /usr/local/tomcat7/lib/ (next to "catalina.jar", etc.)

Nothing is set in stone yet, but we want to release 2.0 in August. RC1 is scheduled for mid-July.

What servlet container you are using? Tomcat, Jetty, Winston? Is is installed from package?

Server installer is not affected – problem was because of missing sqlite.ddr, which is included in server package.

Most  likely you don't need it – and it should be completely disabled after upgrade, system should behave exactly as before. However, if for some reason (bug in upgrade procedure, most likely) it's on – server may stop collecting data from older agents (this will be fixed in next release).

Caching is intended for use on unreliable links. When server connects to the agent, complete DCI schedule for this node is sent, then agent collects data on it's own (and keep it in local database, hence new sqlite dependency). When connection is restored, all collected data is sent to server and then processed. Caching can be set globally (not recommended in this release), per node, or per DCI.

If DCIs are not collected, please check cache mode setting, it can be set in two places:
1) Global parameter DefaultAgentCacheMode, 1 is on, 2 is off. Check that with "nxdbmget get DefaultAgentCacheMode" or in server settings.
2) Cache mode on the node and DCIs – in node properties and in DCI properties respectively

You can download missing sqlite.ddr (both 32 and 64bit versions) here: https://www.dropbox.com/s/to6n0azk3j6qxui/sqlite.zip?dl=0
We will repack installer shortly.

For crashing agents, please add these options to config file and then send us minidump:
CreateCrashDumps = yes
DumpDirectory = c:\path