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

    Incident: K-1571 error messages from kopano-server

    Kopano Groupware Core
    2
    10
    3030
    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.
    • darootler
      darootler last edited by darootler

      Date Seen
      30.05.2016, these error messages occur since Zarafa 7.2.3.

      Versions
      Ubuntu 16.04.1 LTS
      Kopano 8.3.0-534
      Apache 2.4.18
      MySQL 5.7.16

      Bug Description
      kopano-server is filling the log file (syslog) with error messages. These messages occur for example on processing mails, starting the kopano-server service and so on.

      Severity
      Minor

      Steps to Reproduce
      Restart kopano-server and review the logs or just send or receive an email:
      0_1483744327173_upload-ee304e9f-27ca-4552-af88-b44469fe2f7d

      Actual Behavior
      Log messages are generated with severity “error”.

      Expected Behavior
      No log messages are generated or if this is not an error the severity must not be “error”.

      Troubleshooting/Testing Steps Attempted
      I searched for similar messages but was not able to get any information about what these messages are trying to tell me.

      Workaround
      Filter these messages from syslog.

      fbartels 1 Reply Last reply Reply Quote 0
      • darootler
        darootler last edited by

        I just upgraded to Kopano Core 8.3.0-585 and this error is still present.

        Regards
        Richard

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

          I just upgraded to Kopano Core 8.3.0-618 and this problem is still present.

          Regards
          Richard

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

            I just upgraded to Kopano Core 8.3.0-694 and this problem is still present.

            Regards
            Richard

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

              @darootler its an actual error, just not a fatal one. So suppressing the error will not make it go away ;-)

              The code in question is located at https://stash.kopano.io/projects/KC/repos/kopanocore/browse/provider/libserver/cmdutil.hpp#88

              and seems originate from https://jira.kopano.io/browse/KC-60 and https://jira.zarafa.com/browse/ZCP-13900

              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/

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

                @fbartels

                that’s correct and the reason why i submitted this thread. That’s my personal workaround for suppressing the triggered mails that i am receiving from this error.

                KC-60 is not accessable for me, so i assume this ticket is not resolved?

                Regards
                Richard

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

                  @darootler kc-60 is a duplicate of the zcp ticket, both are now closed. As part of this ticket the error message you now see was implemented to solve a crash at startup.

                  Since this then potentially concerns search folders, rebuilding these (which is not the same of deleting the index of kopano-search) might help.

                  The man page of kopano-server states the following:

                         --restart-searches, -R
                             Rebuild all search folders. This may take some time and is only needed when your search folders have become out-of-sync with the actual data in the
                             database. The sync will start synchronously at the start of the server, and you will have to wait for all searches to complete before connecting to the
                             server.
                  

                  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/

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

                    @fbartels

                    I just rebuilded all search folders using the -R startparameter but the error still occurs.

                    Regards
                    Richard

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

                      @darootler ok, was worth a try. Just today a similar report came through our support. For this https://jira.kopano.io/browse/KC-525 was created. I linked this thread in there as well.

                      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/

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

                        @fbartels

                        Thank you!

                        Regards
                        Richard

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