Date: Thu, 25 Apr 2019 22:03:41 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 237568] Panic when closing socket descriptor? Message-ID: <bug-237568-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237568 Bug ID: 237568 Summary: Panic when closing socket descriptor? Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Keywords: crash, panic Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: rlwestlund@gmail.com Created attachment 204020 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D204020&action= =3Dedit Stack trace from kernel panic Our setup is like this: FreeBSD 12.0-RELEASE-p3 running deployments of a web service in multiple jails, each has nginx as an upstream to the nginx runni= ng on the host, which is a reverse proxy (I think that's the right term?). The in-jail nginx's are themselves partially reverse proxies to a Go program; static files are served by nginx itself but dynamic content comes from the = Go server. Problem: Occasionally, loading the web page crashes the entire host. There doesn't seem to be any reliable way to reproduce it. We've tried turn= ing HTTP 2 on and off; it happens either way, but we haven't found any combinat= ion of circumstances that causes it to happen more than occasionally (I'd estim= ate something like 1 in 20 page reloads on average). Many times we've made a ch= ange and thought we fixed it after >50 successful reloads but found that it does still crash occasionally. I'll attach the stack trace from the crash. Kernel: GENERIC Architecture: amd64 nginx version: 1.14.2_13,2 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237568-227>