From owner-freebsd-ports-bugs@freebsd.org Mon Jun 27 20:56:25 2016 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49496B857B3 for ; Mon, 27 Jun 2016 20:56:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 201A92E0E for ; Mon, 27 Jun 2016 20:56:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5RKuO2J033596 for ; Mon, 27 Jun 2016 20:56:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 210642] www/nginx: "service nginx upgrade" results in shutdown() failed (54: Connection reset by peer) Date: Mon, 27 Jun 2016 20:56:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: adam.strohl-fbsd@ateamsystems.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: osa@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 20:56:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210642 Bug ID: 210642 Summary: www/nginx: "service nginx upgrade" results in shutdown() failed (54: Connection reset by peer) Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: osa@FreeBSD.org Reporter: adam.strohl-fbsd@ateamsystems.com Flags: maintainer-feedback?(osa@FreeBSD.org) Assignee: osa@FreeBSD.org We use 'service nginx upgrade' to do seamless restarting of NginX processes= on high volume sites when needed (ie; an upgrade). We recently just upgraded most of our clients to 1.10.1, and started seeing this in the log when we run the 'service nginx upgrade' command: Code: 2016/06/27 00:18:58 [error] 73757#0: shutdown() failed (54: Connection rese= t by peer) 2016/06/27 00:18:58 [error] 73757#0: shutdown() failed (54: Connection rese= t by peer) 2016/06/27 00:18:58 [error] 73757#0: shutdown() failed (54: Connection rese= t by peer) 2016/06/27 00:18:58 [error] 73757#0: shutdown() failed (54: Connection rese= t by peer) 2016/06/27 00:18:58 [error] 73757#0: shutdown() failed (54: Connection rese= t by peer) 2016/06/27 00:18:58 [error] 73757#0: shutdown() failed (54: Connection rese= t by peer) 2016/06/27 00:18:58 [alert] 73753#0: worker process 73757 exited on signal = 11 2016/06/27 00:18:56 [emerg] 74294#0: bind() to 1.2.3.4:443 failed (48: Addr= ess already in use) nginx: [emerg] bind() to 1.2.3.4:443 failed (48: Address already in use) 2016/06/27 00:18:56 [emerg] 74294#0: still could not bind() nginx: [emerg] still could not bind() This happens even on idle servers (backups) with no traffic. The end result is that NginX exits entirely and doesn't come back up. Wait= ing a few seconds and 'service nginx start' will work, but at that point there = has been a lot of missed traffic if the site is busy. --=20 You are receiving this mail because: You are the assignee for the bug.=