Fatal Protocol Error
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
Fatal Protocol Error Bad Line Length Character Pass
Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs fatal: protocol error: bad line length character: git@ Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, fatal: protocol error: bad line length character: logi just like you, helping each other. Join 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
Fatal Protocol Error Bad Line Length Character Do
to get GitLab working on my server (running CentOS 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
Fatal Protocol Error Bad Line Length Character Gitlab
user? ... yes Checking Environment ... Finished Checking GitLab Shell ... GitLab Shell version >= 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
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the fatal: protocol error: bad line length character: unab workings and policies of this site About Us Learn more about Stack
Heroku Fatal: Protocol Error: Bad Line Length Character: Erro
Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs git protocol error bad line length character git@ Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join http://stackoverflow.com/questions/22314298/git-push-results-in-fatal-protocol-error-bad-line-length-character-this them; it only takes a minute: Sign up fatal: protocol error: bad line length character: [-] up vote 1 down vote favorite 1 in Git Bash (Windows XP) an error occurs permanent [-] mapping_data_source::init error: file not found. But earlier it wasn't cause of other errors. Now I'm trying to clone my repositorie and get errors: $ git clone hello http://stackoverflow.com/questions/33947422/fatal-protocol-error-bad-line-length-character cloned_hello [-] mapping_data_source::init error: file not found Cloning into 'cloned_hello'... fatal: protocol error: bad line lengt character: [-] fatal: write error: Invalid argument And without "_" $ git clone hello clonedhello [-] mapping_data_source::init error: file not found Cloning into 'clonedhello'... fatal: protocol error: bad line length character: [-] fatal: The remote end hung up unexpectedly git github-for-windows share|improve this question edited Nov 28 '15 at 22:26 asked Nov 26 '15 at 21:43 Drew 62 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote That can happen when you have a .profile or .bashrc in $HOME (in your Windows bash session) which does some echo (which is not silent) To test that, check if the issue persists when you try and clone from a CMD session instead of a bash session (call c:\path\to\PortableGit-2.6.3-64-bit\git-cmd.exe to open such a session) share|improve this answer answered Nov 27 '15 at 5:38 VonC 626k19018011887 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using F
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 http://stackoverflow.com/questions/28290596/git-on-windows-fatal-protocol-error-bad-line-character About Us Learn more about Stack Overflow the company Business Learn more https://forum.gitlab.com/t/fatal-protocol-error-bad-line-length-character-no-s/347 about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up git on Windows: protocol error fatal: protocol error: bad line character: @- up vote 3 down vote favorite 1 I was using SourceTree + Git on Windows without any problem. I was able to use git commands from command (terminal/BASH). I prefer to use terminal for git push/pull etc. Unfortunately, after reinstallation of my machine (server/git are the same), I'm getting this painful error. On a new machine, I installed bad line length Git 1.9.5 (Git-1.9.5-preview20141217.exe) and configured to use BASH only and plink with proper SSH key file. I can do git log on my repository, but git pull or git push gives this error: me@NEW-MACHINE /c/Workspace/project (master) $ git pull fatal: protocol error: bad line length character: @- ERROR: Problem parsing the command line arguments. Of course, I searched many articles related to "fatal: protocol error: bad line length character". But, couldn't find any clue. Interestingly, on SourceTree, I can do git pull or push successfully. I'm only getting this error in BASH terminal. Note that SourceTree doesn't use embedded git. Here are my investigations so far: I installed an older version of git (1.8.x), still getting error. Moved .bashrc, but no good. Obviously, not a problem of SourceTree as SourceTree doesn't use embedded Git. The server is in Github (enterprise, private). I have no problem using any git commands on my Linux with the same git repository/server. My clue is
s Does anyone have some suggestions on how to troubleshoot this? axil 2015-03-10 06:29:26 UTC #2 Is this a private repo? Can you post the link to reproduce maybe? etc 2015-03-10 12:59:50 UTC #3 Yes, it was a private repo on gitlab.com. I believe we moved it to another group, and it seemed to work fine, so I'm not sure if it was just a fluke or what. bhagwatchouhan 2015-05-06 05:45:17 UTC #4 We face this error when we have access lower than Developer. We must have access level set to at least Dev. axil 2015-05-06 07:25:39 UTC #5 bhagwatchouhan: We face this error when we have access lower than Developer. We must have access level set to at least Dev. Is this on gitlab.com or on your hosted instance? hectorlee369 2015-05-07 15:41:10 UTC #6 I got the same error "Fatal: protocol error: bad line length character: No s" when I tried to push to other user created project on our hosted instance. The project is an internal repo and I can pull it to my client.Then I add member in the project and set project access as Master, everything is fine. Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled What is GitLab? Try it! Download It! Blog Docs