Debian SSH Login Issue
I'm dealing with a client network that has had 4 or 5 under qualified or under paid (stopped showing up because of non-payment) consultants pour through the servers. My goal is to take all of their existing environment and move it into a new VMWare environment. There are a variety of hardware failures showing up on the NAS they are using so all help is appreciated.
Long story short (tldr) is a battery backup died, the owner plugged the servers right into the outlets in their office. The room had power issues, the servers that ran their business stopped booting. The environment consisted of two Debian Linux servers talking to a Promise NAS over iSCSI. One was a vserver box the other a file server. Nothing is documented.
The long story for those who want to read, assuming it might be helpful to better understand that I'm flying blind.
Consultant 1 comes in and sells them a new server (SuperMicro) that is setup as a new Linux vserver box to boot the clients apps and a used Sun Server that will be setup the clients Friend (Friend 1). Consultant 1 is new to sys admin work (less than 2 years experience) and only succeeds in getting one of the servers operational. Consultant 1 walks out because he's unable to complete the job.
Consultant 2 comes into the picture. Consultant 2 recommends a new server, the client goes out and purchases something less expensive without adhering to the recommendations. Consultant 2 sets it up as a Debian server running X11, Oracle Virtual Box and as a File Server. Consultant 2 then configures public ip addresses onto the Consultant 2 walks out because of payment issues.
I'm here now. The clients billing app is still down, its been months, we take a retainer.
The first Debian box that runs vserver doesn't want to let me login with SSH. I have root access from the physical terminal but I need to be able to SSH in for me to run the VMWare Converter.
This is the output from my attempts:
To view the sshd_config you will need to view a video I captured of the screen.
http://cl.ly/3Z261Y0h3X13
Long story short (tldr) is a battery backup died, the owner plugged the servers right into the outlets in their office. The room had power issues, the servers that ran their business stopped booting. The environment consisted of two Debian Linux servers talking to a Promise NAS over iSCSI. One was a vserver box the other a file server. Nothing is documented.
The long story for those who want to read, assuming it might be helpful to better understand that I'm flying blind.
Consultant 1 comes in and sells them a new server (SuperMicro) that is setup as a new Linux vserver box to boot the clients apps and a used Sun Server that will be setup the clients Friend (Friend 1). Consultant 1 is new to sys admin work (less than 2 years experience) and only succeeds in getting one of the servers operational. Consultant 1 walks out because he's unable to complete the job.
Consultant 2 comes into the picture. Consultant 2 recommends a new server, the client goes out and purchases something less expensive without adhering to the recommendations. Consultant 2 sets it up as a Debian server running X11, Oracle Virtual Box and as a File Server. Consultant 2 then configures public ip addresses onto the Consultant 2 walks out because of payment issues.
I'm here now. The clients billing app is still down, its been months, we take a retainer.
The first Debian box that runs vserver doesn't want to let me login with SSH. I have root access from the physical terminal but I need to be able to SSH in for me to run the VMWare Converter.
This is the output from my attempts:
mactopgo:.ssh myname$ ssh -v root@192.168.10.72
OpenSSH_5.9p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: Connecting to 192.168.10.72 [192.168.10.72] port 22.
debug1: Connection established.
debug1: identity file /Users/myname/.ssh/id_rsa type -1
debug1: identity file /Users/myname/.ssh/id_rsa-cert type -1
debug1: identity file /Users/myname/.ssh/id_dsa type -1
debug1: identity file /Users/myname/.ssh/id_dsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-5
debug1: match: OpenSSH_5.1p1 Debian-5 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA 98:9b:3d:71:5f:a6:35:a7:50:e6:2f:08:30:63:0f:f1
The authenticity of host '192.168.10.72 (192.168.10.72)' can't be established.
RSA key fingerprint is 98:9b:3d:71:5f:a6:35:a7:50:e6:2f:08:30:63:0f:f1.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.10.72' (RSA) to the list of known hosts.
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/myname/.ssh/id_rsa
debug1: Trying private key: /Users/myname/.ssh/id_dsa
debug1: Next authentication method: password
root@192.168.10.72's password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
root@192.168.10.72's password: To view the sshd_config you will need to view a video I captured of the screen.
http://cl.ly/3Z261Y0h3X13
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I resolved the issue before the community could assist.
Strange :)
The first issue is getting you logged in over SSH.
Google 'setting up SSH for authentication using PAM'
Next pick the best box - or use both if needed.
Check the spec on the software to see what it will run under and what other requirements it has (like databases).
Install that and then get it running.
Do I get a retainer fee ? :)