ubuntu-389-directory-server team mailing list archive
Mailing list archive
Re: Problem with 389-ds-base/389-ds-admin
On 29.02.2012 18:38, Timo Aaltonen wrote:
> On 29.02.2012 07:54, Timo Aaltonen wrote:
>> On 29.02.2012 01:24, Justin Chudgar wrote:
>>> Manually creating the lock directory allows start-dirsrv to work. That
>>> eliminates the bind error after running start-ds-admin. I does NOT
>>> however fix everything. Even when the base directory server is running
>>> (checked with Luma), visiting the ds-admin index page
>>> gives the following error in browser:
>>> NMC_Status: 1
>>> NMC_ErrType: System Error
>>> NMC_ErrInfo: Could not read from pipe
>>> NMC_ErrDetail: Could not read authentication information from pipe.
>>> while nothing is printed in the admin-serv/error log.
>> This is an upstream bug, currently under investigation:
> Actually, it's probably not the same that I had. My test server had a
> hostname of '389ds' and the admin server currently doesn't allow a digit
> as the first character of a hostname.. it's still a bug but not what
> you're seeing..
> Anyway, check out the debug instructions I was given on the 389-users ml:
before you do that, check dmesg if it really is some cgi-bin
segfaulting, and if not then check /var/log/dirsrv/admin-serv/error.