[Bug 210642] www/nginx: "service nginx upgrade" results in shutdown() failed (54: Connection reset by peer)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210642

            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 at FreeBSD.org
          Reporter: adam.strohl-fbsd at ateamsystems.com
             Flags: maintainer-feedback?(osa at FreeBSD.org)
          Assignee: osa at 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 reset by
peer)
2016/06/27 00:18:58 [error] 73757#0: shutdown() failed (54: Connection reset by
peer)
2016/06/27 00:18:58 [error] 73757#0: shutdown() failed (54: Connection reset by
peer)
2016/06/27 00:18:58 [error] 73757#0: shutdown() failed (54: Connection reset by
peer)
2016/06/27 00:18:58 [error] 73757#0: shutdown() failed (54: Connection reset by
peer)
2016/06/27 00:18:58 [error] 73757#0: shutdown() failed (54: Connection reset 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: Address
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.  Waiting
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.