Highlighted
Peter Tomasi II Absent Member.
Absent Member.
7649 views

NDSD fails to stay running

Recently we had a power anomoly that dropped an entire VM server, I was able to get all but this one server up. rcndsd status says that its running but its not the case when I look at the logs.
I have included as much info here as I think can help. Please note the server and tree names have been changed to anonomize the data

I appreciate any help you can provide.
cat /etc/SuSE-release
SUSE Linux Enterprise Server 10 (x86_64)
VERSION = 10
PATCHLEVEL = 3

cat /etc/novell-release
Novell Open Enterprise Server 2.0.2 (x86_64)
VERSION = 2.0.2
PATCHLEVEL = 2
BUILD = FCS

/etc/novell/eDirectory/conf/nds.conf
Nds.conf
n4u.server.interfaces=10.10.1.23@524
n4u.server.vardir=/var/opt/novell/eDirectory/data
n4u.nds.dibdir=/var/opt/novell/eDirectory/data/dib
http.server.clear-port=8028
http.server.tls-port=8030
http.server.interfaces=10.10.1.23@8028
https.server.interfaces=10.10.1.23@8030
n4u.server.libdir=/opt/novell/eDirectory/lib64
n4u.server.configdir=/etc/opt/novell/eDirectory/conf
http.server.module-base=/var/opt/novell/eDirectory/data/nds-http/
n4u.server.log-file=/var/opt/novell/eDirectory/log/ndsd.log
n4u.nds.server-name=pdq-xyz
n4u.base.tree-name=PDQ
n4u.nds.preferred-server=PDQ-XYZ
n4u.nds.server-context=OU=XYZ.OU=DEPTS.O=TESTER
https.server.cached-cert-dn=SSL CertificateIP - pdq-xyz.XYZ.DEPTS.TESTER

/etc/opt/novell/eDirectory/conf/.edir/instances.0
Instances.0
/etc/opt/novell/eDirectory/conf/nds.conf

