ubuntu-389-directory-server team mailing list archive

[Timo Aaltonen <tjaalton@xxxxxxxxxx>]

On 29.02.2012 00:47, Justin Chudgar wrote:
> Problem 1:
> Directory /var/run/dirsrv was owned by root:root. This caused the
> following message in /var/log/dirsrv/admin-serv/error:
>     [Tue Feb 28 14:29:50 2012] [error] (98)Address already in use:
> Couldn't bind unix domain socket /var/run/dirsrv/admin-serv.cgisock.2873
> chown dirsrv:dirsrv /var/run/dirsrv fixed that error.

You don't seem to have dirsrv running? I see that the dirsrv-admin
initscript has bugs that prevent it from chown'ing the dir, but dirsrv
initscript works and should've set that up for you (works here).

> Problem 2:
> Again from /var/log/dirsrv/admin-serv:
>     [Tue Feb 28 14:29:50 2012] [error] Could not bind as []: ldap error
> -1: Can't contact LDAP server
>     [Tue Feb 28 14:29:50 2012] [error] Could not bind as []: ldap error
> -1: Can't contact LDAP server
>     [Tue Feb 28 14:29:50 2012] [warn] Unable to bind as LocalAdmin to
> populate LocalAdmin tasks into cache.
> I have no idea how to debug this one at the moment. Suggestions for a
> 389/LDAP newb would be appreciated.

Again, most likely you don't have dirsrv running.

> Problem 3:
> Again from /var/log/dirsrv/admin-serv:
>     [Tue Feb 28 14:29:51 2012] [error] restartd daemon process died,
> restarting
> This happens every time at start-ds-admin is run and is the last line in
> that part of the error log. What is the restartd daemon? I've got
> nothing in /etc/init.d/. The only thing that locate finds is the 389
> specific apache2 module. Should the following be listed as a dependency
> of 368-ds-admin?

No, that's mod_restartd, included in 389-admin.


-- 
t