swlist/swagent hang

[Jennifer_20]

Hello,

I am looking for a possible quick fix to swlist not being able to contact the target host.

execute swlist and promt never returns.

ex:
# swlist
# Initializing...
# Contacting target "hostname"...

Can only recover by killing process.
Also top reports swlist at 99% CPU.

Not running glance/measureware.
Thanks.

/etc/hosts looks normal:

#
AA.BB.CC.XXX hostname
AA.BB.CC.XXX hostname.domainname.com
127.0.0.1 localhost loopback

Thanks.

[Sridhar Bhaskarla]

Hi Jennifer,

Two things..

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.

2. If not, kill swagend. Start it with swagentd -r.

Post your status.

-Sri

[A. Clay Stephenson]

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:

AA.BB.CC.XXX hostname.domainname.com hostname

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.

[Jennifer_20]

Yes. Ping works fine from hostmachine and from other networked boxes. thxs

[Anil C. Sedha]

Jennifer,

Do the following and revert if things don't work.

1) ping target_hostname

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)

3) If it doesn't, verify your dns is being resolved correctly.

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.

hosts dns files

4) You may kill the swagentd daemon and start it again by

/usr/sbin/swagentd -r

5) Verify that the target ping is of sustainable performance. Sometimes, target systems have problems in network connectivity too.

Regards,
Anil

[Jennifer_20]

/etc/nsswitch.conf also set to files. thxs

[Ashwani Kashyap]

Try putting your hostname as another alias to 127.0.0.1

[MANOJ SRIVASTAVA]

Hi Jenifer


Do a nslookup hostname

does it resolve correclty ?

If it uses the nsswitch and doesnt resolve correclty then you may try to rename the resolv.conf and let the system
resolve the name using /etc/hosts , this will solve if there are any name issues.


Manoj Srivastava