The queue froze after updating. Kolab 16
Closed, InvalidPublic


i update kolab16 on my centos 7.5

yum update

after that the kolabd service is started with such message:

systemctl status kolabd
● kolabd.service - Kolab Groupware Server.
   Loaded: loaded (/usr/lib/systemd/system/kolabd.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2018-10-10 21:38:27 MSK; 6s ago
  Process: 12899 ExecStop=/bin/kill -TERM $MAINPID (code=exited, status=0/SUCCESS)
  Process: 12902 ExecStart=/usr/sbin/kolabd $FLAGS --pid-file /run/kolabd/ (code=exited, status=0/SUCCESS)
 Main PID: 12904 (kolabd)
   CGroup: /system.slice/kolabd.service
           ├─12904 /usr/bin/python /usr/sbin/kolabd --fork -l warning --pid-file /run/kolabd/
           └─12905 /usr/bin/python /usr/sbin/kolabd --fork -l warning --pid-file /run/kolabd/

Oct 10 21:38:26 mail systemd[1]: Starting Kolab Groupware Server....
Oct 10 21:38:27 mail systemd[1]: kolabd.service: Supervising process 12904 which is not our child. We'll most likely not notice when it exits.
Oct 10 21:38:27 mail systemd[1]: Started Kolab Groupware Server..
netstat -apn | grep 10026 
no ports
ps aux | grep wallaced
no service
export USER=kolab; /usr/bin/python /usr/sbin/wallaced -l warning --pid-file /run/wallaced/
2018-10-10 21:43:51,268 pykolab.wallace WARNING [13052] No contents configured for footer module
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/wallace/", line 480, in run
  File "/usr/lib/python2.7/site-packages/wallace/", line 203, in do_wallace
  File "/usr/lib/python2.7/site-packages/wallace/", line 333, in pickup_spool_messages
    pickup_message(filepath, self.modules, module=module, stage=stage)
  File "/usr/lib/python2.7/site-packages/wallace/", line 81, in pickup_message
    cb_action_ACCEPT('wallace', filepath)
  File "/usr/lib/python2.7/site-packages/wallace/", line 333, in cb_action_ACCEPT
    message = Parser().parse(open(filepath, 'r'), True)
IOError: [Errno 2] No such file or directory: '/var/spool/pykolab/wallace/footer/incoming/tmp9judaN'
Traceback occurred, please report a bug at
systemctl status postfix

Oct 10 21:49:54 mail postfix/error[13910]: 4756D13CFDA: to=<>, relay=none, delay=8877, delays=8873/3.5/0/...refused)
Oct 10 21:49:54 mail postfix/error[13880]: 4550A197830: to=<>, relay=none, delay=340744, delays=340740/3.5/0/0....refused)
Oct 10 21:49:54 mail postfix/error[13133]: 4B82113AD04: to=<>, relay=none, delay=12780, delays=12776/3.5...refused)
Oct 10 21:49:54 mail postfix/error[13894]: 459B7177224: to=<>, relay=none, delay=427404, delays=427400/3.5/0/0....refused)
Oct 10 21:49:54 mail postfix/error[13883]: 4B60D177022: to=<>, relay=none, delay=7184, delays=7180/3.5/0/0.07, d...refused)
delivery temporarily suspended: connect to[]:10026: Connection refused

what fix it?


Ticket Type

Event Timeline

SergeyDjam updated the task description. (Show Details)Oct 10 2018, 8:52 PM

I am affected by this issue too. On Ubuntu 16.04. Wallaced crashes. Systemd shows that it is still running (because there is no unit file, only init script, which calls wallaced with the --fork option) - very confusing. Wallaced started again after deleting the content of /var/spool/pykolab/wallace/footer/incoming/. Will it happen again?

vanmeeuwen closed this task as Invalid.Mar 21 2019, 11:29 PM
vanmeeuwen added a subscriber: vanmeeuwen.

Wallace on CentOS 7 for kolab 16 uses systemd, not sysvinit, so I don't understand what I'm being told here.