389 Console

[Isaac Aaron]

Hmm...

I guess that depends on how deep you want to go into 389. The proper procedure should be:
1. Save (backup) slapd-mail, the database and config files
2. Run setup-ds-admin
3. Restore slapd-mail

The above should get you back to the exact state you were at before installing the admin instance and get you back to work almost immediately after the procedure. It does however require some investigation on what to back up and how to restore it.

Isaac Aaron


-----Original Message-----
From: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org] On Behalf Of Stefan Froehlich
Sent: Sunday, May 12, 2013 12:07 PM
Cc: kolab-users at kolab.org
Subject: Re: 389 Console


Can't do that. It is a production server...

MfG Stefan Fröhlich
42 ;-)

On 12/05/2013 6:35 PM, Isaac Aaron wrote:
> Hi Stefan
>
> I have run into this issue myself. My quick workaround was to run setup-ds-admin.pl and remove the mail LDAP instance BEFORE I run setup-kolab.
>
> Somethink like:
> setup-ds-admin.pl
> remove-ds.pl -I slapd-mail
> setup-kolab
>
> Isaac Aaron

_______________________________________________
Kolab-users mailing list
Kolab-users at kolab.org
https://www.intevation.de/mailman/listinfo/kolab-users
.
.
Quality Bytes MailXpress Message:
Spam? Click the link below
http://10.0.0.3:16000/spam.php?spam=1&qid=000000000026d433
.