You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@brooklyn.apache.org by tb...@apache.org on 2018/06/05 08:20:46 UTC
[1/4] brooklyn-docs git commit: Fix/improve links
Repository: brooklyn-docs
Updated Branches:
refs/heads/master e066c9cbd -> 9bf6a18bc
Fix/improve links
Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/55055c33
Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/55055c33
Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/55055c33
Branch: refs/heads/master
Commit: 55055c33235b1ece629afb7e4d40fbd60a1e06b7
Parents: e066c9c
Author: Aled Sage <al...@gmail.com>
Authored: Mon Jun 4 09:52:40 2018 +0100
Committer: Aled Sage <al...@gmail.com>
Committed: Mon Jun 4 09:52:40 2018 +0100
----------------------------------------------------------------------
guide/ops/troubleshooting/connectivity.md | 4 ++--
guide/ops/troubleshooting/softwareprocess.md | 5 +++--
2 files changed, 5 insertions(+), 4 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/55055c33/guide/ops/troubleshooting/connectivity.md
----------------------------------------------------------------------
diff --git a/guide/ops/troubleshooting/connectivity.md b/guide/ops/troubleshooting/connectivity.md
index 6da18ec..7b0daf4 100644
--- a/guide/ops/troubleshooting/connectivity.md
+++ b/guide/ops/troubleshooting/connectivity.md
@@ -104,8 +104,8 @@ example, execute `sudo iptables -n --list` and `iptables -t nat -n --list`.
## Cloud firewalls
Some clouds offer a firewall service, where ports need to be explicitly listed to be reachable.
-For example, [security groups for EC2-classic]
-(http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html#ec2-classic-security-groups)
+For example,
+[security groups for EC2-classic](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html)
have rules for the protocols and ports to be reachable from specific CIDRs.
Check these settings via the cloud provider's web-console (or API).
http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/55055c33/guide/ops/troubleshooting/softwareprocess.md
----------------------------------------------------------------------
diff --git a/guide/ops/troubleshooting/softwareprocess.md b/guide/ops/troubleshooting/softwareprocess.md
index 976444b..0e93a70 100644
--- a/guide/ops/troubleshooting/softwareprocess.md
+++ b/guide/ops/troubleshooting/softwareprocess.md
@@ -40,8 +40,9 @@ in the run directory (such as console output).
It is worth checking that the process is running, e.g. using `ps aux` to look for the desired process.
Some entities also write the pid of the process to `pid.txt` in the run directory.
-It is also worth checking if the required port is accessible. This is discussed in the guide
-"Troubleshooting Server Connectivity Issues in the Cloud", including listing the ports in use:
+It is also worth checking if the required port is accessible. This is discussed in the troubleshooting guide
+[Server Connectivity]({{book.path.docs}}/ops/troubleshooting/connectivity.md),
+including listing the ports in use:
execute `netstat -antp` (or on OS X `netstat -antp TCP`) to list the TCP ports in use (or use
`-anup` for UDP).
[4/4] brooklyn-docs git commit: This closes #256
Posted by tb...@apache.org.
This closes #256
Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/9bf6a18b
Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/9bf6a18b
Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/9bf6a18b
Branch: refs/heads/master
Commit: 9bf6a18bca84003e634043024b2961379c301f99
Parents: e066c9c 4219028
Author: Thomas Bouron <th...@cloudsoftcorp.com>
Authored: Tue Jun 5 09:20:38 2018 +0100
Committer: Thomas Bouron <th...@cloudsoftcorp.com>
Committed: Tue Jun 5 09:20:38 2018 +0100
----------------------------------------------------------------------
guide/ops/troubleshooting/connectivity.md | 4 ++--
guide/ops/troubleshooting/deployment.md | 24 +++++++++++++++++++++++
guide/ops/troubleshooting/softwareprocess.md | 5 +++--
3 files changed, 29 insertions(+), 4 deletions(-)
----------------------------------------------------------------------
[3/4] brooklyn-docs git commit: PR #256: incorporate review comments
Posted by tb...@apache.org.
PR #256: incorporate review comments
Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/42190285
Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/42190285
Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/42190285
Branch: refs/heads/master
Commit: 4219028575474d5fc43b6f28e4b1ed5d0e3adfe9
Parents: 093f483
Author: Aled Sage <al...@gmail.com>
Authored: Mon Jun 4 21:57:03 2018 +0100
Committer: Aled Sage <al...@gmail.com>
Committed: Mon Jun 4 21:57:03 2018 +0100
----------------------------------------------------------------------
guide/ops/troubleshooting/connectivity.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/42190285/guide/ops/troubleshooting/connectivity.md
----------------------------------------------------------------------
diff --git a/guide/ops/troubleshooting/connectivity.md b/guide/ops/troubleshooting/connectivity.md
index 7b0daf4..82917c2 100644
--- a/guide/ops/troubleshooting/connectivity.md
+++ b/guide/ops/troubleshooting/connectivity.md
@@ -105,7 +105,7 @@ example, execute `sudo iptables -n --list` and `iptables -t nat -n --list`.
Some clouds offer a firewall service, where ports need to be explicitly listed to be reachable.
For example,
-[security groups for EC2-classic](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html)
+[security groups for AWS EC2](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html)
have rules for the protocols and ports to be reachable from specific CIDRs.
Check these settings via the cloud provider's web-console (or API).
[2/4] brooklyn-docs git commit: BROOKLYN-588: add to troubleshooting
for curl failure
Posted by tb...@apache.org.
BROOKLYN-588: add to troubleshooting for curl failure
See https://issues.apache.org/jira/browse/BROOKLYN-588
Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/093f483c
Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/093f483c
Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/093f483c
Branch: refs/heads/master
Commit: 093f483c133b856369afc2f7a7a2cdd9b1a74e4f
Parents: 55055c3
Author: Aled Sage <al...@gmail.com>
Authored: Mon Jun 4 09:54:11 2018 +0100
Committer: Aled Sage <al...@gmail.com>
Committed: Mon Jun 4 09:54:11 2018 +0100
----------------------------------------------------------------------
guide/ops/troubleshooting/deployment.md | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/093f483c/guide/ops/troubleshooting/deployment.md
----------------------------------------------------------------------
diff --git a/guide/ops/troubleshooting/deployment.md b/guide/ops/troubleshooting/deployment.md
index 75bd140..38121e2 100644
--- a/guide/ops/troubleshooting/deployment.md
+++ b/guide/ops/troubleshooting/deployment.md
@@ -189,3 +189,27 @@ traffic filtering such as child-safe type filtering:
To resolve this try disabling traffic filtering and setting your DNS to a public server such as 8.8.8.8 to use google
[DNS](https://www.wikiwand.com/en/Google_Public_DNS). [See here](https://developers.google.com/speed/public-dns/docs/using) for details on how to configure this.
+
+
+## Download with Curl Fails on CentOS 7.0 due to TLS Negotiation
+
+When downloading an install artifact with Curl, using CentOS 7.0, one can get the failure shown below:
+
+ curl: (35) Peer reports incompatible or unsupported protocol version.
+
+This can be caused by incompatible TLS negotiation with the web server (e.g. with github). For more details, see
+[Red Hat bug 1170339, "use the default min/max TLS version provided by NSS [RHEL-7]"](https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1170339).
+
+To confirm this is the issue, try running the failing curl command on the same machine with `curl -v` for verbose output.
+You should see a more detailed error such as:
+
+ NSS error -12286 (SSL_ERROR_NO_CYPHER_OVERLAP)
+ Cannot communicate securely with peer: no common encryption algorithm(s).
+ Closing connection 1
+
+Possible workarounds include:
+
+1. Use a more recent version of CentOS. On AWS, a good choice is the most recent centos.org image from the
+[AWS marketplace](https://aws.amazon.com/marketplace/pp/B00O7WM7QW). However, this involves first subscribing to it in the marketplace. The Amazon Linux AMI is another good choice, but this is not a normal CentOS image so it depends what distro(s) the entity was developed/tested against.
+
+2. Change your blueprint to first do `sudo yum update -y curl nss`, before the curl command is executed.