Bad 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 protocol error bad mode more about Stack Overflow the company Business Learn more about hiring developers or posting scp protocol error bad mode ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community protocol error bad pack header 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 push results in fatal: protocol error: bad line length fatal protocol error bad line length character character: This up vote 24 down vote favorite 4 I am trying 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
Fatal: Protocol Error: Bad Line Length Character: Git@
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 >= 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 mor
Support Search GitHub This repository Watch 49 Star 269 Fork 134 andyedinborough/aenetmail Code Issues 80 Pull requests 2 Projects 0 Wiki Pulse Graphs New issue Exchange 2003 responds with BAD Protocol Error:
Fatal Protocol Error Bad Line Length Character Pass
"Invalid key supplied in the SEARCH command" with SearchCriteria SentBefore #109 Open swhitlock fatal: protocol error: bad line length character: logi opened this Issue Nov 21, 2012 · 7 comments Projects None yet Labels None yet Milestone No milestone Assignees No one fatal: protocol error: bad line length character: http://stackoverflow.com/questions/22314298/git-push-results-in-fatal-protocol-error-bad-line-length-character-this SENTBEFORE "21-Sep-2012 12:00:00 -04" Here is the response: xm004 BAD Protocol Error: "Invalid key supplied in the SEARCH command". Here's a full post of the entire exchange: xm001 LOGIN "xyz" "lkasjflkjasflkjksl" xm001 OK LOGIN completed. xm002 CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 IDLE LOGIN-REFERRALS MAILBOX-REFERRALS NAMESPACE LITERAL+ UIDPLUS CHILDREN xm003 SELECT "INBOX" * 20 EXISTS xm004 UID SEARCH SENTBEFORE "21-Sep-2012 12:00:00 -04" xm004 BAD Protocol Error: "Invalid key supplied in the https://github.com/andyedinborough/aenetmail/issues/109 SEARCH command". swhitlock commented Nov 21, 2012 In the routine ImapClient.Search(string criteria, bool uid = true), I put this hack in just to test: string command = tag + isuid + "SEARCH " + criteria; command = command.Replace("\"21-Sep-2012 12:00:00 -04\"", "\"21-Sep-2012\""); // HACK string response = SendCommandGetResponse(command); When I did that, it seemed to work correctly. swhitlock commented Nov 21, 2012 I did find one likely bug, though fixing it doesn't fix this problem I'm having. Here's the current GetRFC2060Date function: internal static string GetRFC2060Date(this DateTime date) { return date.ToString("dd-MMM-yyyy hh:mm:ss zz", _enUsCulture); } Note that the "hh" used for displaying the Hour only gives you "The hour, using a 12-hour clock from 01 to 12.". The correct format string should use "HH": "The hour, using a 24-hour clock from 00 to 23.". swhitlock commented Nov 21, 2012 According to RFC3501 section 6.4.4: SENTBEFORE
Start here for a quick overview of the site Help Center Detailed answers to any http://serverfault.com/questions/334726/verify-imap-pop3-connection-to-microsoft-exchange-server-5-5 questions you might have Meta Discuss the workings and policies https://bugzilla.mozilla.org/show_bug.cgi?id=357284 of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for protocol error system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Verify IMAP/POP3 connection to Microsoft Exchange Server 5.5 up vote 1 down vote favorite I wanted to protocol error bad fully explore IMAP connections from the command line, if I can connect via Thunderbird, then I should be able to via telnet?! Microsoft detail IMAP login as :- LOGIN NTDOMAIN/NTACCOUNT/ALIAS PASSWORD The settings in my Thunderbird are :- did not succeed ... Protocol Error: "Unidentifiable command specified" to two commands, "getacl" and "myrights". Mirapoint Proxy looks to return ACL even though real MAP server doesn't return ACL. Summary: Pointless IMAP protocol error alerts, "The current command did not succeed ..... Status: NEW Whiteboard: Keywords: Product: Thunderbird Classification: Client Software Component: General (show other bugs) Version: Trunk Platform: All All Importance: -- minor (vote) TargetMilestone: --- Assigned To: Nobody; OK to take it and work on it QA Contact: TriageOwner: Mentors: URL: Depends on: 564642 Blocks: Show dependency tree /graph Reported: 2006-10-19 08:36 PDT by Kenneth Herron Modified: 2011-02-22 03:42 PST (History) CC List: 6 users (show) Bruno.Harbulot jwalden+bmo m-wada shopik terry vseerror See Also: Crash Signature: (edit) QA Whiteboard: Iteration: --- Points: --- Tracking Flags: Attachments Sample protocol log (101.83 KB, text/plain) 2006-10-19 08:38 PDT, Kenneth Herron no flags Details Sample alert (8.55 KB, image/gif) 2006-10-19 08:39 PDT, Kenneth Herron no flags Details View All Add an attachment (proposed patch, testcase, etc.) Description Kenneth Herron 2006-10-19 08:36:55 PDT I first experienced this with TB 1.5.0.x. I've just updated to a nightly trunk build and it still occurs. For my corporate email I connect to a Mirapoint IMAP proxy which connects to a backend server. The backend was migrated a few months ago to MS Exchange. Since then, every time TB accesses a folder--including inbox--for the first time after being started, I get two annoying modal alerts about IMAP protocol errors. Typical behavior is as follows: 1) Start TB. It displays a (cached?) copy of my IMAP folder list and a (cached) list of INBOX messages in the message list. Then an alert