IBM E027SLL-H Troubleshooting Guide - Page 208

Deploy cannot tell if the installation failed, An agent does not display in the portal client or

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 208 highlights

Table 16. Resolutions for agent deployment operations that TIMEOUT (continued) Problem A system error occurs when running a tacmd command. Resolution Increase the timeout for the tacmd setting environment variable to 3600 seconds. On Windows: Enter the following command: set timeout=3600 Note: Be aware that this command does not affect the TACMD_TIMEOUT in the KUIRAS1.log, but it does indeed change the timeout period. Another solution is to change the TACMD_TIMEOUT environment variable in the itm_home/bin/tacmd file on GNU/Linux and UNIX systems or the itm_home/bin/KUIENV file on Windows systems. The TACMD_TIMEOUT in these files must be in minutes. You can also change the environment variable in the kui.env file on Windows systems and the tacmd shell script on non-Windows systems. Both of these files can be found in the CANDLEHOME/logs directory. A failure occurs The Tivoli Enterprise Portal Server times out waiting for deployment when deploying action to complete. The default timeout is 600 seconds. You can change an agent from the the timeout setting to KFW_SQL1_ASYNC_NOTIFY_MAX_WAIT in Tivoli Enterprise kfwenv: Portal. KFW_SQL1_ASYNC_NOTIFY_MAX_WAIT=1000 KUICCN068E error when running tacmd createnode. Increase the timeout value in seconds by adding "-o TIMEOUT=3600" to the createnode command. Deploy cannot tell if the installation failed When installing an OS Agent on an endpoint that already has an OS Agent, the installation program does not write out a C:\IBM\ITM\InstallITM\Abort IBM Tivoli Monitoring 20070924 1319.log in the createNode specified directory. It writes messages to the existing C:\data\itm61_oqv_ga2_koy\InstallITM\IBM Tivoli Monitoring 20070924 1319.log log file and reports the error in that log file. An agent does not display in the portal client or in the output from the listSystems command About this task If you have multiple instances of a monitoring agent, you must decide how to name the monitoring agents. This name is intended to uniquely identify that monitoring agent. The agent's default name is composed of three qualifiers: v Optional instance name v Machine network host name v Agent product node type An agent name truncation problem can occur when the network domain name is included in the network host name portion of the agent name. For example, instead of just the host name myhost1 being used, the resulting host name might 190 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
Table 16. Resolutions for agent deployment operations that TIMEOUT (continued)
Problem
Resolution
A system error
occurs when
running a tacmd
command.
Increase the timeout for the tacmd setting environment variable to 3600
seconds.
On Windows:
Enter the following command:
set timeout=3600
Note:
Be aware that this command does not affect the
TACMD_TIMEOUT in the
KUIRAS1.log
, but it does indeed change the
timeout period.
Another solution is to change the TACMD_TIMEOUT environment
variable in the
itm_home/bin/tacmd
file on GNU/Linux and UNIX
systems or the
itm_home/bin/KUIENV
file on Windows systems. The
TACMD_TIMEOUT in these files must be in minutes.
You can also change the environment variable in the
kui.env
file on
Windows systems and the tacmd shell script on non-Windows systems.
Both of these files can be found in the CANDLEHOME/logs directory.
A failure occurs
when deploying
an agent from the
Tivoli Enterprise
Portal.
The Tivoli Enterprise Portal Server times out waiting for deployment
action to complete. The default timeout is 600 seconds. You can change
the timeout setting to KFW_SQL1_ASYNC_NOTIFY_MAX_WAIT in
kfwenv:
KFW_SQL1_ASYNC_NOTIFY_MAX_WAIT=1000
KUICCN068E
error when
running tacmd
createnode.
Increase the timeout value in seconds by adding "-o TIMEOUT=3600"
to the
createnode
command.
Deploy cannot tell if the installation failed
When installing an OS Agent on an endpoint that already has an OS Agent, the
installation program does not write out a
C:\IBM\ITM\InstallITM\Abort IBM
Tivoli Monitoring 20070924 1319.log
in the
createNode
specified directory. It
writes messages to the existing
C:\data\itm61_oqv_ga2_koy\InstallITM\IBM
Tivoli Monitoring 20070924 1319.log
log file and reports the error in that log file.
An agent does not display in the portal client or in the output from the
listSystems command
About this task
If you have multiple instances of a monitoring agent, you must decide how to
name the monitoring agents. This name is intended to uniquely identify that
monitoring agent. The agent's default name is composed of three qualifiers:
v
Optional instance name
v
Machine network host name
v
Agent product node type
An agent name truncation problem can occur when the network domain name is
included in the network host name portion of the agent name. For example,
instead of just the host name myhost1 being used, the resulting host name might
190
IBM Tivoli Monitoring: Troubleshooting Guide