kolab 3.0 alpha error during setup-kolab

Dirk Werner dwerner at curiousbits.de
Wed Aug 15 21:20:09 CEST 2012


On 08/15/2012 09:13 PM, Jeroen van Meeuwen wrote:
> On Wednesday, August 15, 2012 07:22:40 PM Dirk Werner wrote:
>> On 08/15/2012 06:49 PM, Jeroen van Meeuwen wrote:
>>> On Wednesday, August 15, 2012 06:03:44 PM Dirk Werner wrote:
>>>> There is no directory /etc/dirsrv/slapd-remote existing.
>>> Hi Dirk,
>>>
>>> could you run setup-kolab with -d 9 please, capturing the output?
>>>
>>> # setup-kolab -d 9 2>&1 | tee setup-kolab.log
>> Hi Jeroen,
>> this did go much further than the first try, it did hang at one point,
>> so I had to cancel the process. Here's the content of the file
>> setup-kolab.log:
>>
>> (...snip...)
>> Setup is now going to set up the 389 Directory Server. This may take a
>> little
>> while (during which period there is no output and no progress indication).
>>
>> 2012-08-15 19:08:17,138 pykolab.setup INFO Setting up 389 Directory Server
>> 2012-08-15 19:08:30,389 pykolab.setup DEBUG [2220]: Setup DS stdout:
>> 2012-08-15 19:08:30,391 pykolab.setup DEBUG [2220]: Creating directory
>> server . . .
>> Your new DS instance 'remote' was successfully created.
>> Creating the configuration directory server . . .
>> Error: failed to open an LDAP connection to host 'remote.airwerk.net'
>> port '389' as user 'cn=Directory Manager'.  Error: unknown.
> Here is a clue... though this is only stdout.
>
> Regrettably, the stdout output doesn't show the cause of the configuration 
> server failing to be bootstrapped.
>
> The rest of the output indicates to me that the processes completed 
> successfully, actually.
>
> Kind regards,
>
> Jeroen van Meeuwen
>
OK, I'll try to work with this installation tomorrow, many thanks for
your attention!
Dirk




More information about the users mailing list