- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Regards,
The system displays the following error when I try to update the LDAP Server:
Encountered The Following error while trying to update: Splunkd daemon is not responding : ( u'Error connecting to / servicesNS / nobody / system / authentication / providers / LDAP /<Server Name> : The read operation timed out ' )
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You may have logged in using a LDAP account. Make sure to use a local account when making LDAP configuration changes
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

I get the same error when changing password and using the local splunk admin account. We have a 2nd searchhead cluster for ES that had no issue, and all of the setting are the same.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content


@robjackson This thread is more than two years old with an accepted answer. For a better chance at a helpful response, please post a new question describing your problem.
If this reply helps you, Karma would be appreciated.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You may have logged in using a LDAP account. Make sure to use a local account when making LDAP configuration changes
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Hello Yungro ,
In fact I did not notice this detail . I will do according to their orientation.
Thanks man.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Hi @ppblo
Sorry for the delay. I have not had time to test this solution because this problem has occurred in the customer environment.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

No worries @markux, just update here when you can 🙂
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Hi @markux
If @yungro's answer solved your question, don't forget to accept it by clicking "Accept" directly below the answer to resolve the post.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Could anyone help me on this issue?