/var/opt/novell/eDirectory/log/ndsd.log
ndsd.log
Mar 29 12:20:35 Path of Novell eDirectory configuration file /etc/opt/novell/eDirectory/conf/nds.conf
Mar 29 12:20:37 Init NCPServer
Mar 29 12:20:37 DSRegisterSignalHandler succeeded for signal 63
Mar 29 12:20:37 Host process for Novell eDirectory 8.8 SP5 v20506.04 successfully started
Mar 29 12:20:37 DHLog: file size 1048576
[ -- DHost Logging STARTED Tue Mar 29 12:20:37 2011 -- ]
Mar 29 12:20:37 MASV Init called
Mar 29 12:20:37 Mandatory Access Control Service Version: 2.0.1 started
Mar 29 12:20:37 NMAS Server Version:3.3.2.5 Build:20110103 started
Mar 29 12:20:37 SPM DClient Version:3.3.2.5 Build:20110103 started
Mar 29 12:20:37 MASV Init called
Mar 29 12:20:37 MASV already initialized.
Mar 29 12:20:37 Opening NCPServer
Mar 29 12:20:37 NCP Server name pdq-xyz
Loader Failed:for dxevent,error dxevent: cannot open shared object file: No such file or directory,errno 2
NCP Engine Mounting Volume SYS
Primary path: /usr/novell/sys
Mar 29 12:20:40 volume SYS has matching attribute
Mar 29 12:20:40 CertMutual Method LSM Version:2820 Build:20090226 loaded
Mar 29 12:20:40 CertMutual Method Proxy LCM Version:2820 Build:20090226 loaded
Mar 29 12:20:40 Digest MD5 LSM Version:2800 Build:20080623 loaded
Mar 29 12:20:40 Digest MD5 Proxy LCM Version:2800 Build:20080623 loaded
Mar 29 12:20:40 Simple Password Method LSM Version:2800 Build:20080623 loaded
Mar 29 12:20:40 Simple Password Method Proxy LCM Version:2800 Build:20080623 loaded
Mar 29 12:20:40 GAMS Init called
Mar 29 12:20:40 Graded Authentication Management Service Version: 2.0.1 started
Mar 29 12:20:40 Information: SNMP Trap Server for Novell eDirectory 8.8.5 v20505.02 started.Mar 29 12:20:41 NDS iMonitor for Novell eDirectory 8.8.5 SP5 v20506.04 SP5 started successfully.
Mar 29 12:20:41 Loading SecretStore Server...
Mar 29 12:20:41 Novell SecretStore Service Version 3.4.2 Loaded Successfully
Mar 29 12:20:41 Loading SecretStore LDAP Transport Plugin...
Mar 29 12:20:41 Novell SecretStore LDAP Plugin Version 3.4.2 Loaded Successfully.
Mar 29 12:20:41 SecretStore LDAP Extension Handler Loaded Successfully
Mar 29 12:20:41 NMAS Server Version:3.3.2.5 Build:20110103 started
Mar 29 12:20:41 SPM DClient already started (2)
Mar 29 12:20:41 LDAP Agent for Novell eDirectory 8.8 SP5 (20506.05) started
We are in DHost.
Mar 29 12:20:42 Novell PKI Services Started Successfully
Mar 29 12:20:42 PKIHealth.log in directory: /var/opt/novell/eDirectory/log/
Mar 29 12:20:42 Novell PKI Services Started Successfully
Mar 29 12:20:42 PKIHealth.log in directory: /var/opt/novell/eDirectory/log/
Mar 29 12:20:42 SASL Version:3.3.2.5 Build:20110103 started
Mar 29 12:20:43 Loading SecretStore NCP Transport Plugin...
Mar 29 12:20:43 Novell SecretStore NCP Plugin Version 3.4.2 Loaded Successfully.
Mar 29 12:25:30 Repair utility for Novell eDirectory 8.8 - 8.8 SP5 v20506.04 Successfully loaded
Mar 29 12:25:30 Repair utility for Novell eDirectory 8.8 - 8.8 SP5 v20506.04 Successfully unloaded
Mar 29 12:25:44 Repair utility for Novell eDirectory 8.8 - 8.8 SP5 v20506.04 Successfully loaded
Mar 29 12:25:44 Repair utility for Novell eDirectory 8.8 - 8.8 SP5 v20506.04 Successfully unloaded
Mar 29 12:26:10 Got SIGINT/SIGTERM signal, server shutting down
Mar 29 12:26:20 Unloading SSNCP...
Mar 29 12:26:20 SecretStore NCP Plugin Unloaded Successfully
Mar 29 12:26:20 Novell PKI Services unloaded
Mar 29 12:26:20 SPM DClient closed
Mar 29 12:26:23 NDS iMonitor for Novell eDirectory 8.8.5 SP5 v20506.04 SP5 shutdown successfully.
Mar 29 12:26:24 Unloading SSLDP...
Mar 29 12:26:24 SecretStore LDAP Plugin Unloaded Successfully
Mar 29 12:26:24 SecretStore LDAP Extension Handler Unloaded
Mar 29 12:26:24 LDAP Agent for Novell eDirectory 8.8 SP5 (20506.05) stopped
Mar 29 12:26:24 Information: SNMP Trap Server for Novell eDirectory 8.8.5 v20505.02 stopped.
Mar 29 12:26:24 GAMS closed
Mar 29 12:26:25 MASV closed
[ -- DHost Logging STOPPED Tue Mar 29 12:26:26 2011 -- ]
Mar 29 12:26:26 Shutdown NCPServer
Mar 29 12:26:26 Shutdown NCPServer ... beginning check for packets in process
Mar 29 12:26:28 DSDeregisterSignalHandler succeeded for signal 63
Mar 29 12:26:28 ... NCPServer halted
Mar 29 12:26:28 SASL closed


