IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agentless OS Monitor User's Guides > Agentless Monitoring for Linux User's Guide > Troubleshooting > Problems and workarounds IBM Tivoli Monitoring, Version 6.3


Workspace troubleshooting

Problems can occur with general workspaces and agent-specific workspaces.
Table 1 contains problems and solutions related to workspaces.


Workspace problems and solutions

Problem Solution
Process application components are available, but the Availability status shows PROCESS_DATA_NOT_ AVAILABLE. This problem occurs because the PerfProc performance object is disabled. When this condition exists, IBM Tivoli Monitoring cannot collect performance data for this process. Use the following steps to confirm that this problem exists and to resolve it:

  1. In the Windows Start menu, click Run.

  2. Type perfmon.exe in the Open field of the Run window. The Performance window is displayed.

  3. Click the plus sign (+) in the toolbar. The Add Counters window is displayed.

  4. Look for Process in the Performance object menu.

  5. Complete one of the following actions:

    • If you see Process in the menu, the PerfProc performance object is enabled and the problem is coming from a different source. You might need to contact IBM Software Support.

    • If you do not see Process in the menu, use the Microsoft utility from the Microsoft.com Operations website to enable the PerfProc performance object.

      The Process performance object becomes visible in the Performance object menu of the Add Counters windows, and IBM Tivoli Monitoring is able to detect Availability data.

  6. Restart the monitoring agent.

Event Log workspace events are unfiltered, are not collected more than every 60 seconds, and are removed from the Event Log Views after 1 hour of being received. All events currently in the Application Event Log are sent to the Tivoli Enterprise Monitoring Server when the agent starts. Environment variables that control the behavior of the Event Log Workspace are stored in the agent ENV file on the Tivoli Enterprise Monitoring Agent where the agent is running. These variables are stored:

CDP_DP_CACHE_TTL

This value is the minimum number of seconds before data (for a particular table) is collected again. By default this variable is present in the ENV file and the value is set to 60.

CDP_NT_EVENT_LOG_GET_ALL_ENTRIES_FIRST_TIME

This variable determines whether the agent sends all events currently in the Application Event Log to the Tivoli Enterprise Monitoring Server when the agent starts. Legal values are YES and NO. By default this variable is present in the ENV file and the value is set to NO.

CDP_NT_EVENT_LOG_CACHE_TIMEOUT

This variable determines how long in seconds that events are displayed in the Tivoli Enterprise Monitoring Server Event Log Views. By default, this variable is not present in the ENV file. A default value of 3600 (1 Hour) is used unless overridden by the presence of this variable in the agent ENV file. The minimum legal value is 300.
To view or edit the agent ENV file on the Tivoli Enterprise Monitoring agent where the agent is installed, use Manage Tivoli Enterprise Monitoring Services to select the agent. Right-click and select Advanced - Edit ENV File. The agent must be restarted to implement changes.
Name of the attribute does not display in a bar chart or graph view. When a chart or graph view that includes the attribute is scaled to a small size, a blank space is displayed instead of a truncated name. To see the name of the attribute, expand the view of the chart until sufficient space is available to display all characters of the attribute name.
At the bottom of each view, you see the following Historical workspace KFWITM220E error: Request failed during execution. Ensure that you configure all groups that supply data to the view. In the Historical Configuration view, ensure that data collection is started for all groups that supply data to the view.
You start collection of historical data but the data cannot be seen. Use the following managing options for historical data collection:

  • Basic historical data collection populates the Warehouse with raw data. This type of data collection is turned off by default. For information about managing this feature including how to set the interval at which data is collected, see Manage historical data in the IBM Tivoli Monitoring Administrator's Guide. By setting a more frequent interval for data collection, you reduce the load on the system incurred every time data is uploaded.

  • Use the Summarization and Pruning agent to collect specific amounts and types of historical data. Historical data is not displayed until the Summarization and Pruning monitoring agent begins collecting the data. By default, this agent begins collection at 2 a.m. daily. At that point, data is visible in the workspace view. For information about how to modify the default collection settings, see Manage historical data in the IBM Tivoli Monitoring Administrator's Guide.

Historical data collection is unavailable because of incorrect queries in the Tivoli Enterprise Portal. Sort By, Group By, and First/Last functions column are not compatible with the historical data collection feature. Use of these advanced functions makes a query ineligible for historical data collection.

Even if data collection has started, you cannot use the time span feature if the query for the chart or table includes column functions or advanced query options (Sort By, Group By, First / Last).

To ensure support of historical data collection, do not use the Sort By, Group By, or First/Last functions in your queries.

For information about the historical data collection function, See Manage historical datain the IBM Tivoli Monitoring Administrator's Guide or the Tivoli Enterprise Portal online help .

When you use a long process name in the situation, the process name is truncated. Truncation of process or service names for situations in the Availability table in the portal display is the expected behavior. The maximum name length is 100 bytes.
Regular (non-historical) monitoring data fails to be displayed. Check the formation of the queries you use to gather data. For example, look for invalid SQL statements.
No row of data for 64-bit applications is displayed in the workspaces when the monitoring agent is running on a 64-bit operating system. The Tivoli Enterprise Portal shows data only for 32-bit applications. No solution is available for this problem at this time.
SNMP attribute group is not collecting data reliably.

Data is collected intermittently or not at all. The SNMP version and credentials are configured correctly. The Performance Object Status Error Code for the attribute group shows "NO RESPONSE RECEIVED".

This problem applies to SNMP attribute groups, so the Object Type in the Performance Object Status table is SNMP.

The agent trace file shows the following message: Timeout occurred. No response from agent.

Here is a sample entry: (48A18C71.000A-12:snmpqueryclass.cpp,1714, "internalCollectData") Timeout occurred. No response from agent.

The IBM Tivoli Monitoring SNMP data provider is multithreaded to enhance performance. The SNMP data source that is being monitored might not be able to respond to multiple incoming requests in a timely manner. The following tuning options can improve reliability of data collections:

Reduce the thread pool size

The default thread pool size is 15. Try reducing the size to 5. This setting can be adjusted in the agent ENV file by setting the CDP_DP_THREAD_POOL_SIZE environment variable.

Increase the SNMP Response Timeout

The default SNMP Timeout is 2 seconds. Try increasing the timeout to 6 seconds. This setting can be adjusted in the agent ENV file by setting the CDP_SNMP_RESPONSE_TIMEOUT environment variable.

Reduce the number of SNMP retries

The default number of SNMP retries is 2. Try reducing the size to 1. This setting can be adjusted in the agent ENV file by setting the CDP_SNMP_MAX_RETRIES environment variable.
Navigator items and workspace titles are labeled with internal names such as Kxx:KXX0000 instead of the correct names (such as Disk), where XX and xx represent the two-character agent code. Ensure that application support has been added on the monitoring server, portal server, and portal client.

For more information about installing application support, see Install and enable application support in the IBM Tivoli Monitoring Installation and Setup Guide.


Parent topic:

Problems and workarounds

+

Search Tips   |   Advanced Search