-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/openldap] exits with status 123 when loading custom ldif #26518
Comments
Hi, Could you launch it with BITNAMI_DEBUG=true to see if it provides more information? |
|
After testing a bit more, I found out that, when using a custom ldif, the object |
It is problably it, with custom ldifs the root object is not created. If the custom ldif create the root object before the other objects, container starts fine. |
Thanks for letting us know! |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
This issue is still unsolved in 2.6.7. |
Hi, did you check this comment about the expected behavior with custom ldif #26518 (comment)? |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Ran into this one to. Especially confusing when the readme states
"ou should set LDAP_ROOT to your base to make sure" .. which really suggest that the root is created. Or why set it at all otherwise? For anybody in need, this needs to be added (changed according to your olcSufffix) to your ldif at the top
|
Name and Version
bitnami/openldap:2.6.4
What architecture are you using?
amd64
What steps will reproduce the bug?
echo $?
, it will print123
What is the expected behavior?
The container loads the custom ldif and starts
What do you see instead?
The container exits with return code
123
Additional information
Ldap return code
123
is "authorizationDenied", which means:https://ldap.com/ldap-result-code-reference-other-server-side-result-codes/#rc-authorizationDenied
https://docs.ldap.com/specs/rfc4370.txt
The text was updated successfully, but these errors were encountered: