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

    Lock wait timeout exceeded

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

      Hi,

      I’m using Kopano 10.0.6.406 with MySQL 8.0.21 on Debian Buster.

      The server often gets inaccessible (several times per day) with server log showing lot of :
      [error ] SQL [00000105] result failed: Lock wait timeout exceeded; try restarting transaction, Query: “SELECT 1 FROM properties WHERE hierarchyid IN(5582484) LOCK IN SHARE MODE”
      [error ] KDatabase::I_Update() query failed: “Lock wait timeout exceeded; try restarting transaction”, query: INSERT INTO hierarchy (parent, type, flags, owner) values(28745561, 5, 0, 933)

      This disappears for few hours after restarting kopano-server, kopano-gateway and MySQL.

      Any idea of the source of this problem ?

      Thank you in advance

      fbartels 1 Reply Last reply Reply Quote 0
      • fbartels
        fbartels Kopano @Guizmo last edited by

        Hi @guizmo,

        this is usually a sign of insufficient database tuning. The database server cannot perform its writes fast enough (data to be updated still locked) and therefore kopano-server will retry the same write later on.

        Regards Felix

        Resources:
        https://kopano.com/blog/how-to-get-kopano/
        https://documentation.kopano.io/
        https://kb.kopano.io/

        Support overview:
        https://kopano.com/support/

        Guizmo 1 Reply Last reply Reply Quote 0
        • Guizmo
          Guizmo @fbartels last edited by

          Hi @fbartels

          Thank you for your answer.

          I followed the recommendations from the performances tuning section of manual :
          innodb_buffer_pool_size = 8G
          innodb_log_file_size = 2G
          innodb_log_buffer_size = 512M
          max_allowed_packet = 32M

          Do you have any suggestion on where to improve tuning or where to look to see what could cause the bottleneck ?

          Thanks

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