Gateway imap error - Invalid size tag received:
-
Thanks for testing the restore quickly @fbartels.
Did you test on Debian 9 with the default mariadb installed?
Attachments are saved as files.
Edit: server.cfg and mysql files sent.
edit2: These are probably useful -
# dpkg -l|grep kopano ii kopano-backup 8.4.0~1074-4.1 amd64 Utility to back up and restore Kopano stores ii kopano-client 8.4.0~1074-4.1 amd64 Kopano MAPI provider library ii kopano-common 8.4.0~1074-4.1 amd64 Shared files for Kopano Core services. ii kopano-contacts 8.4.0~1074-4.1 amd64 MAPI provider adding contact folders in the addressbook ii kopano-dagent 8.4.0~1074-4.1 amd64 E-Mail Delivery Agent for the Kopano Core ii kopano-gateway 8.4.0~1074-4.1 amd64 POP3 and IMAP Gateway for the Kopano Core ii kopano-ical 8.4.0~1074-4.1 amd64 ICal and CalDAV Gateway for Kopano Core ii kopano-lang 8.4.0~1074-4.1 all Translations for Kopano Core components ii kopano-monitor 8.4.0~1074-4.1 amd64 Quota Monitor for Kopano Core ii kopano-presence 8.4.0~1074-4.1 amd64 kopano presence daemon ii kopano-search 8.4.0~1074-4.1 amd64 Indexed search engine for Kopano Core ii kopano-server 8.4.0~1074-4.1 amd64 Server component for Kopano Core ii kopano-server-packages 8.4.0~1074-4.1 all Metapackage to install the entire Kopano Core stack ii kopano-spooler 8.4.0~1074-4.1 amd64 E-mail Spooler for Kopano Core ii kopano-utils 8.4.0~1074-4.1 amd64 Admin command-line utils for Kopano Core ii kopano-webapp 3.4.0.758-514.7 all New and improved WebApp for Kopano ii libgsoap-kopano-2-8-48 2.8.48-3.1 amd64 Runtime libraries for gSOAP ii libvmime-kopano1 0.9.2-12.1 amd64 a C++ mail library (runtime library) ii python-kopano 8.4.0~1074-4.1 all High-level Python bindings for Kopano# dpkg -l|grep sql ii default-mysql-server 1.0.2 all MySQL database server binaries and system database setup (metapackage) ii libaprutil1-dbd-sqlite3:amd64 1.5.4-3 amd64 Apache Portable Runtime Utility Library - SQLite3 Driver ii libdbd-mysql-perl 4.041-2 amd64 Perl5 database interface to the MariaDB/MySQL database ii libsqlite3-0:amd64 3.16.2-5 amd64 SQLite 3 shared library ii mysql-common 5.8+1.0.2 all MySQL database common files, e.g. /etc/mysql/my.cnf ii mysql-server 5.5.9999+default amd64 MySQL database server binaries and system database setup [transitional] ii postfix-sqlite 3.1.4-7 amd64 SQLite map support for PostfixWelcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 2 Server version: 10.1.23-MariaDB-9+deb9u1 Debian 9.0 Copyright (c) 2000, 2017, Oracle, MariaDB Corporation Ab and others.G
-
@Galen I personally tested on the latest ubuntu lts, but my college tried on debian 9 (not sure about his sql version, though). will forward the configuration to him.
-
ok, so we’ve been toying around with this internally for a bit. One way we are able to trigger a similar error message is by reducing the
innodb_log_file_sizeto 5mb, but with the mariadb version supplied in debian 9 it should actually default to 50mb.apart from that your configuration pretty much looks like the default values, which is of course not good for performance either. I would therefore recommend to go through the suggestions at https://kb.kopano.io/display/WIKI/Tuning and then try again.
-
I’ve been testing this here with an fresh install of 16.04 LTS and with mysql 5.7 on Debian 9 instead of mariadb - both with default sql settings.
Both instances will restore the complete user set with only one warning thrown at the end of each user restore
backup - WARNING - skipping rule for unknown store/folderI’m not sure what the skipped rule is as i can’t see any missing.
I’ll reload everything on Debian 9 afresh with mariadb and see if i can determine what the differences are.
Thanks for your assistance so far @fbartels
G
-
I can’t see anything between the mysql and mariadb settings that would break things. The innodb_log_file_size does default to 50M in maraiadb.
Pretty much everything that comes up in a search for the sql has gone away suggests that increasing max_allowed_packet or if timing out extend wait_timeout.
The log file time stamps show that there’s no waiting involved so it’s probably not that.
I’ve got these settings in mariadb at the moment and it still has errors with sql went way logged.
echo “show variables” | mysql |egrep “allowed|innodb_log|innodb_buffer_pool|wait_timeout”
innodb_buffer_pool_dump_at_shutdown OFF innodb_buffer_pool_dump_now OFF innodb_buffer_pool_dump_pct 100 innodb_buffer_pool_filename ib_buffer_pool innodb_buffer_pool_instances 8 innodb_buffer_pool_load_abort OFF innodb_buffer_pool_load_at_startup OFF innodb_buffer_pool_load_now OFF innodb_buffer_pool_populate OFF innodb_buffer_pool_size 2147483648 innodb_lock_wait_timeout 50 innodb_log_arch_dir ./ innodb_log_arch_expire_sec 0 innodb_log_archive OFF innodb_log_block_size 512 innodb_log_buffer_size 33554432 innodb_log_checksum_algorithm INNODB innodb_log_compressed_pages OFF innodb_log_file_size 524288000 innodb_log_files_in_group 2 innodb_log_group_home_dir ./ lock_wait_timeout 31536000 max_allowed_packet 536870912 slave_max_allowed_packet 1073741824 wait_timeout 28800 -
-
@Galen are you referring to another post than the one starting with “I can’t see anything between” because I can see this one even when i’m not logged in.
-
@fbartels The askimet spam error came up when i tried to edit the “I can’t see anything between” email. I tried to add “G” to the end but the spam message prohibit the edit
G
-
@Galen hm… since askimet is now also blocking me from editing posts i have deactivated it again.
-
Well, no matter what i try i cannot get KC to work with mariadb on Debian 9 without KC server throwing mysql has gone away errors during migration :(
Although it does work with the Oracle mysql packages installed it does bother me a little not using a database from the main Debian repository .
At least i have working options now and i know how to fix my broken user accounts :)
G
