NetXMS Support Forum

Hello.

Sorry it took so long. Packages are pushed to public repository (both jessie/wheezy, 32 and 64 bit).

I forgot to push packages from staging area into publicly-available repo; new packages will be available either today or tomorrow morning.

Quote from: jaivar on July 08, 2015, 09:13:15 PM
Hello!

Somebody know how upgrade from 2.0-M4 to 2.0-M5?

I install via repositories and the new version ins't upgrade.

Thanks!

That means that netxms thinks this node it not running server anymore.
Have you changed IP address of the server recently?

Обновите сервер до последнего M5

Are there any errors in catalina.out?

SNMP встроенный в Windows вроде как поддерживает .1.3.6.1.2.1.25.2.3 из HOST-RESOURCES-V2-MIB.
Альтернативный путь – через WMI, запросом из win32_logicaldisk (или через WMI-субагент, или использовать PowerShell как external parameter)

Even simple queries are taking ages (e.g. 10 seconds for update by PK).
What PostgreSQL version are you using? Please share your postgresql.conf.
Do you have battery installed on 410i? Is it in write-back or write-through mode?
What's your read-ahead settings for drives? Please also show output of "iostat -x 5 5".

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.