Hello Carsten,
You're right, my bug-report is a duplicate of the one you mentioned. Please mark my ticket so, I'm looking forward for the next point release. I was already puzzled that nobody filed a bug-report for this, now I see that it was filed in sid. Is it custom in the debian-world to report bugs for testing only, not for stable? In the future I'm willing to do testing for you, for the moment I'm just happy that my 3rd install-from-scratch while still having my mail-database just works. Thanks to you guys it was a lot easier than installing the communitiy-edition from kopano. Kind regards, Albert -----Original message----- From: Carsten Schoenert <[email protected]> Sent: Thursday 19th December 2019 21:11 To: Albert (programming) <[email protected]> Cc: [email protected] Subject: Re: Bug#947040: kopano-core: PIDFILE in /etc/init.d/kopano-* does not match /etc/kopano/*.cfg Hello Albert, Am 19.12.19 um 12:43 schrieb Albert: > 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. we had several bug reports about this or similar issues. Your report sounds like https:/bugs.debian.org/924569 There is currently version 8.7.0-5 in testing which needs to get into the next point release of Debian buster. I'm quite sure your problem is solved within the modifications we have added to that version. You might want to look at the modifications since 8.7.0-3 within our packaging repository on Salsa. https://salsa.debian.org/giraffe-team/kopanocore/commits/debian/sid If you are willing to test this version I can provide some packages. -- Regards Carsten Schoenert
