Re: [Kolab-devel] Kolab 3.3 feedback

Daniel Hoffend wrote:
> Hello
> 
> this is a follow up on my initial test run of Kolab 3.3. Last
> evening/night I started to reinstall my testsystem again and tried to
> configure and test a few things that were announced as the big new
> features of Kolab 3.3. Well ... apart from stuff that is not enabled by
> default or parameter that haven't been configured I came a cross lots of
> default configuration, packaging or other bugs.

Hi Daniel

Thanks a lot for reporting your findings! See some comments further below.


> roundcubemail-plugin-contextmenu
> --------------------------------
> 
> ## incompatible
> 
> The contextenu 1.x won't work with roundcube 1.1 but 2.x has problems
> that needs to be resolved in the upstream package first before packaging
> Ticket: https://issues.kolab.org/show_bug.cgi?id=3266

Known issue, we're working on that.


> resources/wallace
> -----------------
> 
> ## Summary
> 
> * booking of single resources == FAIL (NDR)
> * booking of resource collection == SUCCESS
> * booking of resource collection at the same time == ERROR
> 
> ## booking single resource
> 
> 1) enable wallace via postfix master.conf
> 2) create resource beamer1
> 3) create appointment + book resource beamer1 + save
> 
> I receive a non-delivery-notification even the mail is getting processed
> by wallace and the mailbox in general should exist

The message should be fully consumed by wallace and don't get passed
along. Need to investigate this.


> ## booking resource collection
> 
> 1) create resource collection beamers + add beamer1
> 2) create appointment + book resource collection beamers + save
> 
> SUCCESS
> * from: beamers - Reservation Request for test1 was Delegated
> * from: beamer1 - Reservation Request for test1 was Accepted
> 
> 3) create appointment different date/time + book resource collection
> beamers + save
> 
> Note: You don't see the freebusys calendar of the resources. it's
> completely empty

Filed in https://issues.kolab.org/show_bug.cgi?id=3324

> SUCCESS
> 
> 4) create appointment same date/time + book resource collection beamers
> + save
> 
> ERROR:
> [...]
> UnboundLocalError: local variable 'done' referenced before assignment
> 
> the incoming file is laying in the spool file and is blocking all other
> incoming wallace resource requests until I empty the spool folder

