Highlighted
Anonymous_User Absent Member.
Absent Member.
700 views

DDCGetServerName failed: -6038 in eDirectory


Good afternoon we saw a strange issue on our 23 node cluster this
morning.

The Cluster was restarted last night as part of an ongoing maintenance
issue, when all the Nodes came back up things looked like they were
running normally. However on Node 1, there was an issue when you
performed an rcndsd status you were getting the following error, rcndsd
status dead

When we did rcndsd start it would look like ndsd was running, but in
reality the service was dead. Following TID 7010298 DDCGetServerName
failed: -6038 in eDirectory we found that the error code matched what we
were seeing on the menu screen

running an ndsrepair -T from the Master replica server did not reveal
any errors, actually was able to contact a2c1s01 as if ndsd was actually
running, which we know was not. Further using the df -h the "/" volume
was actually at 21% filled, basically over 200 GB free.

The two volumes that were on that Node would not allow you to access
them, the Novell login screen would pop up asking you to login which
would fail, in the end we restarted the Node, but were confused why 1.)
ndsrepair -T revealed no errors when ran from the Master replica server,
2.) df -h showed plenty of space,

Any thoughts?


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

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

Re: DDCGetServerName failed: -6038 in eDirectory

On Tue, 21 Aug 2012 17:44:01 +0000, dschaldenovell wrote:

> When we did rcndsd start it would look like ndsd was running, but in
> reality the service was dead.


Does "ps ax | grep ndsd" show one or two ndsd processes?


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

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

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DDCGetServerName failed: -6038 in eDirectory


We did not have a chance to try that yesterday, we instead rebooted the
Node, and migrated the resources. I have looked on some of my test boxes
and they show two processes. An example is below:


3473 ? Sl 28:15 /opt/novell/eDirectory/sbin/ndsd
9233 pts/0 S+ 0:00 grep ndsd


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

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DDCGetServerName failed: -6038 in eDirectory

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

No, that's just one process. Looks normal. The "second process" is
grep finding itself because its own parameter is the thing for which it
is searching; this happens all of the time and is why 'pgrep' is such a
neat command, or else just append as shown below:

ps aux | grep ndsd | grep -v grep

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

iQIcBAEBAgAGBQJQNM+XAAoJEF+XTK08PnB5LmQP/37GMDDch7raFR7kg8beYYVl
KH9KB8cfuTASLD8rCf/Cc4ZCOuD62SL4ZdxzmdUq24u73dvE/jFxWu4Mo5gAR5S1
CuGWiM9ccUUwwYG08hDcLSJULgxGtqUhkBHhO+Z9SuFRa5yt4rQ68QC8IalyyoVi
MFssm74EqvT27p/FkbA7meijNQXHkyxSIeqSsTnLYn9UIVdHwEfXe/kGYEpeAGJE
xZGPWlnRkGO73Y7eKz8M+1Kyc00pBltGhueC6HYbUEz/uz1CXGFauXxJC/6RRsUw
OAqkh1cTpqgEwuCPWz9zC35PMhlX91h/C2ALZCZ2ovNlVZ3YwcTXxFVbYje1Qk2a
MvlAKNMOHqTCDE0UICa9ma1a1vJEWUJWiHzOBp03iJ43zv/GgFJm+azZt6KvgypV
F43hQNwRSTIdAJt1fwlySV/hu5AkuFGxqD6IU+RPnoTX918WYsH07X1cHtRguHfV
fZYQex7blCaPwX5w+luTZ7z9lmWAKct4toOWuEqzU57Th9BsLtQ/Kx28PjK7+yWn
LuzGswpVOvXq51MjdaLCanTSQoTshorRDw6v72cW9gUO8/vKCihvRAm2Hz1wrZvm
23oVmmi8Vb2yvIc0uUNT4tn751z6iPB4b2xTg3SqjfpnEjCrcdNllEmhCWwpbPfR
YXKsUsJNEnxxw6EBFPzv
=kzNy
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DDCGetServerName failed: -6038 in eDirectory

On Wed, 22 Aug 2012 12:14:01 +0000, dschaldenovell wrote:

> We did not have a chance to try that yesterday, we instead rebooted the
> Node, and migrated the resources. I have looked on some of my test boxes
> and they show two processes. An example is below:
>
>
> 3473 ? Sl 28:15 /opt/novell/eDirectory/sbin/ndsd 9233 pts/0
> S+ 0:00 grep ndsd


Well, not really. They show one 'ndsd' process, and one that's your
'grep' looking for it.

This is what you should see. If you can reproduce the problem, I'm
curious to know if you see two like:

3473 ? Sl 28:15 /opt/novell/eDirectory/sbin/ndsd 9233 pts/0

I've seen sporadic reports of that happening, when it shouldn't but I've
never seen it happen myself.


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

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

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DDCGetServerName failed: -6038 in eDirectory


Sorry to jump in on an older thread, but wanted to share our recent
experience with -6038... This is a non-cluster node, nds (primarily via
ldap) failed to respond. Running ndsstat gave :

Code:
--------------------
[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf: mgmtsrvr-va1.OU=OPERATIONS.OU=VA.O=xxxxxx.xxxx-TREE
DDCGetServerName failed: -6038
--------------------
and claimed the process to be dead, although 'ps' showed the process
still running.

Found TID7010298, and we are running IDM, but disk space is not an
issue here.

Then found in /var/opt/novell/eDirectory/log/ndsd.log the following:

Code:
--------------------
1400756544: RECM: [Mon Sep 24 10:34:59 2012] FATAL: DB : ERROR: Flaim IO error in lowLevelWrite: pwrite2 29, fd 0, iBytesWritten -1, uiBytesToWrite 1024, ui64WriteOffset 0,
1400756544: RECM: [Mon Sep 24 10:34:59 2012] FATAL: DB+: i 1
--------------------


Did a 'rcndsd restart' which threw a couple java exceptions (related to
the IDM drivers), then logged "WARNING: ndsd process is still running.
Killing ndsd." and then finally ndsd started and all seems to be ok.
Now to track down the FLAIM error. Interestingly, we had this same IO
error once before back on December 28, but not again until today.


--
mstatman
------------------------------------------------------------------------
mstatman's Profile: https://forums.netiq.com/member.php?userid=1078
View this thread: https://forums.netiq.com/showthread.php?t=2500

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DDCGetServerName failed: -6038 in eDirectory


I did a ps -A and I did see that "ndsd" is indeed showing as a running
process. As of this time I cannot "kill" that process, because a
GroupWise post office is currently running on that server as of now. I
would like to try that method first, "kill" the "ndsd" process, and then
try to restart "ndsd" however; I cannot make that decision, the customer
has to decide how to proceed.

I'm happy though with the fact that I was seeing a similar issue to what
you described.


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

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.