Imap memcached deserialize error - 8.8.11P3

[dapa6]

Hello everyone,

yesterday I updated a Zimbra Network Edition multi node cluster ver. 8.8.11 to patch level P3.

After that on mailbox.log I see a lot of those WARN errors when user log in:

2019-03-18 22:59:34,218 WARN [ImapSSLServer-522] [name=xxx@yyy;mid=12;ip=xxx.xxx.xxx.xxx;oip=xx.xx.xx.xx;vi
a=xx.xx.xx.xx(nginx/1.7.1);ua=Microsoft Outlook/15.0.5101.1000;cid=7367;] imap - Failed to load from cache
com.zimbra.common.service.ServiceException: system failure: Failed to deserialize ImapFolder
ode:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:288)
at com.zimbra.cs.imap.MemcachedImapCache$ImapMemcachedSerializer.deserialize(MemcachedImapCache.java:118)
at com.zimbra.cs.imap.MemcachedImapCache$ImapMemcachedSerializer.deserialize(MemcachedImapCache.java:97)
at com.zimbra.common.util.memcached.MemcachedMap.get(MemcachedMap.java:101)
at com.zimbra.cs.imap.MemcachedImapCache.get(MemcachedImapCache.java:59)
at com.zimbra.cs.imap.MemcachedImapCache.get(MemcachedImapCache.java:40)
at com.zimbra.cs.imap.ImapSessionManager.getCache(ImapSessionManager.java:724)
at com.zimbra.cs.imap.ImapSessionManager.duplicateSerializedFolder(ImapSessionManager.java:552)
at com.zimbra.cs.imap.ImapSessionManager.openFolder(ImapSessionManager.java:318)
at com.zimbra.cs.imap.ImapHandler.setSelectedFolder(ImapHandler.java:1195)
at com.zimbra.cs.imap.ImapHandler.selectFolder(ImapHandler.java:1783)
at com.zimbra.cs.imap.ImapHandler.doSELECT(ImapHandler.java:1749)
at com.zimbra.cs.imap.ImapHandler.executeRequest(ImapHandler.java:836)
...

this happen for the most part of the users (different IMAP clients) but the user can login without problem.

Any advice please ?

Thanks.

[pup_seba]

Hi mate,

I wasted 15 mins, reading the code here https://github.com/jimedler/Zimbra-1/bl ... nager.java but I fool nobody...I have absolutly no java skills so I couldn't understand what is really causing that error Maybe you are more fluent than me in java and can make some better sense of it?

What I do can see, is that in the release notes for that patch, something is mentioned about fixing a problem with imap deserialization with a reference to bug 109097...which I can not see because you know...reasons. So maybe that is expected behaviour, maybe is only temporal, maybe the instructions for applying tha patch are not complete or maybe you are facing a bug.

I'm really sorry I cannot be of any more help. I'll try to talk today with some community colleages to see if they also came accross this, and let you know if this is something affecting more people or not.

Regards,

[Klug]

Might be related to that: https://blog.tint0.com/2019/03/a-saga-o ... imbra.html

[maxxer]

Is this causing any performance or functionality issue? Or is the server working fine?

[dapa6]

At the moment I don't see any issue impacting on server functionality.

The main problem is the mailbox.log size, 1GB per day with that amount of warning.

grazie.

[Sixtus81]

Hello,

I have the same case on my server. Everything works, but the logfile gets very big.

[pup_seba]

Maybe any of you can open a support case
? I can't reproduce the error to open it myself :/

[dapa6]

Ok I try to open a support case.
I will keep you posted about the issue.

[pup_seba]

That will be really helpful. Thank you very much!

[Sixtus81]

Ok I try to open a support case.
I will keep you posted about the issue.

Thank you