Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Knowledge Partner Knowledge Partner
Knowledge Partner
802 views

How to stop NIT from complaining if no AD hooked up

All the NSS OES 2015+ boxes at a client without any Microsoft Active Directory (acronym really should be MAD 😉 are getting a series of errors in /var/log/messages every few minutes (varies in range of 10 to 60 minutes, no nice pattern) Always the same 4 messages.
How can I stop those without breaking OES from any future interaction with AD if it happens to be introduced.

 

 

.. nitd[3312]: [NIT_THRD 0x7fa8f5740700]: ERROR: nitd_get_domain_admins_sid: Error, NIT is configured to run in eDirectory only mode.
.. ndpapp[23200]: [NIT_IPC  0x7f98a3401700]: ERROR: nitlib_get_domain_admins_sid: Error response from nit  for getting the Domains Admins group SID, error: -9008
.. nitd[3312]: [NIT_THRD 0x7fa8f5740700]: ERROR: nitd_get_adlicense_group_handler: Error, NIT is configured to run in eDirectory only mode.
.. ndpapp[23202]: [NIT_IPC  0x7f98a3c02700]: ERROR: nitlib_get_adlicense_group: Error response from nitd for getting the AD license group details, error: -9008

 

 

 

 

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
Labels (1)
Tags (2)
0 Likes
2 Replies
Ensign
Ensign

This behaviour is document for OES2015 back in 2016. Here is the TID: https://support.microfocus.com/kb/doc.php?id=7017654
The TID says it is fixed "... has been resolved with the Scheduled Maintenance Update for May '16 (May 2016 Update - OES 2015 10911)" But clearly it has become unfixed, or it never was truly fixed.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

and to add to the fun of

TID: https://support.microfocus.com/kb/doc.php?id=7017654

on the systems without NSS (i.e. not running nit)  I am getting a logrotate error as the /etc/logrotate.d/novell-nit file is missing the "missingok" flag casing logrotate to kick errors and appear to hang.  Now to see if having added the missing 'missingok' tag clears those issues and doesn't find anymore.

 

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
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.