Troubleshooting Tomcat Linux

This document helps you troubleshoot the common problems that you might encounter when using Tomcat Linux functionalities. This guide will give more troubleshooting processes on issues related to the Tomcat Linux server. The issues are device addition, communication to the server, CSR generation, access to the server, 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.
Device name accepts '-' , '_' , '.' , '*' , '|' , '!' and space only, with min 2 and max 64 characters. Server name is not valid. Provide a server name with min 2 and max 64 characters with only the allowed characters.

Issues in Communicating to the server

Error Message Possible Cause Possible Solution
Failed to make the ssh connection with the given IP. Given IP may not be connected to the network. Validate whether username and password given during device addition are valid.
Username/Password provided may be incorrect. Ensure given IP is connected to the network.
SFTP port is not open for SSH communication. Open given port for the SSH communication.
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.
Password / key Mismatch or incorrect. Unable to decrypt the password with the given key. Provide a valid password that matches the key.
Device does not belong to Tomcat Server. Device does not have any running tomcat instances. Start any tomcat server in the device.
Failed to make ssh connection. Target device may not be connected to the network. Validate whether username and password given during device addition are valid.
Username/Password provided may be incorrect. Ensure the target device is connected to the network.
The User may not have permission to execute the command. Provide permission for the user to execute \"ps -ef\" command.
Linux rest agent communication failed Rest agent installed in the device might not be running. Install AppViewX Rest agent in device.
The Client certificate installed in AppViewX might not be valid. Install valid client certificate in AppViewX.
Rest agent port might not be open for communication. Ensure port is open for communication.
Error while decrypting password. Password invalid for decryption key. Check if the password matches with the decryption key.

Issues in CSR Generation

Error Message Possible Cause Possible Solution
CSR Generation Failed. Given CSR Location is not available in device. Provide a valid path to store CSR and key.
User does not have read/write permission for the location. Ensure the user has read/write permission to the given location.
“Openssl” package is not installed Install “Openssl” package in the device
The User does not have permission to execute “Openssl” commands. Provide permission for user to execute “Openssl” commands

Issues in Access

Access Issues might occur when 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.
File Download Failed. User or User group does not have read/write permission for server.xml in device. Provide read/write permission for user in device

Issues in Fetch Config

Error Message Possible Cause Possible Solution
XML Parsing Failure FileName provided might not be a valid XML file. Ensure the provided filename is a valid XML file.
File Download Failed. server.xml is not found in the specified directory. Ensure server.xml is present in the conf directory.

Issues in Certificate Discovery

Error Message Possible Cause Possible Solution
File Not Found server.xml is not present in the specified directory. Ensure server.xml is present in the conf directory.
SSL certificate or key file parsed from configuration file is not present in the specified directory. Ensure parsed certificate or key file is present in the directory specified in server.xml
JKS Parsing Failure Password for Keystore file may not be present in server.xml Password given in server.xml might be incorrect.

Issues in Push and Rollback

Error Message Possible Cause Possible Solution
Push failed. Creating local certificate files failed while Backup. Provide required access to AppViewX to create local files
Certificate Push Failure Invalid certificate, key, or trust location is given. Provide the valid certificate, key, or trust location while adding an application connector.
Bind Failed as the SSL is disabled for the port SSL is disabled for the given port on the server. Kindly enable SSL for the port on the server.
KeyStore creation failed Unable to create the Keystore locally. Provide required access to AppViewX to create local files