Hi all!
NetXMS version 1.2.15 is out. Changes since previous release:
- LDAP support
- Event names support in nxevent
- Previous state parameter added to SYS_NODE_UP event
- Added file management subagent (filemgr.nsm)
- Removed agent configuration parameter EnableArbitraryFileUpload
- New NXSL class "Zone"
- New attributes "zone" and "zoneId" in NXSL classes "Node" and "Interface"
- Syslog records from unmanaged nodes do not generate events
- Syslog node matching improved
- New access rights for nodes:
- Download File (download file from agent to local workstation)
- Upload File (upload file from local workstation to remote node)
- Manage Files (move, rename and delete files on remote node)
- Management console:
- "Commands" box on node overview page made configurable
- Object tools can have icons
- "Last value" type gauge can show non-numeric values
- "Trusted Nodes" property page shown for condition objects
- Network map content can be copied to clipboard
- Perspectives export/import
- Topology related options in node's context menu grouped in "Topology" submenu
- Added specialized view for IP routing table
- Added specialized view for switch forwarding database
- Agent configurations manager implemented
- Android Console:
- Added option in preference to show/hide legend in graphs
- Object comments displayed
- Added "Navigate to" option for objects with geolocation set
- Fixed issues: #136, #158, #457, #512, #537, #540, #555, #564, #566, #584, #586, #594, #596, #597, #598, #602, #605, #606, #607, #608, #610, #612, #614
Best regards,
Victor
Thanks for the new release!
But I get this db upgrade error when I upgrade from V1.2.14 to V1.2.15 on linux 64bit with PostgreSQL:
Upgrading database...
Upgrading from version 318 to 319
Upgrading from version 319 to 320
Upgrading from version 320 to 321
Upgrading from version 321 to 322
Upgrading from version 322 to 323
Upgrading from version 323 to 324
NOTICE: CREATE TABLE / UNIQUE will create implicit index "tdata_257_record_id_key" for table "tdata_257"
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "tdata_records_257_pkey" for table "tdata_records_257"
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "tdata_rows_257_pkey" for table "tdata_rows_257"
SQL query failed (42830 ERROR: there is no unique constraint matching given keys for referenced table "tdata_records_257"):
CREATE TABLE tdata_rows_257 (row_id bigint not null,column_id integer not null,value varchar(255) null,PRIMARY KEY(row_id,column_id),FOREIGN KEY (row_id) REFERENCES tdata_records_257(row_id) ON DELETE C ASCADE)
SQL query failed (25P02 ERROR: current transaction is aborted, commands ignored until end of transaction block):
SELECT id FROM clusters
SQL query failed (25P02 ERROR: current transaction is aborted, commands ignored until end of transaction block):
SELECT id FROM mobile_devices
SQL query failed (25P02 ERROR: current transaction is aborted, commands ignored until end of transaction block):
DELETE FROM metadata WHERE var_name='ValidTDataIndex'
Rolling back last stage due to upgrade errors...
Database upgrade failed
Quote from: Dani@M3T on July 28, 2014, 11:29:49 AM
But I get this db upgrade error when I upgrade from V1.2.14 to V1.2.15 on linux 64bit with PostgreSQL:
Hello.
Thank you for report. This bug in upgrade procedure is already fixed, we testing it right now.
Hi Alex
Ok, thanks. So I wait for your patched version.
Hi,
updated source package and Windows installers are on web site.
Best regards,
Victor
I just tested the fixed version. DB update is working now. Thanks for the fast fix!!
I download latest source package, but also have error when upgrade on Solaris 10 SPARC with PostgreSQL:
bash-3.2# /opt/netxms/bin/nxdbmgr upgrade
NetXMS Database Manager Version 1.2.15 Build 7881
Upgrading database...
Upgrading from version 323 to 324
SQL query failed (42P01 ERROR: table "tdata_rows_500" does not exist):
DROP TABLE tdata_rows_500
SQL query failed (25P02 ERROR: current transaction is aborted, commands ignored until end of transaction block):
DELETE FROM metadata WHERE var_name='ValidTDataIndex'
Rolling back last stage due to upgrade errors...
Database upgrade failed
Hi!
Seems that table is missing while it should exist. Try to create table with that name (any structure, it will be dropped anyway) and run upgrade again.
Best regards,
Victor
I created all the missing tables and the db upgrate was successful. Thank you, Victor!
Is there somewhere a documentation of the new file management subagent (filemgr.nsm)?
I didn't found anything in the wiki.
All new documentation is added there:
https://www.netxms.org/documentation/adminguide/index.html
Information about file management:
https://www.netxms.org/documentation/adminguide/file-management.html
https://www.netxms.org/documentation/adminguide/subagents.html#filemgr-subagent-label
Thank you. I was looking in the wiki.
Is the file management subagent only available on linux agents?
Should work on all platforms. Tested also on Windows.
Windows path:
RootFolder = C:\log
I installed the windows agent by the 'nxagent-1.2.15-x64.exe' but there is no File Management Subagent in the subagent selection list of the installer (only ecs.nsm, ping.nsm, logwatch.nsm, portcheck.nsm, winperf.nsm, wmi.nsm, ups.nsm) and there is no 'filemgr.nsm' file in the 'bin'-directory after installation.
In log file I get:
Error loading subagent module "filemgr.nsm": The specified module could not be found.
wooooooooohooooooooooo
finally. i will wait for the fix of the missing nsm file and then...
partyyyyyyyyyyyy
Hi,
was the problem with the filemgr.nsm fixed ? can i download ?
10x,
Lindeamon
Hi,
I forgot to include filemgr.nsm into binary package. I'll repack agent installer soon. For now filemgr.nsm for Windows x64 attached.
Best regards,
Victor
and for Windows x86
System: Debian 7
DB: Oracle 11.2
Upgrade troubles
Upgrading database...
Upgrading from version 318 to 319
Upgrading from version 319 to 320
Upgrading from version 320 to 321
Upgrading from version 321 to 322
SQL query failed (ORA-01440: column to be modified must be empty to decrease precision or scale):
ALTER TABLE users MODIFY system_access number(20)
Rolling back last stage due to upgrade errors...
Database upgrade failed
After truncate table users
appeared:
$ nxdbmgr upgrade
NetXMS Database Manager Version 1.2.15 Build 7881
Upgrading database...
Upgrading from version 321 to 322
SQL query failed (ORA-01440: column to be modified must be empty to decrease precision or scale):
ALTER TABLE user_groups MODIFY system_access number(20)
Rolling back last stage due to upgrade errors...
Database upgrade failed
upd.
All ok.
I have made backup, truncated data and restored.
nxdbmgr upgrade finished in 40 minutes.
hi victor,
how soon will you do it ? i want to download a full working version without extra files.
Best Regards,
Lindeamon
Debian 7
Oracle 11
An error apears after upgrade
Target: INSERT INTO dc_tables (node_id,template_id,template_item_id,name,description,flags,source,snmp_port,polling_interval,retention_time,status,system_tag,resource_id,proxy_node,perftab_settings,transformation_script,comments,item_id) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
Alert: ORA-00947: not enough values
Yes, it's a bug. Updated version will be available later today.
Best regards,
Victor
Quote from: lindeamon on July 31, 2014, 12:03:51 PM
how soon will you do it ? i want to download a full working version without extra files.
I plan to release 1.2.16 with all hotfixes today or tomorrow.
Best regards,
Victor
thank you victor.
Hi,
Am I supposed to update all the agents I've running with previous versions (1.2.8 and 1.2.14) in order to upload a file from the netxms server (1.2.15)? and wait until the new realese (inclundin the missing file manager subagent).
I've having a really hard time trying to install remotly software using the package manager on server 1.2.15, could it be a new bug?. NPI file are ok and sometime the server could achieve the task but mostly it fails.
Thanks,
Hi!
Quote from: flynao on August 01, 2014, 08:47:54 PM
Am I supposed to update all the agents I've running with previous versions (1.2.8 and 1.2.14) in order to upload a file from the netxms server (1.2.15)? and wait until the new realese (inclundin the missing file manager subagent).
Remote upgrade and file upload are supported by older agents also. For fully functional file manager you need agent 1.2.15 or higher and filemgr subagent (which will be included in 1.2.16).
Quote from: flynao on August 01, 2014, 08:47:54 PM
I've having a really hard time trying to install remotly software using the package manager on server 1.2.15, could it be a new bug?. NPI file are ok and sometime the server could achieve the task but mostly it fails.
Can you please provide more details? What errors you got, on what platforms, etc.
Best regards,
Victor
After upgrade from .14, am getting a lot of these in Event Monitor:
Posting as an image because "Copy to Clipboard" is not working for some reason.
(http://s2.postimg.org/rp6rf1qqh/error.png)
Hi!
Seems that you have some object (with ID 492)being deleted for which corresponding idata table does not exist. As a workaround try to create table with that name and any structure so server can delete it and proceed.
Best regards,
Victor
Quote from: Victor Kirhenshtein on August 04, 2014, 11:22:52 AM
Hi!
Seems that you have some object (with ID 492)being deleted for which corresponding idata table does not exist. As a workaround try to create table with that name and any structure so server can delete it and proceed.
Best regards,
Victor
Did that, created the table manually, the server then dropped the table.
Error still in log however, even after doing this.
Strange. Is it really same table, or maybe it is now with different ID or tdata instead of idata? Try to create four tables: idata_492, tdata_492, tdata_rows_492, tdata_records_492.
Best regards,
Victor
Quote from: Victor Kirhenshtein on August 04, 2014, 11:51:53 AM
Strange. Is it really same table, or maybe it is now with different ID or tdata instead of idata? Try to create four tables: idata_492, tdata_492, tdata_rows_492, tdata_records_492.
Best regards,
Victor
First I was getting many of there errors (as in my original post):
(http://s14.postimg.org/3x6iq9l81/error1.png)
So I created a table "idata_492" in DB. The server then dropped this table.
After the server dropped that table in DB, I got this error:
(http://s4.postimg.org/rbe0p85nh/error2.png)
I created that table in the DB as well. The server then dropped that table as well.
Now I am getting the original "idata_492" error again tho.
(http://s27.postimg.org/bawvmmpjn/error3.png)
Hi Victor.
This is the message I received after trying to upload a xml file from the server to the nodes (Win 64 and 32 architecure). Basically the files I'm tryining to upload, are log parse configuration files. Before the upgrade I was able to do it and any problem came up.
To do any manipulations with files on a node it is required to load filemng subagent and configure accessible paths. https://www.netxms.org/documentation/adminguide/file-management.html
The only 2 exceptions are agent update and upload of file to default path(When destination path is empty). Upload to default path is broken in version 1.2.15.
Hi Tatiana. Thanks for your reply.
what do you mean by "upload of file to default path(When destination path is empty)"?
the only way I found to deploy these xml files to my nodes was as follows:
I created a npi file for each file, so then I uploaded the xml files as a software using the package manager, then as usual I deployed the files to the nodes (the files have been stores at the directory set up on the agent's configuration file.
I know the new version has a file manager subagent. I added the filemgr.snm by hand on one of my nodes. please find attached the configfile used. the file manager worked, I was able to upload a file using the new manager. But in this new case I've to update every single node I've (we're talking about 80 nodes) by hand, and Im still no able to deploy in one shot one file to all the nodes.
Quote from: flynao on August 04, 2014, 11:41:46 PM
the only way I found to deploy these xml files to my nodes was as follows:
I created a npi file for each file, so then I uploaded the xml files as a software using the package manager, then as usual I deployed the files to the nodes (the files have been stores at the directory set up on the agent's configuration file.
Package manager should not be affected by changes in file transfer (and introducing filemgr subagent). Could you please check it with "nxupload" command line tool? Syntax is "nxupload AGENT_IP local_file_name". File should be uploaded into FileStore (C:\NetXMS\etc in your case).
I'd use slightly different way (but you'll need file manager subagent for that):
1) Tools -> Upload File to Server (select target XML configuration as "local file", leave "remote name" empty to use local name)
2) Right click on any node or container and select "File upload". Click on "select" button and select file you uploaded in step 1, leave name blank
3) Click "Ok"
Hi Alex.
The way you suggested, its the way I normally use to upload files. but the result is the same "Unknown command" in server Jobs window. I'm going to check the nxupload command. Thanks for your help.
Note about enabled filemgr subagent on the large network, there are two ways:
1) Create configuration policy and deploy to all agents, where required.
Sample policy:
<config>
<agent>
<subagent>filemgr.nsm</subagent>
</agent>
<filemgr>
<RootFolder>/opt</RootFolder>
<RootFolder>/private/etc</RootFolder>
</filemgr>
</config>
2) Use nxshell-based script to fetch existing agent config remotely, modify it and reapply. I don't have script on hand at the moment, but can share it later.
Hi Victor,
I runned the nxupload on line command and the result is:
903: I/O failure
thanks
Hi,
don't want to be a nag but, when does 1.2.16 with all the bugs fixes will be out ?
10x,
Lindeamon
Quote from: lindeamon on August 05, 2014, 09:12:54 PM
Hi,
don't want to be a nag but, when does 1.2.16 with all the bugs fixes will be out ?
10x,
Lindeamon
Hi,
it's being packed and will be available later today.
Best regards,
Victor
Quote from: flynao on August 05, 2014, 04:30:18 PM
Hi Victor,
I runned the nxupload on line command and the result is:
903: I/O failure
thanks
Hi,
file upload using core agent is fixed. We will release version 1.2.16 which will include that fix later today.
Best regards,
Victor
Thanks Guys, great job!!!!! :D