From Newsgroup: muc.lists.freebsd.stable
--0000000000002962ef06414914f7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
On Thu, Oct 16, 2025 at 8:12=E2=80=AFAM Alan Somers <
asomers@freebsd.org> w= rote:
The "boot" command will give you a vague description like "shutdown" or "crash".
boot command? I don't have this on my system. How do yo uget that?
If a crash was the cause then maybe your system isn't configured to make
core dumps. I suggest forcing a crash with "sysctl debug.kdb.panic=3D1" while you watch the screen to see what happens.
Yea. If it is a reboot, and crash dumps are enabled, and there's nothing is
in /var/log/messages, you have limited options.
If there's a BMC, and it speaks IPMI, there might be something in the IPMI
log if it was hardware triggered (ipmitool sel list):
1 | Pre-Init |0000001024| Processor #0xe4 | Presence detected |
Asserted
2 | Pre-Init |0000000000| System Event | OEM System boot event |
Asserted
3 | Pre-Init |0000000001| System Event | Timestamp Clock Sync |
Asserted
4 | 04/17/23 | 16:07:49 MDT | System Event | Timestamp Clock Sync |
Asserted
5 | 04/17/23 | 16:11:12 MDT | OS Boot #0x22 | boot completed - device
not specified | Asserted
6 | 04/17/23 | 16:20:42 MDT | System Event | OEM System boot event | Asserted
7 | 04/17/23 | 16:23:16 MDT | System Event | OEM System boot event | Asserted
8 | 04/17/23 | 16:28:44 MDT | System Event | OEM System boot event | Asserted
9 | 04/17/23 | 16:30:25 MDT | OS Boot #0x22 | boot completed - device
not specified | Asserted
...
(oh my, I need to clear my log)
Warner
On Thu, Oct 16, 2025 at 7:35=E2=80=AFAM void <void@f-m.fm> wrote:
Hi,
I'm trying to work out why a reboot is happening.
line power is fine. PSU is fine.
There's no coredump.
Nothing in /var/log/messages console.log all.log or daemon.log
Is there a thing I can set somewhere which when enabled will
capture why a system reboots?
thnx
--
--0000000000002962ef06414914f7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g= mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 16,=
2025 at 8:12=E2=80=AFAM Alan Somers <<a href=3D"mailto:asomers@freebsd.= org">
asomers@freebsd.org</a>> wrote:<br></div><blockquote class=3D"gmail= _quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204= ,204);padding-left:1ex"><div dir=3D"ltr"><div>The "boot" command = will give you a vague description like "shutdown" or "crash&= quot;. </div></div></blockquote><div><br></div><div><div>boot command? I do= n't have this on my system. How do yo uget that?</div></div><div>=C2=A0= </div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b= order-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><d= iv>If a crash was the cause then maybe your system isn't configured to = make core dumps.=C2=A0 I suggest forcing a crash with "sysctl=C2=A0deb= ug.kdb.panic=3D1" while=C2=A0you watch the screen to see what happens.= </div></div></blockquote><div><br></div><div>Yea. If it is a reboot, and cr= ash dumps are enabled, and there's nothing is in /var/log/messages, you=
have limited options.</div><div><br></div><div>If there's a BMC, and i=
t speaks IPMI, there might be something in the IPMI log if it was hardware = triggered (ipmitool sel list):</div><div>=C2=A0 =C2=A01 | =C2=A0Pre-Init = =C2=A0|0000001024| Processor #0xe4 | Presence detected | Asserted<br>=C2=A0=
=C2=A02 | =C2=A0Pre-Init =C2=A0|0000000000| System Event | OEM System boot=
event | Asserted<br>=C2=A0 =C2=A03 | =C2=A0Pre-Init =C2=A0|0000000001| Sys= tem Event | Timestamp Clock Sync | Asserted<br>=C2=A0 =C2=A04 | 04/17/23 | = 16:07:49 MDT | System Event | Timestamp Clock Sync | Asserted<br>=C2=A0 =C2= =A05 | 04/17/23 | 16:11:12 MDT | OS Boot #0x22 | boot completed - device no=
t specified | Asserted<br>=C2=A0 =C2=A06 | 04/17/23 | 16:20:42 MDT | System=
Event | OEM System boot event | Asserted<br>=C2=A0 =C2=A07 | 04/17/23 | 16= :23:16 MDT | System Event | OEM System boot event | Asserted<br>=C2=A0 =C2= =A08 | 04/17/23 | 16:28:44 MDT | System Event | OEM System boot event | Ass= erted<br>=C2=A0 =C2=A09 | 04/17/23 | 16:30:25 MDT | OS Boot #0x22 | boot co= mpleted - device not specified | Asserted</div><div>...</div><div>(oh my, I=
need to clear my log)</div><div><br></div><div>Warner=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px = solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gma= il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 16, 2025 at 7:3= 5=E2=80=AFAM void <<a href=3D"mailto:
void@f-m.fm" target=3D"_blank">void= @f-m.fm</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"= margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef= t:1ex">Hi,<br>
I'm trying to work out why a reboot is happening.<br>
line power is fine. PSU is fine.<br>
There's no coredump.<br>
Nothing in /var/log/messages console.log all.log or daemon.log<br>
Is there a thing I can set somewhere which when enabled will <br>
capture why a system reboots?<br>
thnx<br>
-- <br>
</blockquote></div></div>
</blockquote></div></div>
--0000000000002962ef06414914f7--
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to
news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2