kopano-search no longer starting ...

Hello Forum,

found, that after a while the Debian7-Repository is present again, so I yesterday initiated an

apt-get update
apt-get upgrade

on a Debian7 Kopano-Server. Some Debian- and some Kopano-Parts were updated and everything seems 2b fine … except: kopano-search wont start any longer, silentely, no logfile enries, nothing.

To catch any error-messages at all, I had to invoke kopano-search manually like:

start-stop-daemon --start  --pidfile /var/run/kopano/search.pid --exec /usr/bin/python /usr/sbin/kopano-search --  -c /etc/kopano/search.cfg

which is exactely the line from /etc/init.d/kopano-search with all the variables resolved, and without redirecting console/error output to /dev/null.

The result look like:

Traceback (most recent call last):
  File "/usr/sbin/kopano-search", line 3, in <module>
    import kopano_search
  File "/usr/lib/python2.7/dist-packages/kopano_search/__init__.py", line 20, in <module>
    import kopano
  File "/usr/lib/python2.7/dist-packages/kopano/__init__.py", line 53, in <module>
    from .config import Config, CONFIG
  File "/usr/lib/python2.7/dist-packages/kopano/config.py", line 17, in <module>
    import utils as _utils
  File "/usr/lib/python2.7/dist-packages/kopano/utils.py", line 40, in <module>
    import user as _user
  File "/usr/lib/python2.7/dist-packages/kopano/user.py", line 26, in <module>
    from .store import Store
  File "/usr/lib/python2.7/dist-packages/kopano/store.py", line 19, in <module>
    from MAPI.Tags import (
ImportError: cannot import name PR_EXTENDED_FOLDER_FLAGS
Error in sys.exitfunc:
Traceback (most recent call last):
  File "/usr/lib/python2.7/atexit.py", line 28, in _run_exitfuncs
    import traceback
  File "/usr/lib/python2.7/traceback.py", line 3, in <module>
    import linecache
  File "/usr/lib/python2.7/linecache.py", line 9, in <module>
    import os
  File "/usr/lib/python2.7/os.py", line 119, in <module>
    sys.modules['os.path'] = path
AttributeError: 'module' object has no attribute 'modules'

What’s goin’ wrong, what am I missing?

Thanks for reading, thinking, commenting!


Hi @troubleticket ,

from which version did you upgrade and which version did you upgrade to?

Hello fbartels,

as I’m updating the Debian-Servers I’m responsible for in a regular weekly rhythm, I’m sure the old version was the last one before the 7-ers repository was taken from the internet, don’t please ask me for the version numbers of all the core-components … thenadays kopano-search was running … from the very moment of the update on monday evening, I find the last logfile-entry … and then: silence …

Thanks for helping


Hi @troubleticket ,

ok, then lets just assume that you are running from the final branch, which means you must currently be on 8.4.4 and theoretically speaking must have run 8.4.3 before.

There was no related change to kopano-search between these two versions: https://documentation.kopano.io/kopano_changelog/kc.html#kopano-core-8-4-4-8-4-4-0

<sigh> … means to me, I have to search the reason for this in any of the other updated Debian-Packages, haven’t I … <sigh>

Thanks anyway


Hi @troubleticket ,
I’d try to delete pre-compiled python-files, first:
Recursively remove all *.pyc in folders like/usr/lib/python2.7/dist-packages/kopano*, then restart kopano-search and check results again.


Hi @umgfoin ,

thanks for another light at the end of the tunnel (or at least in the tunnel) … ;o)

Does this affect any other parts of kopano-core?
I see five(5) .pyc’s in a folder “kopano-search” but 47 all in all …?

Are these precompiled’s be rebuilt later automagically?

Thanks for helping.


@troubleticket said in kopano-search no longer starting ...:

Does this affect any other parts of kopano-core?…?

No. Precompiled byte-code (.pyc) only loads, but never executes faster than its plaintext counterpart. So you might notice - if any - only a difference at first access.

Are these precompiled’s be rebuilt later automagically?

Yes, they’ll get rebuilt upon first call of the corresponding .py-script/ module.


@troubleticket said in kopano-search no longer starting ...:

I see five(5) .pyc’s in a folder “kopano-search” but 47 all in all …?

Delete them all e.g. find . -name "*.pyc" -delete and start in /usr/lib/python2.7/dist-packages

Hi @umgfoin ,

… deleted everything like you suggested, checked: no more .pyc’s …
-> no change in behavior: kopano-seach woń’t start, messages the same …

… no idea … =o(

Greetings, thanks …


next step:

Locate file/usr/lib/python2.7/dist-packages/MAPI/Tags.py and check if a line like


is present.


Hi @umgfoin ,

nope, no such line … <hope arisin’> … =o}


@troubleticket said:

<hope arisin’> … =o}

…not sure ;-)
I’d say atleast, package python-mapi didn’t upgrade, correctly. You might reinstall this package, but possibly other (/kopano-search/python-)packages are concerned, too.

Btw., where did you install this from? As of today, I can’t see any Debian7-core-packages under community-downloads.


@umgfoin ,

this kopano installation I maintain for a friend of mine who has a small office of his own, and he has an account for the official repositories, which (as mentioned above) were without debian7-versions for quite some week, whereafter these suddenly reappeared.

I’ll give it a try and reinstall python-mapi … oooops …:

Besides lots of other “libmapi1 php5-mapi python-mapi” are kept back from being updated by “apt-get”???
I suppose, this is been setup by kopano, isn’t it …?

Regards and lots of thanks for your time!


Hi everyone,

I got the problem solved: It was my misunderstanding of “kept back” and “hold”.
All packages are now being installed manually/updated correctly and kopano-search is working again.

Thanks @umgfoin for leading my eyes to the malfunction of upgrades, and to everyone else for reading, thinking, answering, helping.