Important

   

Starting version 8.9.03, BMC Server Automation is renamed to TrueSight Server Automation. This space contains information about BMC Server Automation 8.9.02 and previous versions. For TrueSight Server Automation 8.9.03 and later releases, see TrueSight Server Automation 8.9.

Troubleshooting the Live Reporting dashboard

This topic contains troubleshooting information for issues you may encounter with the Live Reporting dashboard. The topic includes the following sections: 

Where can I find Yellowfin troubleshooting installation?

The BMC Server Automation Yellowfin post-installation logs are located here: <path-to-postinstaller>\log\yellowfinpostinstaller.log). You might see the following -2 error code from the post-installer script.

[main] INFO com.bmc.postinstaller.livereporting.LiveReportingPostInstaller - Setting the SOURCEPARAMETER_MODE mode to SID
[main] ERROR com.bmc.postinstaller.livereporting.LiveReportingPostInstaller - The status of import service is FAILURE , the errorCode is -2 and the error message is UNKNOWN_ERROR
[main] INFO com.bmc.postinstaller.livereporting.LiveReportingPostInstaller - Error occured while importing the content , skipping the step

In this case, the BladeLogic database is not configured correctly as a data source for the post-installer, but you may require additional information to troubleshoot the problem. 

Workaround:

In this example, review the actual logs generated by Yellowfin (for example, located at /usr/loca/Yellowfin71/appserver/logs). They typically contain more detailed troubleshooting information. 

Can I install Live Reporting on a system that does not have internet access?


If you need to install Live Reporting on a system that does not have internet access, perform the following steps:

  1. Install Live Reporting on a supported Microsoft Windows or Linux operating system.
  2. Stop the Yellowfin service.
  3. Locate the following section in the <yellowfin_installation_directory>/appserver/webapps/root/web-inf/web.xml file:
    <!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd" [
    <!ENTITY jsps SYSTEM "file:/opt/bmc/Yellowfin/appserver/webapps/ROOT/WEB-INF/web-jsps.xml">
    ]>
  4. Replace the above with the following: 
    <!DOCTYPE web-app
    SYSTEM "web-app_2_3.dtd" [
    <!ENTITY jsps SYSTEM "file:/opt/bmc/Yellowfin/appserver/webapps/ROOT/WEB-INF/web-jsps.xml">
    ]>
  5. Start the Yellowfin service.
  6. Run the post-installation script:
    • postinstaller.bat (Windows)
    • postinstaller.sh (Linux)

Note

A sample path for Microsoft Windows in the ENTITY jsps SYSTEM tag is

<!ENTITY jsps SYSTEM "file:C:\Program Files\BMC Software\Live_Reporting\Yellowfin\appserver\webapps\ROOT\WEB-INF\web-jsps.xml">


How do I configure Yellowfin after changing the password of the Oracle metadata database used with Live Reporting?

The following steps describe how to configure Yellowfin after you changed the password of the Oracle metadata database user.

Note

These steps do not apply to Windows SQL Server environments.
  1. Stop the Yellowfin Tomcat service, 

    /usr/local/Yellowfin71/appserver/bin/shutdown.sh

    If you do not stop the Yellowfin service and you change the database password, the Yellowfin service still uses the old password connect to the database and the password could become locked. 

  2. Change the database user password in Oracle.
  3. Start the Yellowfin Tomcat service.

    /usr/local/Yellowfin71/appserver/bin/startup.sh
  4. Execute the live patching post installer. The script prompts you for the BSA database user password.
  5. Enter the new password. 
    If the script finishes successfully, the configuration of the new password is complete. 

How do I refresh the list of server groups on the Live Reporting dashboard?

