OH... eol in like a month. Maybe you are planning an upgrade?Centos 6
Code:cd /usr/local/directadmin/custombuild ./build update ./build icu
Try this?
What OS and version?
Yeah just found out , I'm working on itRequirements https://github.com/grosjo/fts-xapian
OH... eol in like a month. Maybe you are planning an upgrade?
did running the icu cmds help?
We will be here. Welcome to DA and the Forum.Yeah just found out , I'm working on it
You cant directly upgrade. You must do a fresh install. I would jump straight to version 8 btw.Okay, I'll try to upgrade my CentOS version (riskier than I thought) before November and let it know how it worked out.
please dont double post. you are littering in th forum. one problem one post..but search using roundcube doesnt works im missing something?
sorry about thatplease dont double post. you are littering in th forum. one problem one post..
Thanks
fts-xapian code quality is really, really terrible.We're having issues with fts xapian, for example Mailbox is only 10MB big, but xapian-indexes folder gets to over 1GB size over time. Maybe it indexed all the emails ever received but never noticed the customer deletes the emails soon (pop3 etc.)?
Customers complain as they are over quota because of this and their mailboxes are almost empty...
I also tried reindexing or optimizing the mailbox, but all it does is deletes all files and folders in xapian-indexes folder.
EDIT: it looks like this is expected behaviour. It also looks like xapian is indexing attachments and can create the DB many times the size of the messages themselves. I'll try fiddling with some other config options.
EDIT2: I've reverted to solr, magnitude faster initial database building and much smaller database. Although it would be nice if solr could keep the database in each user's Maildir, the benefits outweigh this drawback for us, YMMV.
We're having issues with fts xapian, for example Mailbox is only 10MB big, but xapian-indexes folder gets to over 1GB size over time. Maybe it indexed all the emails ever received but never noticed the customer deletes the emails soon (pop3 etc.)?
Customers complain as they are over quota because of this and their mailboxes are almost empty...
I also tried reindexing or optimizing the mailbox, but all it does is deletes all files and folders in xapian-indexes folder.
EDIT: it looks like this is expected behaviour. It also looks like xapian is indexing attachments and can create the DB many times the size of the messages themselves. I'll try fiddling with some other config options.
EDIT2: I've reverted to solr, magnitude faster initial database building and much smaller database. Although it would be nice if solr could keep the database in each user's Maildir, the benefits outweigh this drawback for us, YMMV.
fts-xapian code quality is really, really terrible.
Memory leaks, file locking issues and much more
Until the code is completely rewritten, I wouldn't hope that any patch would improve it.