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

    [warning] SQL [00000044] info: Try to reconnect

    Kopano Groupware Core
    4
    6
    520
    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.
    • Chris2
      Chris2 last edited by

      Hello Community,

      does anyone know what is causing this warning?

      mysql errorlog is empty, and there are no tasks stopping mysql.

      I could not reproduce what is actually triggering the warning,
      and also I could not find any problems because of it.

      Platform:
      ubuntu 18.04 amd64
      kopano-server 8.7.81.138.d6c70dcba-0+242.1 amd64
      mariadb-server 1:10.1.38-0ubuntu0.18.04.2

      mariadb.cnf:
      innodb_log_file_size = 512M
      innodb_log_buffer_size = 32M
      max_allowed_packet = 32M

      Thanks in advance

      mcostan fbartels 2 Replies Last reply Reply Quote 0
      • mcostan
        mcostan @Chris2 last edited by

        @Chris2

        perhaps the database was down at that time?

        Chris2 1 Reply Last reply Reply Quote 0
        • Chris2
          Chris2 @mcostan last edited by

          @mcostan

          Thank you for this hint, but database-server was not touched and online.

          Is there anyone with a comparable setup, not faceing this warning?

          Thanks in advance

          mcostan 1 Reply Last reply Reply Quote 0
          • mcostan
            mcostan @Chris2 last edited by

            @Chris2

            Every time I had that message it meant that the database was unavailable…

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

              @Chris2 this error message as in the past discussed in https://forum.kopano.io/topic/1189/server-log-warning-sql-00011047-info-try-to-reconnect-german-umlauts (which also gives some indicators on settings to adjust)

              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/

              1 Reply Last reply Reply Quote 0
              • deajan
                deajan last edited by

                Here’s some gravedigging for that issue ;)

                There’s also the default timeout where mysql / mariadb just closes the connection.
                The default timeout is 8 hours.

                In my case, it happend like once per day (don’t receive much mail by night):

                2020-09-04T17:23:59.183721: [warning] SQL [00000090] info: MySQL server has gone away. Reconnecting.
                2020-09-05T11:39:32.273025: [warning] SQL [00001879] info: MySQL server has gone away. Reconnecting.
                2020-09-06T07:58:08.715451: [warning] SQL [00000045] info: MySQL server has gone away. Reconnecting.
                2020-09-06T13:04:17.721408: [warning] SQL [00000141] info: MySQL server has gone away. Reconnecting.
                2020-09-07T07:52:11.653321: [warning] SQL [00000223] info: MySQL server has gone away. Reconnecting.
                2020-09-07T08:42:28.721501: [warning] SQL [00000333] info: MySQL server has gone away. Reconnecting.
                

                Solution came from the MariaDB manual: increase the default timeout to something that is never reached.
                In my case:

                [mysqld]
                wait_timeout = 288000
                

                Other scenarios include max_packet_size or innodb_log_file_size (search for them in the forum).

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