kopano-search throws lot of error/warnings when reindexing



  • Because of missing search results we started a complete reindexing by stopping kopano-search, renaming the data folder /var/lib/kopano/search and starting the damon again.

    Now we get a lot of errors, warnings and seg-faults:

    2017-12-11 16:30:46,641 - index0 - WARNING - output on stderr:
    BOF when current sheet is not flushed

    2017-12-11 16:30:49,728 - index2 - WARNING - output on stderr:
    Can’t create config directory (/.w3m)!..
    2017-12-11 16:31:09,639 - index0 - WARNING - output on stderr:
    Can’t create config directory (/.w3m)!..
    2017-12-11 16:31:09,650 - index0 - WARNING - output on stderr:
    Can’t create config directory (/.w3m)!..
    2017-12-11 16:31:11,090 - index2 - WARNING - output on stderr:
    Segmentation fault

    2017-12-11 16:31:11,090 - index2 - WARNING - return code = 139
    2017-12-11 16:31:18,036 - index2 - WARNING - return code = 1
    2017-12-11 16:31:26,481 - index2 - WARNING - output on stderr:
    Format a4 is redefined
    .
    . — a hundred times —
    .
    Format a4 is redefined
    parser error : out of memory error
    /tmp/tmp5S1Hx6/attachment:518630: parser error : out of memory error
    <PROPERTY NAME=“Source” TYPE=“string”>
    ^
    parser error : out of memory error
    parser error : out of memory error
    parser error : out of memory error
    /tmp/tmp5S1Hx6/attachment:518630: parser error : out of memory error
    <PROPERTY NAME=“Source” TYPE=“string”>
    ^
    unable to parse /tmp/tmp5S1Hx6/attachment
    2017-12-11 16:32:31,674 - index0 - WARNING - output on stderr:
    -:1: parser error : Start tag expected, ‘<’ not found
    z<85>,b<F3><C7><EE> U:<8D><CA>^<9C>+<B6>^G<B3>^Xsׇ<DC><C0>^F^O^]i<CF><D6>+30<F9><87>:q<EF>9L~<9C><E6>;am09=!<98>cw<EB><CA><E4><CC> <E8>uC<E3>ri<CF>Vf<ED><DA>^U<A3><E6>_eS
    ^
    unable to parse -

    2017-12-11 16:32:31,675 - index0 - WARNING - return code = 6
    2017-12-11 16:32:48,101 - index0 - WARNING - return code = 1
    2017-12-11 16:32:48,975 - index0 - WARNING - output on stderr:
    Format a4 is redefined
    Format a4 is redefined
    Format a4 is redefined
    Format a4 is redefined
    Format a4 is redefined


    Parameters of search.cfg:

    #search_engine = xapian
    term_cache_size = 256M
    #index_exclude_properties = 007D 0064 0C1E 0075 678E 678F
    index_processes = 3
    #index_junk = yes
    suggestions = yes
    index_attachments = yes
    index_attachment_max_size = 15M

    Any ideas what is the cause?



  • 2017-12-11 16:45:13,696 - index2 - ERROR - Traceback (most recent call last):
    File “/usr/lib/python2.7/dist-packages/kopano/log.py”, line 87, in log_exc
    try: yield
    File “/usr/lib/python2.7/dist-packages/kopano_search/init.py”, line 262, in update
    doc[‘mapi3098’] += u’ ’ + u’ '.join([subitem.sender.name, subitem.sender.email, subitem.from_.name, subitem.from_.email]) # PR_SENDER_NAME
    File “/usr/lib/python2.7/dist-packages/kopano/address.py”, line 32, in email
    email = self.server._resolve_email(entryid=self.entryid)
    File “/usr/lib/python2.7/dist-packages/kopano/server.py”, line 104, in do_cache
    result = f(*args, **kwargs)
    File “/usr/lib/python2.7/dist-packages/kopano/server.py”, line 611, in _resolve_email
    mailuser = self.mapisession.OpenEntry(entryid, None, 0)
    File “/usr/lib/python2.7/dist-packages/MAPICore.py”, line 1078, in OpenEntry
    def OpenEntry(self, *args): return _MAPICore.IMAPISession_OpenEntry(self, *args)
    MAPIErrorInvalidEntryid: MAPI error 80040107 (MAPI_E_INVALID_ENTRYID)



  • I have a compareable problem and got a MAPI Error too. After a “kopano-search stop”, the system solves every search result. Maybe a future update repairs that issue of the index-service…


  • Kopano

    @cmks

    well, clearly the tools called by kopano-search to index attachments which are having some issues… can you see from the log which kinds of attachments lead to most errors…? you might want to enable debug logging and reindex a certain user for this.



  • @mark-dufour Which loglevel ist suitable therefor?


  • Kopano

    @cmks said in kopano-search throws lot of error/warnings when reindexing:

    @mark-dufour Which loglevel ist suitable therefor?

    please use debug level as much as possible.


Log in to reply
 

Looks like your connection to Kopano Community Forum was lost, please wait while we try to reconnect.