ADMD

Express (Distributed operating systems), v8.0 > Reference > Messages

ADMD

ADMD0001E: The discovery MBean cannot be activated.

Explanation Every Network Deployment process requires one discovery MBean. The discovery MBean could not be activated.
Action Check that the remote process is running with the correct discovery port and, if necessary, start the remote process.

ADMD0002E: Only a multicast address is allowed to open the multicast socket

Explanation The multicast socket could not be opened because the IP address supplied was not a multicast address. Multicast group addresses are in the range of 224.0.0.0 through 239.255.255.255
Action Check the multicast IP address in the serverindex.xml file to verify that the IP address provided is in the valid range. Some multicast IP conflicts might exist in your network. Consult your network administrator.

ADMD0003E: The multicast socket cannot be opened to join multicast group: {0}

Explanation The multicast socket cannot be opened to join the specified multicast group because the router does not have multicasting capability.
Action Consult the network administrator to make sure that the router supports multicasting.

ADMD0004E: The TCP socket: {0} cannot be opened. Check if port is opened by remote process.

Explanation The specified Transmission Control Protocol (TCP) socket cannot be opened. The socket is not listening, the remote socket is not listening, or a network failure has occured. The TCP-based discovery needs to open a TCP socket before sending a discovery message. The socket might be the CELL_DISCOVERY_ADDRESS port for your dmgr or the NODE_DISCOVERY_ADDRESS port for a node agent. If this message is from your deployment manger, then verify that node agents are open for e-business. If the message is from a node agent, then verify that the dmgr is open for e-business.
Action Check that the remote process is running with the correct discovery port and, if necessary, start the remote process.

ADMD0005E: The User Datagram Protocol (UDP) socket: {0} cannot be opened.

Explanation The specified User Datagram Protocol (UDP) socket cannot be opened. The UDP-based discovery needs to open a UDP socket before sending out discovery message. The socket is not listening, the remote socket is not listening, or a network failure has occured.
Action Check that the remote process is running with the correct discovery port and, if necessary, start the remote process.

ADMD0006E: The destination endpoint is not specified

Explanation The destination endpoint is not specified. The discovery needs to know the destination endpoint before sending out the discovery message.
Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0007W: Unable to construct the discovery query message with exception: {0}

Explanation The discovery query message could not be constructed because of the specified exception.
Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0008W: Unable to construct the discovery response message with exception: {0}

Explanation The discovery response message could not be constructed because of the specified exception.
Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0009W: Unable to send out the discovery response message with exception: {0}

Explanation The discovery query message could not be send out because of the specified exception.
Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0010E: Incorrect discovery endpoint address

Explanation Incorrect discovery endpoint address was used.
Action Make sure the discovery endpoint address specified is valid. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0011E: Unsupported transport protocol

Explanation Unsupported transport protocol was used.
Action Make sure the transport protocol such as User Datagram Protocol (UDP), Transmission Control Protocol (TCP) or Multicast specified is valid. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0012E: The transport of type: {0} cannot be initialized.

Explanation The specified transport cannot be initialized. The discovery service is built on top of a specific transport, such as User Datagram Protocol (UDP), Transmission Control Protocol (TCP) or Multicasting.
Action Check the serverindex.xml file to make sure there is no port conflict with the discovery port in your local system. For multicasting discovery, make sure your LAN router supports the multicasting.

ADMD0013W: Invalid discovery message: No Source End Tag

Explanation The discovery message used inside the Java code is not valid.
Action Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0014W: The multicast server cannot be initialized at port: {0}

Explanation A failure occurred while initializing the transport that receives the multicast requests.
Action Verify that multicasting is supported in your local area network and that no port conflict exists.

ADMD0015W: The multicast group: {0} cannot be joined.

Explanation A certain type of discovery requires multicasting support. Either multicasting is not supported within the local area network, or the target multicast group rejects join requests.
Action Make sure that multicasting is supported in your local area network and that the right multicast group is specified for discovery.

ADMD0016W: Unable to close the server socket with exception: {0}

Explanation Unable to shutdown the multicast server.
Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0017W: Datagram socket failure in receiving package: {0}

Explanation Socket may have been timeout. Two possibilities to consider are multicast server may not working or nodeagent process is down.
Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0018E: The TCP transport cannot be initialized; exception: {0}

Explanation The discovery fails to initialize the Transmission Control Protocol (TCP) transport to receive the incoming discovery message.
Action Resolve any port conflicts that might exist. Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0019E: The UDP Transport cannot be initialized; exception: {0}

Explanation The discovery fails to initialize the User Datagram Protocol (UDP) transport to receive the incoming discovery message.
Action Resolve any port conflicts that might exist. Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0020W: Tcp socket failure in receiving package: {0}

Explanation An I/O error occurs when waiting for a connection.
Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0021W: Unable to handle discovery connection with exception: {0}

Explanation The connection failed to get initialized.
Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0022W: Host "{0}" cannot be resolved while sending discovery messages.

Explanation The host in question cannot be resolved from the domain name server (DNS). Several causes are possible: the host to resolve might not exist, or runs on a Dynamic Host Configuration Protocol (DHCP) machine, or has a short host name that cannot be resolved without appending an appropriate DNS suffix.
Action Check whether the host to resolve does exist in the network or runs on a DHCP machine. If it has a short host name, check the default DNS suffix in the local machine where discovery occurs.

