Why did it reboot?

[Ellis Michael Lieberman]

I came back to my desk with a notification email from my firewall. It said:
*Notifications in this message: 1

3:56:39 Bootup complete*

This was Saturday night and everything was pretty much shut down. No one was working.

I checked logs but found no reason for the reboot. How di I learn what caused this?

I saw this:
Sep 2 03:56:20 dpinger 75283 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr 58.69.145.0 bind_addr 58.69.150.45 identifier "WAN_PPPOE "

And this.
Sep 2 03:15:00 sshguard 56259 Now monitoring attacks.
Sep 2 03:26:00 sshguard 56259 Exiting on signal.
Sep 2 03:26:00 sshguard 70226 Now monitoring attacks.
Sep 2 03:37:00 sshguard 70226 Exiting on signal.
Sep 2 03:37:00 sshguard 60557 Now monitoring attacks.
Sep 2 03:48:00 sshguard 60557 Exiting on signal.
Sep 2 03:48:00 sshguard 73921 Now monitoring attacks.
Sep 2 03:56:10 syslogd kernel boot file is /boot/kernel/kernel
Sep 2 03:56:10 kernel ---<<BOOT>>---
Sep 2 03:56:10 kernel Copyright (c) 1992-2023 The FreeBSD Project.
Sep 2 03:56:10 kernel Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994

[stephenw10]

Nothing there shows an issue other than it rebooted. I assume it did not lose power? Was there a crash report shown after it rebooted?

[Ellis Michael Lieberman]

@stephenw10,
At sometime after 6:30AM, a little more than ten hours after I posted about this, and before I even saw your message, the unit totally failed to operate...
Even though:
There was no loss of commercial power
There was no loss of UPS power.

It was a faulty AC/DC transformer. (Testing it that morning, it was producing 12V but the amperage wasn't even detectable on my multi-meter.) That was Sunday morning and the shops where closed.

This is Monday morning and with a new AC/DC transformer connected all is back and working. :-)

[stephenw10]

Nice catch. And relatively easy fix.