From Kolab wiki

A gerneral collection of very basic problems you might experience when administrating a Kolab server.

Contents 1 Server does not start, nothing in the logs 1.1 Problem 1.2 Solution 2 I changed a configuration file xyz.conf to suit my own needs but now my changes have gone! 2.1 Problem 2.2 Solution 3 Unable to determine the gid of user 'kolab' 3.1 Problem 3.2 Solution 4 Unable to connect to local Cyrus admin interface 4.1 Problem 4.2 Solution 5 amavisd ... failed with return code 9 5.1 Problem 5.2 Solution 6 My problem persists 7 Back

Server does not start, nothing in the logs

Operating system		Distribution		Kolab version
Applies to:	probably applies to all *NIX systems	Applies to:	probably all distributions	Applies to:	Kolab 2.0 and higher
Found on:	Linux	Found on:	unknown	Found on:	unknown

Problem

Possible Problem: Large files

One of the files could have been grown beyond 2 Gibibyte on a 32bit system. E.g. Cyrus and fsl do not have large file support and might not be able to bring out another message, if the logfile is too large.

Possible Problem: stale postfix lockfile

After a crash postfix left a stale lockfile and a bug in the openpkg test will prevent that an error message is printed.

Solution

General advice

If starting a component manually will not give you enough information, try starting it with '--keep --verbose'.

Example:

/kolab/bin/openpkg rc --keep --verbose postfix start

Examine the resulting files in '/tmp/rc.*'. You can try to run rc.tmp with bash debug information or manually. If the command give you nothing, try following its system calls, e.g. with 'strace' on GNU/Linux.

Possible Solution: Large files

Search for large files. Make them smaller and inquire the reason for the size. E.g. move away a large logfile.

Possible Solution: stale postfix lockfile

Make sure the process is gone and then move away the master.pid file.

I changed a configuration file xyz.conf to suit my own needs but now my changes have gone!

Operating system		Distribution		Kolab version
Applies to:	applies to all *NIX systems	Applies to:	all distributions	Applies to:	Kolab 2.0 and higher
Found on:	Linux	Found on:	all	Found on:	all

Problem

The kolab server uses templates as a basis for all configuration files relevant to the server. These can be found in /kolab/etc/kolab/templates. Changes in the original configuration files will get overwritten!

Solution

Please edit only the template files in /kolab/etc/kolab/templates to make your changes permanent. After editing a template, run

/kolab/sbin/kolabconf 

to process your changes into the configuration files. Please also read the page dedicated to the Kolab configuration concept

Unable to determine the gid of user 'kolab'

Operating system		Distribution		Kolab version
Applies to:	probably applies to all *NIX systems	Applies to:	probably all distributions	Applies to:	Kolab 2.0 and higher
Found on:	Linux	Found on:	Linux - Suse 9.2 - i386	Found on:	kolab2 beta4, local build

Problem

This is a syslog message. This message is generated for example when kolab is started up (using '/etc/init.d/kolab start' or similar methods). the unique syslog message pattern is:

• "C Error: Unable to determine the gid of user 'kolab'"

Possible Problem

The group 'kolab' is integral part of the Kolab configuration. The existence is not verified prior to use, resulting in a sequence of problems and error messages. See also:

• Unable to connect to local Cyrus admin interface

Solution

• Stop Kolab
• add group 'kolab'
• change group ownership of impacted files. For example do:

find /kolab -group <previous kolab user's group> -exec chgrp kolab {} \;

• change group id of user kolab to group id of group 'kolab'.
• Start Kolab

Unable to connect to local Cyrus admin interface

Operating system		Distribution		Kolab version
Applies to:	probably applies to all *NIX systems	Applies to:	probably all distributions	Applies to:	Kolab 2.0 and higher
Found on:	Linux	Found on:	Linux - Suse 9.2 - i386	Found on:	kolab2 beta4, local build

Problem

This is a syslog message. This message is generated for example when kolab is started up(using '/etc/init.d/kolab start' or similar methods). the unique syslog message pattern is:

• "kolabd[...]: Y Error: Unable to connect to local Cyrus admin interface"

Possible Problem

Certain services do not start up. A dependant service complain about missing service. Could be caused be missing group kolab. See also:

• Unable to determine the gid of user 'kolab'

Solution

See: Unable to determine the gid of user 'kolab'

amavisd ... failed with return code 9

Operating system		Distribution		Kolab version
Applies to:	probably applies to all *NIX systems	Applies to:	probably all distributions	Applies to:	Kolab 2.0 and higher
Found on:	Linux	Found on:	Linux - Suse 9.2 - i386	Found on:	kolab2 beta4, local build

Problem

This is a command output. This message is generated when manually calling the startup command for kolab for example using '/etc/init.d/kolab start' or similar methods. The output is as follows:

openpkg:rc:WARNING: /kolab:amavisd:%start: failed with return code 9
openpkg:rc:NOTICE: output from stdout/stderr is following:
+----------------------------------------------------------------------
| No $LOGFILE is specified (and not logging via syslog) at /kolab/sbin/amavisd line 1050.
+----------------------------------------------------------------------

Possible Problem

Could be caused be missing group kolab. See also:

• Unable to determine the gid of user 'kolab'

Solution

• See: Unable to determine the gid of user 'kolab'

As an alternative you might try to delete your temporary files:

rm -rf /tmp/obmtool* 

and rerun the installation.

My problem persists

None of the above hints did help you to solve your problem?

Please check your options for getting support and reporting errors.

Back

Back to the troubleshooting index