Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Private CLI for 'vserver services name-service ldap check' returns 'Loop detected in next()'
2024-07-02
11:16 AM
824 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello community
we are getting 'Loop detected in next()' errors when invoking 'vserver services name-service ldap check' via Private CLI
curl -k -X GET "https://XXXXX:443/api/private/cli/vserver/services/name-service/ldap/check?return_timeout=120&return_records=true&vserver=XXXXX&privilege_level=diagno..." -u admin
Enter host password for user 'admin':
{
"records": [
],
"num_records": 0,
"error": {
"message": "Loop detected in next() for table ldap_check. Next on \"XXXXX\" returned \"XXXXX\".",
"code": "262146"
}
}
Same command in CLI works fine
Cluster is running 9.10.1P12
Is this a known issue and fixed in later releases?
Any thoughts on how we might be able to overcome this issue?
thank you
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@nainfo Did you find the solution or workaround for above issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
using, /api/name-services/ldap?svm.name=name . this will give something like below output.. this output is almost similar to cmd " ldap check -vserver name "
