I’m experiencing problems ssh-ing into a headless Nano.
I’ve got a four node cluster (https://twitter.com/Grady_Booch/status/1390755224638218240/photo/1) running Kubernetes. Jet Pack 4.5.1 pretty much broke everything :-( so I’ve been rebuilding my stack from scratch.
These are all headless nodes, made so this way (I’ll explain the commands in <> in a moment):
<sudo systemctl set-default multi-user.target> sudo reboot now
I’ve successfully configured one of the boards, but the second one - even though I’m configuring it identically - fails in a strange way.
Specifically, on the first board, I can connect via ssh upon boot. On the second board, however, the ssh service never starts UNLESS I FIRST login in to tty1…and then the service starts immediately.
Now, I tried to purge the display manager, since I don’t need it to run headless, using these commands on both boards:
sudo systemctl stop gdm3 sudo systemctl disable gdm3 <sudo systemctl set-default multi-user.target> sudo apt remove --purge ubuntu-desktop gdm3 sudo apt purge libreoffice* sudo reboot now
If I do all of these on the first board, no problem: upon boot, I can ssh in directly. However, on the second board…the ssh service never starts. IF I don’t carry out the command in <>, I CAN start ssh into the second board (even though there is no graphical display manager running).
(am about to try boards 3 and 4, and see what happens next)