3 ms·
> However I still don't understand your comment about the Linux OOM killer wanting to kill sshd "first" (or _ever_ based on these renewed findings!) Can you ela
by michaelt 6y ago
> However I still don't understand your comment about the Linux OOM killer wanting to kill sshd "first" (or _ever_ based on these renewed findings!) Can you elaborate?
I suspect running low on memory can trigger symptoms that look like sshd failing.
sshd gets paged out (or something else you need for a successful login). Un-paging becomes incredibly slow, as there's lots of IO going on from all the paging. Anything garbage-collected starts running GC constantly, using 100% CPU.
Then your attempt to SSH times out - and with no access to list running processes, one naturally concludes sshd has failed.
- boulos 6y agoYeah, maybe in addition to my survivorship bias from RHEL6-era images, I am mentally conflating samples from “we OOM killed sshd” and “we are swapping violently; we won’t get in via sshd”. In fact, I would guess (especially given all this investigation!) that it’s much more likely that an inaccessible box is just under too much memory pressure for sshd to respond. Amusingly, the answer is still the same: serial port! :). Thanks again for all the pointers (to everyone in this thread).