this post was submitted on 13 Jul 2026
11 points (86.7% liked)

Selfhosted

60789 readers
388 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Hello,

I need some help troubleshooting. As per the title, I'm using a Raspberry Pi 3 Model B Plus Rev 1.3 with Debian bookworm kernel 6.12.93+rpt-rpi-v8 to host a local YunoHost server (12.1.40.1 stable) with the following apps:

  • AdGuard Home (0.107.77)
  • Baïkal (0.9.4)
  • Grocy (4.6.0)
  • Tiny Tiny RSS (2026.07.05)

Sadly, the server randomly crashes and can only be rebooted trough a hardware reset (pulling the plug).

Here are the last 50 lines of journalctl before the last crash: https://privatebin.net/?dbca869581c95573#83bk7W2CEPbeBGAXyg7wG8xLFhmGpwxBD9ReUaFphdCS

Here are the last 50 lines of journalctl before the crash before that: https://privatebin.net/?f7bdf2fd48ab12f7#9ZPh68rJ1p8JdzyLaGTXomZV4Lt7BhQFRYoXBKHMdKMb

I do not see anything troubling. The older journalctl read outs are equally bland. Do you have any advice on how to proceed?

you are viewing a single comment's thread
view the rest of the comments
[–] deviceshelf@lemmy.world 2 points 1 day ago (1 children)

The bland logs are themselves a data point. If the journal just stops mid-line with nothing unusual before it, that points at a hard hang or a power cut rather than something userspace did, because a kernel oops normally leaves a trace behind. There's also a catch-22 in the SD theory: a card that's failing can't reliably write the log that would prove it's failing.

Two things worth doing before the card swap, both cheap. Check vcgencmd get_throttled: bit 16 stays set if undervoltage happened at any point since boot, so you get an answer on power-versus-card without having to catch the crash live. And switch on the hardware watchdog, bcm2835_wdt plus RuntimeWatchdogSec in systemd, so the Pi resets itself instead of waiting for someone to pull the plug. That doesn't fix the cause, but it stops every crash from becoming an outage that lasts until you're back home.

[–] ISOmorph@feddit.org 1 points 1 day ago

I wasn't aware of a hardware watchdog, thank you very much for that. It's now turned on and the new SD card has been active since yesterday without hiccups.