On Wed, Jun 17, 2015 at 02:56:46PM -0400, Gary Dale wrote: > You can ping but not ssh. This suggests that services are not being started. > dmesg confirms this as nothing is showing up after the network is brought > up.
Hmm, no. My system has ssh running but there are no traces of ssh in dmesg at all. dmesg is only about kernel messages. ssh is "userspace" and it's logged elsewhere (for example, auth.log) My crazy ideas about what this could be: * A wrong /etc/fstab (systemd is picky about wrong lines in fstab). * Trying to use ssh with password with the user root after /etc/ssh/sshd_config has been updated to allow only public key. If the user is able to boot into rescue mode, adding a suitable /root/.ssh/authorized_keys should be easy. > Since this seems to be a virtual machine, hooking up a monitor won't work. > [...] Well, the cloud providers I've tested allow you to use a serial console where you can log into the system and use "journalctl" to see what happened, even if eth0 is down. I would try that. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150617202111.ga16...@cantor.unex.es
