<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: memory leak in mxdomainmgr in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855019#M22425</link>
    <description>Wow!  Thanks for the great tip!  Looks like that may be it.  I'll post back once I verify the problem is fixed.</description>
    <pubDate>Fri, 01 Sep 2006 09:18:07 GMT</pubDate>
    <dc:creator>Agnem</dc:creator>
    <dc:date>2006-09-01T09:18:07Z</dc:date>
    <item>
      <title>memory leak in mxdomainmgr</title>
      <link>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855017#M22423</link>
      <description>I am running Insight Manager 5.0 with SP5 on a Windows 2003 Std R2 server with 2GB of ram.  I'm seeing a memory leak in the mxdomainmgr service that eventually consumes the machine, and I have to stop and restart the service to get it working again.  Unfortunately I can't pinpoint any particular events or updates that marked the begining of this problem, because I sloughed it off as a fluke the first few days that it happened.  In general, I get about 5 hours of run time before I have to restart it.  Any suggestions would be appreciated.  Thanks. - Mel</description>
      <pubDate>Fri, 01 Sep 2006 08:01:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855017#M22423</guid>
      <dc:creator>Agnem</dc:creator>
      <dc:date>2006-09-01T08:01:02Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak in mxdomainmgr</title>
      <link>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855018#M22424</link>
      <description>Hi Agnem,&lt;BR /&gt;&lt;BR /&gt;You may want to check this!!!!&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;objectID=c00701425&amp;amp;jumpid=reg_R1002_USEN" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;objectID=c00701425&amp;amp;jumpid=reg_R1002_USEN&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Also try this!!!!&lt;BR /&gt;&lt;BR /&gt;Remove the checkmark from "Send Authentication Trap" in the SNMP properties of the CMS. &lt;BR /&gt;&lt;BR /&gt;      The Send Auth Trap feature is for packet authentication verification. The packet does get through, but the authentication return doesnt come back, resulting in thousands of failed retries. Since this is the CMS, that isnt needed, so it's okay to uncheck it. Dont forget to restart SNMP afterward.&lt;BR /&gt;&lt;BR /&gt;Hope this works!!!!!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;rmn</description>
      <pubDate>Fri, 01 Sep 2006 08:19:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855018#M22424</guid>
      <dc:creator>ramesh_naik_</dc:creator>
      <dc:date>2006-09-01T08:19:43Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak in mxdomainmgr</title>
      <link>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855019#M22425</link>
      <description>Wow!  Thanks for the great tip!  Looks like that may be it.  I'll post back once I verify the problem is fixed.</description>
      <pubDate>Fri, 01 Sep 2006 09:18:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855019#M22425</guid>
      <dc:creator>Agnem</dc:creator>
      <dc:date>2006-09-01T09:18:07Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak in mxdomainmgr</title>
      <link>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855020#M22426</link>
      <description>OK.  I did what you suggested and it DID help, but it did not eliminate the problem.  What I am seeing now, is a much slower memory leak, but a leak just the same.  With the virtual machine config file changed, I went from about 4 hours of run time to maybe 6 or 8.  I've also tried stopping the virtual machine management service (it's stopped right now in fact) and that doesn't seem to make a difference, so I guess the change to the config file took the VM mgmnt service out of the picture.  Any other ideas? - Mel</description>
      <pubDate>Tue, 05 Sep 2006 09:02:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855020#M22426</guid>
      <dc:creator>Agnem</dc:creator>
      <dc:date>2006-09-05T09:02:54Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak in mxdomainmgr</title>
      <link>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855021#M22427</link>
      <description>Hello Agnem,&lt;BR /&gt;&lt;BR /&gt;Had the same issue on the CMS,had to re-install SIM. :(&lt;BR /&gt;Atm,there's no probable fix for the memory leak in mxdomainmgr.&lt;BR /&gt;&lt;BR /&gt;SRH</description>
      <pubDate>Tue, 05 Sep 2006 09:24:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855021#M22427</guid>
      <dc:creator>sandeep_raman</dc:creator>
      <dc:date>2006-09-05T09:24:40Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak in mxdomainmgr</title>
      <link>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855022#M22428</link>
      <description>Agnem,&lt;BR /&gt;&lt;BR /&gt;Just found information today.&lt;BR /&gt;Is it a SQL Database?&lt;BR /&gt;If yes,could you check if SQL DB was querying SIM(could be any instance).&lt;BR /&gt;&lt;BR /&gt;If the above is happening,uncheck "Send Authentication Traps" under SNMP properties both on CMS and Managed node.&lt;BR /&gt;&lt;BR /&gt;Hope it works.&lt;BR /&gt;&lt;BR /&gt;SRH</description>
      <pubDate>Wed, 06 Sep 2006 09:27:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855022#M22428</guid>
      <dc:creator>sandeep_raman</dc:creator>
      <dc:date>2006-09-06T09:27:48Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak in mxdomainmgr</title>
      <link>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855023#M22429</link>
      <description>The box is running MSDE SQL (the one that comes with SIM).  As for the SNMP trap setting, where does one go in the SIM management console to look for that?  I can't find it.  I know the bulk of the machines being monitored are not configured to send traps.  Thanks.</description>
      <pubDate>Fri, 08 Sep 2006 11:53:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855023#M22429</guid>
      <dc:creator>Agnem</dc:creator>
      <dc:date>2006-09-08T11:53:54Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak in mxdomainmgr</title>
      <link>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855024#M22430</link>
      <description>For both CMS and Managed Node.&lt;BR /&gt;&lt;BR /&gt;1.services.msc.&lt;BR /&gt;2.Open SNMP service properties&lt;BR /&gt;3.It should be here.&lt;BR /&gt;&lt;BR /&gt;SRH</description>
      <pubDate>Fri, 08 Sep 2006 13:39:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855024#M22430</guid>
      <dc:creator>sandeep_raman</dc:creator>
      <dc:date>2006-09-08T13:39:21Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak in mxdomainmgr</title>
      <link>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855025#M22431</link>
      <description>Ok.  I follow what your saying.  I thought you meant it was something in CMS.  I didn't have any traps set, but I did have some old community names that didn't belong in there anymore, so I took them out.</description>
      <pubDate>Fri, 08 Sep 2006 14:12:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855025#M22431</guid>
      <dc:creator>Agnem</dc:creator>
      <dc:date>2006-09-08T14:12:42Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak in mxdomainmgr</title>
      <link>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855026#M22432</link>
      <description>1.Was SQL DB querying SIM?&lt;BR /&gt;2.Did you uncheck "Send Authentication Traps"?&lt;BR /&gt;&lt;BR /&gt;SRH</description>
      <pubDate>Fri, 08 Sep 2006 14:18:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855026#M22432</guid>
      <dc:creator>sandeep_raman</dc:creator>
      <dc:date>2006-09-08T14:18:55Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak in mxdomainmgr</title>
      <link>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855027#M22433</link>
      <description>Not sure what you mean by is SQL querying SIM.  I thought it worked the other way around?  Yes, all sending of authentication traps is set to off.</description>
      <pubDate>Mon, 11 Sep 2006 07:01:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/memory-leak-in-mxdomainmgr/m-p/3855027#M22433</guid>
      <dc:creator>Agnem</dc:creator>
      <dc:date>2006-09-11T07:01:50Z</dc:date>
    </item>
  </channel>
</rss>

