IBM E027SLL-H Troubleshooting Guide - Page 226

tacmd suggestbaseline command receives an error

Get IBM E027SLL-H - Tivoli Monitoring - PC PDF manuals and user guides View all IBM E027SLL-H manuals
Add to My Manuals
Save this manual to your list of manuals

Page 226 highlights

tacmd suggestbaseline command receives an error When using this command, you receive this message: " The specified managed system is not overrideable because it does not have the appropriate affinity feature bit enabled." The tacmd suggestbaseline command does not support pre-IBM Tivoli Monitoring v6.2.1 agents. When using the listSystems command, the last two digits for the version appear as 'XX' Extended version information for every agent might not always be available. When this happens, the last two digits of the version displayed are represented as "XX". This occurs for subnode agents or when agents are not enabled for Agent Deploy support. The command tacmd restartAgent fails if the agent is already stopped If the tacmd restartAgent command is issued against an agent that is stopped, it will generate an error message: # /opt/IBM/ITM/bin/tacmd restartagent -n zpmaix13:KUX -t ul KUICRA006I: Are you sure you want to restart the UL agent(s) that manage zpmaix13:KUL? Enter Y for yes or N for no: Y KUICRA007I: Restarting UL agent(s). KUICRA009E: A problem occurred while restarting UL - refer to the following error returned from the server: The monitoring server encountered an error while restarting the managed system. If the error information returned from the server is not sufficient to help you resolve the error, contact IBM Software Support. The command /opt/IBM/ITM/bin/CandleAgent -h /opt/IBM/ITM -c stop ul did not start or stop agent. The command returned a return code. Enable Deployment trace logging on the agent machine. Contact Customer Service for details on this procedure. Collect the following log files On Windows the log kdsmain.msg log is located in the {CANDLEHOME}\CMS directory and {hostname}_ms_{timestamp}-XX.log files are located in CANDLEHOME\logs directory. On Unix-Based systems the logs {hostname}_{timestamp}.log and {hostname}_ms_{timestamp}-XX.log is located in the {CANDLEHOME}/logs directory. On the target Managed System Node machine collect the following log files. On Windows the logs kdyproc_ras1_{timestamp}.log and {hostname}_nt_kntcma_ {timestamp}-XX.log are located in the {CANDLEHOME}\tmaitm6\logs directory. On Unix systems the logs kdyproc_ras1_{timestamp}.log and {hostname}_ ux_kuxagent_{timestamp}-XX.log is located in the {CANDLEHOME}/logs directory. On Linux systems the logs kdyproc_ras1_{timestamp}.log and {hostname}_ lz_klzagent_{timestamp}-XX.log is located in the {CANDLEHOME}/logs directory. Refer to IBM Tivoli Monitoring v 6.2 Problem Determination Guide for more information. The user can verify the agent is stopped by running tacmd listSystems: 208 IBM Tivoli Monitoring: Troubleshooting Guide

  • 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
tacmd suggestbaseline command receives an error
When using this command, you receive this message:
" The specified managed
system is not overrideable because it does not have the appropriate
affinity feature bit enabled."
The
tacmd suggestbaseline
command does not support pre-IBM Tivoli Monitoring
v6.2.1 agents.
When using the listSystems command, the last two digits for the
version appear as 'XX'
Extended version information for every agent might not always be available. When
this happens, the last two digits of the version displayed are represented as "XX".
This occurs for subnode agents or when agents are not enabled for Agent Deploy
support.
The command tacmd restartAgent fails if the agent is already stopped
If the
tacmd restartAgent
command is issued against an agent that is stopped, it
will generate an error message:
# /opt/IBM/ITM/bin/tacmd restartagent -n zpmaix13:KUX -t ul
KUICRA006I: Are you sure you want to restart the UL agent(s) that manage
zpmaix13:KUL?
Enter Y for yes or N for no: Y
KUICRA007I: Restarting UL agent(s).
KUICRA009E: A problem occurred while restarting UL - refer to the following error
returned from the server:
The monitoring server encountered an error while restarting the managed system.
If the error information returned from the server is not sufficient to help you
resolve the error, contact IBM Software Support.
The command /opt/IBM/ITM/bin/CandleAgent
-h /opt/IBM/ITM -c stop ul did not start
or stop agent.
The command returned a return code.
Enable Deployment trace logging on the agent machine. Contact Customer Service
for details on this procedure. Collect the following log files
On Windows the log kdsmain.msg log is located in the {CANDLEHOME}\CMS
directory and {hostname}_ms_{timestamp}-XX.log files are located in
CANDLEHOME\logs directory.
On Unix-Based systems the logs {hostname}_{timestamp}.log and
{hostname}_ms_{timestamp}-XX.log is located in the {CANDLEHOME}/logs directory.
On the target Managed System Node machine collect the following log files.
On Windows the logs kdyproc_ras1_{timestamp}.log and {hostname}_nt_kntcma_
{timestamp}-XX.log are located in the {CANDLEHOME}\tmaitm6\logs directory.
On Unix systems the logs kdyproc_ras1_{timestamp}.log and {hostname}_
ux_kuxagent_{timestamp}-XX.log is located in the {CANDLEHOME}/logs directory.
On Linux systems the logs kdyproc_ras1_{timestamp}.log and {hostname}_
lz_klzagent_{timestamp}-XX.log is located in the {CANDLEHOME}/logs directory.
Refer to IBM Tivoli Monitoring v 6.2 Problem Determination Guide
for more information.
The user can verify the agent is stopped by running
tacmd listSystems
:
208
IBM Tivoli Monitoring: Troubleshooting Guide