Repository: incubator-brooklyn Updated Branches: refs/heads/master f8b7271b0 -> ab81a2fbe
Update connectivity.md Add a note about troubleshooting proxy settings. Project: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/commit/a35849c1 Tree: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/tree/a35849c1 Diff: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/diff/a35849c1 Branch: refs/heads/master Commit: a35849c18e821a72fb53e55d726ca52b5f34f7ba Parents: f968473 Author: Ciprian Ciubotariu <[email protected]> Authored: Wed Aug 5 15:56:45 2015 +0300 Committer: Ciprian Ciubotariu <[email protected]> Committed: Wed Aug 5 15:56:45 2015 +0300 ---------------------------------------------------------------------- docs/guide/ops/troubleshooting/connectivity.md | 11 +++++++++++ 1 file changed, 11 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/blob/a35849c1/docs/guide/ops/troubleshooting/connectivity.md ---------------------------------------------------------------------- diff --git a/docs/guide/ops/troubleshooting/connectivity.md b/docs/guide/ops/troubleshooting/connectivity.md index 07874c0..b6b0ba5 100644 --- a/docs/guide/ops/troubleshooting/connectivity.md +++ b/docs/guide/ops/troubleshooting/connectivity.md @@ -48,6 +48,17 @@ The following commands can be useful: * `dig` stands for "domain information groper". e.g. `dig www.google.com`. * `traceroute` prints the route that packets take to a network host. e.g. `traceroute www.google.com`. +## Proxy settings +Depending on the type of location, brooklyn might use HTTP to provision machines (clocker, jclouds). If the host environment defines proxy settings, these might interfere with the reachability of the respective HTTP service. + +One such case is using VirtualBox with host-only or private internal network settings, while using an external proxy for accessing the internet. It is clear that the external proxy won't be able to route HTTP calls properly, but that might not be clear when reading the logs (although brooklyn will present the failing URL). + +Try accessing the web-service URLs from a browser via the proxy, or perhaps try running brooklyn with proxy disabled: +``` + export http_proxy= + bin/brooklyn launch +``` + ## Service is listening ### Service responds
