Mailing List Archive: authenticated, but no prompt

authenticated, but no prompt

Jul 17, 2009, 11:52 AM

Post #1 of 5 (7008 views)

Hello,

until this morning I was able to ssh from my ubuntu client to my fedora
core 9 server. suddenly (without any config change on the server or the
client), I couldn't ssh anymore: I could still enter the password,
authentication seems to be ok, but no shell prompt :-(

so I am wondering what's going on here. since it is difficult to
physically access the machine, I would be very happy to receive a
suggestion for a workaround.

below is the last part of the ssh -vvv output (I replaced the real
machine name by mymachine.mydomain)

I can still ssh to other servers from my client.

cheers,
dirk

debug1: Next authentication method: password
dirk@mymachine.mydomain's password:
debug3: packet_send2: adding 64 (len 58 padlen 6 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Entering interactive session.
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
#0 client-session (t3 r-1 i0/0 o0/0 fd 4/6 cfd -1)

debug3: channel 0: close_fds r 4 w 6 e 7 c -1
Read from remote host mymachine.mydomain: Connection reset by peer
Connection to mymachine.mydomain closed.
debug1: Transferred: stdin 0, stdout 0, stderr 110 bytes in 0.0 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 4537.2
debug1: Exit status -1

Re: authenticated, but no prompt [ In reply to ]

remo at italy1

Jul 20, 2009, 11:05 AM

Post #2 of 5 (6826 views)

Permalink

I bet the machine is overloaded.. That's why you do not get a shell.. You
need to wait to come down ... Not sure if it got hacked ....

My 2 cents.

Remo

On 7/17/09 12:52 PM, "dirk ooms" <dirk@onesparrow.com> wrote:

> Hello,
>
> until this morning I was able to ssh from my ubuntu client to my fedora
> core 9 server. suddenly (without any config change on the server or the
> client), I couldn't ssh anymore: I could still enter the password,
> authentication seems to be ok, but no shell prompt :-(
>
> so I am wondering what's going on here. since it is difficult to
> physically access the machine, I would be very happy to receive a
> suggestion for a workaround.
>
> below is the last part of the ssh -vvv output (I replaced the real
> machine name by mymachine.mydomain)
>
> I can still ssh to other servers from my client.
>
> cheers,
> dirk
>
> debug1: Next authentication method: password
> dirk@mymachine.mydomain's password:
> debug3: packet_send2: adding 64 (len 58 padlen 6 extra_pad 64)
> debug2: we sent a password packet, wait for reply
> debug1: Authentication succeeded (password).
> debug1: channel 0: new [client-session]
> debug3: ssh_session2_open: channel_new: 0
> debug2: channel 0: send open
> debug1: Entering interactive session.
> debug1: channel 0: free: client-session, nchannels 1
> debug3: channel 0: status: The following connections are open:
> #0 client-session (t3 r-1 i0/0 o0/0 fd 4/6 cfd -1)
>
> debug3: channel 0: close_fds r 4 w 6 e 7 c -1
> Read from remote host mymachine.mydomain: Connection reset by peer
> Connection to mymachine.mydomain closed.
> debug1: Transferred: stdin 0, stdout 0, stderr 110 bytes in 0.0 seconds
> debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 4537.2
> debug1: Exit status -1
>
>
>
> !DSPAM:4a64aee3260209957242535!
>

Re: authenticated, but no prompt [ In reply to ]

sharad2011 at yahoo

Jul 20, 2009, 9:05 PM

Post #3 of 5 (6826 views)

Permalink

Do you check if ssh hostname somecommand works or not? Try to run it with terminal suppression using -T i.e. ssh -T hostname somecommand.

If that works perhaps something wrong with the terminal allocation on the remote side (may they are all utilized? just guessing!) or problem with the shell.

Sharad
--- On Sat, 18/7/09, dirk ooms <dirk@onesparrow.com> wrote:

> From: dirk ooms <dirk@onesparrow.com>
> Subject: authenticated, but no prompt
> To: secureshell@securityfocus.com
> Date: Saturday, 18 July, 2009, 12:22 AM
> Hello,
>
> until this morning I was able to ssh from my ubuntu client
> to my fedora
> core 9 server. suddenly (without any config change on the
> server or the
> client), I couldn't ssh anymore: I could still enter the
> password,
> authentication seems to be ok, but no shell prompt :-(
>
> so I am wondering what's going on here. since it is
> difficult to
> physically access the machine, I would be very happy to
> receive a
> suggestion for a workaround.
>
> below is the last part of the ssh -vvv output (I replaced
> the real
> machine name by mymachine.mydomain)
>
> I can still ssh to other servers from my client.
>
> cheers,
> dirk
>
> debug1: Next authentication method: password
> dirk@mymachine.mydomain's
> password:
> debug3: packet_send2: adding 64 (len 58 padlen 6 extra_pad
> 64)
> debug2: we sent a password packet, wait for reply
> debug1: Authentication succeeded (password).
> debug1: channel 0: new [client-session]
> debug3: ssh_session2_open: channel_new: 0
> debug2: channel 0: send open
> debug1: Entering interactive session.
> debug1: channel 0: free: client-session, nchannels 1
> debug3: channel 0: status: The following connections are
> open:
> #0 client-session (t3 r-1 i0/0 o0/0 fd 4/6 cfd -1)
>
> debug3: channel 0: close_fds r 4 w 6 e 7 c -1
> Read from remote host mymachine.mydomain: Connection reset
> by peer
> Connection to mymachine.mydomain closed.
> debug1: Transferred: stdin 0, stdout 0, stderr 110 bytes in
> 0.0 seconds
> debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr
> 4537.2
> debug1: Exit status -1
>
>
>

Yahoo! recommends that you upgrade to the new and safer Internet Explorer 8. http://downloads.yahoo.com/in/internetexplorer/

Re: authenticated, but no prompt [ In reply to ]

dirk at onesparrow

Jul 21, 2009, 12:30 AM

Post #4 of 5 (6805 views)

Permalink

Hello Sharad and others,

you made my day! i already tried to do ssh as root with the 'reboot'
command, but it didn't work. however when i tried it again with '-T', i
was able to reboot the machine and now i can login again. Still have to
look for the real cause. Anyway, thank you very much!

dirk

On Tue, 2009-07-21 at 09:35 +0530, Sharad wrote:
> Do you check if ssh hostname somecommand works or not? Try to run it with terminal suppression using -T i.e. ssh -T hostname somecommand.
>
> If that works perhaps something wrong with the terminal allocation on the remote side (may they are all utilized? just guessing!) or problem with the shell.
>
> Sharad
> --- On Sat, 18/7/09, dirk ooms <dirk@onesparrow.com> wrote:
>
> > From: dirk ooms <dirk@onesparrow.com>
> > Subject: authenticated, but no prompt
> > To: secureshell@securityfocus.com
> > Date: Saturday, 18 July, 2009, 12:22 AM
> > Hello,
> >
> > until this morning I was able to ssh from my ubuntu client
> > to my fedora
> > core 9 server. suddenly (without any config change on the
> > server or the
> > client), I couldn't ssh anymore: I could still enter the
> > password,
> > authentication seems to be ok, but no shell prompt :-(
> >
> > so I am wondering what's going on here. since it is
> > difficult to
> > physically access the machine, I would be very happy to
> > receive a
> > suggestion for a workaround.
> >
> > below is the last part of the ssh -vvv output (I replaced
> > the real
> > machine name by mymachine.mydomain)
> >
> > I can still ssh to other servers from my client.
> >
> > cheers,
> > dirk
> >
> > debug1: Next authentication method: password
> > dirk@mymachine.mydomain's
> > password:
> > debug3: packet_send2: adding 64 (len 58 padlen 6 extra_pad
> > 64)
> > debug2: we sent a password packet, wait for reply
> > debug1: Authentication succeeded (password).
> > debug1: channel 0: new [client-session]
> > debug3: ssh_session2_open: channel_new: 0
> > debug2: channel 0: send open
> > debug1: Entering interactive session.
> > debug1: channel 0: free: client-session, nchannels 1
> > debug3: channel 0: status: The following connections are
> > open:
> > #0 client-session (t3 r-1 i0/0 o0/0 fd 4/6 cfd -1)
> >
> > debug3: channel 0: close_fds r 4 w 6 e 7 c -1
> > Read from remote host mymachine.mydomain: Connection reset
> > by peer
> > Connection to mymachine.mydomain closed.
> > debug1: Transferred: stdin 0, stdout 0, stderr 110 bytes in
> > 0.0 seconds
> > debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr
> > 4537.2
> > debug1: Exit status -1
> >
> >
> >
>
>
> Yahoo! recommends that you upgrade to the new and safer Internet Explorer 8. http://downloads.yahoo.com/in/internetexplorer/
>

Re: authenticated, but no prompt [ In reply to ]

remo at italy1

Jul 21, 2009, 9:37 AM

Post #5 of 5 (6816 views)

Permalink

Again I would look for cpu utilization..

Ciao

Remo

On 7/21/09 1:30 AM, "dirk ooms" <dirk@onesparrow.com> wrote:

> Hello Sharad and others,
>
> you made my day! i already tried to do ssh as root with the 'reboot'
> command, but it didn't work. however when i tried it again with '-T', i
> was able to reboot the machine and now i can login again. Still have to
> look for the real cause. Anyway, thank you very much!
>
> dirk
>
> On Tue, 2009-07-21 at 09:35 +0530, Sharad wrote:
>> Do you check if ssh hostname somecommand works or not? Try to run it with
>> terminal suppression using -T i.e. ssh -T hostname somecommand.
>>
>> If that works perhaps something wrong with the terminal allocation on the
>> remote side (may they are all utilized? just guessing!) or problem with the
>> shell.
>>
>> Sharad
>> --- On Sat, 18/7/09, dirk ooms <dirk@onesparrow.com> wrote:
>>
>>> From: dirk ooms <dirk@onesparrow.com>
>>> Subject: authenticated, but no prompt
>>> To: secureshell@securityfocus.com
>>> Date: Saturday, 18 July, 2009, 12:22 AM
>>> Hello,
>>>
>>> until this morning I was able to ssh from my ubuntu client
>>> to my fedora
>>> core 9 server. suddenly (without any config change on the
>>> server or the
>>> client), I couldn't ssh anymore: I could still enter the
>>> password,
>>> authentication seems to be ok, but no shell prompt :-(
>>>
>>> so I am wondering what's going on here. since it is
>>> difficult to
>>> physically access the machine, I would be very happy to
>>> receive a
>>> suggestion for a workaround.
>>>
>>> below is the last part of the ssh -vvv output (I replaced
>>> the real
>>> machine name by mymachine.mydomain)
>>>
>>> I can still ssh to other servers from my client.
>>>
>>> cheers,
>>> dirk
>>>
>>> debug1: Next authentication method: password
>>> dirk@mymachine.mydomain's
>>> password:
>>> debug3: packet_send2: adding 64 (len 58 padlen 6 extra_pad
>>> 64)
>>> debug2: we sent a password packet, wait for reply
>>> debug1: Authentication succeeded (password).
>>> debug1: channel 0: new [client-session]
>>> debug3: ssh_session2_open: channel_new: 0
>>> debug2: channel 0: send open
>>> debug1: Entering interactive session.
>>> debug1: channel 0: free: client-session, nchannels 1
>>> debug3: channel 0: status: The following connections are
>>> open:
>>> #0 client-session (t3 r-1 i0/0 o0/0 fd 4/6 cfd -1)
>>>
>>> debug3: channel 0: close_fds r 4 w 6 e 7 c -1
>>> Read from remote host mymachine.mydomain: Connection reset
>>> by peer
>>> Connection to mymachine.mydomain closed.
>>> debug1: Transferred: stdin 0, stdout 0, stderr 110 bytes in
>>> 0.0 seconds
>>> debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr
>>> 4537.2
>>> debug1: Exit status -1
>>>
>>>
>>>
>>
>>
>> Yahoo! recommends that you upgrade to the new and safer Internet
>> Explorer 8. http://downloads.yahoo.com/in/internetexplorer/
>>
>
>
> !DSPAM:4a65e653312254546315325!
>