

Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-09-25
23:12
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!
“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!
2 Replies
rjneilly

Ensign
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-11-07
01:11
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.
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.


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-12-14
04:04
and to add to the fun of
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!
“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!