389-cosole - how to use?

[Jan Kowalsky]

Hi Brian,

thanks again.

Am Sunday, 1. December 2013 schrieb Shaw, Brian:
>  "nobody" is the user (and group) that the embedded Apache web server
> runs as. It appears to be defined in
> /etc/dirsrv/admin-serv/console.conf. You can either change it in the
> config to be whatever non-privileged user you want it to run as or you
> can create the "nobody" local account and group.

Ok, one step further ;-)

No I get in the error log:

[Sun Dec 01 21:41:10 2013] [crit] do_admserv_post_config(): unable to create 
AdmldapInfo
Configuration Failed

I didn't find much related to the error.

Only:
http://lists.kolab.org/pipermail/users-de/2013-March/001060.html (same 
question)

On this tread
https://lists.launchpad.net/ubuntu-389-directory-server/msg00084.html
there is the consideration it's related to libnss3

https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=859750

(did I mention that I use the debian packages? And did anyone manage to access 
the 389-console with debian)

Jan

> Brian
> 
> On 2013-11-30 12:38 pm, Jan Kowalsky wrote:
> > Hi Brian,
> > 
> > thanks a lot.
> > 
> > Unfortuanately it doesn't work yet: starting dirsrv-admin gives
> > 
> > ~# /etc/init.d/dirsrv-admin start
> > Starting dirsrv-admin:
> > apache2.worker: bad group name nobody
> > 
> > And I didn't find out yet how to fix it. But I got at least one step
> > closer ;-)
> > 
> > Kind Regars
> > Jan
> > 
> > Am Saturday, 30. November 2013 schrieb Shaw, Brian:
> > Jan, Here is my adm.conf file. You should just need to update it with
> > your domain and system information. Brian AdminDomain: example.com
> > sysuser: nobody isie: cn=389 Administration Server,cn=Server
> > Group,cn=kolab.example.com,ou=example.com,o=NetscapeRoot SuiteSpotGroup:
> > nobody sysgroup: nobody userdn:
> > uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot
> > ldapStart: /usr/lib64/dirsrv/slapd-kolab/start-slapd ldapurl:
> > ldap://kolab.example.com:389/o=NetscapeRoot SuiteSpotUserID: nobody sie:
> > cn=admin-serv-kolab,cn=389 Administration Server,cn=Server
> > Group,cn=kolab.example.com,ou=example.com,o=NetscapeRoot On 2013-11-26
> > 7:29 pm, Jan Kowalsky wrote: Hi Brian, thanks for your answer. Am
> > Wednesday, 27. November 2013, 01:03:38 schrieb Brian Shaw: Dirsrv-admin
> > is only needed if you are actually manipulating server functions such as
> > replication and password expiration rules. Even then, yes, that's
> > actually my goal: to administrate replication easily - because I don't
> > know ho
> 
>  w to do
> this via ldapmodify and thought this is much easyier via 389-console. all
> the admin functions can be done via ldapmodify. For day to day changes I
> recommend Apache Directory Studio as an easy to use GUI. As for
> documentation, the 389 project recommends the Red Hat Directory Server
> documentation at
> https://access.redhat.com/site/documentation/Red_Hat_Directory_Server/ [1]
> [1] I hope this helps. Not really - I had already a look at it. But the
> main problem seems to be that the dirserv-admin doesn't run. At least I
> think so. Jan Kowalsky <tuxus at notraces.net> wrote: Hi all, is there any
> documentation for using the 389-console? I enabled anonymous bind (not
> during installation but later) - but the dirsrv-admin isn't running (it's
> needed, isn't it) and doesn't start because on missing config-file:
> /etc/init.d/dirsrv-admin start [info] No /etc/dirsrv/admin-serv/adm.conf
> file is present. Is there any possibility to use the 389-console with
> kolab? I'm using Debian ... Thanks in advanc e Jan
>  Links: ------ [1]
> https://access.redhat.com/site/documentation/Red_Hat_Directory_Server/
> [1]
> 
> Links:
> ------
> [1]
> https://access.redhat.com/site/documentation/Red_Hat_Directory_Server/