Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Jan 2025 18:47: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-RPOn0Rl5EQ@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 #16 from Eero H=C3=A4nninen <fax@nohik.ee> ---
Thanks for the explanation!
Currently I don't know of any instant way to reproduce this panic. As I wro=
te
before, in my case if telegraf process is older than 7 or 10 days and then I
restart process, then this panic happens - sometimes there is about 30 - 60
seconds delay between telegraf restart and kernel panic.=20
I'm not sure, but this panic seems to appears from 14.0 release. I'm not su=
re
because our machines do not have crash dump configured by default, but patt=
ern
was the same. About 14.2 I can't confirm yet, but by the end of this week s=
ome
machines will exceed the so-called critical time point, so we'll see if they
crash with 14.2 or not.
I will boot known "crash servers" to debug kernel, so I will get more detai=
led
data.
If you need, I have 3 more crash info samples - but to my eye it seems to be
same.

--=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-RPOn0Rl5EQ>