Thresholds.xml And Tivoli Enterprise Monitoring Server Table Not Cleaned When Managed System Override Is Removed; Situations Fail To Trigger For Attributes By Applying Group Function; Monitoring Server Application Support Completes All Seeding Functions But Might Crash As The Program Is Exiting - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

THRESHOLDS.XML and Tivoli Enterprise Monitoring Server
table not cleaned when managed system override is removed
Removing an existing managed system override definition by removing the
managed system from a situation distribution list does not result in the override
being removed from the Tivoli Enterprise Monitoring Server table and the
THRESHOLDS.xml file on the agent.
You must first check to see if any override is associated with that particular
managed system before removing it from the situation. If an override is found,
remove it before the situation's distribution is modified.
Situations fail to trigger for attributes by applying group
function
If you create a Situation with attributes (for example, 'Elapsed_Time' and 'Virtual
Bytes for 'NT_PROCESS') and then apply the condition (MAX(Elapsed
Time(Seconds))==*TRUE AND Virtual Bytes != 5, the created situation should be
triggered and forwarded to Tivoli Enterprise Console server. However, the
situation is not triggered. The Tivoli Enterprise Portal expects that the Tivoli
Enterprise Monitoring Server should dynamically find the MAX row and then
apply further conditions. This is not how column functions work
According to standard, grouping functions can only return the grouping function
results and any columns used in the grouping. This predicate is looking for a
single row, but a grouping function is an aggregate of the grouped rows.
Monitoring server application support completes all seeding
functions but might crash as the program is exiting
The Tivoli Enterprise Monitoring Server seeding program that adds monitoring
server application support completes all seeding functions, but may crash as the
program is exiting. This crash has only been observed rarely during product
testing. The IBM Tivoli Monitoring configuration tool checks the output produced
by the seeding functions, and it reports that the monitoring server application
support was added successfully. Since all seeding functions were completed, the
monitoring server tables with application support are correct and not corrupted.
A core or dump file might be created during the program crash. Creation of a core
or dump file usually depends on if the system has been configured to save crash
information. However, even if the system is configured to save crash data, this
particular crash might not produce a core or dump file.
The monitoring server seeding output files contain information about the crash. An
operating system message indicates the condition that caused the crash. A sample
crash message would be: signal 11(SIG1_SIGSEGV=29)
0B000000000000000100000000000000F84CD256887CAE56E8F400570000000048010000EE5
DB656B88B9655A4F70057220000002200000000000000D8F900572CF800578C81C056ACEF00
57C04DD256484DD2563EB4B656C04DD2560000000000F500570100000000000000200000000
2000000879D8B558C81C056A8EF0057
The expected seeding completion messages will follow the crash message. The
normal seeding messages are checked by the Tivoli Monitoring configuration tool
for successful completion of all seeding functions. The crash message always
appears in the monitoring server seeding output even if a core or dump file is not
produced.
Chapter 9. Monitoring server troubleshooting
157