Date: Mon, 13 Jan 2025 19:50:58 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 283747] kernel panic after telegraf service restart Message-ID: <bug-283747-227-tjPjkJbj4Z@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-283747-227@https.bugs.freebsd.org/bugzilla/> References: <bug-283747-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283747 --- Comment #17 from Gleb Smirnoff <glebius@FreeBSD.org> --- My current theory is that telegraf closes active connection somehow differe= nt than other applications, which creates conditions to hit this bug. Otherwi= se we would see this panic with all kinds of software. The 30-60 period that = you see is the TCP 2MSL timeout, and that matches the stack trace that you have. It happens in garbage collecting of TCP connections in timewait. If you have possibility, can you please intentionally panic a machine, but first run ktrace on the telegraf. Assuming telegraf PID is 6666, the comma= nd would be 'ktrace -p 6666'. It will write to ktrace.out that would be locat= ed in the current directory, so make sure it is not /tmp or other directory th= at is cleansed on startup. Since you are going to intentionally panic the mac= hine anyway, would be also very helpful if you write kernel crashdump that can be later shared with me and Mark. --=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-283747-227-tjPjkJbj4Z>