NetXMS Support Forum

Hi all!

NetXMS 2.0-M1 is released. This is first release in 2.0 branch. From now on we change version numbering scheme. Now it consists of only two numbers followed by qualifier. Qualifier could me M (for Milestone) which indicates milestone toward release, RC (for Release Candidate), and no qualifier for stable release. Patches after release will be indicated by adding third number.
We do lot of changes in system internals, and much more expected in next milestone versions. Although we do our best to test system before release, M versions may still be unstable, so upgrade with care and be prepared for rollback.

Full change log since previous release:

- New hook script "AcceptNewNode" (can be used as additional filter for network discovery to avoid unnecessary communications)
- SMS driver for Kannel gateway
- Oracle subagent: added parameter Oracle.CriticalStats.Deadlocks
- Reporting server improved
- Code page option added to all client command line tools (nxalarm, nxevent, nxpush, nxsms)
- New NXSL functions: GetNodeTemplates
- New parameters in Windows agent: System.Update.LastDetectTime, System.Update.LastDownloadTime, System.Update.LastInstallTime
- Network service response time can be monitored
- Added driver for HP A-series and V-series switches
- MIB compiler correctly handles REFERENCE keyword in agent capabilities section
- Oracle Tuxedo monitoring subagent
- Improved server performance with PostgreSQL
- Alias and MTU collected and stored for interfaces
- Server uses ipAddressTable and ipAddressPrefixTable to collect configured IP addresses when supported by monitored nodes
- Management console:
    - New dashboard element "DCI summary table"
    - Cluster objects shown on status maps
- Android console:
    - Added date in X axis (graphs) when the time frame is greather that one day
    - Added 10 minutes, 12 hours, 5 days, 30 days, last year options in draw graph for last values tab (5, 7, and 30 days asks for confirmation of long task execution)
    - Fixed graphical problem (checkbox) in last values tab
    - Support for KitKat Wear and Lollipop, updated support library v4
- Fixed issues: #61, #306, #381, #488, #565, #628, #634, #667, #672, #673, #674, #675, #677, #678, #679, #682, #684, #686, #688, #689, #691, #697, #698, #700, #704, #705, #709, #710, #715

Best regards,
Victor

Thanks for the new release.

When I install the Windows(x86) agent on Windows XP (old I know) I get the error that 'libnxsnmp.dll' is not found. The message appears 3times.

We also get an error on Windows2012R2 server with NetXMS V2.0M1 agent. Here in Eventlog:

Faulting application name: nxagentd.exe, version: 0.0.0.0, time stamp: 0x54afa34c
Faulting module name: libnxsnmp.dll, version: 6.3.9600.17476, time stamp: 0x54516b13
Exception code: 0xc0000135
Fault offset: 0x00000000000ec5a0
Faulting process id: 0xdb8
Faulting application start time: 0x01d02dab874d8b4d
Faulting application path: C:\Program Files\NetXMS\bin\nxagentd.exe
Faulting module path: libnxsnmp.dll
Report Id: c4fa1742-999e-11e4-8129-00155d0a6422
Faulting package full name:
Faulting package-relative application ID:

In agent install directory (bin) is no such DLL 'libnxsnmp.dll'

I confirm the problem. Can't install (or upgrade) the new NetXMS agent (2.0-M1) in Windows. Agent can't be started because libnxsnmp.dll library is absent. It seems that the agent's installer should copy this library to bin directory but it doesn't.

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

Thanks Victor for the fast fix.
Manual upgrade install local on a node is working now (Win x64).

But deploy from NetXMS server to a node where agent V1.2.17 is installed does' not work.
The two agent processes (agent and watchdog) are terminated but no update. In Windows eventlog is an error with Event-ID 10006, Source: RestartManager, 'Application or service 'nxagnetd' could not be shut down.

