iliadmin1

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-04-10
16:55
813 views
OES 2018 w/eDirectory 9.1 on SLES 12 SP3. I am seeing entry in the warn log:
2019-04-10T01:45:02.000437-04:00 edir namcd[2235]: GetGIDsGroupListNumberOfGroupsOfWS: Error [-1] in LDAP search while trying to find group FDNs with scope=base for cn=UNIX Workstation - edir,o=oes
I checked in the ndsd.log file for anything, but it looks fine, ends with the restarting of the edirectory server last night, no errors or issues in that log.
I checked the workstation-context= entry in the nam.conf and it is correct, says workstation-context=o=oes.
I did have to re-create expiring certificates on the oes server last night (after I had restarted the OES 2018 eDirectory server).
Would that certificate recreation have triggered this? Perhaps a cache of some sort?
Do I need to restart something on the OES 2018 eDirectory server to refresh everything?
Or is this due to some other cause?
The OES server is SLES 11 SP4 with eDirectory 8.8 sp8 patch 8 I believe.
Kind regards,
Val
GW 2018 & Mobility Service-Version: 18.1.0 Build: 410 on SLES 12SP3, GW Client 18.02 (Build 131493) on Windows 7 64bit; server OES 11 on SLES 11 SP3; eDirectory 9.1 on SLES12SP3 and eDirectory 8.8sp8 on SLES11 SP3
2019-04-10T01:45:02.000437-04:00 edir namcd[2235]: GetGIDsGroupListNumberOfGroupsOfWS: Error [-1] in LDAP search while trying to find group FDNs with scope=base for cn=UNIX Workstation - edir,o=oes
I checked in the ndsd.log file for anything, but it looks fine, ends with the restarting of the edirectory server last night, no errors or issues in that log.
I checked the workstation-context= entry in the nam.conf and it is correct, says workstation-context=o=oes.
I did have to re-create expiring certificates on the oes server last night (after I had restarted the OES 2018 eDirectory server).
Would that certificate recreation have triggered this? Perhaps a cache of some sort?
Do I need to restart something on the OES 2018 eDirectory server to refresh everything?
Or is this due to some other cause?
The OES server is SLES 11 SP4 with eDirectory 8.8 sp8 patch 8 I believe.
Kind regards,
Val
GW 2018 & Mobility Service-Version: 18.1.0 Build: 410 on SLES 12SP3, GW Client 18.02 (Build 131493) on Windows 7 64bit; server OES 11 on SLES 11 SP3; eDirectory 9.1 on SLES12SP3 and eDirectory 8.8sp8 on SLES11 SP3
1 Solution
Accepted Solutions


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-04-10
17:45
Other than the error, do you have anything NOT working with this box that
is running namcd?
That error, as the log shows, is from 'namcd', so it is something you may
need to check on that side. A couple commands come to mind which may or
may not be good to run:
You may want to check the documentation, and whether or not anything is
really broken, before running any commands:
https://www.novell.com/documentation/open-enterprise-server-2018/acc_linux_svcs_lx/data/adxnn04.html
--
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
is running namcd?
That error, as the log shows, is from 'namcd', so it is something you may
need to check on that side. A couple commands come to mind which may or
may not be good to run:
namconfig -k
namconfig cache_refresh
You may want to check the documentation, and whether or not anything is
really broken, before running any commands:
https://www.novell.com/documentation/open-enterprise-server-2018/acc_linux_svcs_lx/data/adxnn04.html
--
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
2 Replies


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-04-10
17:45
Other than the error, do you have anything NOT working with this box that
is running namcd?
That error, as the log shows, is from 'namcd', so it is something you may
need to check on that side. A couple commands come to mind which may or
may not be good to run:
You may want to check the documentation, and whether or not anything is
really broken, before running any commands:
https://www.novell.com/documentation/open-enterprise-server-2018/acc_linux_svcs_lx/data/adxnn04.html
--
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
is running namcd?
That error, as the log shows, is from 'namcd', so it is something you may
need to check on that side. A couple commands come to mind which may or
may not be good to run:
namconfig -k
namconfig cache_refresh
You may want to check the documentation, and whether or not anything is
really broken, before running any commands:
https://www.novell.com/documentation/open-enterprise-server-2018/acc_linux_svcs_lx/data/adxnn04.html
--
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
davidkrotil

Admiral
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2020-12-02
08:32
While namconfig cache_refresh helps, it would be fine to get proper error number . What is -1 ?