-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
install.sh fails to get elasticsearch gpg key #40
Comments
Kenny: I can not seem to duplicate this on my end. Please verify that you have your https_proxy set correctly if you are behind a proxy. Also test if you can hit https://packages.elastic.co/GPG-KEY-elasticsearch from a browser from the server or another computer on that network. Finally, maybe the elastic.co site was having a temporary problem. Please reopen if this continues and I will attempt to help you debug. |
Thank you for the quick reply! How should the proxy variables be set if I
am not using a proxy? i am doing this in an Ubuntu 16.04 virtual machine. I
had previously set the http_proxy=* and https_proxy=*
…On Fri, Jun 16, 2017 at 11:55 AM, Todd Bruner ***@***.***> wrote:
Kenny:
I can not seem to duplicate this on my end. Please verify that you have
your https_proxy set correctly if you are behind a proxy. Also test if you
can hit https://packages.elastic.co/GPG-KEY-elasticsearch from a browser
from the server or another computer on that network. Finally, maybe the
elastic.co site was having a temporary problem. Please reopen if this
continues and I will attempt to help you debug.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#40 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AbaZT5sMf_dFj4ZiGCG2EBBQRV8D_9cOks5sEqVrgaJpZM4N6ozm>
.
|
OK, that's the problem! The install assumes that SCOT will be behind a
proxy. If you don't mind hacking install.sh, here's how you can do it:
1. unset http_proxy and https_proxy (depends on your shell on how to do
that)
2. edit install.sh and comment out lines 24 through 30.
3. Re-run install.sh with no flags.
Let me know if that fixes the problem for you
…------------------------------
todd.bruner@gmail.com
On Fri, Jun 16, 2017 at 6:19 PM, KennyWap ***@***.***> wrote:
Thank you for the quick reply! How should the proxy variables be set if I
am not using a proxy? i am doing this in an Ubuntu 16.04 virtual machine. I
had previously set the http_proxy=* and https_proxy=*
On Fri, Jun 16, 2017 at 11:55 AM, Todd Bruner ***@***.***>
wrote:
> Kenny:
>
> I can not seem to duplicate this on my end. Please verify that you have
> your https_proxy set correctly if you are behind a proxy. Also test if
you
> can hit https://packages.elastic.co/GPG-KEY-elasticsearch from a browser
> from the server or another computer on that network. Finally, maybe the
> elastic.co site was having a temporary problem. Please reopen if this
> continues and I will attempt to help you debug.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#40 (comment)>,
or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AbaZT5sMf_
dFj4ZiGCG2EBBQRV8D_9cOks5sEqVrgaJpZM4N6ozm>
> .
>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#40 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAUAkg3ZuRQchO2FJL5on5TuPsPka_tJks5sExuogaJpZM4N6ozm>
.
|
install.sh fails to get the elasticsearch gpg key from MIT key server and does not finish installing
The text was updated successfully, but these errors were encountered: