Troubleshooting MQServer Linux

This section will guide you to overcome the various issues faced by you during the use of MQServer Linux and its various functionalities.

Issues in Device communication

Error Message Possible Cause Possible Solution

Communication to <ip/fqdn> has failed.

Caused by: java.io.IOException: Unable to authenticate with password, keyboard-interactive and publickey methods

Possible Remediations:

1. Kindly check the credentials provided.

 Password of the device added could be wrong. Click on the device name on the Inventory Page. Update the correct password and click Save.

Communication to <ip/fqdn> has failed.

Caused by: java.net.SocketException: Network is unreachable (connect failed)

 IP/FQDN provided is not reachable Check manually by establishing an SSH session to the target device with the provided IP/FQDN.

Communication to <IP/FQDN> has failed.

Caused by: java.net.ConnectException: Connection refused (Connection refused)

Possible Remediations:

1. Kindly check the SSH Port configurations.

2. Kindly check the firewall settings

 Problem with port configuration Check if the configured port in the device addition page is correct.

Device communication ( 02/24/2021 05:07:25 PM ) Failure

Communication to 192.168.133.31 has failed

Device Version ( 02/24/2021 05:07:25 PM ) Failure

Device version fetch has failed

 MQ is not configured in the target device

Check if MQ server is configured in the target device

Check MQ toolkit is installed in the target device

Device communication ( 02/24/2021 06:12:50 PM ) Failure

Communication to 192.168.133.30 has failed.

Caused by: java.io.IOException: Key exchange was not finished, connection is closed.

 Problem with SSH key handshake Request to check the ciphers, key and HMacs configured in the target device and ensure AppViewX SSH-plugin supports the same

Issues in Certificate Discovery

Error Message Possible Cause Possible Solution
Received failed response from batch MQServer QManager is not up and running.

  1. Login to the target device

  2. Switch to user which has mqm group access

  3. start the QManager

Command:

strmqm <qname>
Received failed response from batch No valid KDB files available in the path configured to the QManager

Ensure the path configured in QManager has valid KDB files and KDB has certs.

Command to find path:

echo "DIS QMGR SSLKEYR" | runmqsc

Issues in CSR generation at Endpoint

Error Message Possible Cause Possible Solution
CSR generation got failed User has restricted access to the path configured for the “CSR FileName” and “Key File name” Kindly ensure the user configured for device addition has read/write access to the path configured.

Issues in Certificate Push

Error Message Possible Cause Possible Solution
Certificate Push failed User has restricted access to the path configured to push the certificate in the application connector Kindly ensure the user is configured while device addition has the read/write access to the path configured in application connector to certificate push.
PrivateKey in device push invalid “Private key in Device” is enabled in application connector, but key is not available in device. Ensure to enable “Private key in Device” attribute in application connector, if the certificate does not have the key and the certificate is generated using CSR gen option from Device.
Push Failed due to KDB push got failed. Target KDB file does not exist in the device Ensure the target KDB file, for which certificate push configured is available and has read/write access.