NetXMS Support Forum

Hi,

I probably found the bug. Try to patch src/server/tools/nxdbmgr/upgrade.cpp as following:

Find line 492 - it should be

         TCHAR *config = DBGetField(hResult, i, 3, NULL, 0);

insert after it the following code:

         if (config == NULL)
            config = _tcsdup(_T(""));

Rebuild nxdbmgr - it should work.

Best regards,
Victor

Hi!

You can execute object tool via Java API or using nxshell (which is a Python wrapper around Java API). Approximate sequence will be following:

1. find cluster object (by name or ID)
2. for each child node object call NXCSession.executeAction

Here you can find more information about API:

http://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations
https://www.netxms.org/documentation/javadoc/latest/

Best regards,
Victor

Actually, this bug is already fixed (I think it was in 1.2.14 or 1.2.15) - service installer no longer adds -D option to service command line unless it was explicitly specified. But if service was created by previous version -D 0option remains because agent installer do not change service definition. Existing services can be re-created by running script like this:


nxagentd -S
nxagentd -R
nxagentd -c C:\NetXMS\etc\nxagentd.conf -I
nxagentd -s


(stop agent, remove service, install service, start agent).

Best regards,
Victor

Hi!

Agent configs on server requires that agent can connect to server - this could be problematic in some environments. On the other hand, agent will receive full config and can be started without config at all.

Agent policies cannot be used to bootstrap agent - you still need local master config with at least master server address set. But they can be used over existing agent connection, via proxy, etc.

We plan to keep both options for foreseeable future. If new agent deployment is not happen very often, I probably would recommend agent policies. They are somewhat easier to manage, and we plan to improve them.

Best regards,
Victor

Hi!

Do you have something in server log regarding LDAP? Also, try to set connection string as ldap://10.192.30.23

Best regards,
Victor

Quite strange. Seems that crash occurs in process initialization, even before our code is called. That usually means that something is wrong with the libraries.

Best regards,
Victor

Hi,

can you please run it under gdb and post backtrace after crash?

Best regards,
Victor

Hi!

No, it is not possible. This is intentional limitation - NXSL scripts executed within a sandbox and cannot communicate with external world directly. However, you can define external parameter on an agent, and use AgentReadParameter function to get it's value.

Best regards,
Victor

Hi,

supposedly I've found the problem. I've made necessary changes in 1.2.16. Please let me know if your problem will be solved after upgrade.

Best regards,
Victor

Hi!

Did you add a rule to generate alarm? Having threshold will only generate you an event - you have to add a rule to event processing policy to make alarm from it. See Event Processing section in user manual for more information.

Best regards,
Victor

Hi!

This can be done using scripts. For example, the following script will return true if node has only subnets a parents:


result = true;
parents = GetNodeParents($node);
foreach(p : parents)
{
   if (p->type != 1)   // Type 1 = subnet
   {
      result = false;
      break;
   }
}


You can create separate container with autobind script which will bind nodes not located in any container. For example, if you call this container "NewNodes", autobind script could be like this:


parents = GetNodeParents($node);
foreach(p : parents)
{
   if ((p->type != 1) && (p->name != "NewNodes"))   // Type 1 = subnet, also ignore "NewNodes" container itself
   {
      return false;
   }
}
return true;


Best regards,
Victor

Hi all!

NetXMS version 1.2.16 is out. It's mostly a bugfix release to fix important issues found in 1.2.15. Full change log is following:

- Fixed database upgrade issues
- Fixed packaging issues
- Fixed bug causing outdated peer information on interface objects
- Fixed bug with upload to agent default path from server file store
- Instance display name for DCIs created via instance discovery
- DCIs created via instance discovery can be combined by instance into one chart on performance tab
- Transformation script terminated by "abort" call will not generate SYS_SCRIPT_ERROR event
- Database manager can detect and fix missing IData and TData tables
- NXSL:
   - String concatenation operation interprets NULL value as empty string instead of throwing runtime error
   - Fixed incorrect processing of ilike, match, and imatch operators
   - Added try / catch operator
- New MIBs added: NETUP-MIB
- Fixed issues: #424, #618, #619, #620

If you are upgrading from version 1.2.14 and below and encounter errors related to missing tdata tables during database upgrade please run command

nxdbmgr check-data-tables

and the run upgrade again.

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

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

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