Re: Metron: Timed out talking to store


Kyle Havlovitz (kyhavlov)
 

I only have one ETCD node, and it's the correct address in the metron config.

From: Rohit Kumar <rokumar(a)pivotal.io<mailto:rokumar(a)pivotal.io>>
Reply-To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Date: Wednesday, October 7, 2015 at 8:24 PM
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Subject: [cf-dev] Re: Metron: Timed out talking to store

Hi Kyle,

How many nodes do you have in your ETCD cluster? Also can you check whether the ETCD servers listed in the metron config match the IP addresses of the machines in your cluster. The config file is located in /var/vcap/jobs/metron_agent/config/metron_agent.json and you should look for the "EtcdUrls" field.

Rohit

On Wed, Oct 7, 2015 at 3:12 PM, Kyle Havlovitz (kyhavlov) <kyhavlov(a)cisco.com<mailto:kyhavlov(a)cisco.com>> wrote:
I'm seeing this error in the Metron logs repeatedly: "ServerAddressList.Run: Timed out talking to store; will try again soon." Metron seems to be able to connect to ETCD just fine, and I can curl /v2/keys/healthstatus/doppler from the machine. I'm not sure what would cause this error and can't think of anything else to try. Later, when it gets logs from the dea agent, it gives the error "can't forward message: loggregator client pool is empty", presumably because of the previous error.

I can't figure out what the problem is with this; the zone property in the logging config files matches and it doesn't seem like a firewall problem, could anyone give advice? CF version is 217.

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.