Re: Kolab 3.0/Debian: Best way to start over?

On Tuesday 18 December 2012 15:04:17 Paul Klos wrote:
> Op Tue, 18 Dec 2012 13:21:38 +0100
>
> ITSEF Admin <[email protected]> schreef:
> > On second thoughts - shouldn't this method also
> > contain the database drops? Something like:
> >
> > On Monday 17 December 2012 19:10:41 Paul Klos wrote:
> > > Thorough:
> > > 1. apt-get remove --purge kolab kolab-syncroton
> > > 2. apt-get autoremove --purge
> >
> > 2a. mysql -u root -p -e "drop database kolab;"
> > 2b. mysql -u root -p -e "drop database roundcube;"
> >
> > > 3. apt-get install kolab
> >
> > Or am I now overly paranoid and does "setup-kolab"
> > deal with existing DBs in a "useful" way?
>
> Not sure, but dropping the databases is probably a
> good idea :-).

Well, after getting bitten once by some python crash upon running setup-kolab 
(which apparently was due to some LDAP leftovers) I come to believe that the 
complete procedure should look like this:

1. apt-get remove --purge kolab kolab-syncroton
2. apt-get autoremove --purge
3. Remove databases:
    a. mysql -u root -p -e "drop database kolab;"
    b. mysql -u root -p -e "drop database roundcube;"
4. Remove IMAP spool files: rm -rf /var/lib/imap/ /var/spool/imap/
5. Remove LDAP files: 
rm -rf /etc/dirsrv/slapd-HOST/ /var/lib/dirsrv/slapd-HOST/
6. apt-get install kolab
7. Re-run setup-kolab

Note of caution: In my case, "apt-get autoremove --purge" failed with an error 
when removing cyrus-imapd: https://issues.kolab.org/show_bug.cgi?id=1481
I got round that by messing with /var/lib/dpkg/info/cyrus-imapd.postrm and 
replacing the line
db_get cyrus-imapd/removespools
with
db_get cyrus-imapd/removespools || true
but I'd be fairly surprised if that was the proper solution and not just an 
ugly hack... (...so be warned).

On first glance, though, I now have a running, pristine server again. If I run 
into any undesired side effects I'll make sure to post them here.

Cheerio,

Thomas
-- 
------------------------------------------------------------------------------
           Thomas Ribbrock, IT-Team brightsight