Gladys's unexpected nighttime interruptions

Configuration
1

For a few days now, my Gladys instance ‹ crashes › during the night for a period of about 1 to 2 hours. I have quite precise information about the durations because I monitor my instance from the healthcheck.io site. Here are the outages recorded in June:

  • 25/6: Gladys unreachable for 1h26, from 3:47 to 5:13

  • 24/6: 0h49, from 3:56 to 4:45

  • 23/6: 0h22, from 2:49 to 3:11

  • 22/6: 1h32, from 2:51 to 4:23

  • 21/6: 0h56, from 2:44 to 3:40

  • 20/6: 2h03, from 2:19 to 4:22

  • 15/6: 1h01, from 2:10 to 3:11

  • 14/6: 0h18, from 3:56 to 4:14

  • 3/6: 0h16, from 0:51 to 1:15

And these correspond to Gladys stopping (and not a network outage or a Healthchecks issue), because I have the line « Gladys just restarted » in Telegram, and without the new version info (I did get them for the transitions to v4.77, 4.78, 4.79, and 4.80, but I excluded them from what I listed above).

Any idea where this could be coming from? Or how to find the cause?

2

Hi @StephaneB :slightly_smiling_face:

Could you download Gladys’s logs in Settings → System and send them to me by email?

Screenshot 2026-06-23 at 19.15.29
Screenshot 2026-06-23 at 19.15.29904×546 33.8 KB

There are several possible scenarios:

  • Either Gladys is restarting.
  • Or the mini-PC itself is restarting.

If it’s the mini-PC, the causes can vary: lack of resources, hardware issue, unstable power supply, power outage, etc. (though for a power outage, I imagine you would have probably noticed :grinning_face_with_smiling_eyes:).

The logs should help us quickly identify what’s happening.

PS: AIs are generally very effective at analyzing this type of problem. You can provide them with the logs and a description of the observed behavior; they sometimes spot interesting leads quite quickly :wink:

3

CPU overheating?