Consul calling home?

Status
Not open for further replies.

Caiman

Cadet
Joined
Jan 20, 2015
Messages
3
Hello
Getting those messages in logs:

Dec 21 16:08:21 nas daemon[3271]: ==> Failed to check for updates: Get https://checkpoint-api.hashicorp.co...c91-5e33-2591-45d0-9425723713f4&version=1.0.0: dial tcp: lookup checkpoint-api.hashicorp.com on 127.0.0.1:53: read udp 127.0.0.1:61248->127.0.0.1:53: i/o timeout

Is this normal ? hidden feature ?


Looks similar to :
https://www.google.ca/url?q=https:/...oBYEQFghBMAg&usg=AOvVaw1z6oJ11Uqog2bEC4iSOYoK

##
Hi,

Doing some testing with Consul on an isolated network, I saw this error in consul's output:

==> Failed to check for updates: Get https://checkpoint-api.hashicorp.co...dac-4c96-b6b8-5776-9ba187cd5c60&version=0.4.0: dial tcp: lookup checkpoint-api.hashicorp.com: no such host

I could find no mention nor documentation for this "update check". Can this be disabled?

Thank you,
--Diego

Re: Consul calling home? Armon Dadgar 9/12/14 12:01 PM
Hey Diego,

This is part of our Checkpoint service (https://checkpoint.hashicorp.com). It is a new feature we are
rolling out to notify users of updates and critical security alerts. It was mentioned in the change log:
https://github.com/hashicorp/consul/blob/v0.4.0/CHANGELOG.md

Additionally, we have documentation about how to disable the update checks here:
http://www.consul.io/docs/agent/options.html
Specifically, see the “disable_update_check” option.

Hope that helps!

Best Regards,
Armon Dadgar
##
 
D

dlavigne

Guest
Please create a ticket at bugs.freenas.org asking that this check be disabled and post the issue number here.
 
Status
Not open for further replies.
Top