Introduction to IBM Tivoli Directory Server 6.0 – Debugging Excerpt taken from presentation given on April 10, 2007Explore methods to debug a failed IBM Tivoli Directory Server instance creation
Introduction to IBM Tivoli Directory Server 6.0 – Debugging Excerpt taken from presentation given on April 10, 2007 Explore methods to debug a failed IBM Tivoli Directory Server instance creation
Basic Debugging – Failed Instance Creation
Basic Debugging – Failed Instance Creation The idsicrt utility provides us with the functionality to trace a failed instance creation and configuration attempt. idsicrt [-I instancename [-e encryptseed] [-p port] [-s secureport] [-a admport] [-c admsecureport] [-t dbinstance] [-C] [-i ipaddress] [-l instlocation] [-r description] [-d debuglevel] [-b outputfile] [-q] [-n]] | -v | -? So using our example from our previous example we would run: #ldtrc on #idsicrt -I nativein -e seedfornativein -p 10389 -s 10636 -a 3550 -c 3553 -t nativein -l /home/nativein -d 65535 -b /tmp/idsicrt.out
Basic Debugging – Failed Instance Creation
Basic Debugging – Failed Instance Creation Common instance creation errors Cannot create additional instance because of invalid IP address On AIX, Linux, Solaris, and HP-UX systems, if you have two IP addresses configured, and you try to configure two directory server instances that use the two IP addresses, you might receive an error.
Basic Debugging – Failed Instance Creation
Basic Debugging – Failed Instance Creation For example, assume that you have IP addresses 9.42.40.67 and 9.42.40.125 configured, and you use the following commands to create directory server instances that use these IP addresses: # idsicrt -I svtinst3 -i 9.42.40.67 # idsicrt -I svtinst4 -i 9.42.40.125 You might receive an error message like this one when you try to create the second instance: [root@tvt5067 root]# idsicrt -I svtinst4 -i 9.42.40.125 GLPCTL062E The specified IP Address '9.42.40.125' is not a valid IP address for this machine.
Basic Debugging – Failed Instance Creation
Basic Debugging – Failed Instance Creation The problem might be one of the following: The Host IP addresses file does not have the correct entry for the second IP address. For example, on Linux systems, the /etc/hosts file must have the second IP entry in the correct format. For example: 9.48.181.173 mymachine.mylocation.ibm.com mymachine The system settings must be such that the system first checks the Host IP addresses file instead of performing a DNS lookup. The setting in the operating system Name service switch file must be changed to perform Host IP resolution lookup before going to the DNS.
Copyright and trademark information
Copyright and trademark information © Copyright IBM Corporation 2000 - 2007. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM web site pages may contain other proprietary notices and copyright information which should be observed. IBM trademarks http://www.ibm.com/legal/copytrade.shtml#ibm Fair use guidelines for use and reference of IBM trademarks http://www.ibm.com/legal/copytrade.shtml#fairuse General rules for proper reference to IBM product names http://www.ibm.com/legal/copytrade.shtml#general Special attributions IBM, the IBM logo and DB2 are trademarks of International Business Machines Corporation in the United States, other countries, or both. MMX, Pentium, and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. Microsoft and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product or service names may be trademarks or service marks of others.