HTTP ERROR 502 Problem accessing ZCS upstream server

[mgarservers]

Hello,
I have a Zimbra server 8.7.11 GA Release (Open Source version) Ubuntu 16.04 LTS.
The server has been working well for about a year but lately Zimbra webmail is not available, I get:

=========
HTTP ERROR 502

Problem accessing ZCS upstream server. Cannot connect to the ZCS upstream server. Connection is refused.
Possible reasons:

upstream server is unreachable
upstream server is currently being upgraded
upstream server is down

Please contact your ZCS administrator to fix the problem.

========

Minutes later Zimbra Admin is also not available, I only get a blank page.

Upon searching I found:
https://wiki.zimbra.com/wiki/Zimbra_Pro ... mbra_Proxy

I applied:

zmprov mcf zimbraMailProxyReconnectTimeout 0

zmprov mcf zimbraMailProxyMaxFails 0

zmprov ms <mailbox server hostname> zimbraMailProxyMaxFails 0

zmproxyctl restart

I restarted Zimbra services and the issue continues.....

Any feedback about this issue will be highly appreciated.

Regards,

Martin

[L. Mark Stone]

502 errors mean the proxy service can’t talk to the mailbox service.

Please take a look in the mailbox log as well as zimbra.log and post what you find.

Mark

[mgarservers]

Hello Mark,

Thank you for your post.

Please find below relevant information from log files ( I have replaced server IP and hostname with 192.168.1.33 and mydomain.com) :

====================
mailbox.log

