My Pi3B+ not reachable

Hi,
For some reason today my Pi3B+ on which I have Home Assistant (using Rasbian and Docker) installed was not reachable. I was able to ping the device from the internal network, but was not able to use HTTPS and SSH.

Since I am using this device for security purposes any hits of what have been the issue?
And is there a way to reset the device automatically once it detects there is something wrong?

thanks!

Are you running Home Assistant on an SD card, and if so, for how long? If you’re not able to reboot your pi via SSH or other means, you might need to pull the power to force a reboot. This of course comes with the risk of data corruption, but it might be the only way.

Hi Tediore,
Thanks for the reply, you are right I have missing info.
I am running HA on an SSD (using a SATA to USB cable), and the only way to solve the problem was to power reset the Pi.

At this stage I would like to know what caused this (maybe through some logs) to avoid to occur again

Odd. What version of Home Assistant are you running?

Were you still able to access the Pi over SSH?

Hi Tediore, I am using Home Assistant v0.100.3, ontop Raspbian GNU/Linux 9 (stretch), but I dont think the issue was with HA

Hi Codec303, no I was not able to login through SSH

I have had it a few times before. Not with HA, but with my mosquitto/pihole pi. Able to ping it, but nothing responding and not able to ssh. Replacing the power supply solved it. (And that pi had been running stable on the old power supply for over 2 years ! )

that’s very strange though!
do you know other people with same issue?

That’s pretty odd, I guess you already have SSH turn on if you’re on Raspbian? I know it’s off by default now.

Usually if something is acting odd I can SSH in and reboot.

There is some sort of hardware watchdog in the RPi, I’ve not really had issues like this however so have never tried it out.

very odd … it has been working for a couple of months now (i.e. this is not a new install)

happened again today … Pi is pingable but not reachable through SSH.
Any idea of what this could be?

happened again … this time I was monitoring the RAM … could this be related?
3 days graph attached