|
| |
| Sun Java(TM) System Directory Server 5 2004Q2 Administration Guide | |
Chapter 16
Troubleshooting Directory ServerThis chapter provides basic troubleshooting information on installing Directory Server.
Troubleshooting Installation
Table 16-1 Common Installation Problems With Solutions
Problem
Possible Solutions
I get a message about missing libraries.
Run idsktune and fix at least all ERROR conditions, installing all recommended patches.
Installation did not work, and now I cannot uninstall. What do I do?
Removing the product registry file unless doing so would negatively impact other products:
Next, remove the partially installed files by hand before reinstalling.
Installation failed and I do not know why. Is there an installation log somewhere?
Yes. The log can be found under the following location:
Clients cannot locate the server.
Try using the host name such as dirserv.
If that does not work, make sure the server is listed in the name service you are using such as DNS, and try the fully qualified domain name such as dirserv.example.com.
If that does not work, try using the IP address for the host such as 192.168.0.30.
The port is in use.
If upgrading, you probably did not shut down Directory Server before you upgraded it. Shut down the old server, then manually start the upgraded one.
Otherwise, another server might be using the port. Examine which ports are in use with an appropriate tool such as the netstat(1M) utility with the -a option on UNIX systems to determine which ports remain available.
An LDAP authentication error causes installation to fail.
You may have provided the incorrect fully qualified domain name during installation, such as dirserv.nisDomain.Example.COM instead of dirserv.example.com.
I have forgotten the Directory Manager DN and password.
The Directory Manager DN is recorded as the value of nsslapd-rootdn in ServerRoot/slapd-serverID/config/dse.ldif.
The Directory Manager password is recorded as the value of nsslapd-rootpw in dse.ldif. If the password is not encrypted — we strongly recommend you encrypt it! — then it appears in dse.ldif in clear text, not prefixed with an encryption scheme identifier such as {SSHA}.
If the password is encrypted, you must fix the problem manually.
1. Stop Directory Server.
2. Change the value of nsslapd-rootpw in dse.ldif, taking care not to add trailing spaces.
3. Save and close dse.ldif.
4. Restart the server.
5. Login as Directory Manager using the value you assigned to nsslapd-rootpw.
6. Set an encryption scheme for the Directory Manager password as described in the Directory Server Administration Guide, and then change the password again.
I installed the 32-bit version of the Directory Server by mistake.
How do I run the 64-bit version instead?
1. Export all suffixes to LDIF as described in the Directory Server Administration Guide.
2. Remove all database files.
Database files are found under the path indicated by the value of nsslapd-directory on cn=config,cn=ldbm database,cn=plugins,cn=config for the instance.3. Install 64-bit components if you have not done so already.
4. Make ServerRoot/bin/slapd/server/64/ns-slapd executable.
5. If the operating system is running in 32-bit mode, reboot it in 64-bit mode.
6. If necessary, change cache size settings to work in 32-bit mode.
7. Initialize all suffixes with the LDIF you exported as described in the Directory Server Administration Guide.
8. Restart the server.
I installed the 64-bit version of the Directory Server by mistake.
How do I run the 32-bit version instead?
1. Export all suffixes to LDIF as described in the Directory Server Administration Guide.
2. Remove all database files.
Database files are found under the path indicated by the value of nsslapd-directory on cn=config,cn=ldbm database,cn=plugins,cn=config for the instance.3. Change the mode of ServerRoot/bin/slapd/server/64/ns-slapd so it is not executable.
4. Initialize all suffixes with the LDIF you exported as described in the Directory Server Administration Guide.
5. Restart the server.
I wrote a script to handle installation. When I tried installing using my script, the installer returned 73, rather than 0.
What is going on here?
The installation program return codes are as follows:
0 - SUCCESS
1 - WARNING_REBOOT_REQUIRED
2 - WARNING_PLATFORM_SUPPORT_LIMITED
3 - WARNING_RESOURCE_NOT_FOUND
4 - WARNING_CANNOT_WRITE_LOG
5 - WARNING_LOCALE_NOT_SUPPORTED
50 - ERROR_FATAL
51 - ERROR_ACCESS
52 - ERROR_PLATFORM_NOT_SUPPORTED
53 - ERROR_NO_WINDOWING_SYSTEM_AVAILABLE
54 - ERROR_RESOURCE_NOT_FOUND
55 - ERROR_TASK_FAILURE
56 - ERROR_USER_EXIT
57 - ERROR_CANNOT_UPGRADE
58 - ERROR_NOTHING_TO_DO
59 - ERROR_IN_SERIALIZATION
60 - ERROR_ABNORMAL_EXIT
61 - ERROR_INCOMPATIBLE_STATEFILE
62 - ERROR_UNKNOWN_COMMANDLINE_OPTION
70 - ERROR_NOT_INSTALLED
71 - PARTIALLY_UNINSTALLED
72 - FULLY_UNINSTALLED
73 - INSTALLED
74 - ERROR_FAILED
75 - ERROR_STOPPED
76 - ERROR_STOPPED_ON_ERROR
77 - PARTIALLY_INSTALLEDIn other words, 73 indicates successful installation.