Can you add a "-v" to the front of the args?
dsidm -v INSTANCE ... ...
On 5/4/20 6:39 PM, Jorge F. Hernandez wrote:
Well, I did try this:
dsidm -b "dc=example,dc=com" -D "cn=Directory Manager"
<instance>
initialise
Enter password for cn=Directory Manager on ldap://localhost:389:
Bur after putting the password, I get this:
Error: No such object
I also get the same error when I try to create a new user using dsidm
and dsctl <instance> status shows as running, I even deleted the
instance and try to recreate it using cockpit and I checked to include
sample data in it, but nothing shows up.
Any other ideas?
Well the cockpit UI does not show database tree structure (we do want to
add this though, but it's not happening anytime soon). When you say
nothing shows up, what are you looking at? Does ldapsearch show you
what you expect?
# ldapsearch -D "cn=directory manager" -W -b <YOUR SUFFIX>
objectclass=*
Of course, checking the server's access log will tell you if a client
connected, what it searched for, and how many entries were returned.
HTH,
Mark
Thanks.
===============
Jorge F. Hernandez
On Mon, May 4, 2020 at 5:59 PM William Brown <wbrown(a)suse.de
<mailto:wbrown@suse.de>> wrote:
> On 5 May 2020, at 05:46, Jorge F. Hernandez <jfha73(a)gmail.com
<mailto:jfha73@gmail.com>> wrote:
>
> Thank you for that, another question, now that I can see my 389
Directory Server, all I see id my base DN, dc=example,dc=com but
nothing else, it shows empty, no OUs, no nothing, how can I
populate it with the default schema of a Directory Server (Users,
Computers, etc.)
If you have a blank backend, you can populate it with sample
entries with "dsidm <instance name> initialise". Have a look at
this quickstart for the dsrc setup
http://www.port389.org/docs/389ds/howto/quickstart.html
Hope that helps,
>
>
> ============
> Jorge F. Hernandez
>
> -----Original Message-----
> From: William Brown <wbrown(a)suse.de <mailto:wbrown@suse.de>>
> Sent: Sunday, May 3, 2020 6:54 PM
> To: 389 Directory server developer discussion.
<389-devel(a)lists.fedoraproject.org
<mailto:389-devel@lists.fedoraproject.org>>
> Subject: [389-devel] Re: Is there going to be a console for
RHEL/CentOS 8?
>
>
>
>> On 4 May 2020, at 04:08, Jorge F. Hernandez <jfha73(a)gmail.com
<mailto:jfha73@gmail.com>> wrote:
>>
>> Hello,
>>
>> I just installed 389 to a CentOS 8 using the instructions from
your website (yum module), but I cannot find an admin/management
tool for it, before there used to be a console or an admin web
site, but I don’t see it anymore, any ideas if this is going to be
available in the future?
>>
>> I can see the 389 Directory Server in the cockpit, but there is
no way to add/edit users/groups on it.
>
> We've been talking about adding a seperate web based tool for
this, but currently it's early stages. For now you'll have to use
apache directory studio, the dsidm command line, or another ldap
editor. Sorry about that :(
>
>
>>
>> Thanks,
>>
>>
>> ============
>> Jorge F. Hernandez
>>
>> _______________________________________________
>> 389-devel mailing list -- 389-devel(a)lists.fedoraproject.org
<mailto:389-devel@lists.fedoraproject.org> To
>> unsubscribe send an email to
389-devel-leave(a)lists.fedoraproject.org
<mailto:389-devel-leave@lists.fedoraproject.org>
>> Fedora Code of Conduct:
>>
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines:
>>
https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>>
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedorapr
>>
oject.org <
http://oject.org>
>
> —
> Sincerely,
>
> William Brown
>
> Senior Software Engineer, 389 Directory Server SUSE Labs
_______________________________________________
> 389-devel mailing list -- 389-devel(a)lists.fedoraproject.org
<mailto:389-devel@lists.fedoraproject.org> To unsubscribe send an
email to 389-devel-leave(a)lists.fedoraproject.org
<mailto:389-devel-leave@lists.fedoraproject.org>
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproje...
> _______________________________________________
> 389-devel mailing list -- 389-devel(a)lists.fedoraproject.org
<mailto:389-devel@lists.fedoraproject.org>
> To unsubscribe send an email to
389-devel-leave(a)lists.fedoraproject.org
<mailto:389-devel-leave@lists.fedoraproject.org>
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproje...
—
Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server
SUSE Labs
_______________________________________________
389-devel mailing list -- 389-devel(a)lists.fedoraproject.org
<mailto:389-devel@lists.fedoraproject.org>
To unsubscribe send an email to
389-devel-leave(a)lists.fedoraproject.org
<mailto:389-devel-leave@lists.fedoraproject.org>
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproje...
_______________________________________________
389-devel mailing list -- 389-devel(a)lists.fedoraproject.org
To unsubscribe send an email to 389-devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproje...
--
389 Directory Server Development Team