[ https://issues.apache.org/jira/browse/BROOKLYN-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16499914#comment-16499914 ]
ASF GitHub Bot commented on BROOKLYN-588: ----------------------------------------- GitHub user aledsage opened a pull request: https://github.com/apache/brooklyn-docs/pull/256 BROOKLYN-588: add to troubleshooting for curl failure See https://issues.apache.org/jira/browse/BROOKLYN-588 You can merge this pull request into a Git repository by running: $ git pull https://github.com/aledsage/brooklyn-docs BROOKLYN-588 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/brooklyn-docs/pull/256.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 #256 ---- commit 55055c33235b1ece629afb7e4d40fbd60a1e06b7 Author: Aled Sage <aled.sage@...> Date: 2018-06-04T08:52:40Z Fix/improve links commit 093f483c133b856369afc2f7a7a2cdd9b1a74e4f Author: Aled Sage <aled.sage@...> Date: 2018-06-04T08:54:11Z BROOKLYN-588: add to troubleshooting for curl failure See https://issues.apache.org/jira/browse/BROOKLYN-588 ---- > SoftwareProcess download with curl can fail on CentOS 7.0 (TLS negotiation) > --------------------------------------------------------------------------- > > Key: BROOKLYN-588 > URL: https://issues.apache.org/jira/browse/BROOKLYN-588 > Project: Brooklyn > Issue Type: Bug > Affects Versions: 0.12.0 > Reporter: Aled Sage > Priority: Major > > When a {{SoftwareProcess}} entity needs to download an install artifact, it > often uses curl. > When running CentOS 7.0, this can fail. For example, when attempting to > download something from github: > {noformat} > /usr/bin/curl > curl: (37) Couldn't open file > /home/users/amp/.brooklyn/repository/EtcdNode/2.3.1/etcd-v2.3.1-linux-amd64.tar.gz > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > curl: (35) Peer reports incompatible or unsupported protocol version. > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > curl: (22) The requested URL returned error: 404 Not Found > Could not retrieve etcd-v2.3.1-linux-amd64.tar.gz. Tried: > file://$HOME/.brooklyn/repository/EtcdNode/2.3.1/etcd-v2.3.1-linux-amd64.tar.gz, > > https://github.com/coreos/etcd/releases/download/v2.3.1/etcd-v2.3.1-linux-amd64.tar.gz, > > http://downloads.cloudsoftcorp.com/brooklyn/repository/EtcdNode/2.3.1/etcd-v2.3.1-linux-amd64.tar.gz > Executed > /tmp/brooklyn-20180521-195405819-Dfo2-installing_EtcdNodeImpl_id_oe3.sh, > result 9 > {noformat} > This can happen when using a 'minimal' location in AWS (e.g. when just > specifying the {{osFamily: centos}}, and not an explicit AMI, which defaults > to a CentOS 7.0 AMI). -- This message was sent by Atlassian JIRA (v7.6.3#76005)