Protocol Error Bad Line Length Character Remo
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring
Git Clone Fatal Protocol Error Bad Line Length Character
developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask fatal protocol error bad line length character do Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join
Fatal Protocol Error Bad Line Length Character Gitlab
them; it only takes a minute: Sign up Git push results in fatal: protocol error: bad line length character: This up vote 25 down vote favorite 4 I am trying to get GitLab working on my server (running CentOS fatal: protocol error: bad line length character: unab 6.5). I followed the gitlab-receipe to the line, but I just can't get it working. I am able to access the web interface, create new projects but pushing to the master branch returns the following error : fatal: protocol error: bad line length character: This I have done checks on the production environment, here are the results : Checking Environment ... Git configured for git user? ... yes Checking Environment ... Finished Checking GitLab Shell ... GitLab Shell version heroku fatal protocol error bad line length character erro >= 1.7.9 ? ... OK (1.8.0) Repo base directory exists? ... yes Repo base directory is a symlink? ... no Repo base owned by git:git? ... yes Repo base access is drwxrws---? ... yes update hook up-to-date? ... yes update hooks in repos are links: ... ASC / Wiki ... repository is empty Running /home/git/gitlab-shell/bin/check Check GitLab API access: OK Check directories and files: /home/git/repositories: OK /home/git/.ssh/authorized_keys: OK Test redis-cli executable: redis-cli 2.4.10 Send ping to redis server: PONG gitlab-shell self-check successful Checking GitLab Shell ... Finished Checking Sidekiq ... Running? ... yes Number of Sidekiq processes ... 1 Checking Sidekiq ... Finished Checking LDAP ... LDAP is disabled in config/gitlab.yml Checking LDAP ... Finished Checking GitLab ... Database config exists? ... yes Database is SQLite ... no All migrations up? ... yes GitLab config exists? ... yes GitLab config outdated? ... no Log directory writable? ... yes Tmp directory writable? ... yes Init script exists? ... yes Init script up-to-date? ... no Try fixing it: Redownload the init script For more information see: doc/install/installation.md in section "Install Init Script" Please fix the error above and rerun the checks. projects have namespace: ... ASC / Wiki ... yes Projects have satellites? ... ASC / Wiki ... can't create, repository is empty Redis version >= 2.0.0? ... yes Your git bin path is "/usr/bin/git" Git version >= 1.7.10 ? ... yes (1.8.3) Checking GitLab
Sign in Pricing Blog Support Search GitHub This repository Watch 1,019 Star
Git Protocol Error Bad Line Length Character Git@
18,587 Fork 5,080 gitlabhq/gitlabhq Code Issues 1 Pull requests 0 fatal: protocol error: bad line length character: inva Projects 0 Pulse Graphs New issue git pull/push/clone error "fatal: protocol error: bad line
"fatal: Protocol Error: Bad Line Length Character: Usin"
length character: Welc" #6537 Closed renanvaz opened this Issue Mar 15, 2014 · 24 comments Projects None yet Labels None yet Milestone http://stackoverflow.com/questions/22314298/git-push-results-in-fatal-protocol-error-bad-line-length-character-this No milestone Assignees No one assigned 6 participants renanvaz commented Mar 15, 2014 Dear, I have a error in my gitlab instalation, can you help me? I think the error is that the welcome message to the user git on ssh should not be this "Welcome to Ubuntu https://github.com/gitlabhq/gitlabhq/issues/6537 13.10 (GNU / Linux 3.11.0-12-generic x86_64) ..." but I can not say what should be. Info: My SSH keys are added. In my repository: $ git remote add origin ssh://git@gitlab.XXXXX.XX:2222/root/luver-bootstrap.git $ git push origin master fatal: protocol error: bad line length character: Welc Debug: $ ssh -vT git@gitlab.XXXXX.XX -p 2222 OpenSSH_6.2p2 Ubuntu-6ubuntu0.1, OpenSSL 1.0.1e 11 Feb 2013 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to gitlab.XXXXX.XXX [162.XXX.XXX.XX] port 2222. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa type -1 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.2p2 Ubuntu-6ubuntu0.1
Thu, 8 Aug 2013 08:24:02 UTC Severity: important Tags: fixed-upstream, patch, upstream Found in https://bugs.debian.org/719069 versions git/1:1.7.2.5-3, git/1:1.7.10.4-1+wheezy1 Fixed in version git/1:1.8.1~rc0-1 Reply or subscribe to this bug. Toggle useless messagesView this report as an mbox folder, status mbox, maintainer https://www.postgresql.org/message-id/1313182388.2094.1.camel@laptop mbox Report forwarded to debian-bugs-dist@lists.debian.org, Gerrit Pape
Regional lists Associations User groups Project lists pgadmin-hackers pgadmin-support pgsql-jdbc pgsql-odbc pgsql-pkg-debian pgsql-pkg-yum psycopg Inactive lists IRC Local User Groups Featured Users International Sites Propaganda Resources Weekly News Re: Weird git messages From: Guillaume Lelarge