Comment on Local homeserver suddenly not responsive to SSH but can be pinged
dhork@lemmy.world 10 hours ago
This can sometimes happen if the filesystem has failed or is otherwise inaccessible. SSH needs to read config files and if it can’t, it fails to connect. It would try to write a failure to the log, but can’t.
Things that don’t require filesystem access, and can run totally from processes in memory interacting with hardware, would be fine. So your Ethernet stack works, and so does ping. A serial port would probably work. SNMP would work, too, for anything that doesn’t need to get a metric from the filesystem. I bet if you had a remote syslog server, you would get the logs that are falling out of your filesystem.
I think you might onto something with the filesystem. I am using Hd-idle to switch off the HDD when not in use. It was of course in use the entire time during this, but I noticed in the logs that it came up multiple times as “assuming disk spun up after long sleep” even though it hadn’t been off at all.
Only saw this after I made my post and I cannot make sense of it, but I have never seen this message otherwise, it only happened during this period of not being able to access the server.
Zwuzelmaus@feddit.org 7 hours ago
I have also seen a situation where ssh did not accept a connection anymore when the disk was full.