Date: Fri, 23 Dec 2022 13:00:20 +0100 From: Gian-Simon Purkert <gspurki@gmail.com> To: Andrea Venturoli <ml@netfence.it>, questions@freebsd.org Subject: Re: Help with crash (13.1/amd64) Message-ID: <4671e6f1-3a3b-be18-953b-a7c801bb5e47@gmail.com> In-Reply-To: <f049bd86-7b38-6191-4ed1-857de772833a@netfence.it> References: <f9df5b20-ab15-d887-6eb8-14924e8295bc@netfence.it> <643d7f82-c276-6813-42bf-a8722e804121@freebsd.org> <f049bd86-7b38-6191-4ed1-857de772833a@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/23/22 12:32, Andrea Venturoli wrote: > On 12/23/22 12:09, Graham Perrin wrote: >> On 23/12/2022 09:13, Andrea Venturoli wrote: >>> >>> … I'm trying hard to get a core, but so far I was not able to achieve >>> this. … >> >> Is the difficulty with configuration? >> >> Or, is configuration correct but /var/crash contains no kernel >> panic-related files? >> > > Problem is with encrypted swap. > See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238301. > > After applying that patch, the current state is: >> # swapinfo >> Device 1K-blocks Used Avail Capacity >> /dev/mirror/swap2.eli 67108860 0 67108860 0% >> # dumpon -l >> mirror/swap2 > > So I hope to get a dump the next time it crashes. > > bye & Thanks > av. > Also you are on patchlevel 3, 5 is actual. And btw have a look at blacklistd instead fail2ban if you just need it for ssh: https://www.freebsd.org/cgi/man.cgi?query=blacklistd&sektion=8&format=html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4671e6f1-3a3b-be18-953b-a7c801bb5e47>