Highlighted
Absent Member.
Absent Member.
581 views

edir 8.8.8.5x not auto-starting on SLES 12

I built a new SLES 12 server to replace our current IDM box. Installed edir drom eDirectory_88SP8_Patch4_SLES12_RHEL7.iso and then applied patch 5. Added it to our tree using ndsconfig add and seems to work fine but I can't get eDir to auto-start at boot.

Is this because I did not use ndsmanage to add the server to our tree? How can I fix?

Thanks,

Al Hidalgo
UNM Hospitals

Labels (1)
0 Likes
4 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: edir 8.8.8.5x not auto-starting on SLES 12

Try running 'ndsconfig upgrade' to see if it will help. I do not know
that it will, but maybe it will per the following TID for a
similar-sounding-ish issue:

https://www.novell.com/support/kb/doc.php?id=7016766


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: edir 8.8.8.5x not auto-starting on SLES 12

Did not fix the auto-start issue. ndsmanage starts and stops it fine but ndsd not does start on a reboot.

Al

On 8/27/2015 at 1:36 PM, ab<ab@no-mx.forums.microfocus.com> wrote:

Try running 'ndsconfig upgrade' to see if it will help. I do not know
that it will, but maybe it will per the following TID for a
similar-sounding-ish issue:

https://www.novell.com/support/kb/doc.php?id=7016766


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: edir 8.8.8.5x not auto-starting on SLES 12

On 27/08/2015 20:57, Al Hidalgo wrote:

> Did not fix the auto-start issue. ndsmanage starts and stops it fine
> but ndsd not does start on a reboot.


I wonder if it's due to the following Upgrade Issue with eDirectory 8.8
SP8 Patch 5 for Linux[1]:

--begin--
On SLES 12 Platform After Upgrading to the Latest Patch the eDirectory
Variables are Lost

After upgrading to the latest patch, the eDirectory related environment
variables in the env file located in /etc/opt/novell/eDirectory/conf
directory needs to be re-entered.

NOTE:To avoid this issue , before upgrading to Patch 5 backup the
environment file.
---end---

HTH.

[1]
https://www.netiq.com/documentation/edir88/edir888_unix_readme/data/edir888_unix_readme.html#b1cp8vx0
--
Simon
Novell/NetIQ Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: edir 8.8.8.5x not auto-starting on SLES 12

No, this was not an upgrade. I installed edir from eDirectory_88SP8_Patch4_SLES12_RHEL7.iso and then applied patch 5 before bring the server into our directory.

env:
NDS_CONF="/etc/opt/novell/eDirectory/conf/nds.conf"
TEXTDOMAINDIR="//opt/novell/eDirectory/share/locale"
libdir="//opt/novell/eDirectory/lib64"
LD_LIBRARY_PATH=//opt/novell/eDirectory/lib64://opt/novell/eDirectory/lib64/ndmodules://opt/novell/eDirectory/lib64/apr://opt/novell/lib64:/opt/novell/lib64:$LD_LIBRARY_PATH
PATH=$PATH:/usr/local/bin:/usr/bin:/bin
sbindir="//opt/novell/eDirectory/sbin"

nds.conf:
n4u.server.vardir=/var/opt/novell/eDirectory/data
n4u.nds.dibdir=/var/opt/novell/eDirectory/data/dib
n4u.server.interfaces=10.235.119.66@524
http.server.clear-port=8028
http.server.tls-port=8030
http.server.interfaces=10.235.119.66@8028
https.server.interfaces=10.235.119.66@8030
n4u.server.libdir=/opt/novell/eDirectory/lib64
n4u.server.configdir=/etc/opt/novell/eDirectory/conf
n4u.server.xdas-conf=/etc/opt/novell/eDirectory/conf/xdasconfig.properties
http.server.module-base=/var/opt/novell/eDirectory/data/nds-http/
n4u.server.log-file=/var/opt/novell/eDirectory/log/ndsd.log
n4u.cluster.nodes=n4u.cluster.nodesuh-idm
n4u.nds.server-name=uh-idm
https.server.cached-cert-dn=IP AG 10\.235\.119\.66 - uh-idm.PWS.MC.HSC
n4u.base.tree-name=UNMHSC
n4u.nds.preferred-server=UH-IDM
n4u.nds.server-context=OU=PWS.OU=MC.O=HSC

Filesystem:
/boot is ext4
/ is ext4

It's a VM under ESX.

Al


On 8/28/2015 at 5:38 AM, Simon Flood<smflood@no-mx.forums.microfocus.com> wrote:

On 27/08/2015 20:57, Al Hidalgo wrote:


> Did not fix the auto-start issue. ndsmanage starts and stops it fine
> but ndsd not does start on a reboot.


I wonder if it's due to the following Upgrade Issue with eDirectory 8.8
SP8 Patch 5 for Linux[1]:

--begin--
On SLES 12 Platform After Upgrading to the Latest Patch the eDirectory
Variables are Lost

After upgrading to the latest patch, the eDirectory related environment
variables in the env file located in /etc/opt/novell/eDirectory/conf
directory needs to be re-entered.

NOTE:To avoid this issue , before upgrading to Patch 5 backup the
environment file.
---end---

HTH.

[1]
https://www.netiq.com/documentation/edir88/edir888_unix_readme/data/edir888_unix_readme.html#b1cp8vx0
--
Simon
Novell/NetIQ Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.