Environment
NetIQ eDirectory
Novell eDirectory 8.8 for Linux
Novell eDirectory 9.0 for Linux
SUSE Linux Enterprise Server 12
systemd
Novell eDirectory 8.8 for Linux
Novell eDirectory 9.0 for Linux
SUSE Linux Enterprise Server 12
systemd
Situation
When running 'ndsconfig new' or 'ndsmanage to create a new instance of eDirectory, the following error is returned after almost immediately as the installation fails:
Attempting the installation again results in the same scenario.
ERROR: ndsconfig return value = 10
Attempting the installation again results in the same scenario.
Resolution
Remove any hyphens (dashes) present in the configuration file's (nds.conf) path which is normally /etc/opt/novell/eDirectory/conf/nds.conf by default.
When ndsconfig returns error 10 it only means the attempt to create a new tree failed as described in the man page. As a result, seeing this error may mean there is something else wrong with the command, such as an invalid parameter, a bad environment setting, or a missing library or other dependency. A hyphen present in the path containing the nds.conf file is one known issue, but others could also exist.
When ndsconfig returns error 10 it only means the attempt to create a new tree failed as described in the man page. As a result, seeing this error may mean there is something else wrong with the command, such as an invalid parameter, a bad environment setting, or a missing library or other dependency. A hyphen present in the path containing the nds.conf file is one known issue, but others could also exist.
Cause
The way that eDirectory's ndsconfig command works in an environment with
systemd is that hyphens/dashes are used as a delimiter in the service name. Because of
this, the installer fails to distinguish delimiters used by ndsconfig
with the same character used in the nds.conf path specified when
calling ndsconfig. As a result, when using systemd a hyphen cannot be
used in the directory structure containing the nds.conf file or strings that end up in paths used to identify
the location of the nds.conf file.
There is no known limitation with regard to paths contained within the nds.conf file, for example the instance directory (vardir) or DIB directory (dibdir) properties, as neither of these are used to generate the name of the systemd service itself like the path to the nds.conf file is.
There is no known limitation with regard to paths contained within the nds.conf file, for example the instance directory (vardir) or DIB directory (dibdir) properties, as neither of these are used to generate the name of the systemd service itself like the path to the nds.conf file is.
Bug Number
907704