After Ignite, swremove doesn't work

[Craig Johnson_1]

This is what I see. The system is on the network and swagentd is running, but for some reason swremove cannot RPC to swagentd. There is no info on the error in swagentd.log. How do I fix this?

ERROR: RPC exception: "Communications failure (dce / rpc)" 10/24/06
16:37:02 EDT
ERROR: A Remote Procedure Call to a daemon has failed. Could not
start a management session for "rhuxutlb:/". Make sure the
host is accessible from the network, and that its daemon,
swagentd, is running.
* Target connection failed for "rhuxutlb:/".
ERROR: More information may be found in the daemon logfile on this
target (default location is
rhuxutlb:/var/adm/sw/swagentd.log).
* Selection had errors.

[Steven E. Protter]

Shalom,

/sbin/init.d/swagentd -r

That restarts the swagentd daemon the most common cause of this problem.

SEP

[Ivan Krastev · Accepted solution]

If you Ignite from golden image check your hosts file.
If any errors correct them and reload swagentd.

ivan

[Craig Johnson_1]

I did both of those things - no luck.

???

[Craig Johnson_1]

There must be something (easy) I am missing.

Do I need to change a setting, delete a file, or reinstall the SD/SW toolset?

[Ivan Krastev]

Try to clear dce/rpc cache :


# /sbin/init.d/Rpcd stop
# rm /var/opt/dce/dced/*.db # /sbin/init.d/Rpcd start


regards,
ivan

[Igor Sovin]

Hi Craig!

See /etc/hosts for proper hostname and IP. Also check /etc/resolv.conf for name resolution

You may try nslookup hostname to see if your hostname resolves correctly.

[Craig Johnson_1]

I figured out my problem - there was a typo in the /etc/hosts file in the second octet of the IP, so it read 150.192... instead of 150.198... My eyes were only looking at the third and fourth octet.

Sorry for the confusion - thanks to everyone who replied and tried to help.

[Yang Qin_1]

compare the output of "ifconfig lan#" with your /etc/hosts file and modify the hosts file if it is neccessary. Then try again with swremove.

Yang