Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
From: drigodwin <git@git.apache.org>
To: dev@brooklyn.apache.org
Reply-To: dev@brooklyn.apache.org
References: <git-pr-102-brooklyn-docs@git.apache.org>
In-Reply-To: <git-pr-102-brooklyn-docs@git.apache.org>
Subject: [GitHub] brooklyn-docs pull request #102: added more to deployment troubleshooting se...
Content-Type: text/plain
Message-Id: <20160830084945.32C87E01D9@git1-us-west.apache.org>
Date: Tue, 30 Aug 2016 08:49:45 +0000 (UTC)
archived-at: Tue, 30 Aug 2016 08:49:47 -0000

Github user drigodwin commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/102#discussion_r76754022
  
    --- Diff: guide/ops/troubleshooting/deployment.md ---
    @@ -143,3 +143,25 @@ start tasks are completed).
     
     See the [overview](overview.html) for where to find additional information, especially the section on
     "Entity's Error Status".
    +
    +## Invalid packet error
    +
    +If you receive an error message similar to the one below when provisioning a Centos VM, you can workaround the issue by explicitly setting the user that AMP should use to login to the VM.
    +
    +`error acquiring SFTPClient() (out of retries - max 50)
    +Invalid packet: indicated length too large
    +java.lang.IllegalStateException
    +Invalid packet: indicated length too large` 
    --- End diff --
    
    This should all be {% highlight bash %} rather than this


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---