Upgrade success but slow stop and Backtrace..

thctlo

Hai,

I’ve just upgrade kopano.
from version : 8.7.80.465.4206adbb5-0+56.1 500
to version : 8.7.80.529.bfd59fc27-0+72.1 500

first i noticed :

Jan 25 16:03:13 mail1 kernel: [1232400.441746] apache2[28180]: segfault at 7fb58d667718 ip 000055962db0f124 sp 00007ffc33ca4b90 error 4 in apache2[55962dad4000+9c000]

First i cleared the logs, then i stoppeded kopano with : systemctl stop kopano-*
This took over 2 minutes.
resulting in :

cat *.log

Fri Jan 25 16:10:21 2019: [=======] LMTP service will now exit
Fri Jan 25 16:10:21 2019: [kopano-gateway|T8035] [=======] POP3/IMAP Gateway will now exit
Fri Jan 25 16:11:51 2019: [debug  ] Previous message logged 7 times
Fri Jan 25 16:11:51 2019: [debug  ] Received signal 15 by TID 7642
Fri Jan 25 16:11:51 2019: [warning] Shutting down
Fri Jan 25 16:11:51 2019: [info   ] Shutdown all current sessions
Fri Jan 25 16:11:51 2019: [error  ] K-1249: abandoned dfpair/ECDatabase instance
Fri Jan 25 16:11:51 2019: [info   ] Shutdown notification manager
Fri Jan 25 16:11:51 2019: [crit   ] ----------------------------------------------------------------------
Fri Jan 25 16:11:51 2019: [crit   ] Fatal error detected. Please report all following information.
Fri Jan 25 16:11:51 2019: [crit   ] Application kopano-server version: 8.7.80
Fri Jan 25 16:11:51 2019: [crit   ] OS: Linux, release: 4.9.0-8-amd64, version: #1 SMP Debian 4.9.130-2 (2018-10-27), hardware: x86_64
Fri Jan 25 16:11:51 2019: [crit   ] Thread name: z-s: idle threa
Fri Jan 25 16:11:51 2019: [crit   ] Peak RSS: 28136
Fri Jan 25 16:11:51 2019: [crit   ] Pid 7642 caught SIGSEGV (11), traceback:
Fri Jan 25 16:11:51 2019: [crit   ] Backtrace:
Fri Jan 25 16:11:51 2019: [crit   ] #0. /usr/lib/x86_64-linux-gnu/libkcutil.so.0(+0x48860) [0x7f46fe5b3860]
Fri Jan 25 16:11:51 2019: [crit   ] #1. /usr/lib/x86_64-linux-gnu/libkcutil.so.0(+0x31d7d) [0x7f46fe59cd7d]
Fri Jan 25 16:11:51 2019: [crit   ] #2. /usr/lib/x86_64-linux-gnu/libkcutil.so.0(_ZN2KC23generic_sigsegv_handlerEPNS_8ECLoggerEPKcS3_iPK9siginfo_tPKv+0x1bd) [0x7f46fe59d05d]
Fri Jan 25 16:11:51 2019: [crit   ] #3. /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0) [0x7f46f925c0c0]
Fri Jan 25 16:11:51 2019: [crit   ] #4. /usr/lib/x86_64-linux-gnu/libkcserver.so.0(_ZN2KC17ECDatabaseFactory12S_thread_endEPv+0x33e) [0x7f46fe1ef3be]
Fri Jan 25 16:11:51 2019: [crit   ] #5. /lib/x86_64-linux-gnu/libpthread.so.0(+0x65e9) [0x7f46f92515e9]
Fri Jan 25 16:11:51 2019: [crit   ] #6. /lib/x86_64-linux-gnu/libpthread.so.0(+0x7648) [0x7f46f9252648]
Fri Jan 25 16:11:51 2019: [crit   ] #7. /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f46f86ebacf]
Fri Jan 25 16:11:51 2019: [crit   ] Signal errno: Success, signal code: 128
Fri Jan 25 16:11:51 2019: [crit   ] Sender pid: 0, sender uid: 0, si_status: -450016384
Fri Jan 25 16:11:51 2019: [crit   ] Signal value: -450016384, faulting address: (nil)
Fri Jan 25 16:11:51 2019: [crit   ] When reporting this traceback, please include Linux distribution name (and version), system architecture and Kopano version.

im configuring the server, ( and yes i know how ), is it possible that this happens because i only enabled :
kopano-server.service kopano-search.service kopano-spooler.service

i’ve not yet configured the others.
and im overridding some settings:

# /etc/systemd/system/kopano-server.service.d/override.conf
[Unit]
After=network-online.target mysql.service mariadb.service
Wants=network-online.target

# /etc/systemd/system/kopano-search.service.d/override.conf
[Unit]
After=kopano-server.service
Wants=kopano-server.service

# /etc/systemd/system/kopano-spooler.service.d/override.conf
[Unit]
After=kopano-server.service
Wants=kopano-server.service

which results in a bit cleaner logs when starting.

The configured services all start without any errors.

The service which is slow stopping is the spooler.