2018-07-29 00:19:06,526 WARN [Index-7] [name=admin@mydomain.com;mid=4;] mailbox - transaction canceled because of lock failure
2018-07-29 00:19:06,527 INFO [qtp1798286609-777:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-752:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-803:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-770:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-748:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-759:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-734:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-737:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-770:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-724:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-740:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-773:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-781:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-799:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-725:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:06,527 INFO [qtp1798286609-724:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:00,200 INFO [qtp1798286609-740:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:19:44,710 INFO [LmtpServer-18] [name=admin@mydomain.com;mid=4;ip=192.168.1.33;] sqltrace - Slow execution (18032ms): SELECT mi.id, mi.type, mi.parent_id, mi.fo$
2018-07-29 00:21:27,423 ERROR [Index-7] [name=admin@mydomain.com;mid=4;] mailbox - Failed to lock mailbox
Write Lock Owner - LmtpServer-18 prio=5 id=829 state=RUNNABLE
at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1019)
at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
at sun.util.resources.ParallelListResourceBundle.loadLookupTablesIfNecessary(ParallelListResourceBundle.java:169)
at sun.util.resources.ParallelListResourceBundle.handleKeySet(ParallelListResourceBundle.java:134)
at sun.util.resources.ParallelListResourceBundle.keySet(ParallelListResourceBundle.java:143)
at sun.util.resources.ParallelListResourceBundle.containsKey(ParallelListResourceBundle.java:129)
at sun.util.resources.ParallelListResourceBundle$KeySet.contains(ParallelListResourceBundle.java:208)
at sun.util.resources.ParallelListResourceBundle.containsKey(ParallelListResourceBundle.java:129)
at sun.util.resources.ParallelListResourceBundle$KeySet.contains(ParallelListResourceBundle.java:208)
at sun.util.resources.ParallelListResourceBundle.containsKey(ParallelListResourceBundle.java:129)
at java.text.DateFormatSymbols.initializeData(DateFormatSymbols.java:716)
at java.text.DateFormatSymbols.<init>(DateFormatSymbols.java:145)
at sun.util.locale.provider.DateFormatSymbolsProviderImpl.getInstance(DateFormatSymbolsProviderImpl.java:85)
at java.text.DateFormatSymbols.getProviderInstance(DateFormatSymbols.java:364)
at java.text.DateFormatSymbols.getInstance(DateFormatSymbols.java:340)
at java.util.Calendar.getDisplayName(Calendar.java:2110)
at java.text.SimpleDateFormat.subFormat(SimpleDateFormat.java:1125)
at java.text.SimpleDateFormat.format(SimpleDateFormat.java:966)
at java.text.SimpleDateFormat.format(SimpleDateFormat.java:936)
at java.text.DateFormat.format(DateFormat.java:345)
at org.apache.log4j.pattern.CachedDateFormat.format(CachedDateFormat.java:279)
at org.apache.log4j.pattern.DatePatternConverter.format(DatePatternConverter.java:158)
at org.apache.log4j.pattern.DatePatternConverter.format(DatePatternConverter.java:145)
at org.apache.log4j.rolling.RollingPolicyBase.formatFileName(RollingPolicyBase.java:150)
at org.apache.log4j.rolling.TimeBasedRollingPolicy.rollover(TimeBasedRollingPolicy.java:226)
at org.apache.log4j.rolling.RollingFileAppender.rollover(RollingFileAppender.java:240)
at org.apache.log4j.rolling.RollingFileAppender.subAppend(RollingFileAppender.java:352)
at org.apache.log4j.WriterAppender.append(WriterAppender.java:162)
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
at org.apache.log4j.Category.callAppenders(Category.java:206)
at org.apache.log4j.Category.forcedLog(Category.java:391)
at org.apache.log4j.Category.info(Category.java:666)
at com.zimbra.common.util.Log.info(Log.java:247)
at com.zimbra.cs.db.DebugPreparedStatement.log(DebugPreparedStatement.java:127)
at com.zimbra.cs.db.DebugPreparedStatement.executeQuery(DebugPreparedStatement.java:171)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at com.zimbra.cs.db.StatTrackingPreparedStatement.executeQuery(StatTrackingPreparedStatement.java:352)
at com.zimbra.cs.db.DbMailItem.getByHashes(DbMailItem.java:2706)
at com.zimbra.cs.mailbox.Threader.lookupByReference(Threader.java:348)
at com.zimbra.cs.mailbox.Threader.lookupConversation(Threader.java:304)
at com.zimbra.cs.mailbox.Mailbox.addMessageInternal(Mailbox.java:6078)
at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:5913)
at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:5847)
at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:5842)
at com.zimbra.cs.filter.IncomingMessageHandler.addMessage(IncomingMessageHandler.java:137)
at com.zimbra.cs.filter.IncomingMessageHandler.implicitKeep(IncomingMessageHandler.java:129)
at com.zimbra.cs.filter.ZimbraMailAdapter.keep(ZimbraMailAdapter.java:446)
at com.zimbra.cs.filter.ZimbraMailAdapter.executeActions(ZimbraMailAdapter.java:274)
at org.apache.jsieve.SieveFactory.evaluate(SieveFactory.java:175)
at com.zimbra.cs.filter.RuleManager.applyRulesToIncomingMessage(RuleManager.java:537)
at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliverMessageToLocalMailboxes(ZimbraLmtpBackend.java:615)
at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver(ZimbraLmtpBackend.java:385)
at com.zimbra.cs.lmtpserver.LmtpHandler.processMessageData(LmtpHandler.java:445)
at com.zimbra.cs.lmtpserver.TcpLmtpHandler.continueDATA(TcpLmtpHandler.java:79)
at com.zimbra.cs.lmtpserver.LmtpHandler.doDATA(LmtpHandler.java:434)
at com.zimbra.cs.lmtpserver.LmtpHandler.processCommand(LmtpHandler.java:216)
at com.zimbra.cs.lmtpserver.TcpLmtpHandler.processCommand(TcpLmtpHandler.java:72)
at com.zimbra.cs.server.ProtocolHandler.processConnection(ProtocolHandler.java:189)
at com.zimbra.cs.server.ProtocolHandler.run(ProtocolHandler.java:128)
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)

