Closed lafar6502 closed 9 years ago
@lafar6502 I noticed this during a build yesterday also. It looks like the *.githubusercontent.com
certificate was renewed a few days ago.
I built the container again this AM to verify the issue and I did not see the error this time:
logstash_1 | + wget https://gist.githubusercontent.com/pblittle/8778567/raw/logstash.conf -O /opt/logstash/conf.d/logstash.conf
logstash_1 | converted 'https://gist.githubusercontent.com/pblittle/8778567/raw/logstash.conf' (ANSI_X3.4-1968) -> 'https://gist.githubusercontent.com/pblittle/8778567/raw/logstash.conf' (UTF-8)
logstash_1 | --2015-03-03 04:32:53-- https://gist.githubusercontent.com/pblittle/8778567/raw/logstash.conf
logstash_1 | Resolving gist.githubusercontent.com (gist.githubusercontent.com)... 23.235.39.133
logstash_1 | Connecting to gist.githubusercontent.com (gist.githubusercontent.com)|23.235.39.133|:443... connected.
logstash_1 | HTTP request sent, awaiting response... 200 OK
logstash_1 | Length: 639 [text/plain]
logstash_1 | Saving to: '/opt/logstash/conf.d/logstash.conf'
logstash_1 |
logstash_1 | 0K 100% 706K=0.001s
logstash_1 |
logstash_1 | 2015-03-03 04:32:53 (706 KB/s) - '/opt/logstash/conf.d/logstash.conf' saved [639/639]
Do you mind trying again and let me know how it goes?
Closing due to inactivity. @lafar6502 please reopen if I can do anything to help.
The container terminates just after few seconds here's the stderr output:
converted 'https://gist.githubusercontent.com/pblittle/8778567/raw/logstash.conf' (ANSI_X3.4-1968) -> 'https://gist.githubusercontent.com/pblittle/8778567/raw/logstash.conf' (UTF-8) --2015-02-14 12:35:07-- https://gist.githubusercontent.com/pblittle/8778567/raw/logstash.conf Resolving gist.githubusercontent.com (gist.githubusercontent.com)... 185.31.17.133 Connecting to gist.githubusercontent.com (gist.githubusercontent.com)|185.31.17.133|:443... connected. ERROR: The certificate of 'gist.githubusercontent.com' is not trusted. ERROR: The certificate of 'gist.githubusercontent.com' is not yet activated.
is this an error or something obvious on my side i'm not aware of?