You must refresh the list of server groups (static groups or smart groups) so that Live Reporting will include information for the appropriate groups of servers. Remember to do this each time the server groups have been modified or new server groups have been created.

  1. Run the following BLCLI command to update the server group list, before using Live reporting:
    blcli -v defaultProfile Utility populateServerGrpforLiveReporting
    For more information about this BLCLI command, see Utility populateServerGrpforLiveReporting.
  2. In the Live Reporting dashboard, check the Server Groups drop-down list in the Filters section, and ensure that the list reflects the appropriate server groups.

How can I shorten the list of server groups for filtering?

The list of server groups that displays when you filter the Live Reporting dashboard by server groups might be very long, depending on the number of server groups that you have defined in your environment. To shorten this list, you can perform the following actions:

ObjectiveSteps
Remove existing server groups from the list for filtering on the Live Reporting dashboard

To remove a server group from the list, you set its IS_USED_IN_REPORTS* property to a value of False:

  1. In the Console, open the Servers folder.
  2. Select a server group (either a static group or a smart group) that you do not want to appear in the list for filtering on the Live Reporting dashboard.
  3. In the Properties view, expand the Extended node to display the list of the server group's extended properties.
  4. Click in the Value column of the IS_USED_IN_REPORTS* property.
  5. After the field becomes active, change the value of this property from True to False.
  6. Repeat steps 1-5 for any other server group that you do not want to appear in the list for filtering.
  7. Refresh the list of server groups, as described above.

Ensure that server groups created in the future are not added to the list

As of Service Pack 1 (version 8.9.01), you can use a blasadmin parameter named IsUsedInReports to control the default value of the IS_USED_IN_REPORTS* property in any newly created server group.

  1. Start the Application Server Administration console, as described in Starting the Application Server Administration console.
  2. To change the value of the IsUsedInReports parameter from the default true to false, enter the following command:
    set SmartGroupConfig IsUsedInReports false
  3. In the future, if you define a new server group and want it to appear in the list of server groups for filtering on the Live Reporting dashboard, manually set the IS_USED_IN_REPORTS* property for the server group to True, as described in the row above.

How do I update the filter list for the dashboards?

After you add server groups, patch catalogs, and so on to your environment, you need to refresh the cached filter list to ensure that the latest values are reflected in the dashboards.

  1. Log on to Yellowfin using the REPORT_ADMIN user.
  2. Select Administration > Admin Console
  3. From the Administration section on the right (outlined in red below), select Schedule Management
     
  4. Select the following filter schedules, and then click Run Now:
    • Analysis Run Progress Status (Non-distinct server count if multiple catalog selected)
    • Compliance Run Progress Status (Non-distinct server count if multiple Template selected) 
    • Job Activity Summary by Application Server 
       
  5. Click the Refresh button at the bottom of the page (next to the Run now button) and verify that the Cached Filter Refresh items (outlined in red above) show a current date.
  6. Log out as REPORT_ADMIN. 
  7. Launch the Live Reporting dashboard from the BMC Server Automation console or from an external browser. 
    Ensure that the expected filter values are now shown in the dashboard.

What do the hover icons mean on the reports?

If you hover above the report view, icons are displayed in the upper-right corner of the view.

The following table describes each of the icons you might see.

IconDescriptionRelated panels

This option enables you to do any of the following:

  • View report - Display the report filters, as well as both the line graph and chart views of the report.
  • Print - Print the report.
  • Export - Export the report to Microsoft Word, PDF, rich text, or Microsoft Excel.
  • Share - Send the report to others using email, or produce a code string that you can embed into your HTML page, wiki or blog.
  • Information - Display the report details, report statistics, column definitions, and SQL statement that generates the report.

These two options enable you to switch between the chart version of the report, and the line graph version of the report.

The first icon is for the chart view.

The second icon is for the line graph.

Chart view:

Line graph view:

This option enables you to change the filters that generate the report.

How do I filter the report data?

To refine the scope of the data you see in the dashboard, filter the data presented on the dashboard with the following options:

Filter optionsDescriptionAvailable on these tabs
Time periodSelect a time period from the drop-down list. You can choose between the last 24 hours or intervals that span up to the last 90 days. The default is 24 hours.
  • Patch
  • Compliance
  • Job Activity