com.zimbra.cs.mailbox.MailboxLock$LockFailedException: timeout
at com.zimbra.cs.mailbox.MailboxLock.lock(MailboxLock.java:211)
at com.zimbra.cs.mailbox.Mailbox.beginTransaction(Mailbox.java:1726)
at com.zimbra.cs.mailbox.Mailbox.beginReadTransaction(Mailbox.java:1702)
at com.zimbra.cs.mailbox.MailboxIndex.indexItemList(MailboxIndex.java:744)
at com.zimbra.cs.mailbox.MailboxIndex.indexDeferredItems(MailboxIndex.java:408)
at com.zimbra.cs.mailbox.MailboxIndex.access$600(MailboxIndex.java:86)
at com.zimbra.cs.mailbox.MailboxIndex$BatchIndexTask.exec(MailboxIndex.java:1442)
at com.zimbra.cs.mailbox.MailboxIndex$IndexTask.run(MailboxIndex.java:1421)
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)
2018-07-29 00:21:40,526 WARN [Index-7] [name=admin@mydomain.com;mid=4;] mailbox - transaction canceled because of lock failure
2018-07-29 00:20:29,084 INFO [qtp1798286609-720:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:20:29,082 INFO [qtp1798286609-724:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:20:23,386 INFO [qtp1798286609-753:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:20:23,380 INFO [qtp1798286609-795:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:22:00,070 INFO [qtp1798286609-764:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:22:00,070 INFO [qtp1798286609-770:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:22:00,070 INFO [qtp1798286609-742:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:22:00,070 INFO [qtp1798286609-720:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:22:00,070 INFO [qtp1798286609-760:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:22:00,070 INFO [qtp1798286609-737:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:22:00,071 INFO [qtp1798286609-773:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:22:00,071 INFO [qtp1798286609-746:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$
2018-07-29 00:22:00,071 INFO [qtp1798286609-562:https:https://mail.mydomain.com:7073/service/admin/soap/] [] misc - Suspending for 1000ms because context path /service is at 20$

============================

============================
nginx.log


2018/07/28 21:02:36 [notice] 22592#0: memcached channel:192.168.1.33:11211 down, reconnect after:60000 ms
2018/07/28 21:02:41 [notice] 22594#0: *24 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /img/logo/$
2018/07/28 21:02:41 [notice] 22593#0: *23 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /img/zimbr$
2018/07/28 21:02:41 [notice] 22593#0: *22 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /img/zimbr$
2018/07/28 21:02:41 [notice] 22594#0: *24 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:41 [notice] 22593#0: *11 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "HEAD /public/b$
2018/07/28 21:02:41 [notice] 22593#0: *41 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /js/MailCo$
2018/07/28 21:02:41 [notice] 22593#0: *42 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /img/anima$
2018/07/28 21:02:42 [notice] 22593#0: *41 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:42 [notice] 22593#0: *43 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /skins/_ba$
2018/07/28 21:02:42 [notice] 22593#0: *42 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:42 [notice] 22593#0: *11 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:42 [notice] 22593#0: *22 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:42 [notice] 22593#0: *23 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:42 [notice] 22593#0: *43 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:44 [notice] 22594#0: *24 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "POST /service/$
2018/07/28 21:02:44 [notice] 22593#0: *23 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "POST /service/$
2018/07/28 21:02:44 [notice] 22593#0: *41 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /img/logo/$
2018/07/28 21:02:44 [notice] 22593#0: *22 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /img/logo/$
2018/07/28 21:02:44 [notice] 22594#0: *24 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:44 [notice] 22593#0: *22 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:44 [notice] 22593#0: *41 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:44 [notice] 22593#0: *23 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:45 [notice] 22594#0: *24 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /js/Contac$
2018/07/28 21:02:45 [notice] 22594#0: *24 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:46 [notice] 22594#0: *24 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /home/admi$
2018/07/28 21:02:46 [notice] 22594#0: *24 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /home/admi$
2018/07/28 21:02:46 [notice] 22594#0: *24 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:46 [notice] 22594#0: *24 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:47 [notice] 22594#0: *24 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /skins/har$
2018/07/28 21:02:47 [notice] 22593#0: *23 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /skins/har$
2018/07/28 21:02:47 [notice] 22593#0: *23 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:47 [notice] 22594#0: *24 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:02:48 [notice] 22593#0: *41 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "GET /js/Startu$
2018/07/28 21:03:56 [notice] 22593#0: *11 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "POST /service/$
2018/07/28 21:03:56 [notice] 22593#0: *11 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:03:57 [notice] 22593#0: *23 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "POST /service/$
2018/07/28 21:03:57 [notice] 22593#0: *23 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:03:58 [notice] 22593#0: *11 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "POST /service/$
2018/07/28 21:03:58 [notice] 22593#0: *11 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:03:59 [notice] 22593#0: *23 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "POST /service/$
2018/07/28 21:03:59 [notice] 22593#0: *23 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:04:06 [notice] 22593#0: *11 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "POST /service/$
2018/07/28 21:04:06 [notice] 22593#0: *11 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:04:07 [notice] 22593#0: *23 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "POST /service/$
2018/07/28 21:04:08 [notice] 22593#0: *23 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:04:09 [notice] 22593#0: *11 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "POST /service/$
2018/07/28 21:04:09 [notice] 22593#0: *11 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:04:10 [notice] 22593#0: *23 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "POST /service/$
2018/07/28 21:04:10 [notice] 22593#0: *23 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:04:11 [info] 22593#0: *135 proxied session done, client: 23.101.117.29:47702, server: 0.0.0.0:993, login: "diego.ucharo@mydomain.com", upstream: 192.168.1.33:79$
2018/07/28 21:04:11 [info] 22593#0: *158 proxied session done, client: 23.101.117.29:48210, server: 0.0.0.0:993, login: "diego.ucharo@mydomain.com", upstream: 192.168.1.33:79$
2018/07/28 21:04:11 [info] 22593#0: *181 client 23.101.117.29:48614 connected to 0.0.0.0:993
2018/07/28 21:04:12 [notice] 22593#0: *181 no memcache server available, cannot post request while in mail zmauth state, client: 23.101.117.29:48614, server: 0.0.0.0:993, logi$
2018/07/28 21:04:12 [notice] 22593#0: *181 no memcache server available, cannot post request while in mail zmauth state, client: 23.101.117.29:48614, server: 0.0.0.0:993, logi$
2018/07/28 21:04:12 [notice] 22593#0: *181 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 23.101.117.29:48614, server: 0.0.$
2018/07/28 21:04:12 [notice] 22593#0: *181 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 23.101.117.29:48614, server: 0.0.$
2018/07/28 21:04:13 [info] 22593#0: *181 client logged in, client: 23.101.117.29:48614, server: 0.0.0.0:993, login: "diego.ucharo@mydomain.com", upstream: 192.168.1.33:7993 ($
2018/07/28 21:04:13 [notice] 22594#0: *24 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "POST /service/$
2018/07/28 21:04:13 [notice] 22594#0: *24 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:04:14 [notice] 22593#0: *11 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "POST /service/$
2018/07/28 21:04:14 [notice] 22593#0: *11 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:04:15 [info] 22593#0: *188 client 23.101.117.29:48762 connected to 0.0.0.0:993
2018/07/28 21:04:15 [notice] 22593#0: *23 no memcache server available, cannot post request, client: 190.237.183.182, server: mail.mydomain.com.default, request: "POST /service/$
2018/07/28 21:04:15 [notice] 22593#0: *23 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 190.237.183.182, server: mail.clos$
2018/07/28 21:04:15 [notice] 22593#0: *188 no memcache server available, cannot post request while in mail zmauth state, client: 23.101.117.29:48762, server: 0.0.0.0:993, logi$
2018/07/28 21:04:15 [notice] 22593#0: *188 no memcache server available, cannot post request while in mail zmauth state, client: 23.101.117.29:48762, server: 0.0.0.0:993, logi$
2018/07/28 21:04:16 [notice] 22593#0: *188 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 23.101.117.29:48762, server: 0.0.$
2018/07/28 21:04:16 [notice] 22593#0: *188 no memcache server available, cannot post request while SSL handshaking to lookup handler, client: 23.101.117.29:48762, server: 0.0.$
2018/07/28 21:04:16 [info] 22593#0: *188 client logged in, client: 23.101.117.29:48762, server: 0.0.0.0:993, login: "diego.ucharo@mydomain.com", upstream: 192.168.1.33:7993 ($
2018/07/28 21:04:17 [info] 22593#0: *193 client 23.101.117.29:48852 connected to 0.0.0.0:993
2018/07/28 21:04:18 [notice] 22593#0: *193 no memcache server available, cannot post request while in mail zmauth state, client: 23.101.117.29:48852, server: 0.0.0.0:993, logi$
2018/07/28 21:04:18 [notice] 22593#0: *193 no memcache server available, cannot post request while in mail zmauth state, client: 23.101.117.29:48852, server: 0.0.0.0:993, logi$


==============================

==============================

zimbra logegrep '(reject|warning|error|fatal|panic):' /var/log/zimbra.log

Jul 29 16:33:17 mail postfix/submission/smtpd[20069]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:33:17 mail postfix/submission/smtpd[20069]: warning: Connection concurrency limit exceeded: 51 from unknown[192.81.215.213] for service submission
Jul 29 16:33:17 mail postfix/submission/smtpd[20069]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:33:17 mail postfix/submission/smtpd[20069]: warning: Connection concurrency limit exceeded: 51 from unknown[192.81.215.213] for service submission
Jul 29 16:33:18 mail postfix/submission/smtpd[20069]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:33:18 mail postfix/submission/smtpd[20069]: warning: Connection concurrency limit exceeded: 51 from unknown[192.81.215.213] for service submission
Jul 29 16:33:26 mail postfix/submission/smtpd[14634]: warning: unknown[206.189.228.184]: SASL LOGIN authentication failed: authentication failure
Jul 29 16:33:26 mail postfix/submission/smtpd[14678]: warning: unknown[192.81.216.62]: SASL LOGIN authentication failed: authentication failure
Jul 29 16:33:30 mail postfix/submission/smtpd[14634]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:33:30 mail postfix/submission/smtpd[14634]: warning: Connection concurrency limit exceeded: 51 from unknown[192.81.215.213] for service submission
Jul 29 16:33:31 mail postfix/submission/smtpd[14678]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:33:31 mail postfix/submission/smtpd[14678]: warning: Connection concurrency limit exceeded: 51 from unknown[192.81.215.213] for service submission
Jul 29 16:33:32 mail postfix/submission/smtpd[16709]: warning: unknown[192.81.215.213]: SASL LOGIN authentication failed: authentication failure
Jul 29 16:33:36 mail postfix/submission/smtpd[14634]: warning: hostname qa.swarmwkr2 does not resolve to address 192.81.216.62: Name or service not known
Jul 29 16:33:37 mail postfix/submission/smtpd[16917]: warning: unknown[192.81.215.213]: SASL LOGIN authentication failed: authentication failure
Jul 29 16:33:42 mail postfix/submission/smtpd[16709]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:33:42 mail postfix/submission/smtpd[17079]: warning: unknown[192.81.215.213]: SASL LOGIN authentication failed: authentication failure
Jul 29 16:33:47 mail postfix/submission/smtpd[17079]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:33:52 mail postfix/submission/smtpd[20252]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:33:57 mail postfix/submission/smtpd[20455]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:33:57 mail postfix/submission/smtpd[20455]: warning: Connection concurrency limit exceeded: 51 from unknown[192.81.215.213] for service submission
Jul 29 16:34:03 mail postfix/submission/smtpd[20522]: warning: hostname qa.swarmwkr2 does not resolve to address 192.81.216.62: Name or service not known
Jul 29 16:34:08 mail postfix/submission/smtpd[20796]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:34:08 mail postfix/submission/smtpd[20796]: warning: Connection concurrency limit exceeded: 51 from unknown[192.81.215.213] for service submission
Jul 29 16:34:08 mail postfix/submission/smtpd[20796]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:34:08 mail postfix/submission/smtpd[20796]: warning: Connection concurrency limit exceeded: 51 from unknown[192.81.215.213] for service submission
Jul 29 16:34:09 mail postfix/submission/smtpd[20796]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:34:09 mail postfix/submission/smtpd[20796]: warning: Connection concurrency limit exceeded: 51 from unknown[192.81.215.213] for service submission
Jul 29 16:34:09 mail postfix/submission/smtpd[20796]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:34:09 mail postfix/submission/smtpd[20796]: warning: Connection concurrency limit exceeded: 51 from unknown[192.81.215.213] for service submission
Jul 29 16:34:11 mail postfix/submission/smtpd[17089]: warning: unknown[206.189.228.249]: SASL LOGIN authentication failed: authentication failure
Jul 29 16:34:11 mail postfix/submission/smtpd[17142]: warning: unknown[192.81.215.213]: SASL LOGIN authentication failed: authentication failure
Jul 29 16:34:17 mail postfix/submission/smtpd[17370]: warning: unknown[192.81.215.213]: SASL LOGIN authentication failed: authentication failure
Jul 29 16:34:20 mail postfix/submission/smtpd[20796]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:34:22 mail postfix/submission/smtpd[14829]: warning: unknown[192.81.215.213]: SASL LOGIN authentication failed: authentication failure
Jul 29 16:34:26 mail postfix/submission/smtpd[17089]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:34:27 mail postfix/submission/smtpd[15055]: warning: unknown[192.81.215.213]: SASL LOGIN authentication failed: authentication failure
Jul 29 16:34:36 mail postfix/submission/smtpd[15055]: warning: hostname qa.swarmwkr2 does not resolve to address 192.81.216.62: Name or service not known
Jul 29 16:34:41 mail postfix/submission/smtpd[14829]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:34:46 mail postfix/submission/smtpd[20973]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:34:51 mail postfix/submission/smtpd[20977]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:34:51 mail postfix/submission/smtpd[20977]: warning: Connection concurrency limit exceeded: 51 from unknown[192.81.215.213] for service submission
Jul 29 16:34:52 mail postfix/submission/smtpd[20977]: warning: hostname qa.swarmwkr1 does not resolve to address 192.81.215.213: Name or service not known
Jul 29 16:34:52 mail postfix/submission/smtpd[20977]: warning: Connection concurrency limit exceeded: 51 from unknown[192.81.215.213] for service submission

==============================

Any feedback or suggestions will be highly appreciated.

Kind regards,

Martin

[sambhajirb@yahoo.in]

https://mail.digimail.in/
HTTP ERROR 502
Problem accessing ZCS upstream server. Cannot connect to the ZCS upstream server. Connection is refused.
Possible reasons:

upstream server is unreachable
upstream server is currently being upgraded
upstream server is down
Please contact your ZCS administrator to fix the problem.

Powered by Nginx-Zimbra://

[phoenix]

https://mail.digimail.in/
HTTP ERROR 502
Problem accessing ZCS upstream server. Cannot connect to the ZCS upstream server. Connection is refused.
Possible reasons:

upstream server is unreachable
upstream server is currently being upgraded
upstream server is down
Please contact your ZCS administrator to fix the problem.

Powered by Nginx-Zimbra://

You've given no real information with which anyone could help you. Try following some of the highlighted suggestions in your post and read some of the earlier posts in this thread.

[davidkillingsworth]

I'm also getting this problem and I figure that it's a memcache issue, but I am not sure how to debug memcache.

Any guidance or suggestions would be greatly appreciated.

[davidkillingsworth]

Actually, looking on the proxy wiki help page, I found a section that described my problem and had some commands.
https://wiki.zimbra.com/wiki/Zimbra_Proxy_Guide

I looked at this:

Code: Select all

$ zmprov gcf zimbraMailProxyMaxFails

which produced:

Code: Select all

zimbraMailProxyMaxFails: 1

I then ran the following:

Code: Select all

zmprov mcf zimbraMailProxyMaxFails 0

I haven't been able to re-produce the problem since.

I'm not sure what this really means, but it is working fine now and it's a low traffic server, so I guess it's fine.