This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

WMI causing Orion Web Console to crash

When a server goes down that is being polled using WMI, SW tries to poll that node on every port until it reaches port exhaustion and causes the orion web console to crash. This never happened on previous versions, but every since upgrading to 2020.2.1 I have had this issue any time a server goes down. Is there a way to make it so that SW stops trying to poll a node using WMI when it is simply unreachable? or is it just better to deploy the agent on to Windows servers rather than using WMI for this reason?

This is the DCOM error that shows up in the event logs when SW is trying to poll a Windows Server that is down:

MasonLan_0-1610637607791.png

  • Well, I wouldn't guarantee that moving WMI polled servers from the server that hosts the web would solve it completely. You can probably stop the web console from crashing, but you may still get browser lag if there are servers polled from the web server that are down.

    My experience is that even a few WMI nodes being down simultaneously, and having multiple object being polled puts a load on the web server. I think web performance got worse with the 2020 releases, but I haven't had a chance to track anything specific down.

    So I think you may be better off opening a case, and getting to the bottom of it all.

  • Perfect. I will move WMI nodes to my APE and change polling to slightly longer intervals. I have ticket open and am waiting to hear back from SW as they are understandably busy right now. Thanks for your suggestions.

  • Here's my confusion regarding this issue, I've noticed this on a node that "...has been unmanaged. Polling and statistics collection are suspended." but still show these same DCOM errors to the point of exhaustion.