3. Troubleshooting

This section describes some issues and how to resolve them. If you encounter an issue that is not covered here, please report it (see Reporting issues).

3.1. Permission denied on forwarder config file

Example:

$ zhmc_os_forwarder -c foo.yaml
Error: Permission error reading forwarder config file foo.yaml: [Errno 13] Permission denied: 'foo.yaml'

You don’t have permission to read from the forwarder config file. Change the permissions with chmod, check man chmod if you are unfamiliar with it.

3.2. Forwarder config file not found

Example:

$ zhmc_os_forwarder -c foo.yaml
Error: Cannot find forwarder config file foo.yaml: [Errno 2] No such file or directory: 'foo.yaml'

Specify the right path name. Relative path names are relative to the current directory.

3.3. Forwarder config file has YAML syntax issues

Example:

$ zhmc_os_forwarder -c foo.yaml
Error: YAML error reading forwarder config file foo.yaml: <... error details ...>

There is a YAML syntax error in the forwarder config file. The error details provide the actual information on what is wrong.

You can also check the YAML specification.

3.4. Forwarder config file does not validate

Example:

$ zhmc_os_forwarder -c foo.yaml
Error: Validation of forwarder config file foo.yaml failed <... error details ...>

The YAML syntax of the forwarder config file is correct, but there is an issue with its content (i.e. schema). The error details provide the actual information on what is wrong.

You can also check Forwarder config file.

3.5. Timeout accessing HMC

Example:

$ zhmc_os_forwarder -c foo.yaml
Opening session with HMC 99.99.99.99 (user: johndoe@us.ibm.com, certificate validation: False)
zhmcclient._exceptions.ConnectTimeout: HTTPSConnectionPool(host='99.99.99.99', port=6794): Max retries exceeded
  with url: /api/sessions (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x10489fa00>,
  'Connection to 99.99.99.99 timed out. (connect timeout=10)')), reason: (<urllib3.connection.HTTPSConnection object
  at 0x10489fa00>, 'Connection to 99.99.99.99 timed out. (connect timeout=10)')

The HMC cannot be reached. Make sure the IP address is correct, and the VPN, firewall logon, or proxy logon you may need to access the HMC are in place.

3.6. Authentication error accessing HMC

Example:

$ zhmc_os_forwarder -c foo.yaml
Opening session with HMC 10.11.12.13 (user: johndoe@us.ibm.com, certificate validation: False)
zhmcclient._exceptions.ServerAuthError: HTTP authentication failed with 403,0: Login failed.
  Try the operation again.  If the problem persists, contact your security administrator.

The HMC could be reached but rejects the login at the WS API. Reasons may be wrong user/password, or Web Services API in the HMC not enabled. For the latter, see Setting up the HMC.

3.7. Warning: LPAR does not support OS messages

Example:

$ zhmc_os_forwarder
. . .
Warning: The OS in LPAR 'foo' on CPC 'CPCA' does not support OS messages - ignoring the LPAR

This indicates that the operating system in the LPAR does not support writing its console via the console API. The LPAR is being ignored, but the forwarder otherwise keeps on running.

3.8. zhmcclient troubleshooting

The zhmcclient Troubleshooting section also applies to the forwarder.