Bug#924569: kopano-server: SysV init scripts use wrong pid files

2019-04-20 Thread Richard Lucassen
On Sat, 20 Apr 2019 08:10:02 +0200
Carsten Schoenert  wrote:

> > Workaround is to set PIDFILE:
> > 
> > PIDFILE=/var/run/kopano/server.pid
> 
> good catch. Thanks. Remarked for one of the next uploads.
> 
> > Other SysV instances of kopano-* suffer from this issue as well.
> 
> Could you please elaborate this a bit more?

Well, quite simple: all other /etc/init.d/kopano-* init scripts have a
wrong PIDFILE= path.

At the moment I have no kopano server running here.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+



Bug#924569: kopano-server: SysV init scripts use wrong pid files

2019-04-20 Thread Carsten Schoenert
Hi,

please use 'Reply All' so the BTS is getting the information as well.

Am 20.04.19 um 10:46 schrieb Richard Lucassen:
> On Sat, 20 Apr 2019 08:10:02 +0200
> Carsten Schoenert  wrote:
> 
>>> Workaround is to set PIDFILE:
>>>
>>> PIDFILE=/var/run/kopano/server.pid
>>
>> good catch. Thanks. Remarked for one of the next uploads.
>>
>>> Other SysV instances of kopano-* suffer from this issue as well.
>>
>> Could you please elaborate this a bit more?
> 
> Well, quite simple: all other /etc/init.d/kopano-* init scripts have a
> wrong PIDFILE= path.
> 
> At the moment I have no kopano server running here.

It's not that simple.
I don't know at what time Kopano has changed here anything but the old
style was to use a full name of the service to mark the PID file.

kopano-server
kopano-search
...

If I read your previous email correctly the PIF files are now living in
/var/run/kopano/

As I normally don't use SysV scripts anymore and also don't do any
testing of the Kopano packages in this regard and I'm not sure what the
correct naming now is.
I guess the new behavior is dropping the prefix name 'kopano' and only
use the service name as PID file name within /var/run/kopano/. But
without some verification it's not clear what we need to adjust in the
packaging. If someone will come up with a validated checking I'm happy
to adjust this into the packaging.

-- 
Regards
Carsten Schoenert



Bug#924569: kopano-server: SysV init scripts use wrong pid files

2019-04-19 Thread Carsten Schoenert
Hello Richard,

Am 14.03.19 um 14:08 schrieb Richard Lucassen:
> Package: kopano-server
> Version: 8.7.0-2
> Severity: normal
> 
> Dear Maintainer,
> 
> Running e.g. "service kopano-server stop" results in:
> 
> [] Stopping Kopano server: kopano-server
> No /usr/sbin/kopano-server found running; none killed.
> failed!
> 
> The PIDFILE variable in "/etc/init.d/kopano-server":
> 
> PIDFILE=/var/run/$NAME.pid
> 
> (where NAME=`basename /usr/sbin/kopano-server`)
> 
> does not correspond to the real pid file:
> 
> /var/run/kopano/server.pid
> 
> Workaround is to set PIDFILE:
> 
> PIDFILE=/var/run/kopano/server.pid

good catch. Thanks. Remarked for one of the next uploads.

> Other SysV instances of kopano-* suffer from this issue as well.

Could you please elaborate this a bit more?
It would be helpful if you can provide the needed changes to the other
SysV init scripts somehow. We have the following other init scripts
within the packaging.

> ./kopano-monitor.init
> ./kopano-ical.init
> ./kopano-presence.init
> ./kopano-search.init
> ./kopano-dagent.init
> ./kopano-spooler.init
> ./kopano-server.init
> ./kopano-gateway.init
> ./kopano-spamd.init

Thanks!

-- 
Regards
Carsten Schoenert



Bug#924569: kopano-server: SysV init scripts use wrong pid files

2019-03-14 Thread Richard Lucassen
Package: kopano-server
Version: 8.7.0-2
Severity: normal

Dear Maintainer,

Running e.g. "service kopano-server stop" results in:

[] Stopping Kopano server: kopano-server
No /usr/sbin/kopano-server found running; none killed.
failed!

The PIDFILE variable in "/etc/init.d/kopano-server":

PIDFILE=/var/run/$NAME.pid

(where NAME=`basename /usr/sbin/kopano-server`)

does not correspond to the real pid file:

/var/run/kopano/server.pid

Workaround is to set PIDFILE:

PIDFILE=/var/run/kopano/server.pid

Other SysV instances of kopano-* suffer from this issue as well.

Richard.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-2-amd64 (SMP w/2 CPU cores)
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 /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages kopano-server depends on:
ii  dbconfig-common 2.0.11
ii  debconf [debconf-2.0]   1.5.71
ii  init-system-helpers 1.56+nmu1
ii  kopano-common   8.7.0-2
ii  kopano-libs 8.7.0-2
ii  libc6   2.28-8
ii  libcom-err2 1.44.5-1
ii  libgcc1 1:8.3.0-2
ii  libgsoap-2.8.75 2.8.75-1
ii  libgssapi-krb5-21.17-2
ii  libicu6363.1-6
ii  libk5crypto31.17-2
ii  libkrb5-3   1.17-2
ii  libldap-2.4-2   2.4.47+dfsg-3
ii  libmariadb3 1:10.3.13-1
ii  libpam0g1.3.1-5
ii  libssl1.1   1.1.1b-1
ii  libstdc++6  8.3.0-2
ii  lsb-base10.2018112800
ii  mariadb-client-10.3 [virtual-mysql-client]  1:10.3.13-1
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages kopano-server recommends:
ii  mariadb-server  1:10.3.13-1

kopano-server suggests no packages.

-- Configuration Files:
/etc/init.d/kopano-server changed [not included]
/etc/kopano/server.cfg changed [not included]
/etc/kopano/unix.cfg changed [not included]

-- debconf information excluded