Time RangeSelect a specific range of days by using the calendar icons next to the From and To fields.
  • Patch
  • Compliance
Customer Out-of-the-box property that you can select to filter the data by customer.
  • Patch
  • Compliance
  • Job Activity
Location Out-of-the-box property that you can select to filter the data by location.
  • Patch
  • Compliance
  • Job Activity
Server group

Click Select to choose to display the Server Group window, which shows all of the static and Smart Groups in your environment.

Click the server group, or groups, for which you want to see data and then click Select.

Tip: If you have a lot of server groups and are looking for a specific group, you can enter a name in the Search field at the top of the window, and click the search icon.

Note: Do not select more than 10 server groups at a time, otherwise you will see an error.

  • Patch
  • Compliance
  • Job Activity
Job TypeOn the Job Activity tab only. This option filters which jobs you want to see displayed in the reports.
  • Job Activity

Template Name

On the Compliance tab only. This option filters which compliance templates you want to see displayed in the reports.
  • Compliance
Catalog NameOn the Patch tab only. Choose a patch catalog for which you want to see patching data.
  • Patch
Role NameThis option is available only if you have launched the dashboard from a browser, and if the BSA user that is logged on is assigned multiple roles.
  • Patch
  • Compliance
  • Job Activity

To set a custom view:

  1. Select the tab for which you want to review data. 
  2. Select Current View or Historical View
  3. In Filters, specify criteria to define the scope of the data you see in the reports:
    1. Select a Time Period - For example, the Last 14 Days of data. 
    2. Select a Time Range date - For example, From 2016-07-29 11:58:04 To 2016-08-08 11:57:40.
    3. Select a Customer -  You can use the filter to view all customers, no customers, or enter a specific customer.
    4. Select a Location -  You can use the filter to view all locations, no customers, or enter a specific location (for example, San Jose).
    5. Select a Server Group (if available) - You can filter the view by choosing one or more server groups for which you want to see data.
      Note: Do not select more than 10 server groups at a time, otherwise you will see an error.
    6. Select a Template Name (if available) - You can use the filter to view all templates, no templates, or select one or two templates to restrict the compliance data viewed.
    7. Select a Catalog name (if available) - You can use the filter to view all catalogs, no catalogs, or select one or two catalogs to restrict the catalog data viewed.
    8. Select a Role Name - You can use the filter to restrict the data viewed to that associated with a specific BSA role (BLAdmins, for example).
  4. Click Go to refresh the data selected. 

Once the data is refreshed, you can export the report, print the report, or see a total view of the report (the filters, the graph view, and the table view).

Tip

To keep the data in the dashboard as current as possible, it is important to periodically run the BLCLI Populate Server Group utility. See the How do I refresh the list of server groups for the Live Reporting dashboard? section above, particularly if you have updated your server list or smart groups.

Connection timeout error message during Yellowfin post-installation

You get a timeout after five minutes of importing contents and receive the following error message:

