8.8.15 P31.1 proxy / webapp failure.

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
Posts: 4
Joined: Fri May 06, 2016 4:46 pm

8.8.15 P31.1 proxy / webapp failure.

Post by rsmith999 »

We had our first issue with Zimbra suddenly becoming unavailable (webapp).

Nginx log:

2022/05/13 13:17:07 [error] 3133#0: *1073506 no live upstreams while connecting to upstream,
upstream timed out (110: Connection timed out) while SSL handshaking to upstream

Mail log showed mail not flowing (appears as entire proxy service was down).
Is there a log to take a look at to determine why proxy would have been unresponsive? Zmcontrol status showed that proxy was running but not processing requests.
I think I am limited to the nginx logs?

I am very suspicious that this is related to P31.1 because we have never seen an issue like this in the many years we have been running Zimbra OSE.
Has anyone else experienced this issue post patch?

Last edited by rsmith999 on Sun May 15, 2022 9:20 pm, edited 1 time in total.
User avatar
L. Mark Stone
Posts: 2620
Joined: Wed Oct 09, 2013 11:35 am
Location: Portland, Maine, US
ZCS/ZD Version: 8.8.15 Network Edition

Re: 8.8.15 P31.1 proxy / webapp failure.

Post by L. Mark Stone »

502 errors are posted by the proxy service, so I suspect proxy is running. The text of the error says that no upstream servers can be contacted. That means mailboxd (if a single server) or a separate mailbox server is not responding to the proxy's request.

mailbox.log and zmmailboxd.out are where I would look next.

Hope that helps,
L. Mark Stone
Mission Critical Email - Zimbra VAR/BSP/Training Partner https://www.missioncriticalemail.com/
AWS Certified Solutions Architect-Associate
Post Reply