NetXMS Support Forum

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.

Eto versija 1.1.7? U menja bila takaja problema s serverom na Solarise. No v versii 1.1.7 ja ee vrode kak pochinil.

Hi!

Discovery poller only puts candidate node into poll queue. Another thread is responsible for node validation and appropriate object creation. All this code located in file np.cpp. Polling thread looks like this:

      pInfo = (NEW_NODE *)g_nodePollerQueue.GetOrBlock();
      if (pInfo == INVALID_POINTER_VALUE)
         break;   // Shutdown indicator received

      DbgPrintf(4, _T("NodePoller: processing node %s/%s in zone %d"),
                IpToStr(pInfo->dwIpAddr, szIpAddr), IpToStr(pInfo->dwNetMask, szNetMask), (int)pInfo->zoneId);
      if (AcceptNewNode(pInfo->dwIpAddr, pInfo->dwNetMask, pInfo->zoneId))
      {
         Node *node = PollNewNode(pInfo->dwIpAddr, pInfo->dwNetMask, 0, NULL, 0, 0, NULL, pInfo->zoneId, true);
      }
      free(pInfo);


AcceptNewNode checks candidate node against current discovery filter, and if it passes, PollNewNode is called, where actual node object being created. Inside PollNewNode method Node::configurationPoll is called, where all interface and subnet objects are created, as required.

Best regards,
Victor

Hi!

Try to add /usr/local/lib to /etc/ld.so.conf, run ldconfig, and then try make install again.

Best regards,
Victor

Hi!

You have to install mysql client library package. For CentOS 5 it probably would be mysql-devel.

Best regards,
Victor

Hi!

Done it. It is where the power of Eclipse platform lies - contributing same extensions to different part of UI is very easy and sometimes takes just few minutes.

Best regards,
Victor

Hi!

Server only generates SYS_NODE_UP event for nodes that was previously down. The "down" state is not preserver between server restarts, so if node was started during NetXMS server restart, it marks it as "up" during first poll, and SYS_NODE_UP never generated. I agree that this is not correct. I'll add it to my to-do list, and will fix it (probably by preserving "down" state across server restarts).

Best regards,
Victor

Hi!

It should be 1 under most circumstances. You can monitor event processor queue size to see if there are any bottleneck, but I actually never seen this.

Best regards,
Victor