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

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

don't want to be a nag but, when does 1.2.16 with all the bugs fixes will be out ?

10x,
Lindeamon

I runned the nxupload on line command and the result is:

903: I/O failure

thanks

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.

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.

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"

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.

nxagentd.conf

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.

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.

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):

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:

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.

Best regards,
Victor

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.

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

@flynao said in NetXMS 1.2.15 released:

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).

@flynao said in NetXMS 1.2.15 released:

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

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,

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

Best regards,
Victor

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

how soon will you do it ? i want to download a full working version without extra files.

Best Regards,
Lindeamon

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.