<?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: swlist/swagent hang in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2810001#M84050</link>
    <description>/etc/nsswitch.conf also set to files. thxs</description>
    <pubDate>Thu, 19 Sep 2002 21:30:22 GMT</pubDate>
    <dc:creator>Jennifer_20</dc:creator>
    <dc:date>2002-09-19T21:30:22Z</dc:date>
    <item>
      <title>swlist/swagent hang</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2809996#M84045</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I am looking for a possible quick fix to swlist not being able to contact the target host.&lt;BR /&gt;&lt;BR /&gt;execute swlist and promt never returns. &lt;BR /&gt;&lt;BR /&gt;ex:&lt;BR /&gt;# swlist&lt;BR /&gt;# Initializing...&lt;BR /&gt;# Contacting target "hostname"...&lt;BR /&gt;&lt;BR /&gt;Can only recover by killing process.&lt;BR /&gt;Also top reports swlist at 99% CPU.&lt;BR /&gt;&lt;BR /&gt;Not running glance/measureware.&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;/etc/hosts looks normal:&lt;BR /&gt;&lt;BR /&gt;#&lt;BR /&gt;AA.BB.CC.XXX     hostname&lt;BR /&gt;AA.BB.CC.XXX     hostname.domainname.com&lt;BR /&gt;127.0.0.1       localhost       loopback&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 19 Sep 2002 20:58:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2809996#M84045</guid>
      <dc:creator>Jennifer_20</dc:creator>
      <dc:date>2002-09-19T20:58:49Z</dc:date>
    </item>
    <item>
      <title>Re: swlist/swagent hang</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2809997#M84046</link>
      <description>Hi Jennifer,&lt;BR /&gt;&lt;BR /&gt;Two things..&lt;BR /&gt;&lt;BR /&gt;1. Ping to "hostname" and see if it works. swagent won't work if hostname is wrong. If so, you will need to fix it. &lt;BR /&gt;&lt;BR /&gt;2. If not, kill swagend. Start it with swagentd -r.&lt;BR /&gt;&lt;BR /&gt;Post your status.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Thu, 19 Sep 2002 21:01:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2809997#M84046</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2002-09-19T21:01:26Z</dc:date>
    </item>
    <item>
      <title>Re: swlist/swagent hang</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2809998#M84047</link>
      <description>I'm not sure that you meant this but if your AA.BB.CC.XXX's above are identical then you should make an alias entry instead like this:&lt;BR /&gt; &lt;BR /&gt;AA.BB.CC.XXX hostname.domainname.com hostname&lt;BR /&gt;&lt;BR /&gt;You should also test hostname resolution by pinging by hostname. Check that your /etc/nsswitch.conf is set up correctly as well. You should probably set it to look at FILES first.&lt;BR /&gt;</description>
      <pubDate>Thu, 19 Sep 2002 21:08:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2809998#M84047</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2002-09-19T21:08:57Z</dc:date>
    </item>
    <item>
      <title>Re: swlist/swagent hang</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2809999#M84048</link>
      <description>Yes. Ping works fine from hostmachine and from other networked boxes. thxs&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 19 Sep 2002 21:15:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2809999#M84048</guid>
      <dc:creator>Jennifer_20</dc:creator>
      <dc:date>2002-09-19T21:15:14Z</dc:date>
    </item>
    <item>
      <title>Re: swlist/swagent hang</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2810000#M84049</link>
      <description>Jennifer,&lt;BR /&gt;&lt;BR /&gt;Do the following and revert if things don't work.&lt;BR /&gt;&lt;BR /&gt;1) ping target_hostname&lt;BR /&gt;&lt;BR /&gt;2) nslookup target_hostname (You should get the correct ip address for it or you may ping the ip address and see if it resolves the correct ip address)&lt;BR /&gt;&lt;BR /&gt;3) If it doesn't, verify your dns is being resolved correctly.&lt;BR /&gt;&lt;BR /&gt;Also add an entry in your /etc/hosts file for that system. Verify your /etc/nsswitch.conf file to see how the hosts are resolved.&lt;BR /&gt;&lt;BR /&gt;hosts   dns  files&lt;BR /&gt;&lt;BR /&gt;4) You may kill the swagentd daemon and start it again by&lt;BR /&gt;&lt;BR /&gt;/usr/sbin/swagentd -r&lt;BR /&gt;&lt;BR /&gt;5) Verify that the target ping is of sustainable performance. Sometimes, target systems have problems in network connectivity too.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Anil&lt;BR /&gt;</description>
      <pubDate>Thu, 19 Sep 2002 21:17:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2810000#M84049</guid>
      <dc:creator>Anil C. Sedha</dc:creator>
      <dc:date>2002-09-19T21:17:46Z</dc:date>
    </item>
    <item>
      <title>Re: swlist/swagent hang</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2810001#M84050</link>
      <description>/etc/nsswitch.conf also set to files. thxs</description>
      <pubDate>Thu, 19 Sep 2002 21:30:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2810001#M84050</guid>
      <dc:creator>Jennifer_20</dc:creator>
      <dc:date>2002-09-19T21:30:22Z</dc:date>
    </item>
    <item>
      <title>Re: swlist/swagent hang</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2810002#M84051</link>
      <description>Try putting your hostname as another alias to 127.0.0.1</description>
      <pubDate>Thu, 19 Sep 2002 23:43:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2810002#M84051</guid>
      <dc:creator>Ashwani Kashyap</dc:creator>
      <dc:date>2002-09-19T23:43:16Z</dc:date>
    </item>
    <item>
      <title>Re: swlist/swagent hang</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2810003#M84052</link>
      <description>Hi Jenifer&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Do a nslookup hostname &lt;BR /&gt;&lt;BR /&gt;does it resolve correclty ?&lt;BR /&gt;&lt;BR /&gt;If it uses the nsswitch and doesnt resolve correclty then you may try to rename the resolv.conf and let the system&lt;BR /&gt;resolve the name using /etc/hosts , this will solve if there are any name issues.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Manoj Srivastava</description>
      <pubDate>Fri, 20 Sep 2002 00:58:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swlist-swagent-hang/m-p/2810003#M84052</guid>
      <dc:creator>MANOJ SRIVASTAVA</dc:creator>
      <dc:date>2002-09-20T00:58:50Z</dc:date>
    </item>
  </channel>
</rss>

