setup-kolab crashing in the middle of setup
Closed, ResolvedPublic


rpm -qv pykolab

Today twice reinstall server and start everything from scratch and every time start setup-kolab it crashes after Kolab Service password [password]: . Os Centos 7.2 minimal install so all required packages have been installed with yum install kolab . Kolab log files are empty so don't have anything to post .

Kolab Service password [password]: 
Traceback (most recent call last):
  File "/usr/sbin/setup-kolab", line 43, in <module>
  File "/usr/lib/python2.7/site-packages/pykolab/setup/", line 74, in run
  File "/usr/lib/python2.7/site-packages/pykolab/setup/", line 170, in execute
  File "/usr/lib/python2.7/site-packages/pykolab/setup/", line 202, in execute
    components[component_name]['function'](conf.cli_args, kw)
  File "/usr/lib/python2.7/site-packages/pykolab/setup/", line 478, in execute
  File "/usr/lib64/python2.7/", line 524, in call
    return Popen(*popenargs, **kwargs).wait()
  File "/usr/lib64/python2.7/", line 660, in __init__
    raise TypeError("bufsize must be an integer")
TypeError: bufsize must be an integer


Ticket Type

Event Timeline

Benderis created this task.Oct 1 2016, 5:57 PM
Benderis raised the priority of this task from 60 to Unbreak Now!.Oct 3 2016, 7:51 PM
Benderis updated the task description. (Show Details)

Hi, same Problem here with a fresh installation of CentOS Linux release 7.2.1511 (Core)...

vanmeeuwen closed this task as Resolved.Oct 5 2016, 9:43 AM
vanmeeuwen claimed this task.
Benderis reopened this task as Open.Oct 6 2016, 12:52 PM

To make sure everything started from scratch I just reinstall CentOS again and during kolab-setup it crashes at the same point . Did check file before setup-kolab and it's patched .

Centos 7.2/64 on a fresh system install shows same stack but different exception message, i.e. that /usr/bin/freshclam is not present in the system.
The kolab package should probably have a dependency on clamav-update?

machniak closed this task as Resolved.Oct 11 2016, 2:53 PM

We have a separate ticket for this issue now - T1607.