Driven Administrator Guide: Troubleshooting Drivenversion 2.2.6
- 1. Prerequisite
- 2. Planning a Driven Deployment
- 3. Installing and Configuring the Driven Server
- 4. Starting and Stopping the Driven Server
- 5. Uninstalling the Driven Server
5.1. Stopping the Server
- 6. Using the Driven Admin Features
6.1. Manage Users
6.3. Manage Teams
6.4. Manage System
- 7. The Driven Command Line Client
7.7. How-To Tips
- 8. Integrating with Third-Party Monitoring Applications
- 9. Upgrading Driven Server
- 10. Troubleshooting Driven
This Troubleshooting section is a list of tips for solving common issues that users encounter while deploying and running the Driven Server.
|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:
Ensure that you have at Java 7 installed on your system. Driven Server installation requires Java 7.
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.
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.
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.
|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.