Ansicht
Dokumentation

CPFBB05 - Cluster node &1 cannot be started. ( OS/400 )

BAL Application Log Documentation   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by IBM.


Message : CPFBB05
Cluster node &1 cannot be started.

Message Long Text :

Cause . . . . . : Cluster node &1 in cluster &2 cannot be started. The reason code is &3. The reason code is defined as follows:
1 -- Could not communicate with cluster node &1. The errno value is &4. Some of the possible errno values are:
0 - The TCP/IP interface address for cluster node &1, or the local node, may not be active.
3406 - No response from INETD server on cluster node &1 in allowed time.
3425 - The INETD server is not active on cluster node &1.
3429 - A route to cluster node &1 is not available.
3447 - No response from cluster node &1 in allowed time.
-1610612735 - Local port 5551 on cluster node &1 is still in-use.
-1610612731 - The TCP/IP interface address for cluster node &1 cannot be reached by one or more active cluster nodes.
2 -- Loopback interface address (127.0.0.1) for cluster node &1 is not active or does not exist.
Recovery . . . : Recovery actions for each reason code are:
1 -- If TCP/IP is not active on this system, start TCP/IP communications using the Start TCP/IP (STRTCP) command. If the INETD server is not active on cluster node &1, start it using the Start TCP/IP Server (STRTCPSVR) command. If the INETD server is active on cluster node &1, see messages in QTOGINTD job log to determine the problem. For the following error values:
0 - Start the TCP/IP interface address, if it is currently not active, using the Start TCP/IP Interface (STRTCPIFC) command.
3406 - Verify ports 5550 and 5551 are not in use by something other than Cluster Resource Services on cluster node &1. Verify no failover inquiry messages need to be responded to on any active cluster nodes. Verify a cluster resource group exit program is not waiting to run because a subsystem is not started, a job queue is held, or the maximum number of active jobs has been reached on all the cluster nodes.
3425 - Start the INETD server using the Start TCP/IP Server (STRTCPSVR) command.
3429 or 3447 - Start the TCP/IP interface address, if it is currently not active, using the Start TCP/IP Interface (STRTCPIFC) command on cluster node &1. If the interface on cluster node &1 is IPv4, ensure that all active cluster nodes have an available IPv4 route to that interface. If the interface on cluster node &1 is IPv6, ensure that all active cluster nodes have an active IPv6 route to that interface.
-1610612735 - If local port 5551 is still opened, end it using the End TCP/IP Connection (ENDTCPCNN) command.
-1610612731 - Verify that the TCP/IP interface address for cluster node &1 is reachable by all active cluster nodes via the Verify TCP/IP Connection (PING) and the Trace TCP/IP Route (TRACEROUTE) with UDP protocol command.
2 -- Start or add the loopback interface address for cluster node &1 using the Start TCP/IP Interface (STRTCPIFC) or Add TCP/IP Interface (ADDTCPIFC) command.

Message File : QCPFMSG
Library Message File : QSYS2924


PERFORM Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by IBM.

Length: 3250 Date: 20240419 Time: 132306     sap01-206 ( 2 ms )