Filed in https://issues.kolab.org/show_bug.cgi?id=3312
and fixed in git master.
> 
> 5) rm /var/spool/pykolab/wallace/resources/incoming/* + restart wallace
> 
> ## other tracebacks
> 
> here's another traceback that I've seen when I tried to clean up the messes
> 
> [...]
> line 705, in delete_resource_event
>     targetfolder = imap.folder_quote(resource['kolabtargetfolder'])
> KeyError: 'kolabtargetfolder'

Filed under https://issues.kolab.org/show_bug.cgi?id=3312
and fixed in git master.


> kolab-freebusy
> --------------
> 
> I kinda feel helpless with correct way on how to configure freebusy and
> make it work
> 
> ## debian package bug
> 
> * missing folder /var/{lib,cache}/kolab-freebusy
>   workaround: mkdir -p /var/{cache,lib}/kolab-freebusy ; chown
> kolab:kolab /var/{cache,lib}/kolab-freebusy
> 
> ## config.ini.sample
> 
> * logfolder should be ./logs not ./log
> * rename kolab-ldap to kolab-users
> * add kolab-resources
> * comment out exchange (leave it as example only)
> * default imap connection points to imaps but ssl is not configured in
> the default installation
> ' filter @yourdomain not replaced by the default domain during setup-kolab

These are just samples and are not supposed to be adapted by setup-kolab
for only serve as reference for manual configuration.

> ## strange search / database error
> 
> with debug level = 100
> 
> ==> /var/log/kolab-freebusy/freebusy.log <==
> [...]
> [2014-08-13 13:44:50] web.DEBUG: Trying directory kolab-users ....
> [...]
> [2014-08-13 13:44:50] ldap.INFO: Found 1 entries for
> (&(objectClass=kolabInetOrgPerson)(|([email protected])([email protected])([email protected])))
> {"mail":["[email protected]"]} []
> ==> /var/log/kolab-freebusy/errors <==
> [13-Aug-2014 13:44:50 +0200]: DB Error: Configuration error. Unsupported
> database driver:  in
> /usr/share/kolab-freebusy/lib/Roundcube/rcube_db.php on line 78 (GET
> /freebusy/[email protected])

You likely have fbsource = imap://... configured which is not
recommended for productive systems.

However, the imap:// source uses the Roundcube framework to access event
data in IMAP and also attempts to use caching for this.

Symlinking /etc/roundcubemail/config.inc.php and
/etc/roundcubemail/defaults.inc.php in /etc/kolab-freebusy/ should
resolve these errors.


> ## lib vs cache confusion?
> 
> $ kolab-freebusyd --generateall 2>&1 | grep wrote
> (11:43:50) fbaggregatorjob.cpp(103):    wrote 
> "/var/lib/kolab-freebusy/[email protected]"
> 
> root@kolab33:/var/log/kolab-freebusy# egrep -i "^(cache|fb)"
> /etc/kolab-freebusy/config.ini
> fbsource = file:/var/lib/kolab-freebusy/%s.ifb
> fbsource = file:/var/cache/kolab-freebusy/%s.ifb
> fbsource =
> imap://cyrus-admin:xxxxx@localhost:143/%kolabtargetfolder?acl=lrs
> cacheto = /var/cache/kolab-freebusy/%mail.ifb
> fbsource = imap://%mail:xxxxx@localhost:143/?proxy_auth=cyrus-admin
> cacheto = /var/cache/kolab-freebusy/%mail.ifb

cacheto is optional and not required when free-busy data is generated by
kolab-freebusyd --generateall into /var/lib/kolab-freebusy/.

Some basic information is available here:
http://docs.kolab.org/architecture-and-design/kolab-freebusy.html

But full documentation of the configuration options is yet missing.
> 
> ## cron
> 
> * is it usefull or should freebusy always be generated on demand
> * missing cron job to actually generate the freebusy files
> * not really clear if we should configre nothing (on demand) or via cron
> or via fbdaemon (sample file) which seems to be on the TODO list
> 
> /etc/cron.d/kolab-freebusy
> */15 * * * * root [ $(pgrep kolab-freebusyd >/dev/null 2>&1; echo $?)
> -ne 0 ] && QT_NO_GLIB=1 kolab-freebusyd --generateall
>>/var/log/kolab-freebusyd.log 2>&1

kolab-freebusyd now has a daemon mode which is the preferred way to run
it. It's intended to let the kolab-freebusy service connect to the
daemon and get updated free-busy data when requested:

[directory "kolab-ldap"]
...
fbsource = "fbdaemon://localhost:4455?user=%mail"

This is all bleeding-edge development and unfortunately isn't yet all
reflected in setup-kolab.


> ## resources
> 
> empty FB for resource collecion. this might be okay

https://issues.kolab.org/show_bug.cgi?id=3165

> [2014-08-13 13:52:21] ldap.INFO: No entry found for
> (&(objectClass=kolabInetOrgPerson)(|([email protected])([email protected])([email protected])))
> [] []
> [2014-08-13 13:52:21] web.INFO: Returning empty Free/Busy list for user
> [email protected] [] []
> 
> trying to show the specific freebusy times of a single resource ==>
> Search OK, but FAILED
> 
> [2014-08-13 13:53:51] ldap.INFO: Found 1 entries for
> (&(objectClass=kolabsharedfolder)([email protected]))
> {"mail":["[email protected]"],"kolabtargetfolder":["shared/Resources/[email protected]"]}
> []
> [13-Aug-2014 13:53:51 +0200]: DB Error: Configuration error. Unsupported
> database driver:  in
> /usr/share/kolab-freebusy/lib/Roundcube/rcube_db.php on line 78 (GET
> /freebusy/[email protected])

Same as above and should be solved with kolab-freebusy daemon.


> kolab-notes
> -----------
> 
> ## missing + button
> 
> while plugins like addressbook have a [+] button bottom toolbar, the
> notes plugin does not

True. The notes plugin has a "Create note" button in the top toolbar,
same as in calendars and tasks. But could be added in the list footer
for consistency reasons.

> ## locales
> 
> A few german locales are missing. I know it's time to register at
> transoflex or whatever it is called :-)

https://www.transifex.com/projects/p/kolab/ it is :-)

Kind regards,
Thomas