v3 - Cannot open DCI list for devices with large number of DCIs

Started by rgkordia, October 02, 2019, 02:04:06 AM

Previous topic - Next topic

rgkordia

Hi.

I've just upgraded to v3 (2305).  I'm having a problem accessing some devices in the console, and it appears to be the ones with large numbers of interfaces or DCI's.

I don't recall the issue with v2, although I did add a few more DCI's since upgrading to v3 which could have tipped it over some limit.

Symptoms:

When I right click on a node, sometimes get the hourglass for ~30s and then nothing happens.  Right click again and get a somewhat blank / corrupted popup menu about 1/3rd the size of normal, mostly blank, a few populated items.  If I click on another (smaller) device it seems to clear the problem and I can then right click successfully on the bigger device.  However, attempting to access the DCI configuration, I get the DCI tab pop up but the panel is completely blank.  Not even a blank table, just a grey window with no widgets.

The device in question has 350 interfaces, and I would estimate (can't find out exactly) around 4,000 DCI's

Sometimes when this condition occurs, the console starts acting oddly, and I can't access other things like server console, or edit a dashboard (get blank grey tab).

This is running locally on the server (Windows).  6 CPU, 8GB RAM (mostly dedicated to MariaDB cache).  Also tried console from a remote PC and same issue.  Console is 2284.

Rich

rgkordia

Some screenshots

rgkordia

Another showing the "small" right click corrupted menu.

Just to add, this setup has been working well for a few years (since version 1).  Did an upgrade a week or so back from 2.2.something to 3.

Victor Kirhenshtein

Hi!

Please attach console log (it should be in your user's home folder - C:\Users\<username>\.nxmc\data\.metadata\.log).

Best regards,
Victor

rgkordia

Hi Victor,

Attached is the log.

I also removed some of the DCI's from the template assigned to this node, which resulted in ~200 fewer DCI's for this node, and the problem seems to have resolved itself.  After doing this I was able to confirm that the node has around 4200 DCI's configured.

Regards,
Richard