Server Error: object too large for cache

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
vietjovi
Posts: 2
Joined: Mon Feb 11, 2019 3:12 pm

Server Error: object too large for cache

Post by vietjovi »

Hi all,

Today , I got a blank page after login my account to mail zimbra. I saw the following error from mailboxd.log, and I guest my inbox had a larger email that it can't load.
Please help me fix this problem, I tried many ways from https://wiki.zimbra.com/wiki/Performanc ... eployments(increate waiter, timeout, imap thread), but it doesn't work

Code: Select all

2019-02-11 22:28:57,694 ERROR [Memcached IO over {MemcachedConnection to /127.0.0.1:11211}] [] StoreOperationImpl - Error:  SERVER_ERROR object too large for cache
2019-02-11 22:28:57,698 WARN  [Memcached IO over {MemcachedConnection to /127.0.0.1:11211}] [] MemcachedConnection - Closing, and reopening {QA sa=localhost/127.0.0.1:11211, #Rops=1, #Wops=0, #iq=0, topRop=Cmd: set Key: zmImap:3d97a805-309d-4636-ba1f-2c851062daf6:56697:745214:81358 Flags: 2050 Exp: 86400 Data Length: 3007862, topWop=null, toWrite=0, interested=1}, attempt 0.
2019-02-11 22:28:57,698 WARN  [Memcached IO over {MemcachedConnection to /127.0.0.1:11211}] [] AsciiMemcachedNodeImpl - Discarding partially completed op: Cmd: set Key: zmImap:3d97a805-309d-4636-ba1f-2c851062daf6:56697:745214:81358 Flags: 2050 Exp: 86400 Data Length: 3007862
2019-02-11 22:28:57,699 WARN  [Memcached IO over {MemcachedConnection to /127.0.0.1:11211}] [] misc - Lost connection to memcached at localhost:11211
2019-02-11 22:28:57,699 WARN  [SessionSweeper] [] misc - ExecutionException during memcached set operation
java.util.concurrent.ExecutionException: OperationException: SERVER: SERVER_ERROR object too large for cache
	at net.spy.memcached.internal.OperationFuture.get(OperationFuture.java:174)
	at com.zimbra.common.util.memcached.ZimbraMemcachedClient.put(ZimbraMemcachedClient.java:385)
	at com.zimbra.common.util.memcached.ZimbraMemcachedClient.put(ZimbraMemcachedClient.java:359)
	at com.zimbra.common.util.memcached.MemcachedMap.put(MemcachedMap.java:147)
	at com.zimbra.cs.imap.MemcachedImapCache.put(MemcachedImapCache.java:48)
	at com.zimbra.cs.imap.MemcachedImapCache.put(MemcachedImapCache.java:39)
	at com.zimbra.cs.imap.ImapSessionManager.serialize(ImapSessionManager.java:689)
	at com.zimbra.cs.imap.ImapListener.serialize(ImapListener.java:794)
	at com.zimbra.cs.imap.ImapSession.createPagedFolderData(ImapSession.java:154)
	at com.zimbra.cs.imap.ImapListener.unload(ImapListener.java:584)
	at com.zimbra.cs.imap.ImapSessionManager.closeFolder(ImapSessionManager.java:574)
	at com.zimbra.cs.imap.ImapListener.unregister(ImapListener.java:615)
	at com.zimbra.cs.session.Session.doCleanup(Session.java:310)
	at com.zimbra.cs.session.SessionMap$1.run(SessionMap.java:180)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: OperationException: SERVER: SERVER_ERROR object too large for cache
	at net.spy.memcached.protocol.BaseOperationImpl.handleError(BaseOperationImpl.java:192)
	at net.spy.memcached.protocol.ascii.OperationImpl.readFromBuffer(OperationImpl.java:152)
	at net.spy.memcached.MemcachedConnection.readBufferAndLogMetrics(MemcachedConnection.java:861)
	at net.spy.memcached.MemcachedConnection.handleReads(MemcachedConnection.java:840)
	at net.spy.memcached.MemcachedConnection.handleReadsAndWrites(MemcachedConnection.java:720)
	at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:683)
	at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:436)
	at net.spy.memcached.MemcachedConnection.run(MemcachedConnection.java:1446)
2019-02-11 22:28:57,704 INFO  [SessionSweeper] [] imap - dropping connection for user test@myemail.com (server-initiated)
Post Reply