z-push 2.4.5 sync issue - 0xFFFFFFFF8004010F

rolek

@fbartels I tried to get a bit further. Running with the cache debug log provided some additional info. Whenever the amount of rows is less than 1000, they can be retrieved from the cache:

MatchRestrictions: matching 940 rows
cache: Get object ids from props total ids 940 from disk 940
...
MatchRestrictions: 28 match(es) out of 940 rows (1 properties)

Whenever the number of rows is 1000, they cannot:

MatchRestrictions: matching 1000 rows
cache: Get objects ids warning 1000 objects not found
cache: Get object ids from props total ids 1000 from disk 1000
cache: Get object id 0 error 0x80000002

jengelh

@rolek said in z-push 2.4.5 sync issue - 0xFFFFFFFF8004010F:

@fbartels The function that fails is the call to gcache->GetObject() in ECGetContentChangesHelper::MatchRestrictions()

This is with 8.7.0, btw.

8.7.5 is current. The cache fixes (so far) were done months ago in 8.7.1.

rolek

Rebuilding kopano-libs with 500 instead of 1000 items in provider/libserver/ECICS.cpp, function getchanges_contents() does seem to solve the problem. That got me thinking: maybe we are hitting the max_allowed_packet size? The default for MariaDB is 16MB, the default for MySQL 8 is 64MB.

vincentvana

I can confirm that the problem still exists (with mail, calendar AND contacts) with z-push (2.4.5 and 2.5.1) and kopano-core 8.7.83.106.59c4d1516. If I interpret the thread correctly, the general theory is that it’s a database issue.

My personal setup:

Debian 10
Apache 2.4
php7.3-fpm
MariaDB 10.3
Official z-push 2.5.1
Official kopanocore 8.7.83.106.59c4d1516

I have not found a solution using the current software. Existing syncs work fine, new ones look like they’re choking but don’t know why. Topic 1678 is about the same issue and suggests disabling the enhanced ics, but this does not fix the issue for me. This probably works if the issue is only on the calendar. (Tried it anyway)

Replacing the database software is a BIG step that I’m not willing to take … yet. I did test a full mysqldump and restore of the database. Maybe migrating from mariadb to mysql solved the problem because of the dump/restore…but nope, that’s not it.

I’ve tested the max_allowed_packet setting suggested by rolek and increased it to the mysql8 default of 64M but this also does not solve the issue:

10/10/2019 12:06:01 [28264] [WARN] [user] StatusException: ExportChangesICS->InitializeExporter(): Error, mapi_exportchanges_config() failed: 0xFFFFFFFF8004010F - code: 12 - file: /usr/share/z-push/backend/kopano/exporter.php:230

Maybe there’s more size settings that we need to tweak.

rolek

I can report that the patch from https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=939751;filename=fix-zpush-sync-error.patch;msg=15 fixes the problem for us. It would be nice if somebody else could confirm this.

Regards, Roel

jengelh

If you think you hit max_allowed_packet_size, you want to test that theory:

there should be log messages by k-server (possibly with log_level=0x20006 see manpage for the value)
lower max_allowed_packet_size and observe even more queries being rejected
conversely, raise max_allowed_packet and observe z-push succeeding(?)

Moreover, if you raise the ICS value (in that patch) from 1000 to 500, you should be observing a change in SQL query lengths - and compare with max_allowed_packet_size too.

vincentvana

Finally found a solution. After looking for hours at the increased log level suggested by jengelh and messing with a lot of settings without much luck (even having to restore the whole DB at some point). It looks like my error was related to a corruption in a mailbox. By lowering the SYNC_MAX_ITEMS, in the z-push config, all the way down to 5, z-push started syncing that account on the three new devices (already connected devices were working fine). Maybe running into a corruption stops syncing of the whole batch, and if that batch contains part of the hierarchy, it never manages to set it up.

If that is the case, it can be “fixed” by adding this situation to the loopdetection. It would make z-push more robust when dealing with these errors in a backend.

Anyway, to permanently fix this problem for me:

kopano-backup user
kopano-storeadm -D -n user
kopano-storeadm -C -n user
kopano-backup --restore user

This did take the better part of a day.

Makes me wonder though, what changed in the last half year or so that caused this corruption/errors, or made z-push/kopano more sensitive? Connecting new devices worked fine a few months ago.

P.S. btrfs filesystem snapshots are a life saver. :-)

rolek

@jengelh Jan, I tried increasing the MariaDB value for max_allowed_packet to 64MB, but that didn’t fix the issue. (This was a few days ago). So I don’t think that’s the cause.

jengelh

That sounds familiar. Synchronization streams will currently abort on error (e.g. attachment strangely missing from database).

hugo21212

I had the same error synchronizing a folder in my android phone that had many and messages with big attachments. I store all attachments in the database to make backup easier (just do a mysqldump).

I use Debian 10 and increasing max_allowed_packet for mariadb didn’t work.