{http://xml.apache.org/axis/}stackTrace:java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)

Workaround: 

Perform the following steps:

  1. Open <yellowfin_installation_directory>/appserver/webapps/root/web-inf/web.xml file by using any text editor (for example, Notepad).
  2. Add the following section in the web.xml file, to set the required timeout value in seconds.

    <init-param>
    	<param-name>JDBCTimeout</param-name>
    	<param-value>1800</param-value>
    </init-param>
  3. Re-start the Yellowfin service.

Special considerations when using Live Reporting

When you are using Live Reporting, there are certain considerations you should be aware of. 

CategoryItemDescription
Data displayPatching jobs data

Data for Patching jobs is not available on the Job Activity tab of the Live Reporting dashboard, as the data is already included on the Patch tab.

 In-progress Compliance Jobs data

Data for In-progress Compliance Jobs is not available in the following reports:

Job Activity tab

  • Running Server Summary by Job Type

  • Job Activity Run Progress Status

Compliance tab

  • Compliance Run Progress Status
 Graph legend changes color in Deploy Historical View

In the Deploy Historical View, the graph line legend changes color after selecting or deselecting the options at the bottom of the graph.

 Two status lines displayed in detail report of Deploy Historical Detail ViewIf the Commit phase of a patch job initially fails but then succeeds, the Completed status is correctly shown in the Summary, but the Deploy Historical Detail View shows both the Failed and the Completed status.
 Running Compliance Jobs with correct resultsIf you create a Compliance Job with the Continue despite compliance and data collection errors option set and the job fails, the job will display Completed with warnings, even though individual components might not satisfy some compliance rules. As a result, some of the compliance data displayed in Live Reporting reports might be inaccurate. Use caution when setting this option in a Compliance Job. 
 Details from deleted Application Server still displayed in Job Activity reportWhen you delete an Application Server in BladeLogic, the details continue to be displayed in the Job Activity by Application Server Summary report.
PerformanceRefreshing cached filters on Oracle can take long time to process

If your Oracle database has a large amount of data (for example, 5 million rows), clicking Refresh Cached Filters can take 30 minutes or more to run to completion.

Be sure to take the processing time into account when you plan to refresh the cached filters, especially with large amounts of data.

 Clicking on a dashboard causes data refreshWhen you click on a dashboard tab (for example, the Patch tab), the data for all reports is automatically refreshed. This process make take several minutes.
 To improve performance, avoid using Omit filter when running reports

If you select the default Omit filter when running a report in Live Reporting with the Patch, Compliance, and Job Activity dashboards, you typically see a major performance hit on the database server. You also see an impact on application-server jobs that are running at the same time. This is because application-server jobs and the live patching query uses the same database. In addition, the server frequently fails to generate the reports. The problem is that the database server fetches the report data without any filters.

As a result, always select a minimum time range in the Time Period filter (for example, 1 day or 7 days) when fetching reports. Avoid maximum selections like 120 days. 

 Cohort analysis returns database error under certain conditions

In the Live Reporting dashboard, if you have specified values for all of the filter options , you will experience performance issues when the data is being loaded for the dashboard.

Be sure to select only those filter options that are applicable for the report.

 User accessUser dropped in BladeLogic can still connect to Yellowfin and still see data

If you drop or disable a user in BladeLogic Server Automation, that user is still authorized to log on to Yellowfin and access the data of all reports.

To remove the user, perform the following steps:

  1. Log on to Yellowfin as REPORT_ADMIN.
  2. Select Administration > Admin Console > User Groups .
  3. Select the group that your user belongs to.
  4. Manually delete the user as no longer authorized, as shown in the figure below.
     
  5. Save your changes to the group.
  6. Log out as REPORT_ADMIN.
  7. Try to log in to Yellowfin as the now deleted user. Access should be denied.
 External login to Yellowfin does not work with BSA user password

There are two ways to log on to the Dashboard:

  • Cross-launch from the BMC Server Automation Console.
  • Externally logging on to Yellowfin (for example, https://localhost:8443 ) as a BMC Server Automation user .

Externally logging on to Yellowfin with a BMC Server Automation user name and password (versus the REPORT_ADMIN user) does not work.

If you want to log on to Yellowfin externally, enter BMC Server Automation user name with the Yellowfin default password, "test". All users created in Yellowfin have the default "test" password.

This issue does not affect Live Reporting cross-launch from the BMC Server Automation Console because the connection to Yellowfin is direct and is password-less.

Log filesDEADLOCK error in Yellowfin logsYou may see a DEADLOCK error in the Yellowfin log file (yellowfin.log). This error is related to the Tomcat Server, and does not affect the Live Reporting dashboard reports, nor it is related to the BMC Server Automationn database.
Was this page helpful? Yes No Submitting... Thank you

Comments