How can I debug an unreachable start9 host? (behaves as if shut down, but is actually running and spinning the vents)

Sometimes my start9 becomes unreachable. Over SSH and over the browser. But the ventilators are still spinning and the host is “up”.

I do the classic “unplug/replug” in that case, but I get that issue 1 or 2 times a week currently and it starts to get annoying. I shut down some services that I do not need all the time, but it didn’t help.

How can I find the culprit of something like that?

Greetings
Tennis

Hi, what hardware are your running StartOS on and what services are you running?

Have you tried working through our Start9 | Common Issues to see if any of them solve your issue?

Asus Nuc 13 Pro

I checked the link but all of those tips are for “making it work again”. I can make it work again by resetting power, but I would like to check where the issue emerged from.

I don’t need support in terms of “please find my issue”, but in terms of “how can one debug a non-reachable start9”, if there would be any option like that. :slight_smile:

I think I would keep an eye on htop, to try and obtain some clues.

When the system becomes unresponsive, after the hard power cycle ssh in, and run:

sudo journalctl -ea > journal_output.txt

To create a log. Let’s take a look at that.

Thanks, I will test that next time, if at home at this time. (y)