8.8.5 NGINX recv() failed (111: Connection refused)

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
moebius
Posts: 17
Joined: Sat Sep 13, 2014 3:34 am

8.8.5 NGINX recv() failed (111: Connection refused)

Postby moebius » Wed Jan 03, 2018 6:54 pm

Since 8.8.5, periodically our web services become unavailable. Once this occurs, the nginx.log fills up as follows. Restarting Zimbra restores the web services for a period of a few days. Any ideas on what I should look into here? We've not had this problem in years of uptime on previous versions.

Code: Select all

2018/01/03 10:36:24 [info] 18517#0: *56665 client 208.71.156.254:49224 connected to 173.239.65.92:993
2018/01/03 10:36:24 [error] 18517#0: *56665 recv() failed (111: Connection refused) while reading response from upstream, client: 208.71.156.254:49224, server: 173.239.65.92:993, login: "tbehary", upstream: 173.239.65.92:7143 (208.71.156.254:49224->173.239.65.92:993) <=> (173.239.65.92:36093->)
2018/01/03 10:36:24 [info] 18517#0: *56667 client 208.71.156.254:49225 connected to 173.239.65.92:993
2018/01/03 10:36:24 [error] 18517#0: *56667 recv() failed (111: Connection refused) while reading response from upstream, client: 208.71.156.254:49225, server: 173.239.65.92:993, login: "tbehary", upstream: 173.239.65.92:7143 (208.71.156.254:49225->173.239.65.92:993) <=> (173.239.65.92:36094->)
2018/01/03 10:36:24 [info] 18517#0: *56669 client 208.71.156.254:49226 connected to 173.239.65.92:993
2018/01/03 10:36:24 [error] 18517#0: *56669 recv() failed (111: Connection refused) while reading response from upstream, client: 208.71.156.254:49226, server: 173.239.65.92:993, login: "tbehary", upstream: 173.239.65.92:7143 (208.71.156.254:49226->173.239.65.92:993) <=> (173.239.65.92:36095->)
2018/01/03 10:36:24 [info] 18517#0: *56671 client 208.71.156.254:49227 connected to 173.239.65.92:993
2018/01/03 10:36:24 [error] 18517#0: *56671 recv() failed (111: Connection refused) while reading response from upstream, client: 208.71.156.254:49227, server: 173.239.65.92:993, login: "tbehary", upstream: 173.239.65.92:7143 (208.71.156.254:49227->173.239.65.92:993) <=> (173.239.65.92:36096->)
2018/01/03 10:36:24 [info] 18517#0: *56673 client 208.71.156.254:49228 connected to 173.239.65.92:993
2018/01/03 10:36:24 [error] 18517#0: *56673 recv() failed (111: Connection refused) while reading response from upstream, client: 208.71.156.254:49228, server: 173.239.65.92:993, login: "tbehary", upstream: 173.239.65.92:7143 (208.71.156.254:49228->173.239.65.92:993) <=> (173.239.65.92:36097->)
2018/01/03 10:36:24 [info] 18517#0: *56675 client 208.71.156.254:49229 connected to 173.239.65.92:993
2018/01/03 10:36:24 [error] 18517#0: *56675 recv() failed (111: Connection refused) while reading response from upstream, client: 208.71.156.254:49229, server: 173.239.65.92:993, login: "tbehary", upstream: 173.239.65.92:7143 (208.71.156.254:49229->173.239.65.92:993) <=> (173.239.65.92:36098->)
2018/01/03 10:36:24 [info] 18517#0: *56677 client 208.71.156.254:49230 connected to 173.239.65.92:993
2018/01/03 10:36:24 [error] 18517#0: *56677 recv() failed (111: Connection refused) while reading response from upstream, client: 208.71.156.254:49230, server: 173.239.65.92:993, login: "tbehary", upstream: 173.239.65.92:7143 (208.71.156.254:49230->173.239.65.92:993) <=> (173.239.65.92:36099->)
2018/01/03 10:36:24 [info] 18517#0: *56679 client 208.71.156.254:49231 connected to 173.239.65.92:993
2018/01/03 10:36:24 [error] 18517#0: *56679 recv() failed (111: Connection refused) while reading response from upstream, client: 208.71.156.254:49231, server: 173.239.65.92:993, login: "tbehary", upstream: 173.239.65.92:7143 (208.71.156.254:49231->173.239.65.92:993) <=> (173.239.65.92:36100->)
2018/01/03 10:36:24 [info] 18517#0: *56681 client 208.71.156.254:49232 connected to 173.239.65.92:993
2018/01/03 10:36:24 [error] 18517#0: *56681 recv() failed (111: Connection refused) while reading response from upstream, client: 208.71.156.254:49232, server: 173.239.65.92:993, login: "tbehary", upstream: 173.239.65.92:7143 (208.71.156.254:49232->173.239.65.92:993) <=> (173.239.65.92:36101->)
2018/01/03 10:36:24 [info] 18517#0: *56683 client 208.71.156.254:49233 connected to 173.239.65.92:993
2018/01/03 10:36:24 [error] 18517#0: *56683 recv() failed (111: Connection refused) while reading response from upstream, client: 208.71.156.254:49233, server: 173.239.65.92:993, login: "tbehary", upstream: 173.239.65.92:7143 (208.71.156.254:49233->173.239.65.92:993) <=> (173.239.65.92:36102->)


User avatar
Raun
Zimbra Employee
Zimbra Employee
Posts: 75
Joined: Thu Mar 24, 2016 1:22 pm

Re: 8.8.5 NGINX recv() failed (111: Connection refused)

Postby Raun » Tue Jan 16, 2018 2:31 pm

Connection refused , it says . What I would look for initially is zimbraMailMode on all mailstores and output of zmprov garpb(on proxy) and if it corresponds to the port set .
User avatar
Raun
Zimbra Employee
Zimbra Employee
Posts: 75
Joined: Thu Mar 24, 2016 1:22 pm

Re: 8.8.5 NGINX recv() failed (111: Connection refused)

Postby Raun » Tue Jan 16, 2018 2:33 pm

Also it seems to be an issue with IMAP ( port 993 in the logs) . Double check if mail proxy is set properly. Run the proxyconfig command again if you need to ( look for wiki to enable proxy and you will get the command) :-)

This should fix it for you.
User avatar
Raun
Zimbra Employee
Zimbra Employee
Posts: 75
Joined: Thu Mar 24, 2016 1:22 pm

Re: 8.8.5 NGINX recv() failed (111: Connection refused)

Postby Raun » Tue Jan 16, 2018 2:56 pm

Also check bug 108299 if that is the issue here
moebius
Posts: 17
Joined: Sat Sep 13, 2014 3:34 am

Re: 8.8.5 NGINX recv() failed (111: Connection refused)

Postby moebius » Wed Jan 17, 2018 12:36 am

I agree it is an issue with IMAP not responding to NGINX.
When I run a top I see the mailboxd PID present but with very high CPU.
Until I kill -9 the mailboxd PID, NGINX keeps throwing 111: Connection refused errors.
Once I kill the mailboxd PID IMAP starts responding again. Webmail and Web admin are also unresponsive until the PID is killed.
During the time mailboxd is unresponsive, there is also no logging shown in the mailbox.log

This started with 8.8.5 and continues with 8.8.6

Return to “Administrators”

Who is online

Users browsing this forum: No registered users and 13 guests