Kopano Search Returns MAPI Error -> entire Kopano server stops working

yep_DD

I’ive just installed the lattest 492 release. Let’s see

PS:

dpkg: warning: downgrading libjansson4:amd64 from 2.9-1 to 2.7-1

I’ve been getting these since every Kopano update in the last months. Is there a reason Kopano is using 2.7-1?

Stephan

Ihon

Hi,

I am getting this error message multiple times:

Tue Oct 17 22:45:43 2017: [error ] SQL [00000200] result failed: BIGINT UNSIGNED value is out of range in ‘Zarafa.properties.tag - 0x8501’, Query: “SELECT 0,properties.tag,properties.type,properties.val_ulong,properties.val_string,properties.val_binary,properties.val_double,properties.val_longint,properties.val_hi,properties.val_lo, hierarchyid, names.nameid, names.namestring, names.guid FROM properties FORCE INDEX (PRIMARY) LEFT JOIN names ON (properties.tag-0x8501)=names.id WHERE hierarchyid=316249 AND (tag <= 0x8500 OR names.id IS NOT NULL)”

The server not working in that case anymore.

Regards,

Steffen

yep_DD

Hi @fbartels ,

I can confirm what @Ihon wrote. The problem persists.

Stephan

fbartels

@yep_dd @Ihon

Ok, I see. The last days our nightly upload did not succeed because of test failures. We are hopeful to resolve them today and have a new master build online later today.

Ihon

ok, thank you :-)

yep_DD

and also when the server crashes apache shows the following error occasionally:

[:error] [pid 22638] [client xxxxxxxxxx:44132] PHP Fatal error:  Uncaught MAPIException: MAPI error  in /usr/share/kopano-webapp/server/includes/util.php:225\nStack trace:\n#0 /usr/share/kopano-webapp/server/includes/util.php(225): mapi_msgstore_openentry(Resource id #36, '\\x00\\x00\\x00\\x00\\x00\\x0E\\xEA=`\\xE6I5\\xB5\\x8D"...')\n#1 /usr/share/kopano-webapp/index.php(242): cleanSearchFolders()\n#2 {main}\n  thrown in /usr/share/kopano-webapp/server/includes/util.php on line 225,```

yep_DD

This is the properties table. Changing tag to BIGINT has no effect. The error is getting really serious now, as I have a couple of messages in my postfix queue I can not get delivered!

0_1508326973203_Bildschirmfoto 2017-10-18 um 13.42.22.png

Ihon

@fbartels any update on the community build?
Still having the errors and server is crashing

Thanks,

Ihon

yep_DD

@Ihon same here, and also the community packages haven’t been updated in 7 days…

MS4R

@all same here and crash send my xen server in the eternal datagrounds

fbartels

Hi @yep_dd ,

yes we were still battling some test failures and prevented new packages from being uploaded. In the afternoon all tests were successful again so on monday there should be a new upload.

yep_DD

Hi @fbartels ,

could you just tell us if that issue has been specifically addressed? I see there are already new packages. I will deploy them in a second. Thanks for your help.

Stephan

Ihon

Hi,

I did the update to the new version.
Now kopano-server is providing the following error:

Sat Oct 21 20:37:54 2017: [ notice] Starting kopano-server version 8.4.90 (pid 19164)
Sat Oct 21 20:37:54 2017: [ notice] Server shutdown complete.
Sat Oct 21 20:38:48 2017: [ notice] Starting kopano-server version 8.4.90 (pid 19244)
Sat Oct 21 20:38:48 2017: [notice ] Listening for TCP connections on port 236
Sat Oct 21 20:38:48 2017: [notice ] Listening for SSL connections on port 237
Sat Oct 21 20:38:48 2017: [notice ] Coredumps are disabled via configuration file.
Sat Oct 21 20:38:48 2017: [notice ] Listening for priority pipe connections on /var/run/kopano/prio.sock
Sat Oct 21 20:38:48 2017: [notice ] Listening for pipe connections on /var/run/kopano/server.sock
Sat Oct 21 20:38:48 2017: [notice ] Connection to database ‘Zarafa’ succeeded
Sat Oct 21 20:38:48 2017: [warning] WARNING: DB schema is 49 and older than v63 (ZCP 7.2). KC 8.4 was the last version able to upgrade such.
Sat Oct 21 20:38:48 2017: [warning] You can force the server to start with --ignore-database-version-conflict
Sat Oct 21 20:38:48 2017: [warning] Warning, you can lose data! If you don’t know what you’re doing, you shouldn’t be using this option!
Sat Oct 21 20:38:48 2017: [notice ] Waiting for mysql_server_end
Sat Oct 21 20:38:48 2017: [notice ] Waiting for mysql_library_end
Sat Oct 21 20:38:48 2017: [ notice] Server shutdown complete.

@yep_DD , do you have the same issue?

Regards,

Ihon

yep_DD

@Ihon no i din’t get that problem I’d recommend /etc/init.d/kopano-server stop and then run

kopano-server -c /path/to/your/config/file (etc/kopano/server.cfg) --ignore-database-conflict and see if it starts if it does then restart with: /etc/init.d/kopano-server start and check again

Ihon

Hi,

kopano-server is starting with the parameter --ignore-database-version-conflict.
but when I start it without the parameter, getting the errror again and kopano-server is not starting anymore :-(

In the database, table “versions” I have the folling entries:

7 	0 	0 	24874 	49 	2011-02-22 09:45:42
7 	0 	0 	25734 	50 	2011-03-12 21:33:50
7 	0 	0 	25734 	51 	2011-03-12 21:40:23
7 	0 	0 	25734 	52 	2011-03-12 22:18:00
...
...
...
8 	4 	0 	825 	66 	2017-06-18 15:14:29
8 	4 	0 	1004 	66 	2017-07-03 19:41:15
8 	4 	0 	1054 	66 	2017-07-07 11:37:54
8 	4 	90 	2153381888 	66 	2017-08-01 12:17:35

@fbartels do you have an idea what to do?

Regards,

Ihon

yep_DD

@Ihon which version exactly have you installed?

Can you just make sure your kopano server completed the install successfully?

I installed:

core-8.4.90.550_0+93-Debian_9.0-amd64/

and that is my versions table and it looks like yours:

0_1508684707499_Bildschirmfoto 2017-10-22 um 17.04.31.png

fbartels

@yep_dd said in Kopano Search Returns MAPI Error -> entire Kopano server stops working:

could you just tell us if that issue has been specifically addressed?

The nightly packages will always be built from the master branch. I have linked you the merge commit before, so it should be included in the packages now.

@ihon said in Kopano Search Returns MAPI Error -> entire Kopano server stops working:

Now kopano-server is providing the following error:

this seems to be a side effect of https://jira.kopano.io/browse/KC-839. I have created https://jira.kopano.io/browse/KC-859 to investigate a bit further.

Ihon

Good morning,

@fbartels yes, it looks like a side effect, my question, is it secure to run the server with the --ignore-database-conflict parameter and do you need any information helping you to solve the issue?

Thanks,

Ihon

fbartels

Hi @ihon ,

no I don’t think additional information is needed at the moment. Since you already posted your version table and you internal database is actually already on the newest db revision its save to run with the ignore parameter for now.

fbartels

Small update: the fix that is associated with https://jira.kopano.io/browse/KC-859 is included in the latest nightly, so the messages about old database revisions should now be gone.