Server Management - Systems Insight Manager
1832446 Members
3477 Online
110042 Solutions
New Discussion

Re: mxdomainmgr.exe CPU Utilization @ 98%

 
Lee J milam
Occasional Advisor

Re: mxdomainmgr.exe CPU Utilization @ 98%

I found if I uninstall the old version and upgrade to SIM 4.2sp2, then go into the properties of the SNMP service and uncheck the "Send authenication Trap" on the Security page that it sems to behave much better.

Also make sure you have the latest Java.

And go into SIM and update the scheduled tasks to fit you needs, under Logs, you can further control this monster.

Re: mxdomainmgr.exe CPU Utilization @ 98%

Just encountered the same problem :(
On a Proliant DL580 with 2 CPU's and 2GB RAM, the whole Systems is crawling now because mxdomainmgr uses nearly all cpu resources and after 3 days runnin also around 400mb+

besides that, sim 5.0 is installed ...
Operating system: Windows 2003
Version: Systems Insight Manager 5.0 - Windows
Build version: C.05.00.00.00
Build date: 2005-08-04 16:56
Darran Brown
New Member

Re: mxdomainmgr.exe CPU Utilization @ 98%

Just wanted to add another notch to the number of people suffering with memory issues. I managed to sort cpu useage by reducing polling frequency and removing authentication trap as suggested above, thanks. (using SIM 5)
Keith Anderson_3
New Member

Re: mxdomainmgr.exe CPU Utilization @ 98%

Hi,

I had this problem on SIM 5 on w2k3

Solved it by disabling the "Hardware status Polling for non Servers Task" and further reduced performance overhead by decreasing the default intervals on other tasks.

That may be of use...

Regards
joe zink
New Member

Re: mxdomainmgr.exe CPU Utilization @ 98%

Had a very similar problem. This week we installed the current HP System Manager on our 15 servers. Our file server (about 1.3 terabytes) went to CPU usage of 100% and pretty much just sat there. - Not a good place to be for a primary fileserver.

After panicking, I shut down HP Insight Event Notifier, Foundation Agents, NIC Agent, and Server Agents. CPU went down to 2, 3, or 8%. Completely back to normal.
Very, very disappointing episode.
David Claypool
Honored Contributor

Re: mxdomainmgr.exe CPU Utilization @ 98%

Joe:

I don't think you installed the HP SIM application on 15 servers, did you? That's what this thread is about.
Eric Borgen
New Member

Re: mxdomainmgr.exe CPU Utilization @ 98%

I'd like to restate what someone else said earlier in this thread.

Installing the SNMP service and going into the services properties, under the security tab and deselecting the 'Send Authentication trap' checkbox and restarting the SNMP and SIM services solved the 'mxdomainmgr spawning dozens of mxinventory processes' problem for me.

-E
BR779329
Frequent Advisor

Re: mxdomainmgr.exe CPU Utilization @ 98%

Hello.

I am running HP SIM 5.0 on an DL380 G3 with:

- 2x Pentium Xeon at 2.4 GHz
- 4 GB Memory
- Windows Server 2003 SP1
- Aprox 170 devices monitored

With this config the mxdomainmgr.exe runs steady at 280 MB memory, and the overal CPU utilization is below 10 %.

I can't complain.
Ken Rackow_1
Occasional Contributor

Re: mxdomainmgr.exe CPU Utilization @ 98%

I have a similar issue. In my shop, although CPU utilization isn't an issue, mxdomainmgr.exe starts at around 380 MB, but within 24 hours is using 780 + MB, and the page file goes over 1 GB. At this point, HP SIM stops responding, and the server must be rebooted, starting the process again.

HP SIM 5 is monitoring about 500 servers from a Proliant DL380 G3 management server with:
Dual 2.4 GHz Xeon processors
2 GB RAM
Windows Server 2003 SP1
Separate, same-sized server running the SQL piece.

As recommended earlier in this thread, I have turned off Send authentication trap in the SNMP service.
Alfred_21
New Member

Re: mxdomainmgr.exe CPU Utilization @ 98%

As others have already stated, my situation has stabilized after making the suggested change, listed below.

Installing the SNMP service and going into the services properties, under the security tab and deselecting the 'Send Authentication trap' checkbox and restarting the SNMP and SIM services solved the 'mxdomainmgr spawning dozens of mxinventory processes' problem for me.

I am running HP SIM 5.0 on an ProLiant DL380 G2 with:

- Pentium III /1.266GHz
- 1.25 KB GB Memory
- Windows Server 2003 SP1
- Aprox 370 devices monitored

With this config and deselecting the 'Send Authentication trap' checkbox, mxdomainmgr.exe runs steady at 208 MB memory, and the overal CPU utilization is below 10 %.

It's been running this way for a couple of weeks now.
GIannotta
New Member

Re: mxdomainmgr.exe CPU Utilization @ 98%

To lessen the CPU usage during data collection on the CMS:

Limit the number of systems that are being collected at one time. For example, create separate data collection tasks for different groups of systems and schedule them to run at different times.

Configure the CMS to use a remote database on a system other than the CMS. A substantial portion of the CPU load is consumed by the database during data collection. This option is only supported with a Windows CMS.

Lower the DataCollectionThreadCount parameter in the globalsettings.props file. This parameter defaults to 3. Lowering it to 2 or 1 reduces the CPU demand of data collection tasks, but it increases the time required to complete the tasks.

This is from the HP SIM5 user manual.
Russ_50
Advisor

Re: mxdomainmgr.exe CPU Utilization @ 98%

I tried removing the checkbox from Send Authentication Trap, and the mxdomainmgr.exe is still using 80-99% of the CPU. Didnt work for me... Any ideas?
Russ_50
Advisor

Re: mxdomainmgr.exe CPU Utilization @ 98%

I may have spoke too soon. It looks like it is recovering a bit now...
yendorl
New Member

Re: mxdomainmgr.exe CPU Utilization @ 98%

Hello,

I am having an issue with msdomainmgr.exe. The fixes listed in this forum have not helped the situation. I'm running HP SIM on a Proliant DL380 G2, Windows 2003 Server, ver. 5.0 w/SP5, Build ver. C.05.00.02.00

Does anyone have any other ideas?

Much appreciated!
Rodney

Re: mxdomainmgr.exe CPU Utilization @ 98%

Well I am still having this issue with mxdomainmgr.exe. I just removed the insight product for now as I am new to HP hardware. I have a GL380 storage server/SAN. I have been having some performance issues which had lead to finding mxdomin using 192MB of ram.

Becasue I am a single admin for 30 servers (most are 2000 & NT) at multiple locations I just don't have time to troubleshoot this issue.

What am I loosing by removing insight?
Thanks
Anthony Kizka
Rick Gatti
Occasional Advisor

Re: mxdomainmgr.exe CPU Utilization @ 98%

Mostly server monitoring and automated alerts.
Tobias Åman
New Member

Re: mxdomainmgr.exe CPU Utilization @ 98%

This seems to be a SNMP bugg that not goes away. I have installed HP SIM 5.1 and i got this performance issue as well. CPU Throttle at 98% and PF file of 2GB and all RAM is used up in a minute. I'm running on a Vm Ware ESX with Opteron CPU and 2GB RAM.

today i turned off the "Send authentication trap" in the SNMP service security settings and voila the CPU throttle got down to 0-2%, i will try rebooting and tweak some more to get it in better shape.

Regards Tobias
Stefan Laemmer
Valued Contributor

Re: mxdomainmgr.exe CPU Utilization @ 98%

Ok, let's see if this works. I just unchecked the "Send Authentication Box" and restarted SNMP on my SIM..


I opened a thread about my issue here..
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1120213


Stefan Laemmer
Valued Contributor

Re: mxdomainmgr.exe CPU Utilization @ 98%

I unchecked the SNMP Send authorization box, no change.. MXDomainMgr is still at 25% CPU Util and consumes 900+Mb of memory. Guess, i'll give HP a call and see if they cant figure this out.
Mark_672
Advisor

Re: mxdomainmgr.exe CPU Utilization @ 98%

Me too. Here is my machine:

Proliant ML350 G5
Xeon Quad Core E5310
1GB RAM
Windows 2000 Server SP4

CPU Usage for some (not all) core spikes to 70 to 100% but over all CPU usage ranges from 25 to 29%. But it seems that mxdomainmgr.exe uses very high Mem Usage.
Kevin Bickerton
Occasional Advisor

Re: mxdomainmgr.exe CPU Utilization @ 98%

The CPU on cpqsrhmo.exe was very high. Wasn't able to get into VCA on any host (timeout). I stopped the ISEE_CMS_SWMAGENT and was able to get into the VCA and VCRM.
Kevin Bickerton
Occasional Advisor

Re: mxdomainmgr.exe CPU Utilization @ 98%

The CPU on cpqsrhmo.exe was very high. Wasn't able to get into VCA on any host (timeout). I stopped the ISEE_CMS_SWMAGENT. The CPU on cpqsrhmo.exe went down to 0 and was able to get into the VCA and VCRM.
Kevin Bickerton
Occasional Advisor

Re: mxdomainmgr.exe CPU Utilization @ 98%

The CPU on cpqsrhmo.exe was very high. Wasn't able to get into VCA on any host (timeout). I stopped the ISEE_CMS_SWMAGENT service. The CPU on cpqsrhmo.exe went down to 0 and was able to get into the VCA and VCRM.
Mark_672
Advisor

Re: mxdomainmgr.exe CPU Utilization @ 98%

I just restarted the server and now running smoothly. What makes that application to run on full process?
iCalvyn
New Member

Re: mxdomainmgr.exe CPU Utilization @ 98%

i have found the solution, just disable the HP insight manager service. see this for detail http://blog.icalvyn.com/mxdomainmgr/