Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
339 views

Troubleshooting eDirectory on Linux


I know this might sound like a simplistic question, but I would like to
attempt to expand my own knowledge of eDirectory, and troubleshooting a
"dead" ndsd process.

My customer has an eDirectory server

Binary Version : 20608.00
Product Version : eDirectory for Linux x86_64 v8.8 SP6 [DS], which I
take to mean eDirectory 8.8.6 (8.8 service pack 6)

They told me that the eDirectory appeared to be "dead" on the server
since 06:30 AM. I would like to start troubleshooting the server, I know
that /var/log/messages will have the bulk of the logs but I also thought
about checking /var/opt/novell/eDirectory/log for additional
information.

I have to ask, what should be the first thing that I'm looking for that
might help, one : explain why the server went down at 6:30, and two what
might be the steps needed to ensure that this does not occur again?

Thank you,

-DS


--
dschaldenovell
------------------------------------------------------------------------
dschaldenovell's Profile: https://forums.netiq.com/member.php?userid=205
View this thread: https://forums.netiq.com/showthread.php?t=49324

Labels (1)
0 Likes
6 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Troubleshooting eDirectory on Linux

On Tue, 26 Nov 2013 19:44:02 +0000, dschaldenovell wrote:

> I know this might sound like a simplistic question, but I would like to
> attempt to expand my own knowledge of eDirectory, and troubleshooting a
> "dead" ndsd process.


How have they (you) determined that ndsd is "dead"?

What's the host operating system here?


> My customer has an eDirectory server
>
> Binary Version : 20608.00
> Product Version : eDirectory for Linux x86_64 v8.8 SP6 [DS], which I
> take to mean eDirectory 8.8.6 (8.8 service pack 6)
>
> They told me that the eDirectory appeared to be "dead" on the server
> since 06:30 AM. I would like to start troubleshooting the server, I know
> that /var/log/messages will have the bulk of the logs but I also thought
> about checking /var/opt/novell/eDirectory/log for additional
> information.


ndsd.log may yield a clue.

If there's a core file, it contains crash data and may be helpful.


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

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Troubleshooting eDirectory on Linux


Good day,

to determine if ndsd was dead, the following command was run

"rcndsd status" showed as "dead" in red - this was the procedure that
was done I assume by another engineer, the only information that I was
given was that "server xyz was down since 6:30 in the morning". However
when I looked at it, the "rcndsd status" and "ndsstat" both returned
positive results.

cat /etc/SuSE-release
SUSE Linux Enterprise Server 10 (x86_64)
Version = 10
PatchLevel = 4

cat /etc/novell-release
Novell Open Enterprise Server 2.0.3 (x86_64)
Version = 2.0.3
PatchLevel = 3
Build

Okay I found the ndsd.log is there anything specific that I should be
looking for?

Where would the core file be located?


--
dschaldenovell
------------------------------------------------------------------------
dschaldenovell's Profile: https://forums.netiq.com/member.php?userid=205
View this thread: https://forums.netiq.com/showthread.php?t=49324

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Troubleshooting eDirectory on Linux


Good day,

Here is an outputting from the ndsd.log, looks like the server was
trying to shutdown at 13:32

Backup completed successfully
Nov 26 13:32:52 Got SIGINT/SIGTERM signal, server shutting down
Nov 26 13:33:02 Unloading SSNCP...
Nov 26 13:33:02 SecretStore NCP Plugin Unloaded Successfully
Nov 26 13:33:04 SPM DClient closed
Nov 26 13:33:04 Novell PKI Services unloaded
Nov 26 13:33:06 NDS iMonitor for Novell eDirectory 8.8 SP6 v20608.00
shutdown successfully.
Nov 26 13:40:13 Path of Novell eDirectory configuration file
/etc/opt/novell/eDirectory/conf/nds.conf
Nov 26 13:40:13 Init NCPServer
Nov 26 13:40:13 DSRegisterSignalHandler succeeded for signal 63
Nov 26 13:40:13 Host process for Novell eDirectory 8.8 SP6 v20608.00
successfully started
Nov 26 13:40:13 DHLog: file size 1048576
[ -- DHost Logging STARTED Tue Nov 26 13:40:13 2013 -- ]
Nov 26 13:40:13 MASV Init called
Nov 26 13:40:13 Mandatory Access Control Service Version: 2.0.1
started
Nov 26 13:40:13 NMAS Server Version:3.3.3.6 Build:20120630 started
Nov 26 13:40:13 SPM DClient Version:3.3.3.6 Build:20120630 started
Nov 26 13:40:13 MASV Init called
Nov 26 13:40:13 MASV already initialized.
Nov 26 13:40:13 Opening NCPServer


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
Nov 26 13:40:35 volume SYS has matching attribute
Nov 26 13:40:35 CertMutual Method LSM Version:2834 Build:20120229
loaded
Nov 26 13:40:35 CertMutual Method Proxy LCM Version:2834 Build:20120229
loaded
Nov 26 13:40:35 GAMS Init called
Nov 26 13:40:35 Graded Authentication Management Service Version: 2.0.1
started
Nov 26 13:40:35 Information: SNMP Trap Server for Novell eDirectory
8.8.6 v20606.01 started.

