topic Re: mxdomainmgr.exe gone wild in Server Management - Systems Insight Manager

mxdomainmgr.exe gone wild

Terrence — Fri, 23 Jan 2004 15:39:20 GMT

I just installed Systems Insight Manager on XP Pro and now the mxdomainmgr.exe process has gone wild and is spiking cpu utilization. I haven't done anything other than try to install this thing. Everything looked fine during the install except that the version control install failed. Haven't done any configuration or anything beyond the install. Even after rebooting, the cpu pegs and the machine is virtually locked it's so slow. Any ideas as to the cause/solution?

Re: mxdomainmgr.exe gone wild

Rob Buxton — Sun, 25 Jan 2004 14:53:41 GMT

When you install HPSIM it then goes out and tries to discover devices on the local subnet and then identify them.

Yes, this process is a bit heavy on the system.

I've not seen it slow a machine to this point though, check that the machine specs meet the minimum requirements.

Re: mxdomainmgr.exe gone wild

Darrin Rawls — Mon, 20 Dec 2004 17:29:05 GMT

Once the system reboots it tries to do Status Polling, Data Collection, etc. and Data Collection/Discovery are the ones that use all available resources to get the job done. Once discovery/data collection have completed, the system should settle down. If it doesn't post it here (could be 15-45 minutes depending on how large your discovery IP ranges are - by default it is only one subnet).

Hope this helps.

Re: mxdomainmgr.exe gone wild

Timothy Ford — Wed, 05 Jan 2005 11:53:50 GMT

I have just installed SIM 4.2 on a Windows 2003 Server and have the same issue with the processor pegged because of the mxdomainmgr.exe process.

Is there a related fix or workaround to this problem?

-Tim

Re: mxdomainmgr.exe gone wild

Darrin Rawls — Wed, 05 Jan 2005 12:29:55 GMT

How long has been running in that state? It will peg the processor while it is doing discovery/identification.

Re: mxdomainmgr.exe gone wild

Timothy Ford — Wed, 05 Jan 2005 12:58:25 GMT

It's been running for an 1 hrs and 40 minutes.

Re: mxdomainmgr.exe gone wild

Timothy Ford — Wed, 05 Jan 2005 17:08:19 GMT

I think I have found the problem. The SNMP stack was corrupt. The SNMP service appeared to be installed, (listed as an option selected in windows components of the control panel) but it didn't appear as an installed service in the services applet. I have a new install of 4.2 running without this process issue.

Re: mxdomainmgr.exe gone wild

Pedro Azevedo — Sat, 15 Jan 2005 13:15:19 GMT

Make shure you disable SNMP authentification trap on all the agents (you can doo it all at once with insight agent settings replication tool) and also... see if there aren't any servers sending SNMP traps to your server without beeing registered (inserted) in the management program
Hope that helped!

Re: mxdomainmgr.exe gone wild

larry_59 — Fri, 18 Mar 2005 17:49:45 GMT

I had the same problem. Ihad to install snmp and then cycle the snmp trap service. now it looks like it is working properly.