Driven Administrator Guide: Troubleshooting Driven

version 2.2.6

Driven Administrator Guide: Troubleshooting Driven

1. Prerequisite: 1.1. Upgrading

1.2. Check your team’s demands and expectations

1.3. Check your hardware and software
2. Planning a Driven Deployment: 2.1. Understanding the Deployment Architecture

2.2. External Dependencies

2.3. Selecting a Deployment Topology
3. Installing and Configuring the Driven Server: 3.1. Downloading the Driven Server

3.2. Installing the Driven Server

3.3. Configuring the Driven Server
4. Starting and Stopping the Driven Server: 4.1. Starting the Driven Server

4.2. Stopping the Driven Server
5. Uninstalling the Driven Server: 5.1. Stopping the Server

5.2. Removing All Files and Data
6. Using the Driven Admin Features: 6.1. Manage Users

6.2. Managing A Single User

6.3. Manage Teams

6.4. Manage System
7. The Driven Command Line Client: 7.1. Installing the Driven CLI Client

7.2. Backing Up and Restoring Driven Repositories

7.3. Backing Up Your Driven Data

7.4. Extracting Data with the scope Command

7.5. Examples of Command Usage

7.6. Common Command-Line Options

7.7. How-To Tips
8. Integrating with Third-Party Monitoring Applications: 8.1. Using Java Management Extensions (JMX) with Driven

8.2. Using Nagios Plugins with Driven
9. Upgrading Driven Server: 9.1. Before WAR Replacement

9.2. Upgrade the Driven Server
10. Troubleshooting Driven: 10.1. The Driven Server installation generates a Java incompatibility error

10.2. Can not install a valid license

10.3. Transmission of application metrics data to Driven stops but app status remains in RUNNING state

Troubleshooting Driven

This Troubleshooting section is a list of tips for solving common issues that users encounter while deploying and running the Driven Server.

If you still have problems after reading this page, feel free to post your queries to Driven Forums or email us at support@concurrentinc.com.

Tip	See the Driven Compatibility Matrix section of the Planning a Driven Deployment page for version compatibilities among Driven, Cascading, JDK, and other components that you need for the deployment.

If you are having issues with the Driven Agent or Driven Plugin, see the following sections:

The Driven Server installation generates a Java incompatibility error

Ensure that you have at Java 7 installed on your system. Driven Server installation requires Java 7.

Can not install a valid license

If you see a log message similar to the following, then make sure that the user running tomcat has a home directory

ERROR driven | java.io.IOException: java.util.prefs.BackingStoreException: Couldn’t get file lock.

Transmission of application metrics data to Driven stops but app status remains in RUNNING state

Sometimes an application fails or a functioning Driven deployment no longer receives telemetry data from a running application. If application updates to Driven cease when this is not your intention, it is important that the application status in Driven change from RUNNING to STOPPED. Unresponsive applications can distort the accuracy of the Status Timeline graph if the status remains in RUNNING state.

Step 1: Display all applications in RUNNING status

If your Status View in Driven is not filtered appropriately, set the search Status filter menu to Running.

Step 2: Open details about the unresponsive application

Click the Name link for the unresponsive application. The performance view will appear, showing the application’s flow and status state. Example of performance view window with warning in top right corner shows an example of the performance view.

Figure 1. Example of performance view window with warning in top right corner

The application’s condition is displayed in the top right corner of the screen shot in Example of performance view window with warning in top right corner. The warning here indicates that the application is unresponsive, and the Driven Server is not receiving updates from the Driven Plugin.

Step 3: Stop the unresponsive application

After you confirm that this is the specific application you want to stop, click Mark as stopped.

Figure 2. The Mark as stopped button and application status

Note

The application has a stop timestamp at the time when the Driven Server last received an update timestamp from the Driven Plugin that monitors application processes in the Hadoop infrastructure. For example, if you stopped an application at the current (system) time, Driven will mark the stop time at the last updated timestamp that might have occurred three months previously.