So tried it out and wanted to report my findings.
First I have
Centos 7 latest DA and all up to date CB and software.
I started by running just this below.
No errors during install
However Roundcube had a storage area issue and would not load.
So I tried running
Nope
Then just to be sure I did this.
Then I wondered if this would help being after fts-xapian
That fixed it to work in Roundcube
So now I wonder should the order be
OR
Like I said I seems to install fine just broke roundcube.
Also there's a bug in doveadmn if you run
Deletes all the indexes
First I have
Centos 7 latest DA and all up to date CB and software.
I started by running just this below.
Code:
cd /usr/local/directadmin/custombuild
./build update
./build dovecot
./build fts-xapian
However Roundcube had a storage area issue and would not load.
So I tried running
Code:
cd /usr/local/directadmin/custombuild
./build update
./build dovecot_conf
Then just to be sure I did this.
Code:
cd /usr/local/directadmin/custombuild
./build update
./build roundcube
Then I wondered if this would help being after fts-xapian
Code:
cd /usr/local/directadmin/custombuild
./build update
./build dovecot
So now I wonder should the order be
Code:
cd /usr/local/directadmin/custombuild
./build update
./build fts-xapian
./build dovecot
OR
Code:
cd /usr/local/directadmin/custombuild
./build update
./build dovecot
./build fts-xapian
./build dovecot
Like I said I seems to install fine just broke roundcube.
Also there's a bug in doveadmn if you run
Code:
doveadmn fts rescan
Deletes all the indexes
Rescan
Dovecot keeps track of indexed messages in the dovecot.index files. If this becomes out of sync with the actual FTS indexes (either too many or too few mails), you’ll need to do a rescan and then index missing mails:
doveadm fts rescan -u user@domain
doveadm index -u user@domain -q '*'
Note that currently most FTS backends don’t properly implement the rescan. Instead, they simply delete all the FTS indexes. This may change in the future versions.