0
I cannot access an Ubuntu Server via SFTP. Follow Winscp error:
Received Too large (1919905652 B) SFTP Packet. Max supported Packet The error is typically caused by message printed from startup script (like .profile). The message may start with "root".
I put this line on . bashrc, but the problem remains:
*If not running Interactively, don’t do Anything if [[ $- != i ]]; then Return; fi*
The user-name used nay is root, but rather one randomly generated by the contracted Linux VPS service. I believe it has something to do with this, but I don’t know much about linux.... I can access the server from Putty, with this same random user. Despite this, the prompt displays root@server:/#
here is the contents of . bashrc:
login as: A3Pkxv [email protected]'s password: Last login: Mon May 2
21:59:39 2016 from 199.99.99.99 Could not chdir to home directory
/home/console-Z2MPld: No such file or directory
entered into CT 1918 [email protected]:/# vim ~/.bashrc
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything [ -z "$PS1" ] && return [ -z "$PS1" ] && exit if [[ $- != *i* ]]; then return; fi
# don't put duplicate lines in the history. See bash(1) for more options
# ... or force ignoredups and ignorespace HISTCONTROL=ignoredups:ignorespace
# append to the history file, don't overwrite it shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1) HISTSIZE=1000 HISTFILESIZE=2000
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS. shopt -s checkwinsize
# make less more friendly for non-text input files, see lesspipe(1) [ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
# set variable identifying the chroot you work in (used in the prompt below) if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot) fi
# set a fancy prompt (non-color, unless we know we "want" color) case "$TERM" in
xterm-color) color_prompt=yes;; esac
# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes
if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi fi
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
' else
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ ' fi unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir case "$TERM" in xterm*|rxvt*)
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
;;
*)
;; esac
# enable color support of ls and also add handy aliases if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto' fi
# some more ls aliases alias ll='ls -alF' alias la='ls -A' alias l='ls -CF'
# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases fi
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
#if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
# . /etc/bash_completion
#fi
This is the contents of . profile:
[email protected]:/# vim ~/.profile
~/.profile: executed by Bourne-compatible login shells.
if [ "$BASH" ]; then
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
i
mesg n
As the error message speaks, the error may be in
.profile
or.bashrc
from your server, as you have logged in, these files are uploaded and they may be making print of some message. If possible, display their contents. If you can, for testing purposes, move the contents of.profile
to a backup file or move the contents of.bashrc
to the archive.bash_profile
– user3603
Also check with the server administrators if the protocol
SFTP
is released– user3603
Can you edit your question and use the correct formatting for code? This very confusing your editing, has text along with command and this is not a "normal" content of a
.bashrc
– user3603
Hi, sorry, I just found Ctrl+K.
– Michel
What would be the normal content ? Can I just delete the whole script and try to connect with winscp ? I’m worried about doing this and losing access through Putty...
– Michel
When you opened the . profile using vim it showed this in the terminal
~/.profile: executed by Bourne-compatible login shells.
before opening the file. I believe that when you access via ssh, these files are printing something and this is what is causing your error– user3603
I never used
WinSCP
but there is some option that you can choose to use the protocolSCP
?– user3603