Admin Center troubleshooting
You might encounter some common issues when you troubleshoot Centro de administración. Browse the list of issues to learn how to resolve them.
- Server Config tool issues
- Server information cannot be retrieved
- CWWKX7204E: Cannot connect to host host_name with the credentials provided
- CWWKX0279E: The host path information for the host_name host is not available
- CWWKX0261E: The host authentication information for the host host_name is not available
- CWWKX2003E: A write list for host host_name must be registered with the collective repository
- Error 500: The system cannot find the file specified
- Error 500: sh: java: Permission denied
- Explore tool issues
For fixes to other issues, see Resolución de problemas de colectivo de Liberty and Liberty: Restricciones conocidas del entorno de ejecución.
Server Config tool issues
- Server information cannot be retrieved
If no error code is given, look at the network debugger or enable trace logs.
- CWWKX7204E: Cannot connect to host host_name with the credentials provided.
- Message:
Cause:localhost,C:/wlp,member1 stop operation resulted in an Exception: ConnectException caught while performing stopCluster operation on member localhost,C:/wlp,member1: java.net.ConnectException: CWWKX7204E: Cannot connect to host localhost with the credentials provided.The RPC credentials are invalid or SSH is not working.
Solution:Ensure that the RPC user and password values for hostAuthInfo in the server configuration are correct. See Alteración temporal de información de host de servidor de Liberty.
- CWWKX0279E: The host path information for the host_name host is not available.
- Message:
Cause:CWWKX0279E: The host path information for the localhost host is not available. The /sys.was.collectives/local/hosts/localhost/sys.host.paths node does not exist in the repository.The collective server must be running to join a member to the collective.
Solution:Ensure that the collective controller server is started.
If the collective server is running, but the host path information is still not available, run the collective updateHost command with correct values for the --hostReadPath and --hostWritePath parameters. For information about updateHost, see CWWKX0261E or Registro de sistemas principales con un colectivo de Liberty.
- CWWKX0261E: The host authentication information for the host host_name is not available.
- Message:
Cause:CWWKX0261E: The host authentication information for the host localhost is not available.The collective updateHost command was not run for the host on which the member resides.
Solution:Run the collective updateHost command for the member host with either RPC or SSH information specified. Ensure that the command also has --hostReadPath and --hostWritePath parameters.
wlp/bin/collective updateHost memberHost --host=collectiveHost --port=controllerHTTPSPort --user=controllerAdmin --password=controllerAdminPassword --rpcUser=osUser --rpcUserPassword=osUserPassword --hostReadPath=serversPath --hostWritePath=serversPathSee Registro de sistemas principales con un colectivo de Liberty.
- CWWKX2003E: A write list for host host_name must be registered with the collective repository.
- Message:
Cause:CWWKX2003E: A write list for host localhost must be registered with the collective repository.The collective updateHost command did not run with the --hostWritePath parameter.
Solution:Run the collective updateHost command with the --hostWritePath parameter to specify the configuration files that the Server Config tool must access.
- Error 500: The system cannot find the file specified.
- Message:
Cause:Error 500: The system cannot find the file specified.The schema is not generated.
Solution:Ensure that the server schema is generated. Also ensure that the server is running or that the server contains the generated schema. You can manually generate the schema by using the wlp/bin/tools/ws-serverSchemagen.jar file. See Liberty: Generación de esquema de configuraciones Liberty desde la línea de mandatos.
- Error 500: sh: java: Permission denied
- Message:
Cause:Error 500: sh: java: Permission deniedThe Java path is not correct for the Java installation.
Solution:See information about setting the Java path in Edición de archivos de configuración del servidor en el Centro de administración and Establecimiento de la variable JAVA_HOME para miembros del colectivo de Liberty.
Explore tool issues
- Monitor view shows 0% CPU usage for JVMs that do not supply process CPU statistics.
- The CPU Usage chart of the Centro de administración Monitor view shows 0% CPU usage for JVMs that do not supply process CPU statistics. For information about the chart, see Métricas de supervisión en el Centro de administración.
Tema de referencia