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

    Upgrade core 11.0.1.2 to 11.0.2.41 - High search cpu usage

    Kopano Groupware Core
    14
    36
    3532
    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.
    • zara-kopa
      zara-kopa last edited by

      @naspelupo

      yes you are rigth. Without any reason k-search results in a new high cpu usage. But in my enviroment this error starts only after reveral days and not in hours. I control my network with PRTG, and create an alarm for a persistent high cpu usage over 40% for longer then 2 hours. Then i stop and restart the MariaDB server for several minutes.
      After that cpu usage is normal for nearly a week. Everything, included k-search, runs fine.
      Actually i have no time to get deeper in this problem.
      “Ja die Sache nervt, bringt aber meine Hardware nicht ins Nirwana”

      grüßing
      Zara-Kopa

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

        Hi All,
        same here. Fresh installation, just 6 users added, no big data yet as it is not yet running in “production”.
        Core 11.0.2.43, as soon as kopano-search is started the CPU is at round about 50% continually. A service kopano-search stop takes its time and then CPU drops to 1%, everything is fine.
        In the log of k-search:

        Traceback (most recent call last):
          File "/usr/lib/python3/dist-packages/kopano/log.py", line 140, in log_exc
            try: yield
          File "/usr/lib/python3/dist-packages/kopano_search/__init__.py", line 200, in main
            path = folder.path
          File "/usr/lib/python3/dist-packages/kopano/folder.py", line 250, in path
            subtree_entryid = self.store.subtree.entryid
          File "/usr/lib/python3/dist-packages/kopano/store.py", line 242, in subtree
            return _folder.Folder(self, _benc(ipmsubtreeid))
          File "/usr/lib/python3/dist-packages/kopano/folder.py", line 145, in __init__
            self.mapiobj
          File "/usr/lib/python3/dist-packages/kopano/folder.py", line 158, in mapiobj
            IID_IMAPIFolder, MAPI_MODIFY)
          File "/usr/lib/python3/dist-packages/MAPICore.py", line 602, in OpenEntry
            return _MAPICore.IMsgStore_OpenEntry(self, cbEntryID, lpInterface, ulFlags)
        SystemError: <built-in function IMsgStore_OpenEntry> returned a result with an error set
        

        Anyone an idea?
        Thanks in advance
        Icey

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

          Dear all,

          does nobody has an idea how this could be fixed? It is weird, cause actually there is nearly nothing to be indexed by now. Nothing in attachements folder and also approxiametly 12 mails in all mailboxes.
          Would be great if anybody could help.
          What about the others? Probs solved?

          Thanks in advance,
          Icey

          umgfoin 1 Reply Last reply Reply Quote 0
          • JungleMarc
            JungleMarc last edited by

            I experience same issue.

            I am not on mariadb, but on mysql.

            My sql is not part of the same machine. I can confirm mysql is very stable and no performance issues. It does not appear the issue is with the database server.

            On the application server for Kopano, yes I can reach high cpu usage for both kopano-server and kopano-search after several weeks of uptime.

            My only workaround is a restart of kopano-server, kopano-search

            How can we debug this further?

            1 Reply Last reply Reply Quote 0
            • umgfoin
              umgfoin @icey last edited by umgfoin

              @icey said in Upgrade core 11.0.1.2 to 11.0.2.41 - High search cpu usage:

              does nobody has an idea how this could be fixed?

              Hello @icey ,
              I fixed the possible cause some time ago, but didn’t have time to create a qualified PR, yet.
              You can resolve the problem by replacing a few lines in /usr/lib/python3.6/site-packages/kopano_search-11.0.2-py3.6.egg/kopano_search/__init__.py (the exact path on your system depends on distribution, python- and kopano-version).
              Take a look here.

              bg,
              umgfoin.

              umgfoin stan23 externa1 Joost mhope 5 Replies Last reply Reply Quote 2
              • umgfoin
                umgfoin @umgfoin last edited by

                (the exact path on your system depends on distribution, python- and kopano-version).

                In your case more likely to be found here: /usr/lib/python3/dist-packages/kopano_search/__init__.py
                ++umgfoin.

                1 Reply Last reply Reply Quote 1
                • stan23
                  stan23 @umgfoin last edited by

                  @umgfoin that did the trick, thanks a lot!

                  1 Reply Last reply Reply Quote 1
                  • externa1
                    externa1 @umgfoin last edited by

                    @umgfoin
                    works also for 8.7.23

                    rg
                    Christian

                    1 Reply Last reply Reply Quote 1
                    • icey
                      icey last edited by

                      Hi umgfoin,

                      THANKS a lot --> That did the needed magic ;)

                      Thanks.
                      Icey

                      1 Reply Last reply Reply Quote 0
                      • Joost
                        Joost Kopano @umgfoin last edited by Joost

                        @naspelupo Thank you for reporting this issue, I’ve created a ticket to track it:
                        https://jira.kopano.io/browse/KC-2005

                        And thanks to @umgfoin’s fix, I’ve also been able to quickly create a PR:
                        https://stash.kopano.io/projects/KC/repos/kopanocore/pull-requests/3559/overview

                        umgfoin 1 Reply Last reply Reply Quote 0
                        • umgfoin
                          umgfoin @Joost last edited by

                          @joost said in Upgrade core 11.0.1.2 to 11.0.2.41 - High search cpu usage:

                          I’ve also been able to quickly create a PR:

                          Yeah - and an impressively minimalistic one ;-) …
                          Thanks!

                          dev107 1 Reply Last reply Reply Quote 0
                          • zara-kopa
                            zara-kopa last edited by

                            The fix from @umgfoin is great! Works for me either!

                            Thanks a lot.

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

                              Yep: fix did the trick. Load is normal again!
                              Many thanks for this!
                              _paul

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

                                This edit plus a reboot fixed the high CPU for me too, now CPU is negligible.

                                core-11.0.2.43

                                1 Reply Last reply Reply Quote 0
                                • mhope
                                  mhope @umgfoin last edited by

                                  @umgfoin Thank you very much! That did the trick for me too :)
                                  Kopano 11.0.2, running under Ubuntu 18.04 as LXC on QNAP NAS.

                                  1 Reply Last reply Reply Quote 0
                                  • dev107
                                    dev107 @umgfoin last edited by

                                    @umgfoin thank you so much. It also works in supported version 8.7.23 and Debian 10.

                                    kapeleha 1 Reply Last reply Reply Quote 0
                                    • kapeleha
                                      kapeleha @dev107 last edited by

                                      The fix also works for my environment: KC 8.7.23 and virtual ucs-4.4.8 on a QNAP NAS. Thx a lot ;-)

                                      JungleMarc 1 Reply Last reply Reply Quote 0
                                      • JungleMarc
                                        JungleMarc @kapeleha last edited by

                                        I applied the patch. Thank you for getting this fixed. :)

                                        index_processes = 1 in /etc/kopano/search.cfg

                                        Made a big difference on system load during cache rebuild.

                                        Marc

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

                                          Just to have it said, the fix is part of the nightly releases for a few days already.

                                          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/

                                          JungleMarc 1 Reply Last reply Reply Quote 2
                                          • JungleMarc
                                            JungleMarc @fbartels last edited by

                                            @fbartels amazing. :)

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