--- title: "Basic Troubleshooting" slug: "basic-troubleshooting" tags: ["troubleshooting", "administration", "server status", "error log", "brainspace log", "build log"] updated: 2025-04-25T06:48:40Z published: 2025-04-25T06:48:40Z canonical: "docs.revealdata.com/basic-troubleshooting" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.revealdata.com/llms.txt > Use this file to discover all available pages before exploring further. # Basic Troubleshooting Basic troubleshooting includes checking the status of all three Brainspace servers, reviewing logs, monitoring the build process, and reviewing the results of the build to identify and to resolve common problems when using Brainspace. > [!NOTE] > **Note** > > To view a list of error codes, see [***Error Resolution Troubleshooting Table***](/brainspace/docs/error-resolution-troubleshooting-table). ## Verify Server Status The first step in basic troubleshooting is to verify that each Brainspace server is in Active status, that each server has sufficient disk space and memory, and that the Brainspace license has not expired or exceeded capacity. To verify server status: 1. In the user drop-down menu, click **Administration**: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-nmst8p0p.jpg) The Datasets screen will open. 2. In the Datasets screen, Click the **Services** button: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-hkog33l9.jpg)The Services screen will open. 3. On the Services screen, verify that the three Brainspace servers are active: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-ypie9mb2.jpg) 4. If a server is not in Active status, check server and data volume health (both /data and /localdata), verify that required services are running (postgres, Tomcat on the Application server, On-Demand Analytics server, and others), and verify that the Analytics and On-Demand servers are accessible from the Application server (port 1604). 5. Click the **Server Information** icon, and then verify that a green check-mark displays next to Disk, License, and JVM Memory: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-k0u63ht9.jpg) ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-fxzebdqk.jpg) ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-4vxt59ni.jpg) After verifying server status, verify connector configuration. ## Verify Connector Configuration After verifying server status, verify connector configuration and ability to access the data source. To verify connector configuration: 1. In the user drop-down menu, click **Administration**: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-ownf9rne.jpg) 2. The Datasets screen will open. 3. Click the **Connectors** button: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-cxmb0wpe.jpg) 4. The Connectors screen will open. 5. In the Connectors screen, click the **Update Connector** icon in the first dataset in the list: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-w1dq6vf0.jpg) 6. The Connector Name dialog will open. 7. Verify that the external data source is online and available (correct service running, correct port, network access, correct account permissions, etc.). 8. Click the **Test Connector** button. If the connector is configured correctly, a validation message will display: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-qxnry7lp.jpg) 9. If the connector is not configured correctly, a failure message will display: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/image(82).png) > [!NOTE] > **Note** > > The following links provide information about specific connector requirements: > > 1. [Connectors](/brainspace/docs/brainspace-supported-connectors) > 2. [DAT Connector](/brainspace/docs/create-a-dataset-with-a-dat-connector) > 3. [Native File Connector](/brainspace/docs/create-a-dataset-with-a-native-connector) > 4. [Nuix Connector](/brainspace/docs/create-a-dataset-with-a-nuix-connector) > 5. [Relativity® Connector](/brainspace/docs/create-a-dataset-with-a-relativity-connector) > 6. [Supported Connector Matrix](/brainspace/docs/brainspace-supported-connectors) > 7. [XML Connector](/brainspace/docs/create-an-xml-transformer) After verifying connector configuration for all datasets, review the Error Log. ### Review the Error Log After verifying connector configuration, review the Error Log for any recent errors related to problems you are experiencing. To review the Error Log: 1. In the user drop-down menu, click **Administration**: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-h7t7fdfa.jpg) The Datasets screen will open. 2. Click the **Errors** button: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-5uiwvjhq.jpg) The Error Log screen will open. 3. Click an error in the list, and then review the error details: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/image(84).png) > [!NOTE] > **Note** > > You can also type a search word in the **Quick Search** text box, and then select a date range using the **Select a start date** and **Select end date** drop-down calendars: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-7z8g6qp1.jpg) 4. To include archived errors in the search results, click the **Include archived errors** check box: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-qh29gf4q.jpg) 5. The Error Log will refresh and display applicable errors. After reviewing the Error Log, download and review the Brainspace Log. ## Download and Review the Brainspace Log After reviewing the Error Log, download and review the Brainspace Log. To download and review the Brainspace Log: 1. In the user drop-down menu, click **Administration**: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-tmn4q90j.jpg) The Datasets screen will open. 2. In the Datasets screen, Click the **Services** button: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/image(85).png) The Services screen will open. 3. Click the Application server's **Download** icon: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-p9iw76qb.jpg) The Application server Report list will open. 1. Locate **brainspace.log**, and then click the **Download** button: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/image(86).png) 2. The Brainspace Log text file will download to your local machine. 3. Open the text file, and then search the Brainspace Log for the word "ERROR," generally in all-caps, and a timestamp that corresponds to the time that the problem was encountered: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/image(87).png) > [!NOTE] > **Note** > > Look for brainspace.log.[date], such as brainspace.log.2018-10-10, if the error was experienced during a prior day. A new Brainspace log file is created each day (typically at midnight server time), and the prior days are saved with their dates. 4. Review the ERROR and first “Caused by” instance following the error to determine the root cause. > [!NOTE] > **Note** > > If the error indicates something infrastructure related (for example, cannot write to a file or to a disk could indicate that the drive volume is full or unreachable) or a data problem (for example, cannot recognize ingested data format), escalate the issue within your organization. 5. Using the error keyword(s) from the Brainspace log, search the Brainspace [***Error Resolution Troubleshooting Table***](/brainspace/docs/error-resolution-troubleshooting-table) to find an explanation of and recommended resolution for the error. If you cannot determine the root cause from the Error Log or the Brainspace Log, save the Brainspace Log and contact Brainspace Support for assistance. ## Download and Review the Build Log If an error or build failure occurs after successful ingestion and during a build, download and review the Build Log. The Build Log provides dataset-specific build information. To download and review the Build Log: 1. In the user drop-down menu, click **Administration**: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-52hz4k19.jpg) The Datasets screen will open. 2. Choose a dataset, and then click the **Download Reports** icon: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-clvbi5vh.jpg) 3. Locate Build Log, and then click the **Download** button: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/image(88).png) 4. The Build Log text file will download to your local machine. 5. Open the text file, and then review the Build Log for errors and the build summary in the last few lines of the Build Log. After downloading and reviewing the Build Log, download and review the Analysis (Analytics) Server Log if the Build Log does not indicated a root cause or if the root cause indicates a problem with the Analysis (Analytics) server. ## Download and Review the Analysis (Analytics) Server Log After downloading and reviewing the Build Log, download and review the Analysis (Analytics) Server Log if no root cause was found in the Build Log or if the root cause indicates a problem with the Analytics server. > [!NOTE] > **Note** > > The Analysis Server Log shows local errors on the Analytics server only; however, these local errors are the same details shown in the Brainspace Log if the application server retained connectivity with the Analytics server throughout the build. To download and review the Analysis (Analytics) Server Log: 1. In the user drop-down menu, click **Administration**: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-h3and8qp.jpg) The Datasets screen will open. 1. In the Datasets screen, click the **Services** button: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/image(89).png) 2. The Services screen will open. 3. Click the Analytics server's **Download logs** icon: ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/basic-troubleshooting-image-o5fmp6x7.jpg) The Analytics server's Report list will open. > [!NOTE] > **Note** > > This report is also available for the Build server. 4. Locate **analysisserver.log**, and then click the **Download** button. ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/image(90).png) 5. The Analysis Server Log text file will download to your local machine. 6. Open the text file, and then review the Analysis Server Log for errors around the time that the issue was encountered. > [!NOTE] > **Note** > > If you are concerned about the status of a build, look at the status report to see what part of the build is running. ## Related - [View Errors in the Error Log](/view-errors-in-the-error-log.md) - [Brainspace System Health Checks](/brainspace-system-health-checks.md) - [Error Resolution Troubleshooting Table](/error-resolution-troubleshooting-table.md)