Nov 26 13:40:36 Digest MD5 LSM Version:2800 Build:20080623 loaded
Nov 26 13:40:36 Digest MD5 Proxy LCM Version:2800 Build:20080623
loaded
Nov 26 13:40:36 Simple Password Method LSM Version:2834 Build:20120229
loaded
Nov 26 13:40:36 NDS iMonitor for Novell eDirectory 8.8 SP6 v20608.00
started successfully.
Nov 26 13:40:36 Simple Password Method Proxy LCM Version:2834
Build:20120229 loaded
Nov 26 13:40:36 Novell PKI Services Started Successfully
Nov 26 13:40:36 Novell Enhanced Smartcard Method loaded LSM Version:
3.0.7.0
We are in DHost.
Nov 26 13:40:36 PKIHealth.log in directory:
/var/opt/novell/eDirectory/log/
Nov 26 13:40:45 Loading SecretStore Server...
Nov 26 13:40:45 Novell SecretStore Service Version 3.4.3 Loaded
Successfully
Nov 26 13:40:45 Loading SecretStore LDAP Transport Plugin...
Nov 26 13:40:45 Novell SecretStore LDAP Plugin Version 3.4.3 Loaded
Successfully.
Nov 26 13:40:45 SecretStore LDAP Extension Handler Loaded Successfully
Nov 26 13:40:45 NMAS Server Version:3.3.3.6 Build:20120630 started
Nov 26 13:40:45 SPM DClient already started (2)
Nov 26 13:40:45 LDAP Agent for Novell eDirectory 8.8 SP6 (20608.00)
started
Nov 26 13:40:45 SASL Version:3.3.3.6 Build:20120630 started
Nov 26 13:43:57 Loading SecretStore NCP Transport Plugin...
Nov 26 13:43:57 Novell SecretStore NCP Plugin Version 3.4.3 Loaded
Successfully.
Command line backup -b -f /dsback/nds.bak -l /dsback/backup.log -t -w
-e XXXXXXXX
Processing command line
Backup type: Full
Log file name: /dsback/backup.log
Backup started: 2013-11-26'T20:15:2
Backup file name: /dsback/nds.bak


--
dschaldenovell
------------------------------------------------------------------------
dschaldenovell's Profile: https://forums.netiq.com/member.php?userid=205
View this thread: https://forums.netiq.com/showthread.php?t=49324

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Troubleshooting eDirectory on Linux

On Wed, 27 Nov 2013 15:24:02 +0000, dschaldenovell wrote:

> Nov 26 13:32:52 Got SIGINT/SIGTERM signal, server shutting down


Yeah, that's interesting. So who shut it down?

And then started it again, a few minutes later:

> Nov 26 13:40:13 Path of Novell eDirectory configuration file
> /etc/opt/novell/eDirectory/conf/nds.conf
> Nov 26 13:40:13 Init NCPServer


Core files would be found in the dib directory. But I don't think you'll
find one from this, because it didn't crash, it was stopped or shut down,
cleanly by the messages in the log file.


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

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Troubleshooting eDirectory on Linux

/var/log/messages will probably not be that useful unless you have a weird
issue. The ndsd log is probably the best place to look assuming the
process is really dead (non-existent now) and that is under the 'log'
directory for eDirectory.

Other than that you may want to look for a 'core' file in the DIB
directory ('data' is a sibling of 'log' by default, and 'dib' is a
subdirectory of 'data' by default). If you find a core, submit it to
NetIQ, but only if you're on current code since 8.8 SP6 is pretty old.
Since you're not current, use the novell-getcore script to package up the
core and then look at what is created, specifically in the gdb-output
files in the 'generated 'tmp' directory within the archive. This can be
interesting, and it is also pretty deep, and ultimately since you're not
current and do not have (probably anyway) the MALLOC_CHECK_ environment
variable set to '2' the core is not valid, but it's something interesting
to troubleshoot.

--
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
Anonymous_User Absent Member.
Absent Member.

Re: Troubleshooting eDirectory on Linux


Good day,

I looked in the /var/opt/novell/eDirectory/data/dib directory and there
did not appear to be a core file there. The last date of one is from the
10th of November.

I did look through the ndsd.log and I will be posting a partial of the
outputted log in the prior message. Looks like the server was shutting
down at or around 13:40 PM.


--
dschaldenovell
------------------------------------------------------------------------
dschaldenovell's Profile: https://forums.netiq.com/member.php?userid=205
View this thread: https://forums.netiq.com/showthread.php?t=49324

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.