IBM E027SLL-H Troubleshooting Guide - Page 175

THRESHOLDS.XML and Tivoli Enterprise Monitoring Server

Page 175 highlights

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310

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