I tried the solution, did not work though. Earlier I had also tried by
putting
/usr/local/libexec in the PATH before starting the sshd without any
success.
This was not my case (since I don't have any command in my .profile or
.cshrc), but FYI...
http://info.nccs.gov/faq
==================================================
File transfer server could not be started or it exited unexpectedly.
Exit value 0 was returned. Most likely the sftp-server is not in the path
of the user on the server-side.
or
Received message too long 1500476704
These errors are usually caused by commands in a shell run-control file
(.cshrc, .profile, .bashrc, etc.) that produce output to the terminal.
This output interferes with the communication between the SSH daemon and
the sftp-server subsystem. Examples of such commands might be date or
echo. If you use the mail command to check for mail, it can cause the
error, too.
You can check to see if this is likely the problem. If you are unable to
sftp to a machine, try to connect via ssh. If you are able to ssh, and you
receive output to your terminal other than the standard login banner (for
example “You have mail”), then you need to check your run control files
for commands that might be producing the output.
To solve this problem, you should place any commands that will produce
output in a conditional statement that is only executed if the shell is
interactive. For C shell users, a sample test to put in your .cshrc file
would be:
if ($?prompt)
date
endif
The equivalent command for your .profile file (ksh/bash) would be:
if [[ -n $PS1 ]]; then
date
fi
==============================
Regards,
Ben Kim
Developer
http://benix.tamu.edu
