Troubleshooting Apache Linux

This document helps you troubleshoot the common problems that you might encounter when using Apache Linux functionalities. This guide will give more troubleshooting processes on issues related to Apache Linux server. The issues are device addition, communication to the server, CSR generation, access to server, 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 with the Server

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 the device cannot be empty. Credentials not provided for SSH communication. Provide valid credentials for SSH communication.
Username cannot be null or empty. Username is not provided or is empty. Provide a valid username.
The Password cannot be null or empty. Password is not provided or is empty. Provide a valid password.
Key cannot be null or empty. Key is not provided or is empty. Provide a valid SSH key.
Ip is not reachable/invalid. Invalid credentials Kindly check the credentials provided.
IP is not reachable Kindly check if IP is pingable or not and make it up and running.
IP is blocked by the firewall Kindly check firewall settings.
Password / key Mismatch or incorrect. Unable to decrypt the password with the given key. Provide a valid password that matches the key.
Communication Failed Username or password may be invalid Check and provide the correct username and password.
java.io.IOException: Unable to authenticate with password, keyboard-interactive and publickey methods. Authentication Failure Provide correct credentials for authentication. Make sure SSH is enabled on the given server.
Linux rest agent communication failed. Rest agent running on the destination machine might be down. Please check the status of the rest agent in the destination machine.

Issues in CSR Generation

Error Message Possible Cause Possible Solution
Problem while generating csr on target server

General Failure -

SSH/SFTP communication failure

 Provide correct credentials and make sure device communication is successful.
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.
Problem while generating csr on the target server. Location might not have permission. Check the permission and provide it.
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 Access

Access Issues occur while communicating with servers while discovering or fetching configuration files. These errors can be collected either from logs, API responses, or the status field of that server.
Error Message Possible Cause Possible Solution
Sudo Access failure Linux Commands execution with sudo fails. Verify if the system has the correct sudo setup.
dzdo Access failure Linux Commands execution with dzdo fails. Verify if the system has the correct dzdo setup.
Permission denied for file/location. File might not be present in the avx environment. Check whether someone deleted the file from AppViewX environment.
user might not have permission to read in the given source location. Verify if read permission is given for the location.
Device communication might not be established when service has started. Verify the device connection and restart the service.

Issues in Fetch Config

Error Message Possible Cause Possible Solution
Parsing apache configuration failed. Configuration file might be corrupted/ empty. Verify if the configuration file is correct.
AppViewX is not able to read/parse the Config files from the server. Check if the server has proper config files related to Apache Server and AppViewX has proper read permissions.

Issues in Discovery

Error Message Possible Cause Possible Solution
Please provide information as required Discovery name is not entered or the length is less than 2 characters. Enter a valid name with a minimum of 2 characters.
Interval between batches info. is missing when execution type is sequential. 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.

Issues in Push and Rollback

Error Message Possible Cause Possible Solution
Unable to initiate request. Pushing to device when certificate is unavailable, i.e, in a new state. Push to device after certificate has been retrieved from CA.
Previous work order is in progress and not completed. Initiate push after previous work order is finished.
AppConnector might not be in sync. 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.