Traceback for kolab-server service restart

Brad Wilson brad at undercovergarys.com
Mon Nov 17 06:25:46 CET 2014


Hi,

In Kolab 3.3 under Debian 7, when I tell the kolab-server service to 
restart, I get a traceback error. Some accounts are working normally, 
others a return an IMAP "System I/O error". Things were working well 
under 3.2, any idea what I've misconfigured?

Here's what bash looks like:

$ sudo service kolab-server restart
[ ok ] Restarting The Kolab server synchronizes LDAP, SQL and other 
authentication databases with Cyrus IMAP, Dovecot or other IMAP 
servers.: kolabd.
brad at termini:~$ Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/kolabd/__init__.py", line 183, 
in run
     self.do_sync()
   File "/usr/lib/python2.7/dist-packages/kolabd/__init__.py", line 273, 
in do_sync
     sleep_between_domain_operations_in_seconds = 
(float)(conf.get('kolab', 'domain_sync_interval'))
   File "/usr/lib/python2.7/dist-packages/pykolab/conf/__init__.py", line 
528, in get
     return self.cfg_parser.get(section, key)
   File "/usr/lib/python2.7/ConfigParser.py", line 623, in get
     return self._interpolate(section, option, value, d)
   File "/usr/lib/python2.7/ConfigParser.py", line 691, in _interpolate
     self._interpolate_some(option, L, rawval, section, vars, 1)
   File "/usr/lib/python2.7/ConfigParser.py", line 723, in 
_interpolate_some
     option, section, rest, var)
InterpolationMissingOptionError: Bad value substitution:
         section: [kolab]
         option : domain_sync_interval
         key    : givenname
         rawval :

Traceback occurred, please report a bug at http://bugzilla.kolabsys.com

Thanks for your thoughs,
Brad


More information about the users mailing list