I used @vincentvana suggestion (backup of user + deleting / recreating store + restore user) and it worked for me. At least for now and I didn’t dare to resync the big folder - I may try this on the weekend, when I have more time to fix problems.

fbartels

Unfortunately its still unclear how to reproduce the issue.

I have just closed two topics around the same error, the other topics were https://forum.kopano.io/topic/2783/statusexception-exportchangesics-initializeexporter-error-mapi_exportchanges_config-failed-0x8004010f-code-12/ and https://forum.kopano.io/topic/1678/statusexception-exportchangesics-initializeexporter-error-mapi_exportchanges_config-failed-0xffffffff8004010f

vincentvana

It started happening again. My newly imported mailbox is again causing issues. I’m not sure what the problem is because there are no errors I understand.
I have now switched away from using z-push for mail, and instead am using imap for mail sync. This works flawlessly.
Z-push is still used for calendar/contacts.

In response to fbartels: What I believe to be the problem, is troubleshooting. Z-push does not provide the level we apparently need, as does kopano-server. I would expect a log line like “sync of this person on this device aborted due to problematic message x”, or “message x in folder y corrupt/not found”. If you want to reproduce it, just create a big mailbox folder, remove an attachment, and sync. But really, a “MAPI not found” should not abort the sync. It looks like that is the problem/bug.

jengelh

How did you remove that attachment?

Manfred

@vincentvana bumping jengelh’s question. How did you remove that attachment?

weini

I´m also still facing the same issue. I´m facing the issue for mail folders with many (starts with a few 1.000 up to 15.000) entries.

It might be interesting, that the issue only happens when I sync to my mobile (Samsung S8). Sync is limited to last 30 days for emails there. I´m syncing the same inbox via EAS also to Outlook without any time restriction, but that never had an issue.

What I did in the meantime, and what DIDN´T solve the issue:

backup user store with kopano-backup and restore it
play around with MariaDB parameters, esp. max_allowed_packet
rebuild tproperties completely with the script provided in the kopano wiki
use kopano-dbadm to (potentially) cleanup db schema

Only sucessful workaround was to move from MariaDB 10.3 to MySQL. The issue was gone there immediately. I used the Docker image to do this. However, having MySQL 8.0 and MariaDB 10.3 running at the same time (as I need MariaDB for some other stuff) is causing a high load on my server, so I want to avoid this scenario in the mid term.

Hint: If you want to go for a similar approach, do yourself a favor and don´t use MySQL 8.0, but version 5.7 instead. You can move tables / schemas between MariaDB 10.3 (and also 10.4) and MySQL 5.7 very easily via InnoDB tablespace import/export. However, if you use MySQL 8.0, this is a one way trip. Going back from MySQL 8.0 to MariaDB requires a full logical export / import which is quite time consuming.

weini

@rolek said in z-push 2.4.5 sync issue - 0xFFFFFFFF8004010F:

I can report that the patch from https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=939751;filename=fix-zpush-sync-error.patch;msg=15 fixes the problem for us.

@fbartels: Did you integrate that patch into your codebase?

robgnu

I was also facing the same issue. I got a big log flooding with the same message. z-push.log was about 10 GBytes after a day.
I solved the issue, but I am not sure, what the real problem was. So I hope, these information will help anyone:

All users are connected to multiple Outlooks 365 via ActiveSync (no KOE)
Some of the users are connected via an Android Phone (Samsung)
The users have many (>4000) calendar entries.
Sync of calendar items between Outlook seems to work, but didn’t sync to the phones. Deleting and recreation of accounts on the phone didn’t solve the issue.
kopano-backup (backup + restore) did NOT solve the issues.
Changing mariadb parameters did NOT solve the issues.
Switching away from MariaDB to Mysql is currently not an option.

There were so many log entrys, that I decided to remove the affected usersaccounts in Outlook and recreated them. After resync the log flood was gone.

Currently working on Debian 10 (Kopano 8.7.85.0.a02e61d66-0+176.1 with z-push 2.5.1+0-0)

bye
Robert.

weini

@robgnu
What exactly do you mean by “remove affected useraccounts in Outlook”?
I delete the account in Outlook and removed it then in z-push. Afterwards, I connected Outlook again.
Unfortunately, this didn´t cure the issue on my side. Did you do any service restarts in between?

fbartels

@weini said in z-push 2.4.5 sync issue - 0xFFFFFFFF8004010F:

@fbartels: Did you integrate that patch into your codebase?

No, since there was never an answer to https://forum.kopano.io/post/15294

weini

@weini said in z-push 2.4.5 sync issue - 0xFFFFFFFF8004010F:

Unfortunately, this didn´t cure the issue on my side. Did you do any service restarts in between?

It seems I was a bit too fast: about 1h after I deleted the Outlook account (and recreated it), the errors are gone and my mobile is syncing the folders that it was formerly refusing to do so.

Fingers crossed…