<?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: discovery timeout problem in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/discovery-timeout-problem/m-p/5182953#M51331</link>
    <description>wrong forum</description>
    <pubDate>Mon, 22 Jun 2009 10:08:02 GMT</pubDate>
    <dc:creator>Linked</dc:creator>
    <dc:date>2009-06-22T10:08:02Z</dc:date>
    <item>
      <title>discovery timeout problem</title>
      <link>https://community.hpe.com/t5/server-management-systems/discovery-timeout-problem/m-p/5182952#M51330</link>
      <description>hello,&lt;BR /&gt;&lt;BR /&gt;i'm facing the exact same problem in multiple servers with different OSs (HP-UX, AIX..etc)&lt;BR /&gt;&lt;BR /&gt;service discovery always fails on opcservice check. &lt;BR /&gt;i tried to take a look at the xml file that fails and all what i can find inside are these lines:&lt;BR /&gt;&lt;BR /&gt;ERROR:   (depl-86) Unable to execute command 'perl' on node 'swas02'.&lt;BR /&gt;          (depl-176) Message returned from host 'swas02':&lt;BR /&gt;           (xpl-117) Timeout occurred while waiting for data.&lt;BR /&gt;&lt;BR /&gt;i tried to run the discovery from the node it self and they always finish with a correct xml file but after a very long time (15 or 20 mins). &lt;BR /&gt;&lt;BR /&gt;i tried increasing the timeout for discovery by using:&lt;BR /&gt;ovconfpar -host swas02 -change -ns bbc.cb -set RESPONSE_TIMEOUT 120000&lt;BR /&gt;ovconfpar -host swas02 -change -ns depl -set CMD_TIMEOUT 120000000&lt;BR /&gt;&lt;BR /&gt;but even with such high values the discovery still fails when done from OMU server. &lt;BR /&gt;&lt;BR /&gt;any suggestions would be appreciated</description>
      <pubDate>Mon, 22 Jun 2009 10:00:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/discovery-timeout-problem/m-p/5182952#M51330</guid>
      <dc:creator>Linked</dc:creator>
      <dc:date>2009-06-22T10:00:59Z</dc:date>
    </item>
    <item>
      <title>Re: discovery timeout problem</title>
      <link>https://community.hpe.com/t5/server-management-systems/discovery-timeout-problem/m-p/5182953#M51331</link>
      <description>wrong forum</description>
      <pubDate>Mon, 22 Jun 2009 10:08:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/discovery-timeout-problem/m-p/5182953#M51331</guid>
      <dc:creator>Linked</dc:creator>
      <dc:date>2009-06-22T10:08:02Z</dc:date>
    </item>
  </channel>
</rss>

