I need to login to a system that went into a read-only state. I can ping it just fine but I can't ssh in anymore. Is there some special command line flag/parameter I can pass ssh that lets me login into a system that has gone into read-only mode?
Forgot to add the exact connection error:
OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 192.168.0.4 [192.168.0.4] port 22. debug1: Connection established. debug1: identity file /home/username/.ssh/identity type -1 debug1: identity file /home/username/.ssh/identity-cert type -1 debug1: identity file /home/username/.ssh/id_rsa type -1 debug1: identity file /home/username/.ssh/id_rsa-cert type -1 debug1: identity file /home/username/.ssh/id_dsa type -1 debug1: identity file /home/username/.ssh/id_dsa-cert type -1 ssh_exchange_identification: Connection closed by remote host
I should add that ping is pretty robust to that box:
ping 192.168.0.4 PING 192.168.0.4 (192.168.0.4) 56(84) bytes of data. 64 bytes from 192.168.0.4: icmp_seq=1 ttl=64 time=0.662 ms 64 bytes from 192.168.0.4: icmp_seq=2 ttl=64 time=0.088 ms 64 bytes from 192.168.0.4: icmp_seq=3 ttl=64 time=0.089 ms
/tmp, can't make new
lastlogentries, and so on. In brief, unless the
sshserver has been configured to allow completely footprintless logins to a normally-working system, I think it would be highly-remiss of it to allow logins when those footprints can't be laid down - and even more of a security disaster to have a special flag that allowed the client to request such silent operation!
telnet 192.168.0.4 22?
lastlogmight happen within the
sshdprocess, but I don't think a failure to update those would prevent a login.