Troubleshooting Websphere Linux

This section helps you troubleshoot the common problems that you might encounter when using Websphere Linux functionalities. This guide will give more troubleshooting processes on issues related to Websphere Linux server. The issues are device addition, communication to the server, CSR generation, fetch configuration, discovery along with push and rollback.

Issues in Device Addition using AppViewX GUI


Error Message	Possible Cause	Possible Solution
Device Name already exists.	A device with the same name already exists in inventory.	Check the Device name, it should be unique.
Details incorrect	Some of the mandatory fields might either be missing or might be invalid.	Add all the valid information in the mandatory section.
WSadmin User name and WSadmin Password should not be empty	WSadmin username or password might be empty.	Add the valid WSadmin username and password.
Kindly add at least one WSadmin detail before saving.	WSadmin details are not added.	Add at least a single WS admin details.

Issues in Communicating to Apache Linux


Error Message	Possible Cause	Possible Solution
Device name cannot be null or empty.	Device name is empty.	Provide device name as it is a mandatory field.
Invalid device name.	Device Name is not valid.	The Device name can only contain alphanumeric characters, '-' , '_' , '.' , '*' , '\|' , '!' and spaces.
Device IP/FQDN cannot be null or empty.	Device IP/FQDN is empty.	Provide device IP/FQDN as it is a mandatory field.
Invalid device IP/FQDN address.	IP/FQDN address is not valid.	Provide valid IP/FQDN address.
Access list for device cannot be empty.	Access list provided is empty	Provide a valid access list to communicate with the device.
Username cannot be null or empty.	Username is null or empty.	Provide a valid username to communicate with the device.
Password cannot be null or empty.	Password is null or empty.	Provide a valid password to communicate with the device.
Key cannot be null or empty.	Key is null or empty.	Provide a valid key to communicate with the device.
Password / key Mismatch or incorrect.	Unable to decrypt the password with the given key.	Provide a valid password that matches with the key.
Service account user not found.	Credentials to communicate with the device may be invalid.	Check and provide the proper credentials to communicate with the device.
Authentication failure using Service account.	Credentials to communicate with the device may be invalid.	Check and provide the proper credentials to communicate with the device.
Ip does not belongs to Websphere	Destination machine might not have the required configuration for a Websphere application server.	Please check if the machine has Websphere configurations available in the destination machine.

Issues in Fetch Config


Error Message	Possible Cause	Possible Solution
Password / key Mismatch or incorrect.	Unable to decrypt the password with the given key.	Provide a valid password that matches the key.
Service account user not found.	Credentials to communicate with the device may be invalid.	Check and provide proper credentials to communicate with the device.
Authentication failure using Service account.	Credentials to communicate with the device may be invalid.	Check and provide proper credentials to communicate with the device.
Permission denied to installation path.	AppViewX may not have the permission for the installation path.	Check if AppViewX has permission to access the installation path.
Invalid Credentials.	Invalid Credentials given for installation path.	Check if credentials have access to the installation path.
Permission denied	User does not have provision to access the installation path.	Check if AppViewX has permission to access the installation path.
Invalid installation path	Installation path does not exist.	Check if the installation path provided is a valid one.
Wsadmin objects unavailable	Wsadmin objects are unavailable	Check if the configurations related to WS are available in the destination machine.
security.xml file read operation failed	security.xml is not accessible in the given path.	Check if there is permission to access the file.
Config file parsing failed.	Configuration file might be corrupted/ empty.	Verify if the configuration file is correct.

Issues in Certificate Discovery


