NetXMS Support Forum

Hi. When we access a rotating dashboard that contains 3 dashboards via the web interface we receive the following popup message:

Problem Occurred:
'Synchronize alarm list' has encountered a problem.
Cannot synchronize alarm list: Widget is disposed

We can press ok and then the message goes away but it comes back when the page is refreshed.

This does not occur if we access the dashboards individually via the web, only the rotating dashboard.

This is version 2.2.4 (9506)

Any ideas?

Is there a way to set the default ordering for the event log?  I would like to order by ID descending instead of Time as a default.  I didn't see anything in the Server Configuration.

Thanks.

I am trying monitor an internet website using the network service (http) option and I can't get the node status to match the service status.  The service looks to be monitoring the website properly and returning the correct status in the DCI (OK).  The node status stays down and it says "Node is still unreachable" in status poll.  There are no interfaces and the http service is the only child object of the node.

I have "Use this DCI for node status calculation" checked in the DCI.
I have all polling disabled except for "Disable data collection".

Version 2.1-M1

What am I missing?

Any help is appreciated.

Thanks.

Hi,

It appears that nodes are not showing up on the Geo Map using the web version 2.1-M1.  I can see the map but not the nodes.  They do appear on the management console.  I know this is a beta version and I wanted to make the problem known if it wasn't already and also see if there is a work around.

Thanks.

We are currently using Situations to control our Node Down and Up statuses which is working well.  The problem we run into is when we do a weekly backup of NetXMS we shut down the NetXMS service which clears our Situation instances.  When we start the service back up a node may not realize it is down and for how long.

Is there a way to backup the Situation instances or prevent them from being deleted on a service restart?

Thanks for any help.

Hi.  I currently have the following filtering script in my "Interface Up Email" Event Processing Policy:

sub main()
{
   CUSTOM_MESSAGE = "TEST";
   i = GetInterfaceObject ($node, $1);
   include_node = false;
   switch ($node->ipAddr)
   {
      case "10.230.0.212":
         if (i->name == "gi7")
         {
            CUSTOM_MESSAGE = "PC to Switch Test Interface";
            include_node = true;
         }
         if (i->name == "gi2")
         {
            CUSTOM_MESSAGE = "PC to Switch Test Interface2";
            include_node = true;
         }
         break;
      default:
         include_node = false;
   }
   return include_node;
}


My Message Text in Action Configuration for email looks like this:  %n - %m - %M

I am getting the email for the correct interfaces and the first 2 parameters for the message (%n and %m) are being passed but the CUSTOM_MESSAGE (%M) is not being displayed.

Any ideas?

Thanks for any help.

If I go to Monitor -> Syslog in the web interface I get blank screen.  I don't have the problem in the Management Console.

I have version 2.0.3 and also had the problem in 2.0.2. 
I can right-click on any node and go to Syslog and the log information is there.
Server is running on Windows.

Is this a known problem?  Any ideas?

Thanks.

We have approximately 250 switches(nodes) that have other switches that are upstream from them. 

If we would like to verify an upstream switch is up before considering a switch to be down do we need to create 250 event processing rules that check a situation status on the upstream switch? 

Is it better to create one event processing rule that has a filter script with basically 250 if statements to check the situation status?

Is there a better way to manage dependencies?  At this point we only care about pinging switches to see if they are up or down.

Thanks for any help.

We are trying to setup a configuration where if any of our nodes are down it will send an email at first poll and then at 5 minutes if it is still down and then at 20 minutes if it is still down.  We only care about icmp at this point.

Can this be setup globally so each node doesn't have to be configured individually?

Any help is appreciated.

Thanks.