Displaying 3 results from an estimated 3 matches for "ldap_abandon".
2016 Oct 18
2
Lockd: failed to reclaim lock for pid ...
...with "out of memory errors" due to her programs in
the recent past and had to restart all 100 servers.
*/var/adm/messages gives this*
Oct 18 13:26:08 blade5-2-1 nslcd[2520]: [dd5cc5] ldap_result() failed:
Can't contact LDAP server
Oct 18 13:26:08 blade5-2-1 nslcd[2520]: [dd5cc5] ldap_abandon() failed
to abandon search: Other (e.g., implementation specific) error
Oct 18 13:27:14 blade5-2-1 nslcd[2520]: [e01acb] ldap_result() failed:
Can't contact LDAP server
Oct 18 13:27:30 blade5-2-1 nslcd[2520]: [8c7a8f] ldap_result() failed:
Can't contact LDAP server
*dmesg gives these*...
2015 Mar 12
3
AD DC out of sync
Hi Marc,
>> The cause is that the password change didn' reach both AD DCs, but only
>> one. The other one still had the old value as could be seen by
>> samba-tool ldapcmp. Restarting the DCs and waiting for a couple of
>> seconds brings them back to sync and Windows logons work as they used to.
>> Any idea, what I should do next time to obtain valuable output
2016 Oct 18
0
Lockd: failed to reclaim lock for pid ...
...with "out of memory errors" due to her programs in
the recent past and had to restart all 100 servers.
*/var/adm/messages gives this*
Oct 18 13:26:08 blade5-2-1 nslcd[2520]: [dd5cc5] ldap_result() failed:
Can't contact LDAP server
Oct 18 13:26:08 blade5-2-1 nslcd[2520]: [dd5cc5] ldap_abandon() failed
to abandon search: Other (e.g., implementation specific) error
Oct 18 13:27:14 blade5-2-1 nslcd[2520]: [e01acb] ldap_result() failed:
Can't contact LDAP server
Oct 18 13:27:30 blade5-2-1 nslcd[2520]: [8c7a8f] ldap_result() failed:
Can't contact LDAP server
*dmesg gives these*...