Error Message	Possible Cause	Possible Solution
Please provide information as required	Discovery name is not entered or its length is less than 2 characters. Interval between batches info. is missing when execution type is sequential.	Enter a valid name with a minimum of 2 characters. Provide a time interval between batches in minutes.
Please select a device	No device is selected in the “Discover By “section.	Select at least one device to discover certificates from.
Password / key Mismatch or incorrect.	Unable to decrypt the password with the given key.	Provide a valid password that matches the key.
Service account user not found.	Credentials to communicate with the device may be invalid.	Check and provide the proper credentials to communicate with the device.
Authentication failure using Service account.	Credentials to communicate with the device may be invalid.	Check and provide the proper credentials to communicate with the device.
Permission denied to installation path.	AppViewX may not have the necessary permission for the installation path.	Check if AppViewX has permission to access the installation path.
Invalid Credentials.	Invalid Credentials are given to installation path.	Check if credentials have access to the installation path.
Permission denied	User does not have provision to access the installation path.	Check if AppViewX has permission to access the installation path.
Invalid installation path	Installation path does not exist.	Check the installation path provided is a valid one.
Wsadmin objects unavailable	Wsadmin objects unavailable	Check if the configurations related to WS are available in the destination machine.
security.xml file read operation failed	security.xml is not accessible in the given path.	Check for valid permission to access the file.
Config file parsing failed.	Configuration file might be corrupted/ empty.	Verify if the configuration file is correct.

Issues in CSR generation


Error Message	Possible Cause	Possible Solution
Error while establishing SSH connection.	AppViewX is not able to establish a SSH connection using the given credentials.	Check and provide valid credentials to communicate with the device.
Error occurred while creating conf file to create csr.	AppViewX is not able to create a conf file in the export directory.	Check if AppViewX export directory has write permissions.
Invalid key type specified in the request	Given key type might not be supported in the target machine.	Provide valid key type.
CSR and Private key has been failed.	Open SSL configuration might be wrong in the target machine.	Check and correct open SSL configuration in the device.

Issues in Push and Rollback


Error Message	Possible Cause	Possible Solution
security.xml file read operation failed	AppViewX may not be able to read security.xml of the profile.	Check if AppViewX has permissions to read security.xml of the profile.
Config file parsing failed	Configuration file might be corrupted/ empty.	Verify if the configuration file is correct.
Insufficient information to fetch backup data available in the server.	Configuration files fetched from the server may not have sufficient information.	Check if the config file has all the information related to server configuration.
Unsupported bit length	Bit length is not supported by the server.	Provide a valid bit length that is supported by Websphere server.
Unsupported Key Algorithm	Key algorithm of the certificate is not supported by the server.	Provide a valid key algorithm that is supported by Websphere servers.
Creating local certificate file failed - <Detailed Message>	AppViewX is not able to create file in a temporary folder.	Check the detailed message to determine the remedy.
Server certificate is not available to push.	Server certificate location may be invalid.	Check if the trust store location is available.
Private Key doesnot exists for certificate	Private key may not be available for the certificate.	Check if the private key for the certificate is available.
Private key parsing failed for the certificate.	Private key may be a invalid one.	Check if the private key is valid.
Writing of converted certificate related files into file in AppViewX local directory is failed.	AppViewX may not have permission to write a file in the export directory.	Check if AppViewX has proper permissions for the export directory.
Certificate created date is earlier than server present time	The starting of certificate validity period is earlier than the servers present time.	The starting of certificate validity period should match with the server’s time. It should be greater than the server’s present time.
Unsupported Type	Certificate format is not supported by the server.	Check for the supported certificate formats.
Error found in wsadmin response	The WSadmin console may not be working on the server.	Kindly check WSadmin console is properly working or not
Unable to initiate request.	Pushing to device when certificate is unavailable, i.e, in a new state. Previous work order is in progress and not completed. AppConnector might not be in sync.	Push to device after certificate has been retrieved from CA. Initiate push after previous work order is finished. Synchronize the AppConnector and retry.
Unable to initiate request, template is in disabled state	Given workflow is not in enabled state	Enable the push/rollback workflow from the Workflow section.
User is not authorized	User does not have required permissions to push to the device.	Retry after getting the access for required action.
Private key content is unavailable.	Private key content is not available for the certificate.	Private key is mandatory for the certificate to be pushed.
Application connector(s) not found	Application connector info was not found.	Provide the correct connectorId if not pushing using AppViewX UI.
Request associated with the application connector is in progress	Previous work order is in progress and not completed.	Initiate this request after the previous work order is finished.
Push not triggered or succeeded or No existing data available for backup process.	Rollback couldn’t proceed because push was not successful.	Only successfully pushed certificates can be rolled back.
Certificate not found.	Pushing to device when certificate is unavailable, i.e, in a new state.	Push to device after certificate has been retrieved from CA.