Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    Kopano server fatal error when shutting down

    Kopano Groupware Core
    1
    1
    145
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • genesis74
      genesis74 last edited by

      Hi there,

      once a day I am shutting down kopano-server for a maintenance/backup script. This shutdown happens at 5 a.m. During routine check of server.log I found this entry every now and then (once in november, none in december, three times in january):

      Wed Jan 23 05:00:02 2019: [warning] Shutting down
      Wed Jan 23 05:00:03 2019: [crit   ] ----------------------------------------------------------------------
      Wed Jan 23 05:00:03 2019: [crit   ] Fatal error detected. Please report all following information.
      Wed Jan 23 05:00:03 2019: [crit   ] Application kopano-server version: 8.6.9
      Wed Jan 23 05:00:03 2019: [crit   ] OS: Linux, release: 4.15.0-43-generic, version: #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018, hardware: x$
      Wed Jan 23 05:00:03 2019: [crit   ] Thread name: ECScheduler:wor
      Wed Jan 23 05:00:03 2019: [crit   ] Peak RSS: 58828
      Wed Jan 23 05:00:03 2019: [crit   ] Pid 1215 caught SIGSEGV (11), traceback:
      Wed Jan 23 05:00:03 2019: [crit   ] Backtrace:
      Wed Jan 23 05:00:03 2019: [crit   ] #0. /usr/lib/libkcutil.so.0(+0x2a290) [0x7f0ad057e290]
      Wed Jan 23 05:00:03 2019: [crit   ] #1. /usr/lib/libkcutil.so.0(+0x22a2d) [0x7f0ad0576a2d]
      Wed Jan 23 05:00:03 2019: [crit   ] #2. /usr/lib/libkcutil.so.0(_ZN2KC23generic_sigsegv_handlerEPNS_8ECLoggerEPKcS3_iPK9siginfo_tPKv+0x1a3)$
      Wed Jan 23 05:00:03 2019: [crit   ] #3. /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7f0ace939890]
      Wed Jan 23 05:00:03 2019: [crit   ] #4. /usr/lib/libkcserver.so.0(+0x4d27a) [0x7f0acffd927a]
      Wed Jan 23 05:00:03 2019: [crit   ] #5. /usr/lib/libkcserver.so.0(_ZN2KC17ECDatabaseFactory20CreateDatabaseObjectEPPNS_10ECDatabaseERNSt7__$
      Wed Jan 23 05:00:03 2019: [crit   ] #6. /usr/lib/libkcserver.so.0(+0x4d4d0) [0x7f0acffd94d0]
      Wed Jan 23 05:00:03 2019: [crit   ] #7. /usr/lib/libkcserver.so.0(+0x103df5) [0x7f0ad008fdf5]
      Wed Jan 23 05:00:03 2019: [crit   ] #8. /usr/lib/libkcserver.so.0(_ZN2KC17SoftDeleteRemoverEPv+0x175) [0x7f0ad00dd0c5]
      Wed Jan 23 05:00:03 2019: [crit   ] #9. /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7f0ace92e6db]
      Wed Jan 23 05:00:03 2019: [crit   ] #10. /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f0ace0b688f]
      Wed Jan 23 05:00:03 2019: [crit   ] Signal errno: Erfolg, signal code: 1
      Wed Jan 23 05:00:03 2019: [crit   ] Sender pid: 0, sender uid: 0, si_status: 0
      Wed Jan 23 05:00:03 2019: [crit   ] Signal value: 0, faulting address: (nil)
      Wed Jan 23 05:00:03 2019: [crit   ] When reporting this traceback, please include Linux distribution name (and version), system architecture and Kopano version.
      

      When this happens, server shutdown needs around 10 sec instead of normally 1 sec (in the quoted example, the maintenance script continues at 5:00:12). Besides that, I did not notice any unexpected behaviour.

      I stumbled over the thread Fatal error Kopano Server which is a few months old discussing a quite similar, but not identical log entry. Especially, relation to server shutdown is not mentioned there.

      Ubuntu 18.04.1
      Kopano Server 8.6.9 (looking back in the logs I found an entry back in november when running 8.6.8)

      Log is asking me to report this which I am doing now. Thanks in advance for any advice on this.

      1 Reply Last reply Reply Quote 0
      • First post
        Last post