topic Re: HP 7.3 : mxdomainmgr high CPU utilization in Server Management - Systems Insight Manager

HP 7.3 : mxdomainmgr high CPU utilization

sloue — Mon, 23 Jun 2014 15:34:36 GMT

Hi,

We met a problem since we have upgraded HP SIM from 6 to 7 (2 years ago). Windows server was a new new, running Windows Server 2008 R2.

Today, we are running HP SIM 7.3, April patch.

We managed around 300 systems and 12 sites.

Sometimes, on CMS server, we find mxdomainmgr.exe process is consuming 100% of CPU.

HP SIM works normally but to correct this problem, we always need to retart HP SIM services.

We found that we generally met this problem when we lost a site and recieve multiples traps (unreachable systems).

We checked mxdomainmgr logfile (mxdomainmgr.0.log), nothing at all.

On CMS Server, we tried to uncheck "Send authentication trap" in SMNP service. We tried to increase memory size from 4 Gb to 8 Gb.

It didn't change anything.

If any one has resolution on this issue, please help me...

Thanks in advance.

Re: HP 7.3 : mxdomainmgr high CPU utilization

Andrew_Haak — Mon, 23 Jun 2014 20:20:22 GMT

Hello there,

Do you get a lot of authentication traps then? You should find out where the errors come from, if you got a lot of these messages could you check how many informational events you have ? These events can eat-up you system. Disabeling these events should be done at the source servers not your CMS.

Kind regards,

Andrew

Re: HP 7.3 : mxdomainmgr high CPU utilization

jim goodman — Tue, 24 Jun 2014 18:20:55 GMT

You didn't specify whether you are dealing with virtual or physical server....

SIM/SQL will eat up a lot of processor, mxdomainmgr will increase cpu for longer periods of time untilmately crashing the service if you are using Sql Express and have a large number (300 is not a large number) of discovered systems and/or undeleted events. Full SQL has the same problem but typically in a much higher scale. It isn't uncommon for mxdomainmgr to chew up CPU and Memory especially if SQL is local, but it shouldn't be hanging your CMS.