Troubleshooting Adapters; Adapter Startup Errors; All Adapters; Managed Node Adapters - IBM Enterprise Console Manual

Troubleshooting Adapters

The following sections list troubleshooting guidelines for the different types of
adapters.

Adapter Startup Errors

If the adapter fails to start, look in the /tmp directory for the tecadEH.log file. You
might be able to learn why the adapter failed from reading this file. The following
list shows examples of errors you might find in tecadEH.log:

All Adapters

1. You receive a connection error when using wpostemsg or postemsg. The error
2. If the adapter receives the event and you can determine (through tracing or
3. If the event was sent to the event server, verify that the event server is actually
4. Check the cache files to see if the event was cached.

Managed Node Adapters

1. Use the tracing and debugging options detailed in each chapter. This helps
2. Use Tivoli Management Framework debugging output of the odstat and wtrace
3. Use the managed node wpostemsg command from the system the adapter is

Endpoint Adapters

1. Use the wep ls command to make sure that the endpoint appears under the
2. Source the endpoint environment and edit the last.cfg file in $LCF_DATDIR.
indicates that you might be using a user ID other than Administrator or root.
Thus, your ID does not have the correct permissions to create and write the file
specified by the BufEvtPath keyword.
debugging) that the event matches the correct class, use the tracing output to
verify if the event was sent to the event server, not sent, or cached. If the event
was not sent to the event server, check the adapter configuration file to see if
that class was filtered out.
running. Then run the wtdumprl command to check to see if the event server
received the event but failed to parse the event correctly. Also check the current
rule base rules to see if the event was dropped. See the IBM Tivoli Enterprise
Console Reference Manual for more information about wtdumprl.
determine if the adapter receives the event and how the adapter handles the
event.
services. These services show what occurs after the adapter tries to send an
event from the managed node oserv service to the IBM Tivoli Enterprise
Console oserv services, and they also help debug problems that occur during
Adapter Configuration Profile (ACP) distributions.
running on to see if the event arrives at the event server. See the IBM Tivoli
Enterprise Console Reference Manual for more information.
Tivoli Management Framework gateway you want. See the IBM Tivoli Enterprise
Console Reference Manual for more information. Also make sure that any Tivoli
Management Framework gateway the endpoint can log on to has ACF
installed.
Set log_threshold to 3 and then stop and restart the endpoint to enable
endpoint tracing to the lcfd.log file. Check to make sure that the endpoint
logged into an appropriate Tivoli Management Framework gateway.
Chapter 1. Understanding Adapters
21