Problems With mxexec On A Managed Node (#2)

The mxexec command may fail on a managed node when the CMS cannot connect with the node. Several common causes of this situation are:

Symptom

The mxexec command fails on a managed node with the following message:

Unable to retrieve a connection from the RMIRegistry to system node_name.
Exception creating connection to: node_name; nested exception is:
     java.net.NoRouteToHostException: No route to host

where node_name is the hostname of the managed node.

If the mxexec command failed, but this is the correct error message, see “Problems With mxexec On A Managed Node (#1)”.

Verification

If these verification steps fail to establish communication with the managed node then there is a LAN communication problem.

If the verification steps are successful and the host is accessible from the CMS, verify that the mxagent daemon is running on the managed node by logging onto the managed node and executing:

ps -ef | grep mxagent

Fix