edit1:
I don't see any updated files and in Windows Control Panel V1.2.17 is still installed. In 'Services' the NetXMS agent is in 'running' state, but in Task Manager I cannot see any running 'nxagnetd' processes.
Then I  'stopped' the NetXMS agent in 'Services' and started again, service is than in state 'running' but still no 'nxagentd' processes running, and NetXMS server cannot connect to agent.

edit2:
I also tested the agent upgrade by package deploy on a Win-x64 node with 'EnableWatchdog=no', that works! So the problem only exists with 'EnableWatchdog=yes'

edit3:
Agent install path is 'C:\Program Files\NetXMS'

is the package deploy problem with watchdog enabled reproducible? It looks like the same problem I reported for an older version of NetXMS.

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

Best regards,
Victor

Funny bug:
configuration parameter in nxagent ListenAddress actually read backwards.
So instead of 192.168.1.2 you should write 2.1.168.192

Nice catch!
Fixed, will be released in upcoming 2.0-M2.

Quote from: volkoff on January 23, 2015, 06:19:24 PM
Funny bug:
configuration parameter in nxagent ListenAddress actually read backwards.
So instead of 192.168.1.2 you should write 2.1.168.192

This one is much more serious:
I can't create or delete  DCI.
History:
I tried to play with SNMP's table DCI, but wasn't successful. Later we'll get back to that
But I created one for the node (printer). And since that I can't create or delete DCI. Looks like after "sync" period something breaks, sync thread stops answering to watchdog and I can't connect with console.
So, my opinion - something is wrong in sync thread.
Error is 100% reproducible, so I can supply you with any kind of data.
DB is SQLite, Windows server 2008 R2, but since data is accumulated correctly I do believe something is wrong in sync thread (or with SQLite).

Quote from: volkoff on January 24, 2015, 07:41:37 PM
This one is much more serious:
I can't create or delete  DCI.
History:
I tried to play with SNMP's table DCI, but wasn't successful. Later we'll get back to that
But I created one for the node (printer). And since that I can't create or delete DCI. Looks like after "sync" period something breaks, sync thread stops answering to watchdog and I can't connect with console.
So, my opinion - something is wrong in sync thread.
Error is 100% reproducible, so I can supply you with any kind of data.
DB is SQLite, Windows server 2008 R2, but since data is accumulated correctly I do believe something is wrong in sync thread (or with SQLite).

DCI tables do not work with SQLite.

This is a known issue.

As a workaround for now, you can use a different DB.

Quote from: tomaskir on January 24, 2015, 08:00:39 PM
DCI tables do not work with SQLite.
This is a known issue.
As a workaround for now, you can use a different DB.

How terrible I didn't know about that.
But as a guy who do some programming, I'm aware of the fact, that if there is some issue that prevents using of the product you should provide some bugfix rather than "it's a known issue" even for free and open source product
And since I have this particular bug isolated I can provide some (or even all in my case) data to fix it.

Proper solution is to migrate to any sane DBMS – you can do it using "nxdbmgr" tool, there is special "nxdbmgr migrate" mode.
SQLite never was intended for use in production environment, and we will probably remove support in future altogether.
Main reason for that – a lot of features are not supported in SQLite (lack of ALTER TABLE DROP COLUMN is perfect example) or implemented poorly – and while it's possible to add workarounds, it require time, which we prefer to spend on more critical tasks.

Quote from: volkoff on January 24, 2015, 08:14:29 PM

Quote from: tomaskir on January 24, 2015, 08:00:39 PM
DCI tables do not work with SQLite.
This is a known issue.
As a workaround for now, you can use a different DB.

How terrible I didn't know about that.
But as a guy who do some programming, I'm aware of the fact, that if there is some issue that prevents using of the product you should provide some bugfix rather than "it's a known issue" even for free and open source product
And since I have this particular bug isolated I can provide some (or even all in my case) data to fix it.

Quote from: Alex Kirhenshtein on January 24, 2015, 08:52:45 PM
SQLite never was intended for use in production environment, and we will probably remove support in future altogether.

Well, that's the answer Ok, I'll use other DBMS.