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

    Deadlock-s

    Kopano Groupware Core
    2
    3
    548
    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.
    • romeor
      romeor last edited by

      Hello,

      I’ve now managed to restore my public library mai-server that was runnign zarafa for last may be 6 years and i’ve updated to debian 10 from wheezy. I’ve decided to go with kopano-core comming from debian 10 repository for the sake of easy updates and upgrades in the future.

      My new system is running on KVM VM with 16GB of RAM and 6 CPU cores. Host server is using SSD raid5 for fast data systems.

      Debian 10
      WebApp:
      3.5.2+dfsg1-1
      Kopano Core:
      8.7.0

      During the imap syncing there were a lot of

      [error  ] SQL [00000049] result failed: Deadlock found when trying to get lock; try restarting transaction, Query: "SELECT 1 FROM properties WHERE hierarchyid IN(122)LOCK IN SHARE MODE"
      

      any way to debug and fix it?

      My configs:

      my.conf

      [mysqld]
      ignore_db_dirs = lost+found
      transaction-isolation = READ-COMMITTED
      max_connections = 70
      max_allowed_packet = 32M
      tmp_table_size = 64M
      max_heap_table_size = 64M
      sort_buffer_size = 2M
      join_buffer_size = 2M
      thread_cache_size = 13
      innodb_write_io_threads = 6
      innodb_read_io_threads = 6
      table_open_cache = 500
      thread_stack = 512K
      innodb_buffer_pool_size = 2G
      innodb_data_file_path = ibdata1:25G:autoextend
      innodb_autoextend_increment = 1000
      innodb_file_per_table = OFF
      innodb_flush_log_at_trx_commit = 2
      innodb_log_buffer_size = 8M
      innodb_log_file_size = 100M
      innodb_log_files_in_group = 3
      innodb_lock_wait_timeout = 120
      # in case of remote storage
      #innodb_flush_method = O_DIRECT
      # otherwise
      innodb_flush_method = O_DSYNC
      

      server.cfg changed values:

      database_engine = mysql
      attachment_storage = database
      threads = 12
      cache_cell_size = 3072M
      user_plugin = ldap
      enable_sql_procedures = yes
      
      1 Reply Last reply Reply Quote 0
      • romeor
        romeor last edited by

        upgraded to the latest kopano env from kopano.io nightly builds.

        klipp 1 Reply Last reply Reply Quote 0
        • klipp
          klipp @romeor last edited by

          @romeor
          same error on current version of kopano core
          restarting mysql works for a few days and then the error appiers again.
          kopano stopped developing the community verson since 08.02.2022 and i dont think the bug will be fixed

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