old bug, upgrade to at least 8.6.6 8.6.7 or 8.6.8

@externa1
do u have an idea how to avoid such a situation in the future or how this could be monitored? It was only by chance, that I realized that mails weren’t sent…

What we did try was switch to mutii tenant and automatically got orphaned stores and no users. So will try and then just add the users back and relink stores.
Might be a bit slow on a large site.

I find out why I got the mapi error during login in the webapp. For all of my created users no store was automatically created, too.

root@kopano:~# kopano-cli --list-users
User list for Default (3):
User Full Name Homeserver Store Brigitte Brigitte kopano SYSTEM SYSTEM kopano 8962FFEFFB7B4D639BC5967C4BB58234 Uwe Uwe kopano

After adding the store manually the logon is working successfully.

root@kopano:~# kopano-cli -u uwe --create-store
root@kopano:~# kopano-cli -u brigitte --create-store
root@kopano:~# kopano-cli --list-users
User list for Default (3):
User Full Name Homeserver Store Brigitte Brigitte kopano 227160E136164EC7835FEAAA20E622CC SYSTEM SYSTEM kopano 8962FFEFFB7B4D639BC5967C4BB58234 Uwe Uwe kopano 4183C8086C584490A54C2E816AA5E840

https://jira.kopano.io/browse/KC-1330

@deHoeninger, @umgfoin
Thank you for replying. With my ordered subscription the issue should be away.

Hi @externa1,

yes we noticed this as well. Since the pre-final repo does not contain any newer releases at the moment this should not be an issue, though. When enabling the pre-final repo I would anyways recommend to also have the final repo setup (this is what the Univention integration does automatically).

When you want to anyways want to go through kopano-backup, then you can also pull the backup directly from your old Zarafa system.

You also do not need to import your mysql database twice if you want to go through the proper update routine. you simply need to start you database once with the required kopano-server (or zarafa-server) binary.

The changelog in RELNOTES.txt is updated regularly.

@fbartels

hi,

yust a update. it was a problem with the database. i dont know what exactly. i deleted the database. recreated the database and restored my backup. if i now restore the mail tha would not restore before al is fine and it restores.

@umgfoin said in [solved] kopano-server[]: setSyncStatus(): collision:

it was merged into master, yesterday - so probably 'be part of the next community-build.

Your are right, my fault. Should already be part of last nightly build.

Best Jan

Hi @genz ,

@genz said in Error on kopano-stats command:

etc/kopano/server.cfg file:

is that all that is in your server.cfg?

With the “default:” socket he usually goes first for the file socket location and then over to the http socket.

Hi @ckruijntjens ,

I could not test this on a centos machine, as either something is broken in webapp or our machine deployment, but I did a small check on a Debian 9 machine from last, week which I updated to the latest master.

I do have both logging in dagent.log (once configured) and out of office messages work as well.

@cpuclan said in Kopano spamd Received a MAPI error or timeout (error=0x80040116):

What does this error mean?

Please see: https://documentation.kopano.io/kopanocore_administrator_manual/appendix_d.html

@fbartels

The single maintainer of the zarafa packages over there lost interest.

OK, people can always get Kopano from here. Most important differences:
icu is updated to 62
python-3 is updated to 3.7

Ohh yes - you are right. The repository URL from z-push was missing in my configuration.
After adding the line;

deb http://repo.z-hub.io/z-push:/final/Ubuntu_18.04/ /

… to the kopano.list i got the right one.

Thanks a lot.
Andre

@ckruijntjens said in Kopano-Search with high load:

i have the same problem

It is totally expected that you have a higher load while indexing. After all there is a service running that has to read out all your data and create index files for it.

@ckruijntjens said in Kopano-Search with high load:

search - WARNING - Received a MAPI error or timeout (error=0x80040115, retry=5/5)

please see https://documentation.kopano.io/kopanocore_administrator_manual/appendix_d.html for the error messge. this is a network error which means, search wanted to retrieve something from kopano-server, and the reply was incorrect. If you search for the error message you will find some other threads explaining this.