IBM E027SLL-H Troubleshooting Guide - Page 190
Linux OS agent fails to start
![]() |
View all IBM E027SLL-H manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 190 highlights
Linux OS agent fails to start On some Linux systems (SUSE 10, Linux Itanium) there is a problem with OS agent operation after deployment. The current workaround is to use the -o KDYRXA.AUTOCLEAN=NO option when executing the tacmd createnode command to deploy the OS agent to a remote node. This option places the transferred installation image in the system temporary directory on the remote node. OS agent start command fails If you receive an error message indicating that your OS agent start command has failed, you might have exceeded the maximum number of supported processes while using the IP.PIPE network protocol. The host using the IP.PIPE network protocol is limited to 16 Tivoli Monitoring processes. You can identify the issue by noting the agent server process exiting unexpectedly with the following key messages: (4E85BA02.005E-1:kdcsuse.c,119,"KDCS_UseFamily") status=1c010005, "cant bind socket", ncs/KDC1_STC_CANT_BIND_SOCK (4E85BA02.005F-1:krabrreg.cpp,1289,"CTRA_reg_base__Load") Use family failed, family=34, st=1c010005 (4E85BA02.0060-9:kde12li.c,189,"KDE1_ServerListen") Status 1DE0002C= KDE1_STC_SERVERNOTBOUND (4E85BA02.0061-9:kdcs1li.c,126,"Listen") KDE1_ServerListen(0x1DE0002C) (4E85BA02.0062-1:kraaumsg.cpp,143,"CTRA_msg_server_exit_status") CTRA Server: exit status, 0 These messages indicate that the server cannot bind a socket and that the server is exiting. This behavior is a known limitation. Specific events are not monitored by the Windows OS agent You might encounter a problem monitoring specific events with the Windows OS Agent. When running IBM Tivoli Monitoring V6.2.3 Fix Pack 1 (or later), you have the capability to display events and event data from any event log you are monitoring. However, the Log Name and Log Name (Unicode) attributes represent input fields, not output fields. Filtering on the event log name is not supported. You must specify the exact name of the event log you want to monitor. The Windows Registry Editor lists the event log name as a key in either of two paths: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\ Channels The name of the event log is the key listed under the Eventlog or Channels key. For example, the Internet Explorer event log has the key HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Services\Eventlog\Internet Explorer and the Channels\Microsoft-Windows-TaskScheduler/Operational event log channel has the key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ WINEVT\Channels\Microsoft-Windows-TaskScheduler/Operational Take action commands and reflex automation Attributes differ between the situation action commands and what is displayed in the portal client The raw data delivered by an monitoring agent is a string or number. The Tivoli Enterprise Portal has format information to control the display. When an attribute 172 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
![]() |
![]() |
![](/manual_guide/products/ibm-e027sllh-troubleshooting-guide-7c8d102/190.png)