Learn more about these different git repos.
Other Git URLs
Occasionally the sssd log get filled up consuming all available disk space with one message:
(<timestamp>) [sssd[be[<domain>]]] [sdap_process_result] (2): ERROR: LDAP connection is not connected!
It happens with openldap 2.3.43 and sssd 1.2.1 on RHEL 5.5. After this the machine becomes unusable.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.4.0 owner: somebody => jhrozek
milestone: SSSD 1.4.0 => SSSD 1.2.4
owner: jhrozek => jzeleny
Dmitri, I tried to reproduce this issue on my virtual machine (RHEL 5.6, sssd and openldap versions are the same) without any success. I tried steps described in ticket #494 with various configurations. I was wondering if you can help me by providing steps to reproduce the issue.
Try the following scenario:
I suspect that the problem is related to the situation when network is there but the server is not reachable since it requires VPN. Since going from home to office and back completely swaps the network environment under SSSD it might be sticking to its old knowledge about the network somehow and getting confused. I would look into netlink related area.
This is the best I can help with.
Thanks you. I don't think VPN causes the issue, because SSSD works with connection to servers, not connection to network. If you have a log describing what happens, it might shed a light on what's going on. Either way I shall investigate further and try to reproduce the issue.
Fixed by 2159516
component: SSSD => LDAP Provider fixedin: => 1.2.4 resolution: => fixed status: new => closed
rhbz: => 0
Metadata Update from @dpal: - Issue assigned to jzeleny - Issue set to the milestone: SSSD 1.2.4
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1641
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.