NetXMS Support Forum

If I understand you need correctly, you need script which will convert numeric codes into strings, right? Then you can do the following:

Create script in script library, with some name, let's say "convert" (here I assume that you need to convert event's parameter %2 into text - otherwise change index in parameters[] accordingly):


switch($event->parameters[2])
{
   case 1: return "test";
   case 2: return "test2";
   // and so on...
}
return "unknown"; // default value


and then use it in a message like %[convert]

Best regards,
Victor

Hi!

It's a bug. Unfortunately there are no workaround, you have to wait for version 1.1.8 with a fix.

Best regards,
Victor

Yes, that's correct.

Best regards,
Victor

It's fixed already in the trunk, so 1.1.8 will not have this bug.

Best regards,
Victor

Try to use netstat -atnp command - then you will see what exact process keeps this port open.

Best regards,
Victor

It should be under /usr/local/bin if you have used default prefix.

Best regards,
Victor

What operating system is on remote machine?

Best regards,
Victor

I agree that this may be useful. One problem is conflict resolution - node can be placed in multiple containers - what settings should be taken in tah situation?

Best regards,
Victor

Yes, I want to create new object type "management board" for this type of situations. I'm also have a lot of servers with iLO boards
Currently you can use the following method as a workaround:

1. Create separate node object for management board
2. Add server node object to "trusted nodes" list of management board node object
3. Create DCI on server node object and specify management board node object as "proxy node"

Then you will have DCIs on server node object, but they will be collected from management board.

Best regards,
Victor

Hi!

You can use unmanage/manage as a workaround for manual maintenance mode. System do nothing with unmanaged node. The only drawback is that unmanage operation is hierarchical, i.e. all interfaces and services of a node will change status as well, and when you do "manage" node again, they all come into "managed" state, even if some of them was unmanaged before.

Best regards,
Victor

Looks like database was not initialized correctly. Try to initialize it by running

nxdbmgr init /usr/local/share/netxms/sql/dbinit_<your_sql_engine>.sql

Best regards,
Victor

Hi!

You either have another NetXMS instance already running, or some other program uses these ports. You can use netstat -an command to check if somebody uses these ports. What operating system you are running on?

Best regards,
Victor

No news, sorry. I keep this in mind, but there are always something to do. Now I'm trying to create to-do lists for each release and follow them. 1.1.8 is already scheduled, so I have added to 1.1.9 to-do.

Best regards,
Victor

Hi!

Yes, this is the reason why event log is empty. Do you get these errors all the time?

Best regards,
Victor

Problema mozet bit' vo vremeni ispolnenija komandi. Po umolchaniju ona dolzna ukladivatsja v 2 sekundi. Esli komanda ispolnjaetsja dol'she, to nado libo uvelichivat' timeout'i, libo komandu zapuskat' iz schedulera s vivodom v fail, a ExternalParametr uze budet tol'ko zabirat' znachenie iz etogo faila, libo ispol'zovat' ExternalParameterProvider.