• State Suggested Answer
  • Replies replies
    5
  • Answers answer
    1
  • Subscribers subscribers
    27
  • Views views
    111
  • Users 0 members are here

Problem starting eDirectory nds services IDM 4.8.7

Cesar Morrone

Hi Team.

We have a problem starting the IDM 4.8.7 eDirectory services.

When I try to start the service using 

systemctl start ndsdtmpl-etc-opt-novell-eDirectory-conf-nds.conf@-etc-opt-novell-eDirectory-conf-env.service

And check status using 

systemctl status ndsdtmpl-etc-opt-novell-eDirectory-conf-nds.conf@-etc-opt-novell-eDirectory-conf-env.service

Show:

ndsdtmpl-etc-opt-novell-eDirectory-conf-nds.conf@-etc-opt-novell-eDirectory-conf-env.service - eDirectory service for /etc/opt/novell/eDirectory/conf/nds.conf.
Loaded: loaded (/usr/lib/systemd/system/ndsdtmpl-etc-opt-novell-eDirectory-conf-nds.conf@.service; enabled; preset: disabled)
Active: active (running) since Wed 2024-11-20 11:05:49 -04; 5h 27min ago
Process: 303970 ExecStartPre=//opt/novell/eDirectory/sbin/pre_ndsd_start_custom (code=exited, status=0/SUCCESS)
Process: 303972 ExecStartPre=//opt/novell/eDirectory/sbin/pre_ndsd_start_factory (code=exited, status=0/SUCCESS)
Process: 303978 ExecStart=/opt/novell/eDirectory/sbin/ndsdwrapper (code=exited, status=0/SUCCESS)
Process: 303984 ExecStartPost=//opt/novell/eDirectory/sbin/post_ndsd_start_custom (code=exited, status=0/SUCCESS)
Process: 303985 ExecStartPost=//opt/novell/eDirectory/sbin/post_ndsd_start_factory (code=exited, status=1/FAILURE)
Main PID: 303983 (ndsd)
Tasks: 101
Memory: 712.9M
CPU: 1min 15.857s
CGroup: /system.slice/system-ndsdtmpl\x2detc\x2dopt\x2dnovell\x2deDirectory\x2dconf\x2dnds.conf.slice/ndsdtmpl-etc-opt-novell-eDirectory-conf-nds.conf@-etc-opt-novell-eDire>
└─303983 //opt/novell/eDirectory/sbin/ndsd

Nov 20 11:04:45 TMP309 systemd[1]: Starting eDirectory service for /etc/opt/novell/eDirectory/conf/nds.conf....
Nov 20 11:04:45 TMP309 pre_ndsd_start_factory[303977]: 2738+0 records in
Nov 20 11:04:45 TMP309 pre_ndsd_start_factory[303977]: 2738+0 records out
Nov 20 11:04:45 TMP309 pre_ndsd_start_factory[303977]: 11214848 bytes (11 MB, 11 MiB) copied, 0.00289943 s, 3.9 GB/s
Nov 20 11:05:18 TMP309 post_ndsd_start_factory[303992]: NetIQ eDirectory LDAP Server is not listening on the TCP port.
Nov 20 11:05:49 TMP309 post_ndsd_start_factory[303992]: NetIQ eDirectory LDAP services are not running.
Nov 20 11:05:49 TMP309 systemd[1]: Started eDirectory service for /etc/opt/novell/eDirectory/conf/nds.conf..

And the ports 389 and 636 is not present in netstat or ss command.

The firewall is down, SELinux is disabled

SELinux status:                 disabled

users nds and novlua has a login shell

novlua:x:989:989:User created by NetIQ Identity Manager Installer:/home/users/novlua:/bin/bash
nds:x:988:987::/home/nds:/bin/bash

Its worked fine and don't kown why now don't start before reboot the machine.

Some idea?

Thanks.

Regards.

  • 0  

    Any more logs in ndsd.log? Also one idea: are LDAP ports free before starting eDirectory? Can you try logging in with iMonitor? Is it available? (https application on 8030 port) Try starting ldap module manually through there. Also this should be available via command line utility

  • 0 in reply to   

    Hi Zan.

    I don't know whta happened, but I stop the services using systemctl and start the instance using ndsmanage and the services start whitout error.

    Look:

    [root@TMP309 ~]# systemctl status ndsdtmpl-etc-opt-novell-eDirectory-conf-nds.conf@-etc-opt-novell-eDirectory-conf-env.service
    â—Ź ndsdtmpl-etc-opt-novell-eDirectory-conf-nds.conf@-etc-opt-novell-eDirectory-conf-env.service - eDirectory service for /etc/opt/novell/eDirectory/conf/nds.conf.
    Loaded: loaded (/usr/lib/systemd/system/ndsdtmpl-etc-opt-novell-eDirectory-conf-nds.conf@.service; enabled; preset: disabled)
    Active: active (running) since Thu 2024-11-21 15:19:15 -04; 17h ago
    Main PID: 444418 (ndsd)
    Tasks: 126
    Memory: 770.2M
    CPU: 4min 29.011s
    CGroup: /system.slice/system-ndsdtmpl\x2detc\x2dopt\x2dnovell\x2deDirectory\x2dconf\x2dnds.conf.slice/ndsdtmpl-etc-opt-novell-eDirectory-conf-nds.conf@-etc-opt-novell-eDi>
    └─444418 //opt/novell/eDirectory/sbin/ndsd

    Nov 21 15:19:13 TMP309 systemd[1]: Starting eDirectory service for /etc/opt/novell/eDirectory/conf/nds.conf....
    Nov 21 15:19:13 TMP309 pre_ndsd_start_factory[444414]: 2738+0 records in
    Nov 21 15:19:13 TMP309 pre_ndsd_start_factory[444414]: 2738+0 records out
    Nov 21 15:19:13 TMP309 pre_ndsd_start_factory[444414]: 11214848 bytes (11 MB, 11 MiB) copied, 0.00272974 s, 4.1 GB/s
    Nov 21 15:19:15 TMP309 post_ndsd_start_factory[444423]: NetIQ eDirectory LDAP Server is listening on the TCP port.
    Nov 21 15:19:15 TMP309 post_ndsd_start_factory[444423]: NetIQ eDirectory LDAP Server is listening on the TLS port.
    Nov 21 15:19:15 TMP309 systemd[1]: Started eDirectory service for /etc/opt/novell/eDirectory/conf/nds.conf..

    Iit it possible that if the instance is ACTIVE (ndsmanage) and try to start ndsdtmpl-etc-opt-novell-eDirectory-conf-nds.conf@-etc-opt-novell-eDirectory-conf-env.service show the error and can't establish the port? 

  • 0   in reply to 

    I would not say so, but it could be that the port was released since the last, start of IDM

  • Suggested Answer

    0  

    From my experience, the easiest way to get to see why nldap isn't loading is to:

    a) enable all trace/screen options for the ldap server

    b) make suere that nldap is stopped (# nldap -u)

    c) reset and use ndstrace with +time +tage +ldap

    d) load ldap using ndstrace: load nldap

    That will probably give some useful information.

    Also never use the service file to start ndsd, that should only happen during system start. Thereafter use ndsmanage startall / stopall (if you got more instances use the options to start / stop the single instance).

  • 0 in reply to   

    Hi man.

    Good plan to execute.

    Thanks,

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.