You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by aledsage <gi...@git.apache.org> on 2016/07/12 18:55:56 UTC

[GitHub] brooklyn-docs pull request #89: BROOKLYN-218: document nss upgrade to avoid ...

GitHub user aledsage opened a pull request:

    https://github.com/apache/brooklyn-docs/pull/89

    BROOKLYN-218: document nss upgrade to avoid KeyException

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/aledsage/brooklyn-docs BROOKLYN-218

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/brooklyn-docs/pull/89.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #89
    
----
commit db76a6bebaf45707d3de2d2acc875fe18e056759
Author: Aled Sage <al...@gmail.com>
Date:   2016-07-12T18:54:56Z

    BROOKLYN-218: document nss upgrade to avoid KeyException

----


---
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.
---

[GitHub] brooklyn-docs pull request #89: BROOKLYN-218: document nss upgrade to avoid ...

Posted by duncangrant <gi...@git.apache.org>.
Github user duncangrant commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/89#discussion_r70506491
  
    --- Diff: guide/ops/troubleshooting/deployment.md ---
    @@ -75,6 +75,58 @@ There are many possible reasons for this ssh failure, which include:
     A very useful debug configuration is to set `destroyOnFailure` to false. This will allow ssh failures to
     be more easily investigated.
     
    +#### java.security.KeyException when Provisioning VM
    +
    +The exception `java.security.KeyException` can be thrown when jclouds is attempting the SSL handshake,
    +to make cloud API calls. This can happen if the version of nss is older than 3.16 - the nss package
    +includes the ssl library.
    +
    +To fix this on CentOS, run:
    +
    +{% highlight bash %}
    +sudo yum upgrade nss
    +{% endhighlight %}
    +
    +For a discussion of investigating this kind of issue, see this [Backslasher blog](http://blog.backslasher.net/java-ssl-crash.html).
    +
    +The full stacktrace is shown below:
    +
    +{% highlight %}
    --- End diff --
    
    You have to pick a language - otherwise just indent section with tabs


---
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.
---

[GitHub] brooklyn-docs pull request #89: BROOKLYN-218: document nss upgrade to avoid ...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/brooklyn-docs/pull/89


---
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.
---

[GitHub] brooklyn-docs issue #89: BROOKLYN-218: document nss upgrade to avoid KeyExce...

Posted by duncangrant <gi...@git.apache.org>.
Github user duncangrant commented on the issue:

    https://github.com/apache/brooklyn-docs/pull/89
  
    One comment otherwise LGTM


---
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.
---