search - ERROR - sync state not 16 digits

BMWfan

Hello,

today ive checked the logs of kopano and saw this message which comes every 5 second:

2019-01-25 20:11:44,672 - search - ERROR - sync state not 16 digits, expect problems
2019-01-25 20:11:49,685 - search - ERROR - sync state not 16 digits, expect problems
2019-01-25 20:11:54,701 - search - ERROR - sync state not 16 digits, expect problems
2019-01-25 20:11:59,714 - search - ERROR - sync state not 16 digits, expect problems
2019-01-25 20:12:04,726 - search - ERROR - sync state not 16 digits, expect problems

what does it mean?
I’ve tried to change the log level to 6 (debug) but between this log entries arrives nothing.

Best Regards

Daniel

BMWfan

So, ive tried now to reindex my kopano user like:

kopano-search --reindex -u Daniel

after this the log entries are away but only until i restart the kopano-search.

If i search for something in Kopano-webapp i get this log message:

2019-01-26 12:14:19,578 - query - WARNING - could not open database: /var/lib/kopano/search/1C244D94A69B4E8CA4F9CB245BF4D402-A497753E7B1B4CE3894BB06ABB7C1F45
2019-01-26 12:14:19,583 - query - WARNING - could not open database: /var/lib/kopano/search/1C244D94A69B4E8CA4F9CB245BF4D402-A497753E7B1B4CE3894BB06ABB7C1F45

But from my perspective is it not a right issue:

/var/lib/kopano/search# ls -la
total 12212
drwxr-xr-x  2 kopano kopano     4096 Jan 26 12:11 .
drwxr-xr-x 11 kopano kopano     4096 Jan 25 20:04 ..
-rw-------  1 kopano kopano        0 Jan 21 20:38 1C244D94A69B4E8CA4F9CB245BF4D402-A497753E7B1B4CE3894BB06ABB7C1F45.lock
-rw-------  1 kopano kopano 19849216 Jan 26 12:14 1C244D94A69B4E8CA4F9CB245BF4D402_mapping
-rw-------  1 kopano kopano        0 Jan 26 12:14 1C244D94A69B4E8CA4F9CB245BF4D402_mapping.lock
-rw-------  1 kopano kopano   512000 Jan 26 10:52 1C244D94A69B4E8CA4F9CB245BF4D402_state
-rw-------  1 kopano kopano        0 Jan 26 10:52 1C244D94A69B4E8CA4F9CB245BF4D402_state.lock

If I’am not false then this message is initiated by this file:
https://github.com/Kopano-dev/kopano-core/blob/master/swig/python/kopano/kopano/ics.py

There is the following line:

    # TODO add an ICS flag to disable reordering

    if len(state) != 16:
        log.error('sync state not 16 digits, expect problems')

    return state

Anyone a idea what could be the reason?

Best Regards

Daniel

fbartels

Hi @BMWfan ,

reindexing is indeed the current way to fix the index.

I guess the “not found” errors was from the time the index was still being created.

BMWfan

Hey @fbartels,

thanks for your reply.

I’ve executed the reindex command today in the morning again (without to restart the service), so 5 hours in the past, but the log entries are not stopping:

2019-01-27 16:50:28,388 - search - ERROR - sync state not 16 digits, expect problems
2019-01-27 16:50:33,402 - search - ERROR - sync state not 16 digits, expect problems
2019-01-27 16:50:38,418 - search - ERROR - sync state not 16 digits, expect problems
2019-01-27 16:50:43,431 - search - ERROR - sync state not 16 digits, expect problems
2019-01-27 16:50:48,444 - search - ERROR - sync state not 16 digits, expect problems
2019-01-27 16:50:53,457 - search - ERROR - sync state not 16 digits, expect problems
2019-01-27 16:50:58,470 - search - ERROR - sync state not 16 digits, expect problems
2019-01-27 16:51:03,484 - search - ERROR - sync state not 16 digits, expect problems
2019-01-27 16:51:08,497 - search - ERROR - sync state not 16 digits, expect problems
2019-01-27 16:51:13,513 - search - ERROR - sync state not 16 digits, expect problems
2019-01-27 16:51:18,535 - search - ERROR - sync state not 16 digits, expect problems

Is there something else what i could do ?

Best Regards

Daniel

mark dufour

hi daniel,

I’m afraid the main sync state is broken, so reindexing a single user won’t help. if you don’t have too many users, you could try a full reindex perhaps? so stop search, empty the index path (configured in search.cfg), and restart search… then wait… :P

I would love to know how the sync state got broken, so if the problem comes back, please do let us know. ideally with some more logging up to the event.

mark.