Hi all!
NetXMS version 2.2.1 is officially released. Changes since previous release:
- Implemented separate access rights for each DCI object
- Option to read log files using VSS snapshots on Windows
- Per stage confirmation in database manager during database check
- Fixed file download cancelation
- HTTPS support in SMSEagle driver
- New network map element - text box
- New debug log format with tags
- Ability to set debug level per tag or tag mask
- Improved audit logging on object creation
- NXSL function "GeoLocation" replaced with "GeoLocation" class constructor
- Optimized object updates in database (to reduce load on database in large installations)
- Thread pool used for data collection instead of fixed number of poller threads
- Optimized data collection from agents
- Configurable number of records per transaction for writing DCI data
- Fixed issues:
NX-662 (New network map element - text box)
NX-703 (Export/Import actions)
NX-757 (Instance discovery - grace period for removed instances before deleting DCIs)
NX-801 (Deleted nodes not removed from trusted nodes lists of other objects)
NX-1045 (Add rack/chassis diagram as dashboard element)
NX-1142 (Back view for racks)
NX-1201 (Discovered node links on map should automatically be set to color based on the status of the interfaces shown in co
nnector names)
NX-1252 (Fix automatically generated transformation scripts for 64 bit interface counters)
NX-1268 (Do DNS resolve for node names via zone proxy)
NX-1289 (Override PollCountForStatusChange at Node level)
NX-1292 (Option for line charts to not always use 0 as base)
NX-1336 (Cluster DCI Max/Min aggregation returns value from last node instead of expected max/min)
NX-1339 (JIRA restricts subject field to 254 chars, helpdesk integration should trim alarm text or move reset of the message
to issue description)
NX-1341 (Scheduled tasks enabled/disabled indicator)
NX-1342 (Increase text length limit in SMS sender)
NX-1343 (Server crash on re-enabling temporary disabled user)
NX-1344 (Search Bar for Agent Tunnel Manager)
NX-1345 (Add rule number to EPP export)
NX-1347 (New agent parameter File.LineCount)
NX-1348 (Continuous warnings in server log: seed object 0 cannot be found)
NX-1357 (Line chart is now opened on double clicking a Performance Chart)
NX-1359 (Last location in World Map is now saved)
NX-1361 (Data type of transformation script's input value can be incorrect)
Best regards,
Victor
thank you very much for the hard work and this great app.
Yes, Thank you very much for your great work....
p.s. Why the number shift (2.2.1 vs 2.1.3)?
All the netxms agents had stopped working right after upgrade to 2.2.1. Config files of all agents contain the following lines:
RequireEncryption = yes
RequireAuthentication = yes
EncryptedSharedSecret = B/Cx9iK3RpLCpgp+8SvHuMKmCn7xK8e4wqYKfvErx7g=
It worked fine with all previous agent versions but causes 2.2.1 agents to crash soon after they started. Very sad :( What should I do now to get NetXMS working again? I've lost connection with all network nodes...
P.S. Error in Windows logs:
H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems
Right after this NetXMS Agent service crushes.
Quote from: StanHubble on December 07, 2017, 11:55:03 PM
p.s. Why the number shift (2.2.1 vs 2.1.3)?
We had internal build with version number 2.2.0 distributed to our support clients with some important changes backported from 3.0 branch. Before this release we decide to make it new stable branch - because changes are important. To avoid version clashes and uderscore that there are significant changes inside we decide to number this release 2.2.1.
Best regards,
Victor
Quote from: iGodunoff on December 08, 2017, 10:16:43 AM
All the netxms agents had stopped working right after upgrade to 2.2.1. Config files of all agents contain the following lines:
RequireEncryption = yes
RequireAuthentication = yes
EncryptedSharedSecret = B/Cx9iK3RpLCpgp+8SvHuMKmCn7xK8e4wqYKfvErx7g=
It worked fine with all previous agent versions but causes 2.2.1 agents to crash soon after they started. Very sad :( What should I do now to get NetXMS working again? I've lost connection with all network nodes...
P.S. Error in Windows logs:
H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems
Right after this NetXMS Agent service crushes.
From the context I assume it is Windows. Do you have crash dumps from agent? If not, please enable crash dump generation in agent config and send them to us. As a workaround I recommend to rollback to agent version 2.1.2 (they will work with new server).
Best regards,
Victor
If it's Windows then it seems very strange as I have multiple Windows versions (from XP to 10, 31 and 64 bit) but the agents crash everywhere. OK, I'll try to enable dumps and send them.
Thanks to all for the new release.
On WinXP 32bit (I know it's too old) I get Error missing "api-ms-win-crt-runtime-l1-1-0.dll" when I update V2.1.2 to V2.2.1 with package deploy. It seems to be something from a C++ Runtime. Is it not included in the installer? Which C++ is needed?
thanks
Dani
Hi,
try to install runtime from Visual Studio 2017. Seems that we pack it incorrectly.
Best regards,
Victor
Is C++ Runtime 2017 installable on WinXP?
edit:
I tried it on a test VM. It works on WinXP with Visual C++ Runtime 2017 x86.
thanks
Dani
Hi Victor,
there were threads about agents crashing and threads about packaging issues, does the links in download section lead to the latest and fixed packages ?
Best Regards,
Lindeamon
Hi,
current download links points to repackaged agents. It should work fine without separately installed VC++ runtime. We didn't fix agent crash issue yet, but was unable to reproduce it either.
Best regards,
Victor
thank you very much !!!
New Android management console filename suggests it's 2.2.1 version, but when installed it seems to be still 2.1.2, is it me or the apk is wrong?
Hi Victor!
Would you implement nxsl's functions for dealing with persistant storage, please. I see a few functions in ps.cpp, but it seemed those not exported into nsxl.
Hi,
persistent storage is implemented. You can access persistent storage entries using # operator. It has two forms:
#identifier
and
#(expression)
If your key conforms to NXSL identifier requirements you can use first form, otherwise (or if you are building key name dynamically) you should use second form. Examples:
1. Set value of key "test":
#test = 123;
or
#("test") = 123;
2. Set value of a key whose name built from prefix "node_" and current node ID:
#("node_" . $node->id) = 42;
3. Print value of key from example 2 multiplied by 10:
println #("node_" . $node->id) * 10;
Best regards,
Victor
Thank you very much, Victor! It's really nice and convenient.
Quote from: xchema on December 11, 2017, 06:22:24 PM
New Android management console filename suggests it's 2.2.1 version, but when installed it seems to be still 2.1.2, is it me or the apk is wrong?
Same problem for me also with the android apk manager ..
Hey Victor,
After update server to 2.2.1 (database check ok )
update de Windows manager to 2.2.1 I can not login anymore --> Connection Error org/netxms/base/GeoLocation
restart the Netxms server (ubuntu) does not help ...
UPDATE:
after deleting user date on management pc + delete NETXMS manager (new version was extracted over the older version)
and re-unpack the new version i could start the manager again .
Android console version is broken or didn't recompile properly or whatever reason it is.
Filename suggests it's 2.2.1. But after launch program says 2.1.2 and didn't connect to the server due to incompatible version of exchange protocol.
Thanks for your work. You do a great job. It makes our lives much easier ;)
P.S. Oh, and Android AppManager says it's 2.1.0
Hi,
we just updated download link for Android client to properly packaged apk.
Best regards,
Victor
Quote from: Victor Kirhenshtein on December 18, 2017, 02:15:28 PM
Hi,
we just updated download link for Android client to properly packaged apk.
Best regards,
Victor
Thanks Victor, apk version is ok now.