SerializeObject obj 6654 failed: disk error (80000007)
-
Hi,
I am (also) accessing my Kopano server (kopano-server 10.0.1 from nightlies) with the latest Zarafa Client (zarafaclient-7.2.6-52189.msi). I am getting the following message which I always click “Retry”:
Now I know the client is not officially supported any more but it shows that I have some issue with an item and I want to get rid of this item (and hence the message). I turned the server log level to “debug” and all I see in the logs is this:
2020-03-07T20:04:25.550295: [warning] K-1204: The sync ID 16347 does not exist. Session user name: user. 2020-03-07T20:04:26.186593: [warning] K-1204: The sync ID 16348 does not exist. Session user name: user. 2020-03-07T20:04:26.893256: [warning] K-1204: The sync ID 16350 does not exist. Session user name: user. 2020-03-07T20:04:28.176644: [warning] K-1204: The sync ID 16354 does not exist. Session user name: user. 2020-03-07T20:04:32.509885: [warning] K-1204: The sync ID 16361 does not exist. Session user name: user. 2020-03-07T20:04:33.150207: [warning] K-1204: The sync ID 16362 does not exist. Session user name: user. 2020-03-07T20:04:33.799367: [warning] K-1204: The sync ID 16363 does not exist. Session user name: user. 2020-03-07T20:04:34.437459: [warning] K-1204: The sync ID 16364 does not exist. Session user name: user. 2020-03-07T20:04:36.381190: [warning] K-1204: The sync ID 16367 does not exist. Session user name: user. 2020-03-07T20:04:37.014460: [warning] K-1204: The sync ID 16368 does not exist. Session user name: user. 2020-03-07T20:04:37.651678: [warning] K-1204: The sync ID 16369 does not exist. Session user name: user. 2020-03-07T20:04:40.629572: [warning] K-1204: The sync ID 16378 does not exist. Session user name: user. 2020-03-07T20:04:41.265269: [warning] K-1204: The sync ID 16380 does not exist. Session user name: user. 2020-03-07T20:04:42.542338: [warning] K-1204: The sync ID 16382 does not exist. Session user name: user. [...] 2020-03-07T19:59:00.755552: [info ] No certificate in SSL connection. 2020-03-07T19:59:01.220131: [error ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned 2020-03-07T19:59:01.220190: [error ] SerializeObject obj 6654 failed: disk error (80000007) 2020-03-07T19:59:01.220264: [debug ] gSOAP error on processing request: SOAP_FATAL_ERROR
I am not sure how relevant the first entries are (they appear during the “Looking for changes” message). However, the second part appears around the same time in the log as the message so I am confident they are related.
What does the error mean? Why do I get a disk error? And how can I figure out which item is faulty? How can I eliminate it then from the database?
Thanks!!
-
I managed to get rid of them by looking up the items in the database and deleting them.
But after some time, the issue reappeared.Now finally I switched from database to files storage for attachments.
Then I got loads of errors like
2020-06-18T04:22:27.864589: [error ] K-1562: cannot open attachment "/var/lib/kopano/attachments/1/7/471": File or directory not found
Seems there is a bug that causes this data inconsistency.
In any case, I touch’ed each missing file and things are working so far.
Maybe nobody uses database attachment storage any more so bugs are not really recognized by anyone.
-
@divB said in SerializeObject obj 6654 failed: disk error (80000007):
2020-06-18T04:22:27.864589: [error ] K-1562: cannot open attachment "/var/lib/kopano/attachments/1/7/471": File or directory not found
Seems there is a bug that causes this data inconsistency.
In any case, I touch’ed each missing file and things are working so far.Sounds to me like someone did a mysql restore to a different DB state without also restoring /var/lib/kopano/attachments.