ADMD0023I: The system discovered process (name: {0}, type: {1}, pid: {2})

Explanation This informational message indicates the system status. The pid indicates the Process ID for Distributed platforms while on z/OS it represents the Server token(stoken).
Action No user action is required.

ADMD0024W: Failed to send out the discovery message to the process: {0}

Explanation Failed to send out discovery message. Nodeagent process may be down.
Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

ADMD0025W: In process discovery, the 127.0.0.1 IP address is used to advertise an endpoint. This usage might cause problems in a network environment.

Explanation The 127.0.0.1 IP address, or local host, is known as the loopback IP address, which is only valid in a stand-alone environment. Hosts cannot be recognized by others through this IP address over the network.
Action Verify that the host address and the domain name server configurations are set correctly. For Linux configurations, configure the /etc/nsswitch.conf file to search the Domain Name Server (DNS) before the /etc/hosts file.

ADMD0026W: The version of the dmgr ({0}) is earlier than that of this node ({1}).

Explanation A dmgr version that is earlier than that of a node is an unsupported configuration.
Action Upgrade the dmgr to the same or later version as that of the node.

+
Search Tips | Advanced Search

Explanation	Every Network Deployment process requires one discovery MBean. The discovery MBean could not be activated.
Action	Check that the remote process is running with the correct discovery port and, if necessary, start the remote process.

Explanation	The multicast socket could not be opened because the IP address supplied was not a multicast address. Multicast group addresses are in the range of 224.0.0.0 through 239.255.255.255
Action	Check the multicast IP address in the serverindex.xml file to verify that the IP address provided is in the valid range. Some multicast IP conflicts might exist in your network. Consult your network administrator.

Explanation	The multicast socket cannot be opened to join the specified multicast group because the router does not have multicasting capability.
Action	Consult the network administrator to make sure that the router supports multicasting.

Explanation	The specified User Datagram Protocol (UDP) socket cannot be opened. The UDP-based discovery needs to open a UDP socket before sending out discovery message. The socket is not listening, the remote socket is not listening, or a network failure has occured.
Action	Check that the remote process is running with the correct discovery port and, if necessary, start the remote process.

Explanation	The destination endpoint is not specified. The discovery needs to know the destination endpoint before sending out the discovery message.
Action	Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

Explanation	The discovery query message could not be constructed because of the specified exception.
Action	Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

Explanation	The discovery response message could not be constructed because of the specified exception.
Action	Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

Explanation	Incorrect discovery endpoint address was used.
Action	Make sure the discovery endpoint address specified is valid. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

Explanation	Unsupported transport protocol was used.
Action	Make sure the transport protocol such as User Datagram Protocol (UDP), Transmission Control Protocol (TCP) or Multicast specified is valid. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

Explanation	The specified transport cannot be initialized. The discovery service is built on top of a specific transport, such as User Datagram Protocol (UDP), Transmission Control Protocol (TCP) or Multicasting.
Action	Check the serverindex.xml file to make sure there is no port conflict with the discovery port in your local system. For multicasting discovery, make sure your LAN router supports the multicasting.

Explanation	The discovery message used inside the Java code is not valid.
Action	Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

Explanation	A failure occurred while initializing the transport that receives the multicast requests.
Action	Verify that multicasting is supported in your local area network and that no port conflict exists.

Explanation	A certain type of discovery requires multicasting support. Either multicasting is not supported within the local area network, or the target multicast group rejects join requests.
Action	Make sure that multicasting is supported in your local area network and that the right multicast group is specified for discovery.

Explanation	Unable to shutdown the multicast server.
Action	Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

Explanation	Socket may have been timeout. Two possibilities to consider are multicast server may not working or nodeagent process is down.
Action	Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

Explanation	The discovery fails to initialize the Transmission Control Protocol (TCP) transport to receive the incoming discovery message.
Action	Resolve any port conflicts that might exist. Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

Explanation	The discovery fails to initialize the User Datagram Protocol (UDP) transport to receive the incoming discovery message.
Action	Resolve any port conflicts that might exist. Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

Explanation	An I/O error occurs when waiting for a connection.
Action	Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

Explanation	The connection failed to get initialized.
Action	Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

Explanation	The host in question cannot be resolved from the domain name server (DNS). Several causes are possible: the host to resolve might not exist, or runs on a Dynamic Host Configuration Protocol (DHCP) machine, or has a short host name that cannot be resolved without appending an appropriate DNS suffix.
Action	Check whether the host to resolve does exist in the network or runs on a DHCP machine. If it has a short host name, check the default DNS suffix in the local machine where discovery occurs.

Explanation	This informational message indicates the system status. The pid indicates the Process ID for Distributed platforms while on z/OS it represents the Server token(stoken).
Action	No user action is required.

Explanation	Failed to send out discovery message. Nodeagent process may be down.
Action	Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.

Explanation	The 127.0.0.1 IP address, or local host, is known as the loopback IP address, which is only valid in a stand-alone environment. Hosts cannot be recognized by others through this IP address over the network.
Action	Verify that the host address and the domain name server configurations are set correctly. For Linux configurations, configure the /etc/nsswitch.conf file to search the Domain Name Server (DNS) before the /etc/hosts file.

Explanation	A dmgr version that is earlier than that of a node is an unsupported configuration.
Action	Upgrade the dmgr to the same or later version as that of the node.