| 2018-05-04 20:55:39 |
Nic Bernstein |
description |
Using a brand new Bionic 18.04LTS LXC container on a Bionic host, I am unable to complete running setup-ds-admin. When performing the exact same sequence on the physical host it completes as expected.
When run as "setup-ds-admin -k -d" on the container, the run ends with this:
-------------------
Your new DS instance 'ds3891' was successfully created.
Creating the configuration directory server . . .
+Processing /usr/share/dirsrv/data/01nsroot.ldif.tmpl ...
+Processing /usr/share/dirsrv/data/02globalpreferences.ldif.tmpl ...
+Processing /usr/share/dirsrv/data/12dsconfig.mod.tmpl ...
+Processing /usr/share/dirsrv/data/13dsschema.mod.tmpl ...
+Processing /usr/share/dirsrv/data/14dsmonitor.mod.tmpl ...
+Processing /usr/share/dirsrv/data/16dssuffixadmin.mod.tmpl ...
Could not authenticate as user 'uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot' to server 'ldap://ds3891.occinc.com:389/o=NetscapeRoot'. Error: Invalid credentials
Could not register the directory server with the configuration directory server.
Exiting . . .
-------------------
and the UserPassword entry for that user is a bogus string, unrelated to the password entered. By that I mean that I can run the same sequence four times with different passwords (cleaning up the /etc/dirsrv/slapd-* directories in between), and the same exact string will end up stored in the UserPassword entry for that user. The password for "cn=Directory Manager" is fine, however.
The value of admin's UserPassword will always end up being this:
userPassword:: e1NTSEE1MTJ9Y21SMUR1MER0Tk9FNWNZc1VlSTVXRHA1TlBSK2NQeGY1MlJPVTN
GZzFLQW1zTnlQZDRQOXdNNm1YTFJSZ1V0THp0d1ZnQWFyeFc1a2s2UVRMU2s0TDZTcm1xTXkrTmEz
As noted, the same exact sequence run on the bare host (not in an LXC container) yields expected results. |
Using a brand new Bionic 18.04LTS LXC container on a Bionic host, I am unable to complete running setup-ds-admin. When performing the exact same sequence on the physical host it completes as expected.
When run as "setup-ds-admin -k -d" on the container, the run ends with this:
-------------------
Your new DS instance 'ds3891' was successfully created.
Creating the configuration directory server . . .
+Processing /usr/share/dirsrv/data/01nsroot.ldif.tmpl ...
+Processing /usr/share/dirsrv/data/02globalpreferences.ldif.tmpl ...
+Processing /usr/share/dirsrv/data/12dsconfig.mod.tmpl ...
+Processing /usr/share/dirsrv/data/13dsschema.mod.tmpl ...
+Processing /usr/share/dirsrv/data/14dsmonitor.mod.tmpl ...
+Processing /usr/share/dirsrv/data/16dssuffixadmin.mod.tmpl ...
Could not authenticate as user 'uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot' to server 'ldap://ds3891.example.com:389/o=NetscapeRoot'. Error: Invalid credentials
Could not register the directory server with the configuration directory server.
Exiting . . .
-------------------
and the UserPassword entry for that user is a bogus string, unrelated to the password entered. By that I mean that I can run the same sequence four times with different passwords (cleaning up the /etc/dirsrv/slapd-* directories in between), and the same exact string will end up stored in the UserPassword entry for that user. The password for "cn=Directory Manager" is fine, however.
The value of admin's UserPassword will always end up being this:
userPassword:: e1NTSEE1MTJ9Y21SMUR1MER0Tk9FNWNZc1VlSTVXRHA1TlBSK2NQeGY1MlJPVTN
GZzFLQW1zTnlQZDRQOXdNNm1YTFJSZ1V0THp0d1ZnQWFyeFc1a2s2UVRMU2s0TDZTcm1xTXkrTmEz
As noted, the same exact sequence run on the bare host (not in an LXC container) yields expected results. |
|
