[Pkg-giraffe-maintainers] Bug#947040: kopano-core: PIDFILE in /etc/init.d/kopano-* does not match /etc/kopano/*.cfg

Albert programming at kogro.org
Thu Dec 19 11:43:20 GMT 2019


Package: kopano-core
Version: 8.7.0-3
Severity: normal

Dear Maintainer,

First of all thanks for the wonderfull job of bringing kopano to the debian
repositories! It is a lot easier to install/maintain thanks to your work.

When configuring kopano, I needed to restart the server to activate the new
configuration. I did a:

  systemctl restart kopano-server

I noticed the following messages in /var/log/syslog:

Dec 19 11:04:42 defiant systemd[1]: Stopping LSB: Kopano Collaboration
Platform's Storage Server...
Dec 19 11:04:42 defiant kopano-server[4728]: Stopping Kopano server: kopano-
serverNo /usr/sbin/kopano-server found running; none killed.
Dec 19 11:04:42 defiant kopano-server[4728]:  failed!
Dec 19 11:04:42 defiant systemd[1]: kopano-server.service: Succeeded.
Dec 19 11:04:42 defiant systemd[1]: Stopped LSB: Kopano Collaboration
Platform's Storage Server.
Dec 19 11:04:42 defiant systemd[1]: kopano-server.service: Found left-over
process 1506 (kopano-server) in control group while starting unit. Ignoring.
Dec 19 11:04:42 defiant systemd[1]: This usually indicates unclean termination
of a previous run, or service implementation deficiencies.
Dec 19 11:04:42 defiant systemd[1]: Starting LSB: Kopano Collaboration
Platform's Storage Server...
Dec 19 11:04:43 defiant kopano-server[4744]: Starting kopano-server version
8.7.0 (pid 4744 uid 0)
Dec 19 11:04:43 defiant kopano-server[4744]: Unable to bind to port 236:
Address already in use. This is usually caused by another process (most likely
another server) already using this port. This program will terminate now.

In the end the 'old' kopano-server kept running, while the 'one' terminated due
to 'unable to bind port 236'.


Searching for the source of this problem, I found that the PIDFILE directives
in /etc/init.d/kopano-* are not consistent with the ones used in
/etc/init.d/kopano-*.

My problem was locally solved by changing /etc/init.d/kopano-* and running
'systemctl daemon-reload'.

In my opinion others can benefit if this change is integrated in the kopano-
package.

Thanks for all your work.
If you need more info, please contact me.

Albert



-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kopano-core depends on:
ii  kopano-backup   8.7.0-3
ii  kopano-dagent   8.7.0-3
ii  kopano-gateway  8.7.0-3
ii  kopano-ical     8.7.0-3
ii  kopano-monitor  8.7.0-3
ii  kopano-search   8.7.0-3
ii  kopano-server   8.7.0-3
ii  kopano-spamd    8.7.0-3
ii  kopano-spooler  8.7.0-3
ii  kopano-utils    8.7.0-3

kopano-core recommends no packages.

Versions of packages kopano-core suggests:
pn  kopano-webapp  <none>

-- no debconf information



More information about the Pkg-giraffe-maintainers mailing list