Manualshelf

Troubleshooting guide

ManualsBrandsRed Hat ManualsConsumer electronicsDIRECTORY SERVER 7.1 SP7 - S
111112113114115116117118119120
Table Of Contents
118 Novell eDirectory 8.8 SP7 Troubleshooting Guide
23.16 Troubleshooting Ports with Custom eDirectory 8.8
Instances
In eDirectory 8.8, if you configure a new instance in a custom location when the default instance
server is down, it takes the default instance ports. The default instance does not come up, because the
ports of the default instance are allotted to the custom location instance.
Follow the procedure in “Troubleshooting Ports with Custom eDirectory 8.8 Instances” (http://
www.novell.com/coolsolutions/feature/17933.html) before rebooting the host.
23.17 Rebooting the Host
Only the default instance created through using the default instance binaries is started after reboot.
You can set the paths and use
ndsmanage
to start the other instances.
23.18 ndsd Not Listening at the Loopback Address on a Given
NCP Port
When you have more than one eDirectory instance, the second instance and subsequent instances try
to listen at the default 524 port instead of the NCP port on the loopback address.
To work around this issue, set the n4u.server.tcp-port parameter of the second instance to the port
that it is supposed to listen on. The n4u.server.tcp-port parameter is located in the
nds.conf
file.
IMPORTANT: All eDirectory instances must be up before upgrading to eDirectory 8.8 SP7.
23.19 LDAP Transaction OIDs
In LDAP transaction support, the
supportedGroupingTypes
and
transactionGroupingType
OIDs
are the same (
2.16.840.1.113719.1.27.103.7
).
23.20 Errors -5871 and -5875 in LDAP Trace
The -5871 and -5875 errors in LDAP trace are usually caused when LDAP client closes forcibly
without doing an unbind. So, these errors need not be of concern and can be ignored. For more
information on these errors, refer to the Novell Error Codes Web site (http://www.novell.com/
documentation/nwec/).
23.21 NDSCons Gives -625 Error if a Tree is Renamed
If you rename the tree on the primary server and shutdown the DHost on the secondary server, the
NDSCons utility gives transport failure error message -625 on the secondary server while DHost
keeps running on both primary and secondary servers. The error occurs because NDSCons was
running on secondary server when the tree was renamed on the primary server. NDSCons works fine
if you close it and then restart it.