Troubleshooting Weblogic Linux

This section helps you troubleshoot the common problems that you might encounter when using Weblogic Linux functionalities. This guide will give more troubleshooting processes on issues related to Weblogic 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 UI


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 be missing or might be invalid.	Add all the valid information in the mandatory section.

Issues in Communicating to Weblogic 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.
Failed to connect to the server.	Credentials to communicate with the device may be invalid.	Check and provide the proper credentials to communicate with the device.
No weblogic process is running	Weblogic processes running on the destination machine might be down.	Kindly check the status of the Weblogic process running 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.
Domain-registry.xml is not accessible in the given path.	Given path may be invalid or AppViewX does not have permission to access the file in the path.	Please enter a valid path or Check permissions to access the file.
Config file parsing failed.	Configuration file might be corrupted/ empty. AppViewX is not able to read/parse the Config files from the server.	Verify if the configuration file is correct. Check if the server has proper config files related to the Weblogic server and AppViewX has proper read permissions.

Issues in Certificate Discovery


Error Message	Possible Cause	Possible Solution
Please provide information as required	Discovery name is not entered or 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.
Exception while fetching key and location details from request.	Certificate location details provided during the server addition might be wrong.	Check and provide the valid certificate location during server addition.

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.	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 by open SSL 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
Error while establishing SSH connection.	AppViewX is not able to establish a SSH connection using the given credentials.	Provide valid credentials to communicate with the device.
Unable to parse configuration to fetch currently associated data.	AppViewX may not be able to fetch and parse the content of the certificate which is already associated.	Check if AppViewX has permissions for fetching the existing certificate content.
No server certificate is found	AppViewX may not be able to fetch and parse the content of the certificate which is already associated.	Check if AppViewX has permissions for fetching the existing certificate content.
Exception while downloading trust store / Exception while parsing certificate	AppViewX is not able to download the trust store from the server.	Check if AppViewX has permission to download the trust store from the device.
Certificate and/or key missing	Certificate provided in the push request might be invalid.	Check if the certificate that is being pushed is valid.
Unsupported Key Algorithm	Key algorithm of the certificate is not supported by the server.	Provide a valid key algorithm that is supported by Weblogic servers.
Push cannot be performed automatically for the Keystore type 'DemoIdentityAndDemoTrust'. Kindly customize the keystore locations in the connector.	Customize push location not provided during push operation.	Provide a location to push the certificate inside the server.
Parsing a certificate is failed	Certificate content might be invalid.	Check the certificate content.
Exception while writing file to avx local.	AppViewX may not have access to the local/export directory.	Check if AppViewX has permission for the local/export directory.
Certificate push is failed.	Invalid location provided. User is not having permission to push file to the location.	Check the location provided is valid. Check if the user has permission to access the location.
Unable to perform Bind for the server.	Server may not be running in the given address and port.	Check if the server is running in the given port and listen address
Unable to open edit session for the server.	AppViewX is not able to communicate with the server.	Check if the server is up and running and the server credentials are valid.
Unable to perform edit for the server.	AppViewX is not able to communicate with the server.	Check if the server is up and running and the server credentials are valid.
Unable to save the current changes made to the server.	AppViewX is not able to communicate with the server.	Check if the server is up and running and the server credentials are valid.
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.