Backtrace : 8.7.80.569.f0345abbe-0+88.1



  • Hai, just updated to 8.7.80.569.f0345abbe-0+88.1 and this is the result when stopping kopano-server.

    Tue Feb 5 14:20:40 2019: [warning] Shutting down
    Tue Feb 5 14:20:40 2019: [crit ] ----------------------------------------------------------------------
    Tue Feb 5 14:20:40 2019: [crit ] Fatal error detected. Please report all following information.
    Tue Feb 5 14:20:40 2019: [crit ] Application kopano-server version: 8.7.80
    Tue Feb 5 14:20:40 2019: [crit ] OS: Linux, release: 4.9.0-8-amd64, version: #1 SMP Debian 4.9.130-2 (2018-10-27), hardware: x86_64
    Tue Feb 5 14:20:40 2019: [crit ] Thread name: z-s: idle threa
    Tue Feb 5 14:20:40 2019: [crit ] Peak RSS: 27524
    Tue Feb 5 14:20:40 2019: [crit ] Pid 8006 caught SIGSEGV (11), traceback:
    Tue Feb 5 14:20:40 2019: [crit ] Backtrace:
    Tue Feb 5 14:20:40 2019: [crit ] #0. /usr/lib/x86_64-linux-gnu/libkcutil.so.0(+0x48860) [0x7f5006753860]
    Tue Feb 5 14:20:40 2019: [crit ] #1. /usr/lib/x86_64-linux-gnu/libkcutil.so.0(+0x31d7d) [0x7f500673cd7d]
    Tue Feb 5 14:20:40 2019: [crit ] #2. /usr/lib/x86_64-linux-gnu/libkcutil.so.0(_ZN2KC23generic_sigsegv_handlerEPNS_8ECLoggerEPKcS3_iPK9siginfo_tPKv+0x1bd) [0x7f500673d05d]
    Tue Feb 5 14:20:40 2019: [crit ] #3. /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0) [0x7f50013fc0c0]
    Tue Feb 5 14:20:40 2019: [crit ] Signal errno: Success, signal code: 1
    Tue Feb 5 14:20:40 2019: [crit ] Sender pid: 0, sender uid: 0, si_status: 98022544
    Tue Feb 5 14:20:40 2019: [crit ] Signal value: 98022544, faulting address: (nil)
    Tue Feb 5 14:20:40 2019: [crit ] When reporting this traceback, please include Linux distribution name (and version), system architecture and Kopano version.

    Daily package , Debian 9 Amd64
    kopano-server 8.7.80.569.f0345abbe-0+88.1

    Anything else you guys need to debug this?



  • Reply for myself, testing bit more, since i notice more of these backtraces in the forum.

    If someone can check this also, this might help in fixing this problem.

    if i run :

    systemctl stop kopano-server
    systemctl start kopano-server 
    

    i can repeat this without any problems. No crashed.

    if i use this script to stop/start like this :

    /usr/local/bin/kopano-maint.sh stop
    /usr/local/bin/kopano-maint.sh start

    It also works fine. This is the script.

    #!/usr/bin/env bash
    
    # Order matters !
    SERVICES="postfix kopano-spooler kopano-dagent kopano-gateway kopano-ical kopano-search kopano-monitor kopano-server kopano-konnectd"
    
    CMD_SYSTEMCTL="$(which systemctl)"
    
    if [ -z "$1" ]
    then
        echo "Use stop/start to start/stop the needed services, exiting now.."
        exit 1
    fi
    
    if [ "$1" = stop ]
    then
        for x in $SERVICES
        do
            ${CMD_SYSTEMCTL} "$1" "$x"
        done
    fi
    
    if [ "$1" = start ]
    then
        for x in $SERVICES
        do
            ${CMD_SYSTEMCTL} "$1" "$x"
        done
    fi
    

    now if i use :
    bash /usr/local/bin/kopano-maint.sh stop
    bash /usr/local/bin/kopano-maint.sh start

    now it im getting the backtrace.

    If i run all commands in the same order as the script, but manualy it also works fine.

    So i dont understand why this happing? anyone?


Log in to reply