This topic lists common issues, probable causes, and suggestions for troubleshooting the BMC TrueSight IT Data Analytics (IT Data Analytics) product.
To locate an issue, use one of the following options:
|Category||Scenario||Probable causes with solutions (if any)|
|Accessing the product||Unable to access the product from the Start menu|
You might not be able to start the product, if:
|Saved searches||Unable to edit a saved search (or data pattern)|
You cannot edit the following items:
Solution: If you want to edit an object (saved searches or data patterns) that was initially imported by using a content pack, you can clone the object and then modify it per your requirements.
|System response time||The Collection Station went down, and the IT Data Analytics server was restarted, the system became very slow|
When you restart the IT Data Analytics server, all of the data collectors try to catch up and send the old pending data into the Collection Station for indexing.
Based on the number of data collectors, this process can take some time (a few minutes to a few hours) to complete.
|System response time||The Indexer remained down for two days over the weekend, and after IT Data Analytics server was restarted, the system became very slow|
This issue can occur if the Collection Station cached a lot of data over the weekend. When you restart the IT Data Analytics server, the Collection Station pushes all cached data together into the Indexer.
|Product component shows red||Some of the Collection Agents are showing up as red on the Administration > Hosts page and do not change to green, even though all of the servers are running.|
This issue might occur if the Collection Station remains down at the time at which the Collection Agents start.
Solution: Restart the Collection Agents after the Collection Station is up and running.
|Product component shows red||The Configuration Database and Indexer are showing as green on the Administration > Components page, but some of the other components are down (on the Linux operating system).|
The components might not have been started in the recommended order.
Unable to search for indexed data.
This can happen in two scenarios:
The Collection Station on a Windows computer is not starting or working properly after the time it stopped abruptly and you see the following exceptions in the collection.log.
This issue is rare and might occur when the Collection Station stops abruptly, which can happen if the %BMC_ITDA_HOME%\station\collection\data\c*\flume-checkpoint(1)\checkpoint file becomes corrupted.
You can find the exact name of the corrupted checkpoint file in the collection.log file located at %BMC_ITDA_HOME%\station\collection\logs. In this file, you can search for the line containing the
|Search||Data entry time on the Search tab is ahead of the time at which the notification was generated|
By default, there is a delay of 90 seconds between data collection and reporting of search results to the product. Therefore, during notification creation, when you select one of the search duration options and apply a condition related to the number of results, you can expect a delay of 90 seconds.
Solution: You can change the 90 seconds time lag by modifying the value of one of the following properties available in the searchserviceCustomConfig.properties file. For more information, see.
|Data collection||Data collector has been created, but the results cannot be seen|
After the data collector is created, it might take some time (approximately 1 minute) for the first poll to happen. The first poll is used to make the data collector ready for data collection. The data is fetched only from the second poll.
Expected time delay (to see the first set of data for a search) = (Time for first poll) + (Poll interval set for the data collector)
|Search||Data is being generated in the files for monitoring, but no data can be seen when performing a search|
This issue might occur if the time zone specified during data-collector creation is set incorrectly.
Solution: Ensure that the time zone is set correctly when you create data collectors.
|Product component shows red||Status of the Collection Station appears red on the Administration > Components tab.|
This issue might occur in two scenarios:
|Product component shows red||Status of the Search component appears red on the Administration > Components tab.||The host name specified while registering the self-signed certificate does not match the host name of the computer where the Search component is installed. You can find the correct host name by navigating to the %BMC_ITDA_HOME%\logs\itda.log and search for the following line:|
You see the following error on the product user interface:
This can happen if the Configuration Database service is down.
Solution: Perform the following steps:
|Data collection||Some data got lost when the Collection Station (or Collection Agent) went down briefly||By default, the number of days for which data must be collected and indexed (Read from Past (#days) function) is set to zero. As a result, in the process of data collection, if the Collection Station (or Collection Agent) goes down, you can experience data loss. When the Collection Station (or Collection Agent) is up again, it starts collecting data from that point onwards and the time for which it remained down is ignored. You can change the Read from Past (#days) default value for the Monitor Windows events and Monitor using external configuration data collectors.|
The polling status for the following data collectors shows red (unsuccessful polling).
You see the
This issue might occur in the following scenarios:
This issue occurs because the number of concurrent SSH connections allowed to the target host is lesser than the the number of data collectors that you want to create. The number of concurrent SSH connections determine the number of data collectors that you can create for collecting data from the same target host.
Solution: Navigate to the /etc/ssh/sshd_config directory and increase the value of the MaxSessions parameter. This solution is only applicable for OpenSSH version 5.1 and later.
At the time of creating a data collector, when you try to filter the relevant data patterns, you might see the following error:
This issue might occur if the system response time of the server on which you are trying to create the data collector is slow.
Solution: Edit the olaengineCustomConfig.properties file located at %BMC_ITDA_HOME%\custom\conf\server\ and then add the
This property determines the duration of time (in seconds) for which the Console Server waits to receive a response from the Collection Station.
|Saved searches||Unable to use a saved search shared by another user to create views or notifications.|
You cannot use saved searches shared by other users for creating views or notifications.
Solution: Clone the saved search and then use the cloned instance to create views or notifications. For more information, see Managing saved searches
Unable to see the updated UI available for the upgraded version of the product.
To find out if you are still accessing the older UI, navigate to Administration > Components and check if you can see the Version column that is available in the new version of the product.
This might occur if the browser where you are accessing the product continues to access the cached content.
Solution: Press Ctrl+F5 to reload the browser page while ignoring the cached content. If reloading the browser page does not work, then append ?version=1_1 to the browser URL, before the hash sign (#) as follows:
You are experiencing some data loss and you see the following error in the collection.log file located at %BMC_ITDA_HOME%\station\collection\logs.
Even when all the Indexers in the cluster are up and functioning normally, this error might occur due to various reasons. For example, a poor network connection or the system on which the Indexers (or the Collection Station) reside have become slow.
Workaround: Increase the value of the
Some data collected by the Receive over TCP/UDP data collected is not getting indexed and occasionally you find the following message in the collection.log file.
This might occur when the rate at which the sender sends data via the TCP port is greater than the rate at which the Receive over TCP/UDP data collector indexes data. This indicates that the data collector is dropping records and needs to be tuned.
Solution: To allow for indexing higher volumes of data per day on a single data collector, you must add the following properties with appropriate values in the agent.properties file. For more information, see Modifying the configuration files.
Note that the following property values were used for indexing up to 100 GB of data in the lab environment.