Hi all!
NetXMS version 2.0-M5 is out. Changes since previous release:
- Agent-side caching of collected data
- Fixed bug in handling floating point Windows performance counters
- Added "comments" attribute to NXSL "DCI" class
- New NXSL function sha256
- Fixed broken nxagent.sms SMS driver
- Added support for SNMP traps over IPv6
- Switched to SHA-256 for password hashing
- Timestamp can be provided in nxpush and nxapush
- New methods in NXSL class "Event": setMessage, setSeverity, setUserTag
- Command line options for nxagentd to change effective user and group after start
- Fixed occasional NXSL compiler crash on scripts with syntax errors
- Errors in auto bind/apply scripts interpreted as "ignore" instead of "false" result
- New core agent parameter File.FolderCount
- Fixed broken active discovery
- Improved system behaviour on large installations
- Management console:
- Fixed broken VPN connectors configuration
- "Inverted values" option on line charts
- Filter in predefined graphs tree
- Values of selected DCIs can be shown on object overview page
- "Stacked" option added to line charts on dashboards
- In-place file rename in file manager
- Option to export data from line charts on dashboard to CSV file
- "Select all objects" option in network maps
- "Proxy node" option in DCI properties renamed to "Source node" to avoid confusion
- Android Console:
- Added "capabilities" in node overview (changed to expandable list view)
- Fixed issues: #50, #630, #780, #781, #791, #794, #797, #798, #806, #815, #816, #817, #824, #832, #833, #837
Best regards,
Victor
Hello Victor,
the Windows client keeps crashing immediatly after it is contactad by the server. It happens on all machines. I reverted the client to 2.0-M4 which runs without any problems.
Update the windows agents from NetXMS console (V2.0-M4 to V2.0-M5) worked ok (for Win-32bit for the first time in this verson!).
I also see the Windows agent crashes on some nodes, the agent is always restarted from the watchdog process but immediately crashs again.
When I try to stop windows agent from control panel on all Windows nodes I get the error "Error 109: The pipe has been ended". After that the agent ist stopped and can be started again.
Configuration poll on windows agents always give:
[21.06.2015 15:18:15] Capability check finished
[21.06.2015 15:18:15] Checking interface configuration...
[21.06.2015 15:18:15] Unable to get interface list from node
[21.06.2015 15:18:15] Interface configuration check finished
[21.06.2015 15:18:15] Checking node name
[21.06.2015 15:18:15] Node name is OK
[21.06.2015 15:18:15] Reading list of installed software packages
[21.06.2015 15:18:15] Unable to get information about installed software packages
[21.06.2015 15:18:15] Finished configuration poll for node node.domain.com
[21.06.2015 15:18:15] Node configuration was not changed after poll
So get installed software and interface list are not possible.
Downgrade to V2.0-M5 from the NetXMS console works only for nodes where the agent not crash all the time.
Linux agents are ok.
hello,
i have had a problem with agents too.
i have one agent, the server's agent and it only has to monitor a remote file system's free space.
1st restart to the agent did not help and it seems like the agent does not collect the DCI.
2nd restart to the agent and due to a crash, a restart to the server fixed the problem.
Best Regards,
Lindeamon
Hi,
Looks like there is a missing database driver sqlite.ddr in the 64bit agent. Checking the bin folder does not show any file there by that name.
Looks like the sqlite.ddr is also missing from the 32bit package as well.
Also after the upgrade of the server some DCIs did not function. A restart of the server service after the upgrade seemed to bring them all back. Sounds like it may have been a DB upgrade issue?
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
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
hello alex,
can you explain why do i need agent caching ?
can you add needed info like when the cached info get sent to the server ?
Best Regards,
Lindeamon
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.
thank you for the explanation.
when will you post the repacked agents mentioned before ? i save all the releases and i want to save the correct installation files.
Best Regards,
Lindeamon
Here the crash dump of a Win-x64 agent. If you need more information, please ask.
Hi,
I've just uploaded Windows agent installer with a fix.
Best regards,
Victor
Thanks Victor
Only a first short test on Win2012R2 with your fixed agent installer:
- no crashes yet
- it's possible to stop the service in control panel without error
- configuration poll on this node can get network interface configuration
- configuration poll on this node can get installed software packages
thanks for the quick fix, I will test more tomorrow
Dani
thank you victor,
do you plan to upload the windows server installers with this fix too ?
i do not want to remember that i have to install the fixed agent on the server too.
Best Regards,
Lindeamon
Server installer is not affected – problem was because of missing sqlite.ddr, which is included in server package.
thank you alex.
when do you plan to make version 2.x the stable release ?
Best Regards,
Lindeamon
Nothing is set in stone yet, but we want to release 2.0 in August. RC1 is scheduled for mid-July.
Hi,
Am still seeing invalid netmask warnings on x86 systems and a few devices.
Netmask is also showing incorrectly in the console.
Cheers, Brett.
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!
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!
I see this errors in all Agent logs (V2.0-M5, Windows and Linux):
[08-Jul-2015 16:00:04.115] [ERROR] DB Library: Unable to load database driver module "sqlite.ddr": The specified module could not be found.
[08-Jul-2015 16:00:04.115] [ERROR] Unable to open local database
It's not the same as the missing-'sqlite.ddr' issue. The 'sqlite.ddr' is existing in 'bin'-directory. In debug-log are no more information on that and I can't see any faulting functions yet.
Very thanks Alex!
great work and great project!
Regards,
Quote from: Alex Kirhenshtein on July 08, 2015, 10:38:33 PM
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!
Hi.
In repos (wezzy , beta) i see only netxms-server_2.0-M4-1, is any chance to get M-5 via apt in debian ?