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

    [evolution bug]Evolution-3.28.4 -> 3.30.0 Failed to refresh folder “me@localhost : INBOX”. The reported error was “Error fetching message info: expecting number”.

    Kopano Groupware Core
    3
    8
    1272
    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.
    • tjoen
      tjoen last edited by tjoen

      Evolution-3.28.4 -> 3.30.0 new behaviour
      Error message:
      Failed to refresh folder “tdance@localhost : INBOX”.
      The reported error was “Error fetching message info: expecting number”.

      journalctl logs:
      Error while connecting to search on “file:///var/run/kopano/search.sock”

      Is that normal IMAP-client behaviour?

      tjoen 1 Reply Last reply Reply Quote 0
      • tjoen
        tjoen @tjoen last edited by

        Problem starting kopano-search

        File "/usr/sbin/kopano-search", line 3, in <module>
            import kopano_search
        File "/usr/lib/python2.7/site-packages/kopano_search/__init__.py", line 19, in <module>
            import bsddb
        File "/usr/lib/python2.7/bsddb/__init__.py", line 67, in <module>
            import _bsddb
        ImportError: No module named _bsddb
        

        How have the distros solved this?
        I have compiled bsddb3 but the problem is in

        kopano_search/__init__.py", line 19
        
        if sys.hexversion >= 0x03000000:
            import bsddb3 as bsddb
            from queue import Empty
        else: # pragma: no cover
            import bsddb          #line 19
            from Queue import Empty
        
        1 Reply Last reply Reply Quote 0
        • Vogi
          Vogi last edited by

          Hi!

          I am runngin kopano on a Gentoo system.
          I had the same problem with kopano-search and kopano-spamd, which can be solved by changing it that way:

          diff -rupN kopanocore-8.4.90/ECtools/search/kopano_search/__init__.py kopanocore-8.4.90.python2_7/ECtools/search/kopano_search/__init__.py
          --- kopanocore-8.4.90/ECtools/search/kopano_search/__init__.py	2017-07-28 09:58:13.000000000 +0100
          +++ kopanocore-8.4.90.python2_7/ECtools/search/kopano_search/__init__.py	2017-07-28 18:16:32.436270458 +0100
          @@ -6,18 +6,14 @@
           import os.path
           
           from multiprocessing import Queue, Value
           import time
           import sys
           
          -if sys.hexversion >= 0x03000000:
          -    import bsddb3 as bsddb
          -    from queue import Empty
          -else: # pragma: no cover
          -    import bsddb
          -    from Queue import Empty
          +import bsddb3 as bsddb
          +from Queue import Empty
           
           from kopano_search import plaintext
           import kopano
           from kopano import log_exc, Config
           sys.path.insert(0, os.path.dirname(__file__)) # XXX for __import__ to work
           diff -rupN kopanocore-8.4.90/ECtools/spamd/kopano_spamd/__init__.py kopanocore-8.4.90.python2_7/ECtools/search/kopano_search/__init__.py
          --- kopanocore-8.4.90/ECtools/spamd/kopano_spamd/__init__.py	2018-03-18 09:58:13.000000000 +0100
          +++ kopanocore-8.4.90.python2_7/ECtools/spamd/kopano_spamd/__init__.py	2018-03-18 18:16:32.436270458 +0100
          @@ -6,16 +6,13 @@
           import time
           import kopano
           import grp
           from kopano import Config, log_exc
           from contextlib import closing
           
          -if sys.hexversion >= 0x03000000:
          -    import bsddb3 as bsddb
          -else: # pragma: no cover
          -    import bsddb
          +import bsddb3 as bsddb
           
           """
           kopano-spamd - ICS driven spam learning daemon for Kopano / SpamAssasin
           """
           
           CONFIG = {```
          tjoen 1 Reply Last reply Reply Quote 0
          • tjoen
            tjoen @Vogi last edited by

            @vogi Yes, that is the sollution I am trying now. The other sollutions would be patching Python2 or moving to Python3

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

              I don’t understand why it is solved by these steps
              1 Downgrade to evolution-3.28.4 and started. Test-mail displays
              2 stopped kopano-search
              3 Upgrade to evolution-3.30.0, started, no errors, Test-mail displays. No logs compaining that search socket unavailable

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

                I found out that proplem stil persist. no problem startin evolution-3.30 first time. The problem occurs after restarting. I guess something wrong at closin evolution

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

                  Hi @tjoen ,

                  which of the two problems are you referring to with:

                  @tjoen said in [evolution bug]Evolution-3.28.4 -> 3.30.0 Error while connecting to search on "file:///var/run/kopano/search.sock":

                  I found out that proplem stil persist.

                  ?

                  is it the Error while connecting to search on “file:///var/run/kopano/search.sock” log message? This was reported at our support desk a few times already as well, but we are still missing steps to actually reproduce this. normally the imap clients are not supposed to talk to search.

                  edit: dev ticket for that is btw https://jira.kopano.io/browse/KC-1153

                  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/

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

                    @fbartels
                    I was not clear with my comments. There were two problems. One was

                    search on “file:///var/run/kopano/search.sock”

                    That didn’t reappear even without kopano-search running. The second was

                    Error message:
                    Failed to refresh folder “tdance@localhost : INBOX”.
                    The reported error was “Error fetching message info: expecting number”.

                    That persists after first time restarting evolution-3.30 without problems. But closing evolution and restarting the problem persists. 3.28 no problems. I need to report it to the Evolution-team.

                    In debug mode I can see that kopano is sending the email to evolution with headers e.a. but it doesn’t display in the inbox

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