<?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 bug with mxnode and -w parameter in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/bug-with-mxnode-and-w-parameter/m-p/6884287#M60971</link>
    <description>&lt;P&gt;Running HP SIM 7.5 Update 1.&lt;/P&gt;&lt;P&gt;Adding a new node using "mxnode -a 1.2.3.4" completes very quickly (less than 5 seconds).&lt;/P&gt;&lt;P&gt;Adding a new node with the -w (wait) parameter (such as "mxnode -a 1.2.3.4 -w")&amp;nbsp;takes a few minutes as expected.&lt;/P&gt;&lt;P&gt;I find that once I have used the -w parameter, all future runs of "mxnode -a 1.2.3.4" behave as if -w is specified by&amp;nbsp;blocking until completed. &amp;nbsp;&lt;/P&gt;&lt;P&gt;I found that I have to restart the "HP Systems Insight Manager" service to get "mxnode -a 1.2.3.4" behavior back to normal.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 01 Aug 2016 22:16:27 GMT</pubDate>
    <dc:creator>upAndup448768</dc:creator>
    <dc:date>2016-08-01T22:16:27Z</dc:date>
    <item>
      <title>bug with mxnode and -w parameter</title>
      <link>https://community.hpe.com/t5/server-management-systems/bug-with-mxnode-and-w-parameter/m-p/6884287#M60971</link>
      <description>&lt;P&gt;Running HP SIM 7.5 Update 1.&lt;/P&gt;&lt;P&gt;Adding a new node using "mxnode -a 1.2.3.4" completes very quickly (less than 5 seconds).&lt;/P&gt;&lt;P&gt;Adding a new node with the -w (wait) parameter (such as "mxnode -a 1.2.3.4 -w")&amp;nbsp;takes a few minutes as expected.&lt;/P&gt;&lt;P&gt;I find that once I have used the -w parameter, all future runs of "mxnode -a 1.2.3.4" behave as if -w is specified by&amp;nbsp;blocking until completed. &amp;nbsp;&lt;/P&gt;&lt;P&gt;I found that I have to restart the "HP Systems Insight Manager" service to get "mxnode -a 1.2.3.4" behavior back to normal.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Aug 2016 22:16:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/bug-with-mxnode-and-w-parameter/m-p/6884287#M60971</guid>
      <dc:creator>upAndup448768</dc:creator>
      <dc:date>2016-08-01T22:16:27Z</dc:date>
    </item>
  </channel>
</rss>

