SSH cannot login , remote system say /bin/bash: no such file or directory

Hello

I was working on a remote server with centos 5. Trying to re-install glib
an
after it showed /bin/bash: bad interpreter

I logged out of the server and when I try to login, I get connected for
secon
and immediately get disconnected

[suppor@server ~]$ ssh -vv user@remoteserve
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 200
debug1: Reading configuration data /etc/ssh/ssh_confi
debug1: Applying options for
debug2: ssh_connect: needpriv
debug1: Connecting to 192.168.10.55 [192.168.10.55] port 22
debug1: Connection established
debug1: identity file /home/suppor/.ssh/identity type -
debug1: identity file /home/suppor/.ssh/id_rsa type -
debug2: key_type_from_name: unknown key type '-----BEGIN
debug2: key_type_from_name: unknown key type '-----END
debug1: identity file /home/suppor/.ssh/id_dsa type
debug1: loaded 3 key
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.
debug1: match: OpenSSH_4.3 pat OpenSSH
debug1: Enabling compatibility mode for protocol 2.
debug1: Local version string SSH-2.0-OpenSSH_4.
debug2: fd 3 setting O_NONBLOC
debug1: SSH2_MSG_KEXINIT sen
debug1: SSH2_MSG_KEXINIT receive
debug2: kex_parse_kexinit

diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha
debug2: kex_parse_kexinit: ssh-rsa,ssh-ds
debug2: kex_parse_kexinit

aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-(E-Mail Removed),aes128-ctr,aes192-ctr,aes256-ct
debug2: kex_parse_kexinit

aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-(E-Mail Removed),aes128-ctr,aes192-ctr,aes256-ct
debug2: kex_parse_kexinit

hmac-md5,hmac-sha1,hmac-ripemd160,hmac-(E-Mail Removed),hmac-sha1-96,hmac-md5-9
debug2: kex_parse_kexinit

hmac-md5,hmac-sha1,hmac-ripemd160,hmac-(E-Mail Removed),hmac-sha1-96,hmac-md5-9
debug2: kex_parse_kexinit: none,(E-Mail Removed),zli
debug2: kex_parse_kexinit: none,(E-Mail Removed),zli
debug2: kex_parse_kexinit
debug2: kex_parse_kexinit
debug2: kex_parse_kexinit: first_kex_follows
debug2: kex_parse_kexinit: reserved
debug2: kex_parse_kexinit

diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha
debug2: kex_parse_kexinit: ssh-rsa,ssh-ds
debug2: kex_parse_kexinit

aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-(E-Mail Removed),aes128-ctr,aes192-ctr,aes256-ct
debug2: kex_parse_kexinit

aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-(E-Mail Removed),aes128-ctr,aes192-ctr,aes256-ct
debug2: kex_parse_kexinit

hmac-md5,hmac-sha1,hmac-ripemd160,hmac-(E-Mail Removed),hmac-sha1-96,hmac-md5-9
debug2: kex_parse_kexinit

hmac-md5,hmac-sha1,hmac-ripemd160,hmac-(E-Mail Removed),hmac-sha1-96,hmac-md5-9
debug2: kex_parse_kexinit: none,(E-Mail Removed)
debug2: kex_parse_kexinit: none,(E-Mail Removed)
debug2: kex_parse_kexinit
debug2: kex_parse_kexinit
debug2: kex_parse_kexinit: first_kex_follows
debug2: kex_parse_kexinit: reserved
debug2: mac_init: found hmac-md
debug1: kex: server->client aes128-cbc hmac-md5 non
debug2: mac_init: found hmac-md
debug1: kex: client->server aes128-cbc hmac-md5 non
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sen
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROU
debug2: dh_gen_key: priv key bits set: 128/25
debug2: bits set: 539/102
debug1: SSH2_MSG_KEX_DH_GEX_INIT sen
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPL
debug1: Host '192.168.10.55' is known and matches the RSA host key
debug1: Found key in /home/suppor/.ssh/known_hosts:
debug2: bits set: 489/102
debug1: ssh_rsa_verify: signature correc
debug2: kex_derive_key
debug2: set_newkeys: mode
debug1: SSH2_MSG_NEWKEYS sen
debug1: expecting SSH2_MSG_NEWKEY
debug2: set_newkeys: mode
debug1: SSH2_MSG_NEWKEYS receive
debug1: SSH2_MSG_SERVICE_REQUEST sen
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /home/suppor/.ssh/identity ((nil))
debug2: key: /home/suppor/.ssh/id_rsa ((nil))
debug2: key: /home/suppor/.ssh/id_dsa (0x92caea0)
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found

debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found

debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found

debug2: we did not send a packet, disable method
debug1: Next authentication method: publickey
debug1: Trying private key: /home/suppor/.ssh/identity
debug1: Trying private key: /home/suppor/.ssh/id_rsa
debug1: Offering public key: /home/suppor/.ssh/id_dsa
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug2: we did not send a packet, disable method
debug1: Next authentication method: password
user@remoteserver's password:
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 0
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug2: channel 0: request env confirm 0
debug2: channel 0: request shell confirm 0
debug2: fd 3 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 2097152
Last login: Fri Feb 11 15:27:11 2011 from crshost
/bin/bash: No such file or directory
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> closed
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug2: channel 0: rcvd close
debug2: channel 0: close_read
debug2: channel 0: input open -> closed
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
Connection to remoteserver closed.
debug1: Transferred: stdin 0, stdout 0, stderr 37 bytes in 0.0 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 7557.3
debug1: Exit status 1

I noticed the line '/bin/bash:no such file or directory" when
disconnecting. Is that the cause of the problem. Please help.

shashi <(E-Mail Removed)> writes:
> I was working on a remote server with centos 5. Trying to re-install
> glibc and after it showed /bin/bash: bad interpreter.
[...]
> I noticed the line '/bin/bash:no such file or directory&quot; when
> disconnecting. Is that the cause of the problem. Please help.

You broke your glibc installation. Time to restore from backups using a
rescue disk, or reinstall.

--
http://www.greenend.org.uk/rjk/

Richard Kettlewell wrote on 02/11/2011 11:01 ET
> shashi writes
>> I was working on a remote server with centos 5. Trying to re-instal
>> glibc and after it showed /bin/bash: bad interpreter
>>
>>
> [...
>> I noticed the line '/bin/bash:no such file or directory&amp;quot; whe
>> disconnecting. Is that the cause of the problem. Please help
>>
>>
>>
> You broke your glibc installation. Time to restore from backups using
> rescue disk, or reinstall
>
> http://www.greenend.org.uk/rjk
>
Thank you very much for the response

Do I have to just boot up the system in rescue mode and re-install the glib
using 'yum' command
Or is there any other way to do this. Please tell me how to do this

Thanks

>> shashi writes:
>>> I was working on a remote server with centos 5. Trying to re-install
>>> glibc and after it showed /bin/bash: bad interpreter.

> Richard Kettlewell wrote on 02/11/2011 11:01 ET :
>> You broke your glibc installation. Time to restore from backups
>> using a rescue disk, or reinstall.

shashi <(E-Mail Removed)> wrote:
> Do I have to just boot up the system in rescue mode and re-install
> the glibc using 'yum' command.

It's highly unlikely you'll be able to restart your system. (In fact
it's quite probable that it won't shut down cleanly, either.) Instead,
you have to do what RK suggested, and boot from a rescue disk. This is
not rescue mode on your existing installation, this is a CD/DVD or USB
stick that can be booted in rescue mode. Your installation disk (or a
recent downloadable one will probably have a rescue mode.

Chris

On Feb 11, 7:54*am, shashi <sha...@domain-xyz.in> wrote:

> *I was working on a remote server with centos 5. *Trying to re-install glibc
> and
> *after it showed /bin/bash: bad interpreter.
>
> *I logged out of the server and when I try to login, I get connected for a
> second
> *and immediately get disconnected.

Here's a valuable lesson: If there's any chance at all you might have
screwed up a system, DO NOT LOG OUT until you 100% confirm you can LOG
BACK IN!

DS

David Schwartz wrote on 02/13/2011 23:24 ET
> On Feb 11, 7:54&nbsp;am, shashi wrote
>
>> &nbsp;I was working on a remote server with centos 5. &nbsp;Trying t
>> re-install glib
>> an
>> &nbsp;after it showed /bin/bash: bad interpreter
>>
>> &nbsp;I logged out of the server and when I try to login, I get connecte
fo
>>
>> secon
>> &nbsp;and immediately get disconnected
>>
>>
>>
> Here's a valuable lesson: If there's any chance at all you might hav
> screwed up a system, DO NOT LOG OUT until you 100% confirm you can LO
> BACK IN
>
> D
>
Thank you for all your responses..

I will boot using centos bootable usb to find rescue image and will instal
th
glibc* packages. hope everything goes well...