IBM E027SLL-H Troubleshooting Guide - Page 176

Monitoring server seeding output files are stored in different files on UNIX and Windows systems. UNIX examples: $ITM_HOME/logs/Node_ci_query_Process_ID.log $ITM_HOME/logs/Node_ci_query_Process_ID.log where : Node The system host name Process_ID The program process ID Windows example: C:\IBM\ITM\CNPS\logs\seedApp.log where: App The 3-character product code, such as knt for the Monitoring Agent for Windows OS The exact cause of the monitoring server seeding program crash has not been determined. The program has finished all seeding functions and is exiting. The crash has only occurred when only a few seeding changes are required. Seeding functions making many updates to the monitoring server tables have never resulted in this type of program crash. It is very possible that there is something unique about the system where this crash has been seen. The crash has only been observed on one internal test system, which was a Linux for AMD (Opteron) system. tacmd login fails when monitoring server is configured with LDAP authentication About this task Set the monitoring server tracing and LDAP client-side tracing on the hub monitoring server: KBB_RAS1=ERROR (UNIT:kdslg ALL) (UNIT:kdsvl ALL) (UNIT:kgllg ALL) (UNIT:kglld ALL) UNIX or Linux systems Run the following commands on the system hosting the UNIX or Linux hub monitoring server: 1. export LDAP_DEBUG=65535 2. export LDAP_DEBUG_FILE=/opt/IBM/ITM/logs/ldaptrace.txt (or whatever path/file you want) 3. rm /opt/IBM/ITM/logs/ldaptrace.txt (to remove the file before restarting the Hub) Restart the hub monitoring server. Note that these LDAP-related trace settings remain active until the monitoring server is restarted from a shell session where the variables are not exported. If the monitoring server is restarted from the same session where these variables are still exported, then the settings will be active again after restart. 158 IBM Tivoli Monitoring: Troubleshooting Guide