Mar 29 12:20:34 pdq-xyz ntpd[5355]: ntpd 4.2.4p3@1.1502-o Tue Mar 2 17:14:50 UTC 2010 (1)
Mar 29 12:20:34 pdq-xyz ntpd[5377]: precision = 1.000 usec
Mar 29 12:20:34 pdq-xyz ntpd[5377]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Mar 29 12:20:34 pdq-xyz ntpd[5377]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Mar 29 12:20:34 pdq-xyz ntpd[5377]: Listening on interface #1 lo, 127.0.0.1#123 Enabled
Mar 29 12:20:34 pdq-xyz ntpd[5377]: Listening on interface #2 lo, 127.0.0.2#123 Enabled
Mar 29 12:20:34 pdq-xyz ntpd[5377]: Listening on interface #3 eth0, 10.10.1.23#123 Enabled
Mar 29 12:20:34 pdq-xyz ntpd[5377]: kernel time sync status 0040
Mar 29 12:20:34 pdq-xyz ntpd[5377]: frequency initialized -48.082 PPM from /var/lib/ntp/drift/ntp.drift
Mar 29 12:20:34 pdq-xyz id: nds_nss_GetGroupsbyMember: failed to init socket, status = -1
Mar 29 12:20:34 pdq-xyz id: nds_nss_GetGroupsbyMember: failed to init socket, status = -1
Mar 29 12:20:34 pdq-xyz sshd[5478]: Server listening on 0.0.0.0 port 22.
Mar 29 12:20:34 pdq-xyz suse_register: performing registration: reason=regularSync
Mar 29 12:20:38 pdq-xyz kernel: mtrr: type mismatch for d4000000,400000 old: uncachable new: write-combining
Mar 29 12:20:39 pdq-xyz zmd: NetworkManagerModule (WARN): Failed to connect to NetworkManager
Mar 29 12:20:40 pdq-xyz gdm[5956]: nds_nss_GetGroupsbyMember: failed to init socket, status = -1
Mar 29 12:20:40 pdq-xyz id: nds_nss_GetGroupsbyMember: failed to init socket, status = -1
Mar 29 12:20:40 pdq-xyz id: nds_nss_GetGroupsbyMember: failed to init socket, status = -1
Mar 29 12:20:43 pdq-xyz namcd: SIGTTOU caught
Mar 29 12:20:43 pdq-xyz namcd: SIGTTIN caught
Mar 29 12:20:43 pdq-xyz namcd: SIGTSTP caught
Mar 29 12:20:43 pdq-xyz /usr/sbin/namcd[6303]: Starting namcd..
Mar 29 12:20:43 pdq-xyz /usr/sbin/namcd[6303]: namcd populating the user hash tables
Mar 29 12:20:43 pdq-xyz /usr/sbin/namcd[6303]: namcd populating group hash tables
Mar 29 12:20:43 pdq-xyz /usr/sbin/namcd[6303]: namcd Populated hash tables
Mar 29 12:20:43 pdq-xyz /usr/sbin/namcd[6303]: Created all the threads
Mar 29 12:20:44 pdq-xyz nss: Starting Novell Storage Services (NSS)
Mar 29 12:20:44 pdq-xyz /usr/sbin/cron[6470]: (CRON) STARTUP (V5.0)
Mar 29 12:20:44 pdq-xyz nss: Start up eDir and LUM
Mar 29 12:20:44 pdq-xyz ipsmd[6424]: iPrint Manager 'xyz-iprint.Printers.XYZ.DEPTS.TESTER' has started loading.
Mar 29 12:20:44 pdq-xyz nss: Waiting (60 seconds) for eDirectory(ndsd) to start
Mar 29 12:20:45 pdq-xyz kernel: novfs: Loading module compiled for kernel version 2.6.16.60-0.54.5-smp into kernel version 2.6.16.60
-0.76.8-smp
Mar 29 12:20:45 pdq-xyz nss: ERROR: required eDirectory(ndsd) is not running. Exiting.
Mar 29 12:20:45 pdq-xyz smdrd[6765]: SMDR coming up
Mar 29 12:20:45 pdq-xyz ipsmd[6561]: iPrint Manager 'xyz-iprint.Printers.XYZ.DEPTS.TESTER' has successfully loaded.
Mar 29 12:20:46 pdq-xyz smdrd[6765]: Target name PDQ-XYZ successfully advertised with SLP
Mar 29 12:20:47 pdq-xyz smdrd[6765]: Loading TSA tsafs
Mar 29 12:20:48 pdq-xyz smdrd[6765]: Module tsafs successfully loaded
Mar 29 12:20:48 pdq-xyz smdrd[6765]: Loading TSA tsands
Mar 29 12:20:48 pdq-xyz smdrd[6765]: Module tsands successfully loaded
Mar 29 12:21:01 pdq-xyz su: PAM_NAM: pam_sm_acct_mgmt: pam_sm_acct_mgmt called without prior authentication for user [wwwrun]
Mar 29 12:21:01 pdq-xyz su: (to wwwrun) root on none
Mar 29 12:21:05 pdq-xyz zmd: Daemon (WARN): Not starting remote web server
Mar 29 12:21:31 pdq-xyz PAM-devperm[5716]: opendir(/dev/snd/*): No such file or directory
Mar 29 12:21:31 pdq-xyz pam_autoncl[5716]: pam_ncl_autologin authenticate started.
Mar 29 12:21:31 pdq-xyz pam_autoncl[5716]: Auto Login will not continue - disabled for root user
Mar 29 12:21:32 pdq-xyz gconfd (root-7802): starting (version 2.12.1), pid 7802 user 'root'
Mar 29 12:21:32 pdq-xyz gconfd (root-7802): Resolved
Labels (2)
Tags (3)
0 Likes
9 Replies
Knowledge Partner
Knowledge Partner

Re: NDSD fails to stay running

I'd guess one of two things. Either eDir corruption/problem (although hard to run a repair via iMangler/iMOnitor if ndsd isn't running)

If this is really a VM (vmware or XEN) I've had times where after a "crash" I've had to bounce the box once or twice to get things to work.

Failing that, you can follow TID #3078409 to obtain an edir core file to send to Novell for analysis.
0 Likes
Knowledge Partner
Knowledge Partner

Re: NDSD fails to stay running

kjhurni;2090760 wrote:
I'd guess one of two things. Either eDir corruption/problem (although hard to run a repair via iMangler/iMOnitor if ndsd isn't running)

If this is really a VM (vmware or XEN) I've had times where after a "crash" I've had to bounce the box once or twice to get things to work.

Failing that, you can follow TID #3078409 to obtain an edir core file to send to Novell for analysis.


Also do a "shutdown -r -F now" to force a file system check during reboot to make sure the file system is healthy.

Thomas
0 Likes
netwo Absent Member.
Absent Member.

Re: NDSD fails to stay running

have you confiugured rfl(roll forward logs)? NDSd would not start if it cant find the log.
0 Likes
Peter Tomasi II Absent Member.
Absent Member.

Re: NDSD fails to stay running

Yes indeed the server is running in a vmware environemnt, esx4.1.
The first issue I had encountered was a Grub error 17, that was fixed when I ran fsck on the reiser fs. Once it was clean that paved the way for the system to actually boot up.
I have run the shutdown -r -F command and it has not changed anything, I have downed and restarted the server a dozen or so times and still the same result.

The roll forward logs I am not sure what that is, its late here so I will look that up in the morning.
Thanks for everyones help this truly is a bizarre one. BTW this server also holds a read/write replica if that helps clarify anything.
Peter
0 Likes
Peter Tomasi II Absent Member.
Absent Member.

Re: NDSD fails to stay running

One more thing when I do a manual shutdown and start then status of ndsd, this is the message displayed. DDCGetServerName failed: -6038
0 Likes
Knowledge Partner
Knowledge Partner

Re: NDSD fails to stay running

On Tue, 29 Mar 2011 21:06:15 +0000, ptomasi wrote:

> Mar 29 12:26:10 Got SIGINT/SIGTERM signal, server shutting down


Now that's interesting. Who or what sent SIGINT/SIGTERM to ndsd?



--
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Knowledge Partner http://forums.novell.com

Please post questions in the newsgroups. No support provided via email.

0 Likes
Peter Tomasi II Absent Member.
Absent Member.

Re: NDSD fails to stay running

Here is something that I find yet even freakier.

I was looking at time stamps in my /var/opt/novell/eDirectory/data/dib folder and have observed the following

-rw------- 1 root root 9531392 Mar 30 07:13 nds.db
-rw------- 1 root root 9531392 Mar 30 07:16 nds.db
-rw------- 1 root root 9531392 Mar 30 07:19 nds.db

So the time stamp is updating every 3 minutes yet NDSD is reporting as Dead
/var/opt/novell/eDirectory/data/dib # rcndsd status
DDCGetServerName failed: -6038
dead
It does have a running pid
/var/opt/novell/eDirectory/data/dib # ps aux |grep ndsd
root 27614 103 1.6 554740 68688 ? Sl 02:55 277:57 //opt/novell/eDirectory/sbin/ndsd
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: NDSD fails to stay running

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That's not too freaky.... a script could have any number of reasons for
typing 'dead' but in the end your check with 'ps' is the better one since
it shows that ndsd is, indeed, running and that it is, therefore, likely
updating the file as things happen. Checking from my /etc/init.d/ndsd
script that could happen anytime the following command does not return
successfully:

$bindir/ndsstat --config-file $default_config_file > /tmp/nds.stat.$$

So what can cause that? I suppose quite a few things. Anyway, there you go.

Good luck.






On 03/30/2011 05:36 AM, ptomasi wrote:
>
> Here is something that I find yet even freakier.
>
> I was looking at time stamps in my /var/opt/novell/eDirectory/data/dib
> folder and have observed the following
>
> -rw------- 1 root root 9531392 Mar 30 07:13 nds.db
> -rw------- 1 root root 9531392 Mar 30 07:16 nds.db
> -rw------- 1 root root 9531392 Mar 30 07:19 nds.db
>
> So the time stamp is updating every 3 minutes yet NDSD is reporting as
> Dead
> /var/opt/novell/eDirectory/data/dib # rcndsd status
> DDCGetServerName failed: -6038
>
> dead
> It does have a running pid
> /var/opt/novell/eDirectory/data/dib # ps aux |grep ndsd
> root 27614 103 1.6 554740 68688 ? Sl 02:55 277:57
> //opt/novell/eDirectory/sbin/ndsd
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJNkziwAAoJEF+XTK08PnB5W9MQAIOS8cKvIvR0YCRemc2Tzo8w
7UA+nGsOTtDpcXGvWGfOGnziqaWaxmkMVeS5OOB8zvp4lmwsVFBtBZiXGihZNsFW
BtKHvx0kiG+Lu25EiQ0NR2pb4jO9xxTGRiSNoxCOhj2qjind5UxlJ77TdlpzffBE
wiOBeCEa33+yN7lguOzydOlvhM8il2/m6FtyaCAV8txuBzXeUMIfzOFk5yrJnvVC
G67dZo8KfFFujYZeVcRaeHt90Lwbc3ZejHEu2vISQj5BATjneAqfQHh5Jj7JDmkZ
D7gmrU16p141+c98M6cW9D/l5Qqlsh8CrwaWXqaIbalwtpXzdyuiBlcWE/6BaRAn
Uc952KpFByA9X/z/I5GWAxMOE/84xFpYeHBSslxGbDvy1BoIXwT9LtYkjIGVi5J5
wJ/W4Evq+WS5ynAz0kHHg0MegjEgVfKOrXMqO5mCovGVfdya5JQo/Ue9PHTFROyx
XO4lPpb26ZUIi+fXemKTDHVGLme92QvXh5/Y5kMuiMEpZJvii6pRoy0BL9+xCPux
FTaLwwW1ri0eLS2AbZ1mA8LfDFlBK7RV47ob6MXzVKwx6WtbHbrdidBC/yMPQpxz
ZZhJQyHYneUppsV0SQassACtIvtu9Vl+iJGqabxg0AdlQKS6yFvW5oMS7l6fg5yC
rfE+3odzryB1a2Wwtmxs
=T5Tu
-----END PGP SIGNATURE-----
0 Likes
Peter Tomasi II Absent Member.
Absent Member.

Re: NDSD fails to stay running

Worked with Novell today found that the local dib was corrupt. We restored a backup that was on the server, tested it and once edir was found to be working he then deleted the server from the replica. After that ran cleanup on the local server, cleared backlinks etc. Then we added the server back to the replica ring and its all happy now.
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.