cyrus.conf

[kiwi_uk]

Hi,

I sync'd the overlay for Kolab today and emerged the updates which turned out to be a mistake cyrus.conf got absolutely broken - it made the cyrus manager segfault when it read the config file. I'm not 100% sure if it specific to my system or not but the conf file had a load of "FALSE" and "TRUE" lines in it and none of the neccesary config options like enabling imaps. I've configured it by hand for now after a day of beating my head against a wall.

What details can I give to be more helpful?

[Gunnar Wrobel]

Hm, sounds like a strange error. Does /etc/cyrus.conf get rewritten to contain the bad content again once you run kolabconf?

[kiwi_uk]

Yes. It also gets rewritten badly after editting options in the manager web interface. Mail filtering seems to be broken too even though I've got sieve running and defaultbc is in place. I have yet to chase this down. I'm not expert with any of the components of Kolab but I'm sure I'll get there.

Jon

[Gunnar Wrobel]

Do you see the same kind of problematic content in the template /etc/kolab/templates/cyrus.conf.template? This is the file that gets transformed into /etc/cyrus.conf. Or does that file look normal?

[kiwi_uk]

It looks like a valid template to me.

The "@@@xxx@@@" sections in the below sample of said file are where the TRUE and FALSE values appear. It's replacing @@@xxx@@@ with "TRUE" instead of the relevant line of config.

# UNIX sockets start with a slash and are put into /var/imap/socket.
SERVICES {
  @@@cyrus-imap@@@
  @@@cyrus-imaps@@@
  @@@cyrus-pop3@@@
  @@@cyrus-pop3s@@@
  @@@cyrus-sieve@@@

  #sieve                cmd="timsieved" listen="sieve" prefork=0

  # at least one LMTP is required for delivery
  lmtp          cmd="lmtpd -a" listen="127.0.0.1:2003"
  lmtpunix      cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0

  # this is only necessary if using notifications
  notify        cmd="notifyd" listen="/var/imap/socket/notify" proto="udp" prefork=1
}

[Gunnar Wrobel]

Hm, then this would be a kolabconf problem. I cannot verify the problem on my machines but it might somehow be related to the perl packages or perl version you are using. Can you post your version of perl-kolab and perl itself?

[kiwi_uk]

[ebuild   R   ] dev-perl/perl-kolab-20060829  73 kB [1]
[ebuild   R   ] dev-lang/perl-5.8.8-r2  USE="berkdb gdbm -build -debug -doc -ithreads -perlsuid" 0 kB

I'll be happy to give you a shell on the machine in question if that will help.

[kiwi_uk]

I've made ever such a small amount of progress on this but I'm struggling.

It seems that the function that generates the neccesary parts of cyrus.conf (in Conf.pm) is not being run. I entered some additional debug statements and made sure kolab.global had logging set on 100 and nothing gets printed into syslog when I run kolabconf or change the settings in the web interface.

I can't find where the function is called from though... it's "sub genCyrusConfiguration" or similar. I do not remember. Any pointers?

Thanks,
Jon

[kiwi_uk]

Edit: It's only the virtual map thats causing problems, not both.

I made another small bit of progress... still using the version of kolabd and perl-kolab above.

Lines 803 and 804 of Conf.pm call "buildPostfixTransportMap" and "buildPostfixVirtualMap". Both of these cause kolabconf to break and not complete with no useful error messages on screen. They only go into syslog.

I've yet to figure out why these two specifically cause problems as the same function works for "access", aliases, canonical, relocated and kolabvirtual maps.

Jon

[Gunnar Wrobel]

Do you have any strange values within /etc/kolab/templates/virtual.template or transport.template?

The default is that they both contain no value.

[kiwi_uk]

server2 templates # cat virtual.template
#KOLAB_META_START
TARGET=/etc/postfix/virtual
PERMISSIONS=0640
OWNERSHIP=root:root
KOLAB_META_END
# (c) 2003 Tassilo Erlewein <tassilo.erlewein@erfrakon.de>
# (c) 2003 Martin Konold <martin.konold@erfrakon.de>
# This program is Free Software under the GNU General Public License (>=v2).
# Read the file COPYING that comes with this packages for details.

# this file is automatically written by the Kolab config backend
# manual additions are lost unless made to the template in the Kolab config directory

# manual additions are lost unless made to the template in the Kolab config directory
# the template is  /etc/kolab/templates/virtual.template
server2 templates # cat transport.template
KOLAB_META_START
TARGET=/etc/postfix/transport
PERMISSIONS=0640
OWNERSHIP=root:root
KOLAB_META_END
# (c) 2003 Tassilo Erlewein <tassilo.erlewein@erfrakon.de>
# (c) 2003 Martin Konold <martin.konold@erfrakon.de>
# This program is Free Software under the GNU General Public License (>=v2).
# Read the file COPYING that comes with this packages for details.

# this file is automatically written by the Kolab config backend
# manual additions are lost unless made to the template in the Kolab config directory

# manual additions are lost unless made to the template in the Kolab config directory
# the template is  /etc/kolab/templates/transport.template

[Gunnar Wrobel]

A little bit late but at least I do understand your inital error with the "TRUE" and "FALSE" values now. This happens if kolabconf breaks somewhere in the middle of the konfiguration process as in your case with the postfix templates. This needs to be fixed in kolabconf because this type of behaviour is extremely problematic.

[eliasp]

More than 1 year after the last post on this thread, I just stumbled upon this problem too.

Running:

Code:

dev-perl/perl-kolab-2.1
dev-php/horde-framework-kolab-3.2_alpha-r1
net-mail/kolab-resource-handlers-2.1
net-mail/kolab-webadmin-2.1
net-mail/kolabd-2.1
dev-lang/perl-5.8.8-r4

What else do you need to know to debug this?