joebrug Trusted Contributor.
Trusted Contributor.
278 views

NDSD triggering alarm in vSphere


I have about 4 OES boxes.. they vary in versions, Oes2sp2 and oes2sp3..
They all frequently show alarms in my vsphere console related to memory
or processor.. if i log into the servers and check "top" its always NDSD
process.
I don't really know where to look after that to see why its doing it..
tips?


--
#novell on efnet
------------------------------------------------------------------------
joebrug's Profile: http://forums.novell.com/member.php?userid=103
View this thread: http://forums.novell.com/showthread.php?t=450342


#novell on efnet
Labels (1)
0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: NDSD triggering alarm in vSphere

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

Are the alarms valid? Is your system working hard using a lot of memory
to do some big operation? Big operations take a lot of power so that
doesn't seem like a bad thing. If your alarms are configured to go off
at the drop of a hat then their is a problem with the alarms. If the
problem is valid then of course fix it, but do you know that it is?

If eDirectory is using a lot of memory then it's probably doing what it
thinks it must to perform well. You're welcome to impose impose
limitations on the process from the OS, but don't be surprised if things
perform less-well when ndsd cannot do as much cashing or optimizing as
it normally would, or if it crashes due to a lack of necessary
resources. If the processor is high then find out what is happening at
the time. If you have big queries that are not using indexes, add
indexes (at the expense of memory) to make that work better.

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

iQIcBAEBAgAGBQJPBfQmAAoJEF+XTK08PnB5YlEQAJDPAuFZ/ssGqOkzssA1Cc2t
+NrTy3G9kcU06yI86qTiaVSIwloPXyMKwle5Pz7/xnc8IZsrmAdHHww5nqGrHS/T
QeycT5Kd2+B5q2LD1Wo0nK52dYDqJygJj6HaypGgrSxDFEd28j5FVle/iG1z8nnk
uEajADEIwDA8TY/QygMLJqLQafu4/bb4vWZCFupwDjnGbAiT7qaIv4UX1KODRQE1
thEzdnGojQTPIqAKSXsxQEyUmREUdUaeDAcnTNY6dlvaDrCfHnQnkNhjfK3bRQq/
w64qzhd/bunmZ5Jou/GGfddQ8FG1ZSZPyD6J5y7JP4sb4hsFWSr+i8yIDPhQTe8D
I9iofTBWrTVyXwfOjV/dtOwhO4gRqbdH42oDEklHlQH3z5U8du6dQL6FzMmJvnW1
HT1CvxUcAJYiWbyyEQc+STvZ6dyrM+BiD5gAaB9VpgTRCOYwlckpeAwsbAMaPAHK
h8FyuFpXK5gkagClOnYoCwFmTy0ss7WgfT7DFA5Wya07VtrgJFqqCeAMc8EUOaBt
1grdhnCotG5jxOrz7OF+sscUt0KiBcXA058tnZet5OTeAaxTQFD1oUKEh3TASxI4
tYc57I904QU47NQNCBr4zydydLpwYYsbB4uOAtCMMvxk80JvylywJ4yZhtV9Yvsa
YN+5Y919wWTXYS5SlhHj
=GtSa
-----END PGP SIGNATURE-----
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.