Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 01 Oct 2024 18:17:43 +0100
From:      Frank Leonhardt <freebsd-doc@fjl.co.uk>
To:        FreeBSD questions mailing list <freebsd-questions@freebsd.org>
Subject:   I can't get no crash dump
Message-ID:  <e83d4893fcaae0914b4b17c981cc5ea7@fjl.co.uk>

next in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
I've got a host that's mysteriously rebooting. There's no clue in the 
logs. It's not doing much - it's just a gateway. Just every few hours, 
it reboots. (It was a BSD 12 upgraded to 13, and it's been sitting there 
as a standby gateway for ages with no problem - ask it to do a bit of 
work and it gets in a strop).

Anyway, I'm trying to figure out how to get a crash dump, assuming 
there's a kernel panic leading to a reboot.

rc.conf:

dumpdev="AUTO"

# swapinfo -h
Device              Size     Used    Avail Capacity
/dev/ada0p2         8.0G       0B     8.0G     0%

# ls -ld /dev/dumpdev
lrwxr-xr-x  1 root  wheel  11 Oct  1 15:07 /dev/dumpdev -> /dev/ada0p2

# ls -al /crash
total 10
drwxr-x---   2 root  wheel   3 Nov 15  2022 .
drwxr-xr-x  24 root  wheel  24 Oct  1 15:07 ..
-rw-r--r--   1 root  wheel   5 Oct 23  2020 minfree   -   (contains 
"2048")

What am I missing here? Surely when it reboots I should be seeing 
vmcore.0 in there. Unfortunately this host is remote. Any other bright 
ideas about where I can find a clue what's upsetting it would be 
welcome.

Thanks, Frank.
[-- Attachment #2 --]
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>I've got a host that's mysteriously rebooting. There's no clue in the logs. It's not doing much - it's just a gateway. Just every few hours, it reboots. (It was a BSD 12 upgraded to 13, and it's been sitting there as a standby gateway for ages with no problem - ask it to do a bit of work and it gets in a strop).</p>
<p>Anyway, I'm trying to figure out how to get a crash dump, assuming there's a kernel panic leading to a reboot.</p>
<p>rc.conf:</p>
<p>dumpdev="AUTO"</p>
<p><br /></p>
<p># swapinfo -h<br />Device &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Size &nbsp; &nbsp; Used &nbsp; &nbsp;Avail Capacity<br />/dev/ada0p2 &nbsp; &nbsp; &nbsp; &nbsp; 8.0G &nbsp; &nbsp; &nbsp; 0B &nbsp; &nbsp; 8.0G &nbsp; &nbsp; 0%</p>
<p><br /></p>
<p># ls -ld /dev/dumpdev<br />lrwxr-xr-x &nbsp;1 root &nbsp;wheel &nbsp;11 Oct &nbsp;1 15:07 /dev/dumpdev -&gt; /dev/ada0p2</p>
<p><br /></p>
<p># ls -al /crash<br />total 10<br />drwxr-x--- &nbsp; 2 root &nbsp;wheel &nbsp; 3 Nov 15 &nbsp;2022 .<br />drwxr-xr-x &nbsp;24 root &nbsp;wheel &nbsp;24 Oct &nbsp;1 15:07 ..<br />-rw-r--r-- &nbsp; 1 root &nbsp;wheel &nbsp; 5 Oct 23 &nbsp;2020 minfree&nbsp; &nbsp;-&nbsp; &nbsp;(contains "2048")</p>
<p><br /></p>
<p>What am I missing here? Surely when it reboots I should be seeing vmcore.0 in there. Unfortunately this host is remote. Any other bright ideas about where I can find a clue what's upsetting it would be welcome.</p>
<p>Thanks, Frank.</p>
<p><br /></p>
<p><br /></p>
<p><br /></p>
<p><br /></p>
<p><br /></p>
</body></html>

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e83d4893fcaae0914b4b17c981cc5ea7>