Reproduce the problem. As you reproduce it, any LDAP requests add trace content
to that ldaptrace.txt file.
Retrieve that ldaptrace.txt file, and the hub monitoring server log files. The hub
monitoring server logs will show any possible failures that occur leading up to the
calls to the SOAP server. The ldaptrace.txt file will show any activity and
possible failures occurring when it actually binds to the SOAP server and attempts
to lookup users.
Windows Systems
Windows systems use the same KBB_RAS1 trace settings as UNIX and Linux
systems, but enabling the additional LDAP trace requires a different procedure.
From the Manage Tivoli Enterprise Monitoring Services (MTEMS) GUI, complete
the following steps:
1. Stop the monitoring server.
2. Right-click the entry for the monitoring server, and select Advanced... -> Edit
Variables....
3. In the Override Local Variable Settings window that appears, click Add. Enter
LDAP_DEBUG for the Variable, and 65535 for the value, and click OK.
4. Click Add again and enter LDAP_DEBUG_FILEfor the Variable, and any path or
file that you wish (for example, C:\temp\ldaptrace.txt). Then click OK.
5. Click OK to save the changes.
6. Start the monitoring server. New login and LDAP-related monitoring server
activity is now logged in the LDAP_DEBUG_FILE.
When you are finished reproducing the problem and want to stop tracing, go back
to the Manage Tivoli Enterprise Monitoring Services (MTEMS) GUI and complete
the following steps:
1. Stop the monitoring server.
2. Right-click the entry for the monitoring server, and choose Advanced...-->Edit
Variables....
3. Highlight the variables and click Delete to delete both the LDAP_DEBUG and
LDAP_DEBUG_FILE variables. Then click OK to save the changes.
4. Start the monitoring server.
Some agents are displayed in the Service Console list that are
not accessible from that user interface
For instance, if you click IBM Tivoli M5 Agent Service Interface, a popup is
displayed for the User Name and Password. There is no valid user name and
password combination that will work, and you must click Cancel to get out of this
page. Other agents do not have this problem.
tacmd login fails after hub monitoring server is recycled
The tacmd login process uses SOAP to interface with the hub monitoring server
validation process. SOAP runs with the monitoring server process and also with
the IBM Tivoli Monitoring internal web server. All usually run in the same process
during a normal startup. The IBM Tivoli Monitoring internal web sever process
runs on the first IBM Tivoli Monitoring process started up. If that first process
stops, the web server swaps to another IBM Tivoli Monitoring process. The web
server supports the service console and port forwarding logic as well as SOAP.
Chapter 9. Monitoring server troubleshooting 159
To Next Page
Loading...
Need help?
General
