[Solved] ssh debug1: Exit status 254 problem

Hello;

Am experiencing odd problem with ssh:

=========

ssh -vvv remote_host
:
:
debug2: channel 0: rcvd adjust 65536
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
debug2: channel 0: rcvd eow
debug2: channel 0: close_read
debug2: channel 0: input open -> closed
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: rcvd close
debug3: channel 0: will not send data after close
Last   successful login for mgmt: Tue Oct 18 00:00:01 EST5EDT 2011
Last unsuccessful login for mgmt: Sun Jul 10 03:51:04 EST5EDT 2011
Last login: Wed Oct 19 08:15:23 2011 from fidsrv.dataphile.broadridge.com
debug3: channel 0: will not send data after close
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> 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
debug3: channel 0: status: The following connections are open:
  #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cfd -1)

debug3: channel 0: close_fds r -1 w -1 e 6 c -1
Connection to fidfosrv closed.
Transferred: sent 2496, received 2536 bytes, in 247.6 seconds
Bytes per second: sent 10.1, received 10.2
debug1: Exit status 254

===================

What might cause this ??
Any advice is appreciated, thank you

---------- Post updated at 11:11 AM ---------- Previous update was at 09:56 AM ----------

problem solved

I suspect it was a bad shell setting, but it'd be nice to know for sure. Nothing's more annoying than searching for something and finding the question, not the answer.

I follow Corona here, the forum is for the good of all and you accepted the rules, you are also to share, if your problem is solved then you can also share the solution it is the least you can do after asking some help knowing that fellows will be giving their time to help you solve your issue.

found the fix

turned out to be the inconsistent password problem under /tcb/files/auth/first-letter-of-username

Under there, there were username and "username-t" files

deleted "username-t" file and the problem went away

Hope this helps someone

Cheers !!

I can now change the status to solved knowing the solution is given...